26 physical controls + a bridge
Eleven wall switches, nine dimmers, three fan controls, and three Pico remotes. Permanent lighting remains usable at the wall.
Problems from my actual house
The useful part of home automation starts when the individually good products do something stupid together. I use Home Assistant to find those seams, fix them, and document what survived.
The whole setupWhat I would buyLutron CasétaESP32 + WLEDEufyPower and cost
Start here
I tried tracking the RF state with five automations. Then I replaced that with a timed power-on routine. Both approaches were solving the wrong problem. The receiver needed to stay powered.
These counts come from the Home Assistant configuration and device registry I actually run—not a sample dashboard.
Eleven wall switches, nine dimmers, three fan controls, and three Pico remotes. Permanent lighting remains usable at the wall.
Six separate LED runs appear as one kitchen light, with direct JSON commands for color temperature that fought Home Assistant’s normal light entity.
I added the Omni S2 through Matter and built room, zone, whole-floor, and rescue-alert controls around what it actually exposes.
What is installed here and what I would buy today are not always the same answer. These pages keep that distinction explicit.
Caséta is the easy yes. Matter bulbs, WLED, Eufy, and local AI each have a narrower job.
The installed switches still work, so replacing them would waste money. For a compatible new neutral-wire circuit, I would check the current Claro model first.
If Caséta is going into Home Assistant, yes. The useful question is which hub, not whether to skip it.
Only for the Eufy features I actually want. It is not a general-purpose Home Assistant hub.
These are finished builds, including the bad assumption or failure that made each one worth documenting.
Why the normal light entity fought white and color-temperature control, and the direct command path I kept.
Room and zone cleaning, the controls Matter leaves behind, and the alert I added when the vacuum cannot get home.
Measured Qwen3 speed on an RTX 5070 Ti, the setup that appeared to work but did not, and the memory boundary I kept.
An unpowered RF receiver, a controller still booting, and a vacuum that needed to admit it was stuck.
The house is the main lab, but it is not the only place I find bad assumptions. These are failure stories from software I actively publish.
A 40 MHz clock broke Bluetooth, manual light sleep caused watchdog resets, and ESP-IDF power management finally kept the desk display asleep and reachable.
The bridge delivered only the clock on Windows, then treated a quiet queue as a dead connection.
The useful cockpit appeared when live agent state replaced permanent screens for things I rarely opened.
I removed TSIG secrets from browser storage, then fixed a split-DNS path that could send an internal edit to the external view.
Public reads made the service look healthy while protected writes had quietly lost their identity.
DisplayCue coordinates the handoff without pretending DDC/CI can replace a hardware KVM everywhere.
Subtract the plug’s own power use from the load it avoids.
Useful for hubs, routers, mini PCs, and everything else running all year.
Compare the complete purchase price with the electricity it can actually save.