SmartestHome/docs/components.md

Components
==========
##Servers
2 X64 hosts
    1x tiny with 1x zigbee adapter
    1x PC with 1x GPU (rtx 3060 or better)

##Endpoints

#Living Room

1xMedia Station/TVPC (doesn't technically need to be in the same room) -> 1xThinClient (tiny is sufficient)
1xVoice Reciever - Round screen thingy
1xSound System (already have it, see #Have)
1xRuView Presence Node (ESP32-S3 CSI board)

#Loggia

1xMiniscreen System (Lenovo all-in-one PC, large built-in touchscreen — already own it, free, see #Have)
1xSound System
1xVoice Reciever - Round screen thingy
1xRuView Presence Node (ESP32-S3 CSI board)

#Linus Room

1xVoice Reciever - Round screen thingy
1xSound System
1xRuView Presence Node (ESP32-S3 CSI board)
???

#Amirs Room

1xBeamer
1xThinClient (tiny is sufficient)
1xHA Voice PE
1xSound System
1xRuView Presence Node (ESP32-S3 CSI board)

#Kitchen

1xTiny PC with Mini Touchscreen
1xCamera
1xVoice Reciever - Round screen thingy
1xSound System
1xRuView Presence Node (ESP32-S3 CSI board)

#Workshop / Office

The room the workshop assistant runs in (`workshop/`, docs/workshop-assistant.md).
Structurally the kitchen display again — a Sway kiosk, a screen, a camera — with two
differences that matter for buying: the screen wants to be BIG (schematics, board
plans and a camera grid at the same time), and the camera is a MACRO problem, not a
wide-angle one.

1xTiny PC (have — "near infinite Tiny Pcs")
1xLarge monitor or TV, wall-mounted above the bench
1xUSB inspection/macro camera   -> reading a service tag or PCB silkscreen at 10-20cm
1xVoice Reciever - Round screen thingy
1xRuView Presence Node (ESP32-S3 CSI board)

#Network cameras

Distinct from every USB camera in this project, which are all fixed-purpose at angles
useless for anything else (an item held to the kitchen lens; an appliance door). These
are the ones on the network, ingested by the Frigate/go2rtc this stack already runs,
and they are what the workshop display can actually show.

2-4xPoE or WiFi camera (RTSP/ONVIF)  -> count depends on which rooms; see #Open items

#Appliance monitoring (fridges + freezers)

The household runs more than one cold appliance — the main fridge's freezer
compartment is too small, so there is at least a second freezer elsewhere. That is
what makes "which one is it in?" a real question; see
[`fridge-item-location.md`](fridge-item-location.md) for why the answer is *door
sensors plus an outward-facing camera*, and why nothing goes inside the appliance.

Per appliance (assume 3 to start — kitchen fridge, kitchen freezer compartment,
second freezer):
1xZigbee door contact sensor  (mounted on the OUTSIDE face of the door, never inside)
1xDoorway camera              (looking at the door opening from outside, ~1.8-2m up)

The appliances themselves are already owned and are not bought by this project. The
room the second freezer lives in is not decided yet — see #Open items.

##Lighting

~16x RGB smart bulb (exact count/room split TBD — see #Open items). Zigbee, not
WiFi, to match this project's existing local-first Zigbee2MQTT backbone (already
have the coordinator dongle) rather than adding a second, cloud-dependent lighting
ecosystem. See #Need for the specific pick and why.

##Summed totals

#Servers
2x X64 host
1x Zigbee adapter
1x GPU (rtx 3060 or better)

#Endpoints (all rooms combined)
2x ThinClient (tiny)
1x Miniscreen System (Lenovo all-in-one, built-in touchscreen — already owned)
1x Beamer
5x Voice Reciever - round screen thingy (Living Room, Loggia, Linus Room, Kitchen, Workshop)
1x HA Voice PE
5x Sound System (all confirmed: Living Room, Loggia, Linus Room, Amirs Room, Kitchen)
1x Tiny PC with Mini Touchscreen (Kitchen)
1x Camera (Kitchen)
2x Spare webcam (destination TBD)
6x RuView Presence Node (ESP32-S3 CSI board — one per room: Living Room, Loggia, Linus Room, Amirs Room, Kitchen, Workshop)
3x Zigbee door contact sensor (one per cold appliance door — count depends on the final appliance list)
2x Doorway camera (network/RTSP, one per appliance that isn't already covered by a camera pointing the right way)
1x Tiny PC + 1x large monitor/TV + 1x USB inspection/macro camera (Workshop/Office)
2-4x Network camera (RTSP/ONVIF — rooms TBD, see #Open items)

#Lighting
~16x RGB smart bulb (Zigbee) — count/room split not finalized

#By room
Living Room:  1x ThinClient, 1x Voice Reciever, 1x Sound System (have), 1x RuView node
Loggia:       1x Miniscreen System (have), 1x Sound System, 1x Voice Reciever, 1x RuView node
Linus Room:   1x Voice Reciever, 1x Sound System, 1x RuView node, +1 unresolved (???)
Amirs Room:   1x Beamer, 1x ThinClient, 1x HA Voice PE, 1x Sound System, 1x RuView node
Kitchen:      1x Tiny PC w/ Touchscreen, 1x Camera, 1x Voice Reciever, 1x Sound System, 1x RuView node,
              2x door contact sensor (fridge + freezer compartment), 1x doorway camera
Workshop:     1x Tiny PC (have), 1x large monitor/TV, 1x inspection camera, 1x Voice Reciever, 1x RuView node
Wherever the second freezer is: 1x door contact sensor, 1x doorway camera

#Open items
- Linus Room's "???" line is still undecided.
- Bulb count/room split is a guess ("like 16") — not yet mapped to specific rooms
  or fixture counts per room.
- **Which room the second freezer is in**, and therefore whether its doorway camera
  needs its own PoE/power run or can share the kitchen's. Also whether the kitchen
  fridge and its freezer compartment are one door or two — that decides whether the
  contact-sensor count is 2 or 3.
- **How many network cameras, and in which rooms.** Priced at 3 as a placeholder. The
  workshop display can show any of them; which ones are worth watching is a decision
  nobody has made, and unlike the bulbs this one has a privacy dimension — a camera in
  a room is a camera in a room, the same caveat `hosts/thin-client`'s README already
  spends a section on for gesture control.
- **Whether the workshop monitor needs to be new at all.** It is the only display here
  with no touch requirement; almost any HDMI panel or old TV does the job.
- **Whether the kitchen's existing C920 can double as the kitchen fridge's doorway
  camera.** It is already there and already on a host, so it is free if the display
  happens to face the fridge — and useless if it doesn't. Nobody has measured the
  angle; do that before buying a second camera for that room.

#Have
1xSound System (earmarked for Living Room)
Near infinite Tiny Pcs
near infinite ATX Pcs
1xHA Voice PE
1xZigbee adapter
1xLenovo all-in-one PC, large built-in touchscreen (Loggia's Miniscreen System — free, already have it)

##Need

Need = Summed totals minus Have. "Tiny Pcs"/"ATX Pcs" are covered (near-infinite
supply on hand), so ThinClients and the LLM-host chassis are NOT listed below —
only parts not already owned. Composite items ("Sound System", "Voice Reciever")
are broken into their actual sub-components, since "1x Sound System" isn't a single
SKU. Amazon links are real listings found via search (mostly amazon.com — search
only returned US results; check amazon.de for local pricing/shipping/VAT before
buying). No prices are invented below — where docs/project-plan.md already
documents one it's reused as-is, otherwise it says "see link."

#GPU (LLM host) — need 1
- Used RTX 3060 12GB (~€200–250, per docs/project-plan.md §1.2) — condition/model
  don't matter much, 12GB VRAM is the requirement (Q4 Qwen2.5-14B). New alternative:
  [MSI GeForce RTX 3060 Ventus 2X 12G OC](https://www.amazon.com/MSI-GeForce-Ventus-NVIDIA-Graphics/dp/B08WHJFYM8)

#Beamer (Amirs Room) — need 1
- [TMY 1080P Mini Portable Projector, HDMI/USB](https://www.amazon.com/TMY-Projector-Supported-Projection-Compatible/dp/B082F13J55)
  (see link for price) — budget pick; if the ThinClient output needs to look good on
  a big wall, a brighter/native-1080p unit is worth paying more for than a mini
  LED projector like this one
- HDMI cable, length depends on beamer placement vs. ThinClient — not sized yet
- Ceiling/shelf mount — only if not just resting on furniture

#Voice Reciever - round screen thingy (Living Room, Loggia, Linus Room, Kitchen) — need 4
This is `firmware/esp32-s3-touch-lcd-1.85c/` from this repo (Phase 14) — each unit
is a kit of:
- [Waveshare ESP32-S3-Touch-LCD-1.85C, round touch display dev board](https://www.amazon.com/waveshare-ESP32-S3-1-85inch-Touch-LCD/dp/B0DK6NH65T)
  (~€35–45 each per docs/project-plan.md §1.12) — **must be the V2 revision**, see
  `firmware/esp32-s3-touch-lcd-1.85c/README.md`; the listing needs checking for which
  hardware revision it actually ships, this repo's firmware assumes V2 (V1 has no AEC
  circuit and different audio pins)
- USB-C power adapter, one per unit — [5V/3A USB-C wall adapter](https://www.amazon.com/Security-01-Supply-Adapter-Type-C-MLF-C060503000CU/dp/B09JW4QQJ2)
- USB-C cable, one per unit (often included with the board — check the listing before
  buying separately)

4x board + 4x power adapter (+ cable if not bundled).

#RuView Presence Node (Living Room, Loggia, Linus Room, Amirs Room, Kitchen) — need 5
This is `firmware/ruview/` from this repo (Phase 2/§1.6) — anonymous room-level CSI
presence, still an unbuilt placeholder in this repo (no firmware written yet), but
the hardware spec is fixed regardless: a plain ESP32-**S3** board, no camera, no
extra peripherals — CSI presence reads WiFi channel state, not a camera. Separate
boards from the Bermuda BLE-proxy ESP32s (§1.5) — one chip runs one firmware.
- [Espressif ESP32-S3-DevKitC-1-N8R2](https://www.amazon.com/Espressif-ESP32-S3-DevKitC-1-N8R2-Development-Board/dp/B09D3S7T3M)
  (~€8–12 each per docs/project-plan.md §1.6) — the official board, minimal
  8MB-flash/2MB-PSRAM variant; RuView's own firmware has no published minimum spec
  yet (nothing's been written), so this is picked for being the plain, cheap,
  official option rather than a specific requirement.

5x boards, one per room.

#Sound System (all 5 rooms confirmed: Living Room, Loggia, Linus Room, Amirs Room, Kitchen) — need 4
Have 1 already (earmarked for Living Room), need 5 total, all confirmed → need 4 more.
Each unit is a kit of:
- [Fosi Audio V3 stereo amp (300W x2, TPA3255, w/ 48V PSU)](https://www.amazon.com/Fosi-Audio-V3-Amplifier-48V/dp/B0CGCSM191)
  (~€130 per docs/project-plan.md §1.13) — USB DAC/amp for the passive speakers below,
  same choice this repo's `hosts/audio-endpoint/` and `hosts/thin-client/` docs already
  make for amd64 rooms
- [Micca MB42X G2 passive bookshelf speakers, pair](https://www.amazon.com/Micca-Passive-Bookshelf-Speakers-Surround/dp/B0CGBKWBGM)
  (~€100/pair per docs/project-plan.md §1.13)
- [16-gauge speaker wire, 100ft spool](https://www.amazon.com/AmazonBasics-16-Gauge-Speaker-Wire-Feet/dp/B006LW0W5Y)
  (one spool easily covers multiple rooms — buy once, not once per Sound System)

1x spool of wire total; 4x (amp + speaker pair).

#Kitchen — need 1 touchscreen + 1 camera
`hosts/kitchen-display/` (Phase 17) — the Tiny PC is covered by "Have", these two
are not:
- [10.3" portable USB-C touchscreen monitor](https://www.amazon.com/Touchscreen-Stretched-Portable-Computer-Monitoring/dp/B0DFVZ2Z35)
  (see link for price) — needs to expose itself as a native Wayland `wl_touch`
  device, not just an emulated-mouse HID surface (unverified either way — see
  `hosts/kitchen-display/README.md`)
- [Logitech HD Pro Webcam C920](https://www.amazon.com/Logitech-Widescreen-Calling-Recording-Desktop/dp/B006JH8T3S)
  (see link for price) — any UVC webcam works; picked for wide availability/driver
  support, not a specific requirement

#Spare webcams — need 2
Destination not decided yet — going to whichever future camera-equipped clients need
one next (see docs/project-plan.md Phase 6/18: any camera-equipped endpoint can run
the identity registration flow, not just kitchen-display/door-panel).
- [Logitech C270 HD Webcam, 720p](https://www.amazon.com/Logitech-C270-Webcam-Megapixel-Interpolated/dp/B01IFBKK3W)
  (see link for price, typically the cheapest widely-stocked UVC webcam) — cheaper
  than the C920 above on purpose: these two are general-purpose spares, not tied to
  pantry-vision's food-photo use case that specifically wants the C920's autofocus,
  so there's no reason to pay for that here.

#Appliance door sensors — need ~3
One per cold-appliance door, feeding the Zigbee2MQTT mesh this project already runs
(§1.3) — the same reasoning as the bulbs: one local mesh, not a manufacturer cloud.
These are what trigger the doorway cameras below (`pantry-vision`'s
`POST /doorway-event`, see `pantry-vision/README.md`), and they are worth buying
**even if no camera is ever installed**: on their own they already answer "which
appliance was opened, when" and "has the freezer been standing open for four
minutes", which prevents more spoilage per euro than any amount of item-locating.
- [Aqara Door and Window Sensor (Zigbee)](https://www.amazon.com/Aqara-Window-Sensor-Wireless-Security/dp/B07D37FKGX)
  (~€10–15 each) — plain reed-switch contact sensor, long-standing Zigbee2MQTT
  support, coin-cell powered.
- **Mount the sensor body on the OUTSIDE face of the door and the magnet on the
  outside of the frame** (or vice versa). Not inside the compartment: a coin cell at
  −18 °C loses a large part of its usable capacity, and every door opening condenses
  humid room air onto whatever is in there. The reed switch does not care which side
  of the door it is on, so there is no reason to pay the cold penalty.
- Battery life in this application is **unverified** — a fridge door that opens forty
  times a day is a much higher duty cycle than the window these are sold for. Budget
  for spare CR1632/CR2032s and check one after a month.

#Doorway cameras (appliances) — need ~2
Outward-facing, above the door on the hinge side, ~1.8–2 m, angled so the field of
view is the door aperture and the ~40 cm in front of it. **Never inside the
appliance** — `docs/fridge-item-location.md` has the full argument (no interior
power, condensation on every opening, and −18 °C being outside every consumer camera
module's rating, which rules out exactly the compartment the question came from).
- [TP-Link Tapo C120 (2K, RTSP/ONVIF)](https://www.amazon.com/TP-Link-Tapo-Security-Detection-C120/dp/B0CL5RRZ2M)
  (~€30–40 each) — needs to expose a plain **RTSP** stream so Frigate can ingest it,
  the same way `chores`' watch points already work. **Unverified**: whether this
  specific model serves RTSP without go2rtc as a bridge — the same open question
  Phase 20 already carries for its own camera pick (project-plan open decision #23),
  and worth resolving once for both rather than twice.
- One of the two **spare webcams** already on this list is a legitimate substitute
  for whichever appliance sits next to an existing host — a USB webcam needs a
  machine, and the kitchen has one; the second freezer's room probably doesn't.
- Buy **one** first, not both. `docs/fridge-item-location.md` recommends running door
  sensors alone for a month before deciding whether item-level localisation is a
  thing the household actually wanted, and the test that decides whether the camera
  works at all — can a local vision model identify an item in a moving hand at
  doorway distance? — can be run today with the kitchen's existing webcam.

#Workshop display — need 1 screen + 1 macro camera
The Tiny PC is covered by "Have". These two are not:
- Large monitor or TV (32-43", 1080p is enough; 4K only if you want two schematics
  side by side). **Any HDMI display works** — this is the one screen in the project
  with no touch requirement, because the workshop interaction is voice and keyboard
  with dirty hands, not fingers on glass. Reuse anything you have before buying.
- [USB digital microscope / inspection camera, 1080p with adjustable stand](https://www.amazon.com/Microscope-Compatible-Magnification-Adjustable-Compatible/dp/B08BC7GDVL)
  (~€30-60) — **not a webcam.** The job is reading 2mm text on a service tag or a PCB
  silkscreen, so autofocus at 10-20cm and enough resolution to resolve small print
  matter far more than field of view. The C920's autofocus does not go near enough.
  This is the single most important pick for whether the OCR-first identification in
  `docs/workshop-assistant.md` works at all, and it is cheap enough to test the
  premise before committing to the rest.

#Network cameras — need 2-4
For the workshop display's camera view, and to give Frigate something to watch beyond
the peephole cam. Must expose **RTSP** — that is the ingest path Frigate and go2rtc
use, and it is the one thing worth checking on the listing before buying.
- [TP-Link Tapo C120 (2K, RTSP/ONVIF)](https://www.amazon.com/TP-Link-Tapo-Security-Detection-C120/dp/B0CL5RRZ2M)
  (~€30-40 each) — same model already listed for the appliance doorways, deliberately:
  one camera model across the house means one set of quirks to learn, one stream
  configuration to get right, and spares that fit anywhere. **Unverified**: whether
  this model serves RTSP without go2rtc as a bridge (project-plan open decision #23).
- Buy **one first** and get it into Frigate before ordering the rest. Every camera
  after the first is a repeat of a solved problem; the first one is where you find out
  whether the model was the right pick.

#mmWave presence radar — need 1 to start, then 1 per room you care about
For **exact positions inside a room** on the 3D floorplan. BLE answers "which room";
this answers "where in it", and the two are fused in `identity` — see
`docs/endpoint-surfaces.md` for the rule and for why it is deliberately timid.
- [HLK-LD2450 24GHz mmWave radar module](https://www.amazon.com/Waveshare-Millimeter-Detection-Multi-Target-Trajectory/dp/B0CX5QNXH2)
  (~€15–25 each) — tracks up to **three moving targets** and reports each one's x/y,
  which is the specific capability that makes this worth doing at all. Native ESPHome
  support (`ld2450`), so it rides the same firmware pipeline as the other ESP nodes and
  needs an ESP32 per sensor (the RuView boards in this list are a separate job — do not
  double up firmware on one chip).
- **It cannot tell you who.** A radar sees a moving blob. Identity still comes from BLE,
  and with two people in one room neither blob gets a name — by design, because guessing
  is worse than not knowing.
- **Buy one, mount it, and check the rotation before buying more.** Getting the facing
  wrong mirrors every position it reports, and the failure looks plausible rather than
  broken. One room proves the whole chain (sensor → ESPHome → HA → identity's fusion →
  the 3D plan) for ~€20.

#Fixed BLE tags — need ~4 to start
For household members who don't (or shouldn't have to) carry a phone for presence to
work — a grandmother without a smartphone is the concrete case, but this is also just
generally the more reliable anchor `docs/project-plan.md` §1.5 already recommends over
a phone's own randomizing MAC. `identity/`'s registration flow supports registering
someone with **no** device at all (a manual home/away toggle instead), but a physical
tag is the better long-term answer once it's worth the ~€5–8 — see
`identity/README.md`'s "no device" section.
- [The Smart Anti Lost Tracker iTag-Tiny](https://www.amazon.com/iTag-Tiny-Innovative-Bluetooth-Anything-bidirectional/dp/B07FG7XJ9D)
  (see link for price, typically €3–8) — a plain Bluetooth 4.0 beacon with a
  replaceable coin-cell battery, not locked into Apple Find My/Google Find Hub's
  proprietary rotating-identifier scheme (most "key finder" listings on Amazon *are*
  locked to one of those and won't work here) — this is the generic style the HA/
  Bermuda community actually uses. **Verify before buying more than one**: cheap
  tags in this class often advertise a BLE *static random* address (technically
  "random" address-type, but stable for the tag's lifetime, unlike a phone's
  *resolvable private* address which deliberately rotates) — community reports say
  they "show as Random MAC but are stable," which is what actually matters for
  `identity`'s `TRUSTED_ENTITY_PREFIXES` allowlist, not the address-type label
  itself. Confirm one tag's address is genuinely stable (watch it in HA's Bluetooth
  debug log over a few hours) before buying a batch.
4x to start (one for the concrete grandmother case plus a few spares/guests); buy
more as more device-less household members come up.

#Lighting — need ~16 RGB smart bulbs (count TBD)
**Zigbee, not WiFi/cloud bulbs** — the whole point of the Zigbee2MQTT backbone this
project already runs (§1.3) is one local mesh instead of N different manufacturer
clouds; a WiFi bulb (Tuya/WiZ/etc.) would be a second, cloud-dependent ecosystem
bolted onto a stack that's explicitly local-first everywhere else. Mains-powered
Zigbee bulbs also act as mesh **routers**, which matters here specifically: ~16 of
them spread across every room does more for whole-house Zigbee coverage (for the
battery sensors in §1.4) than the coordinator alone ever could.

Three real options were compared, not just the first search hit:

| Option | Router? | Zigbee2MQTT support | Price | Verdict |
|---|---|---|---|---|
| [innr RB 285 C](https://www.amazon.de/Smart-dimmbar-kompatibel-Philips-RB/dp/B07GT1LWDH) (also [2-pack](https://www.amazon.co.uk/Innr-Colour-Philips-Assistant-Required/dp/B07GT12JTJ)) | Yes | Confirmed — [zigbee2mqtt.io device page](https://zigbee.blakadder.com/Innr_RB_285_C.html) | ~€15–20/bulb (docs/project-plan.md §1.4) | **Picked** — already this project's own documented choice, real listings on multiple Amazon EU sites, RGBW + tunable white 2200–6500K |
| IKEA TRÅDFRI color | Yes | Well-supported, huge install base | ~€12–15/bulb (cheapest of the three) | Not on Amazon in most regions (IKEA.com/stores only) — cheaper on paper but doesn't fit "find it on Amazon," and the color-capable SKU specifically (not the tunable-white-only ones) needs care to pick |
| Sengled Zigbee color (e.g. [2-pack](https://www.amazon.com/Sengled-Changing-Dimmable-Multicolor-Equivalent/dp/B0899LJHVV)) | **No** — end device only | Supported, but community reports of RGB/XY color quirks on some zigbee2mqtt versions | Similar ballpark to innr | Skipped — buying 16 non-router bulbs throws away the mesh-strengthening benefit that's the actual reason to prefer mains-powered bulbs here |

Buying at this quantity: check amazon.de for a 4-pack or larger multi-pack of the
RB 285 C (cheaper per-unit than 16x single-packs) before ordering singles.

4x-pack pricing wasn't found in search results — verify against the live listing.

#Open items carried over from above
- Linus Room's "???" line is still a completely open slot — nothing to shop for
  until it's decided what it is.
- Loggia's Lenovo all-in-one is already owned, so nothing to buy. `hosts/touch-panel/`
  now handles either way its touch panel shows up to Linux (native `wl_touch`, or an
  emulated-mouse HID device via the `type:pointer` fallback + a udev override to fix
  it properly — see that host's README "Touch input: two tiers"), so this is no
  longer a go/no-go check, just worth running once to know which tier it landed in
  and whether the override needs filling in for full multi-touch.
- Bulb count/room split — priced below at ~16, but that's a placeholder pending an
  actual per-room fixture count.

##Price estimate

Rough figures in EUR, for the #Need list above. **Estimates, not live-checked
prices** — the four docs/project-plan.md-sourced ones (GPU, ESP32 board, amp,
speakers) are reused from that doc as-is; everything else is a typical-market-price
guess for that exact product category, not pulled from the live Amazon listing (the
search used to find these links doesn't return price data — click through and check
before budgeting against this). All EUR figures assume roughly 1:1 with the USD
prices these products actually list at; check amazon.de directly for real
local pricing/VAT/shipping.

| Item | Qty | Est. unit price | Est. subtotal |
|---|---|---|---|
| Used RTX 3060 12GB | 1 | €200–250 | €200–250 |
| TMY 1080P mini projector | 1 | €40–65 | €40–65 |
| HDMI cable | 1 | €6–10 | €6–10 |
| Ceiling/shelf mount *(optional)* | 1 | €15–25 | €15–25 |
| Waveshare ESP32-S3-Touch-LCD-1.85C board | 5 | €35–45 | €175–225 |
| USB-C 5V/3A wall adapter | 5 | €7–12 | €35–60 |
| Fosi Audio V3 amp | 4 | €130 | €520 |
| Micca MB42X G2 speakers, pair | 4 | €100 | €400 |
| 16AWG speaker wire, 100ft spool *(one-time)* | 1 | €15–22 | €15–22 |
| 10.3" portable USB-C touchscreen monitor | 1 | €85–130 | €85–130 |
| Logitech HD Pro Webcam C920 | 1 | €55–75 | €55–75 |
| Logitech C270 spare webcam | 2 | €25–35 | €50–70 |
| innr RB 285 C Zigbee RGB bulb | ~16 (TBD) | €15–20 | €240–320 |
| iTag-Tiny fixed BLE tag | 4 | €3–8 | €12–32 |
| Espressif ESP32-S3-DevKitC-1-N8R2 (RuView) | 6 | €8–12 | €48–72 |
| HLK-LD2450 mmWave radar *(buy 1 first — see that section)* | ~3 | €15–25 | €45–75 |
| Aqara Zigbee door contact sensor (appliance doors) | ~3 | €10–15 | €30–45 |
| Tapo C120 doorway camera *(buy 1 first — see that section)* | ~2 | €30–40 | €60–80 |
| Tapo C120 network camera (rooms/workshop view) | ~3 | €30–40 | €90–120 |
| Workshop monitor/TV *(reuse one first if you have it)* | 1 | €120–250 | €120–250 |
| USB inspection/macro camera (workshop) | 1 | €30–60 | €30–60 |

**Subtotal (excludes the optional beamer mount): ~€2,289–2,921**
**Subtotal, including the optional beamer mount: ~€2,304–2,946**

The workshop line items are the ones to sequence rather than buy at once: the macro
camera is cheap and decides whether the OCR-first identification works at all, the
monitor can be anything you already own, and the network cameras are one-then-more.

The two appliance-monitoring lines are the only ones on this list bought in a
deliberate order rather than all at once: the door sensors are worth having on their
own merits, the cameras are not worth having until the sensors have proved the
question is real. Buying one camera instead of two costs €30–40 to find out.

All 5 Sound Systems (Living Room, Loggia, Linus Room, Amirs Room, Kitchen) are
confirmed — see `#Open items` above — so all 4 needed amp+speaker kits are in the
main table above. The bulb line is the least certain figure in this whole table —
16 is a round-number placeholder, not a counted fixture list, so treat that
€240–320 as the roughest estimate here. Linus Room's still-blank "???" line isn't
priced at all — there's nothing to estimate until it's decided what it is.