The system I actually run
I do not use one smart-home ecosystem. I use four.
There are 26 Lutron Caséta controls in my walls, six WLED controllers pretending to be one kitchen light, an Eufy Omni S2 connected through Matter, and a HomeBase 3 whose job is not to make Home Assistant happy. The mix works because I give each part a narrow job.
I did not arrive at this by drawing a perfect architecture first. I bought things, built things, lost a doorbell and a robot vacuum to lightning, and discovered which failures were tolerable. Home Assistant became the coordinator, but I stopped asking it to be the only way anything works.
| Job | What is here | Home Assistant’s role | If Home Assistant is down |
|---|---|---|---|
| Permanent lighting | 26 Caséta controls plus one L-BDG2 bridge | Scenes, schedules, state, and Pico events | The wall controls still make sense |
| Custom LED lighting | ESP32 controllers running WLED | Groups separate controllers and coordinates scenes | Behavior depends on power and the controller’s saved state |
| Floor cleaning | Eufy Omni S2 through Matter | Room, zone, whole-floor, and rescue controls | The vacuum and Eufy app remain their own system |
| Security storage | Eufy HomeBase 3, model T8030 | Not treated as a general Home Assistant gateway | The security system keeps its separate control plane |
| Loose lamps | No verified Matter bulb in the live registry | A future local bulb would fill a small gap | The physical lamp control still needs a sensible design |
Caséta is the part I expect everyone to understand
My live inventory contains nine PD-6WCL dimmers, eleven PD-8ANS switches, three PD-FSQN fan controls, two PJ2-3BRL Pico remotes, and one PJ2-2B Pico remote. One L-BDG2 bridge connects those 26 physical controls to Home Assistant.
The numbers matter because this is not a recommendation built from a product page. These are controls I live with. The original PD-6WCL dimmers are old enough that I would choose a Diva DVRF-6L for a compatible new room, but I would not pull nine working dimmers out of the wall for a nicer paddle. The detailed PD-6WCL versus Diva comparison explains that keep-or-buy split. I make the same distinction for on/off loads in my PD-8ANS versus Claro DVRF-5NS comparison.
I also do not infer wiring from a model name in Home Assistant. The PD-6WCL is the no-neutral dimmer in this installed group; the PD-8ANS switch and PD-FSQN fan control require a neutral. My Caséta neutral-wire guide is a model-selection aid, not an invitation to guess inside an electrical box.
The standard hub is enough for this setup. Home Assistant talks to it locally, while the wall devices use Lutron’s own Clear Connect link. I do not need a Pro hub merely to expose normal lights, fans, and Pico events. The full Caséta hub guide covers the device count and the cases where “Pro” is solving a different problem.
The ESP32 controllers exist because the lighting is not ordinary
I do not reach for an ESP32 when a finished wall control will do the job. I use one when the load is a custom LED installation and I need to own the controller behavior.
The kitchen is the clearest example. Six WLED controllers drive six separate runs, but I want the room to behave like one light. Home Assistant groups them for ordinary control. Color temperature exposed another seam: the normal light entity did not produce the white behavior I wanted, so the working path sends bounded JSON commands directly to the controllers. That implementation is in Six WLED Controllers as One Home Assistant Light.
A switched cove created the opposite problem. The controller was healthy, but power disappeared whenever the upstream switch was off. Sending a command immediately after restoring power raced the controller’s boot. The useful fix was not a more elaborate dashboard; it was acknowledging that the controller had lost power and waiting for the controller to become reachable. I documented that in Making a Power-Switched WLED Cove Reliable.
Those projects are why I separate an ESP32 build from a smart-bulb purchase. A custom strip needs a power supply, driver, wiring, fusing, enclosure, service path, and boot behavior. If the actual requirement is “make this table lamp tunable white,” building a controller is usually an expensive way to avoid buying a bulb.
Matter is an interface, not my organizing principle
The live Matter registry I checked on September 13, 2026 contains the Omni S2 and a Shelly flood sensor. It contains no light bulb. I am deliberately saying that because “Matter bulbs” appeared in the early description of this site as if I had already tested a shelf of them. I have not.
My buying rule is narrower: a Matter bulb can make sense in a loose lamp where there is no Caséta-controlled load. A kid’s bedside lamp, a movable reading lamp, or another one-off fixture is the right scale. Permanent room lighting already controlled at the wall is not.
A bulb behind a normal wall switch can become unreachable the moment somebody uses the obvious control. That does not make the person wrong; it makes the control design wrong. If I eventually choose a bulb, I will verify the exact model, its commissioning path, its behavior after power loss, and whether a physical button can coexist with the automation. Until then, the Caséta versus Matter-bulb article is a buying rule, not a product review.
Home Assistant’s Matter integration can provide a useful local common interface over Wi-Fi or Thread. It cannot promise that every vendor feature will cross that interface. The S2 proves the point.
The Eufy products share a logo, not an architecture
The current Eufy equipment is a HomeBase 3, an Omni S2, and permanent outdoor lights. The old doorbell and S1 vacuum were both taken out by lightning. I keep that history visible because stale device names in a registry can look more authoritative than the hardware sitting in the house.
HomeBase 3
The HomeBase 3 is model T8030. I would buy it for compatible Eufy cameras, local recording, and the Eufy security design—not as a shortcut to a polished Home Assistant camera system. The old community websocket route was archived while Eufy changed its API story, and a replacement SDK is not the same thing as a finished Home Assistant integration. The HomeBase 3 purchase guide makes that distinction without pretending the dead doorbell is current equipment.
Omni S2
The S2 is the current vacuum. Matter exposes enough control for room cleaning, zone cleaning, whole-floor runs, operating state, errors, and charging data. I used that surface to build practical scripts and a rescue alert for a vacuum that cannot get home.
Matter does not give me the complete Eufy experience. Maps and model-specific settings still belong in the vendor app. Battery telemetry has also contradicted itself, so I do not present every entity as trustworthy merely because it exists. The complete behavior is documented in Eufy Omni S2 in Home Assistant Through Matter.
Permanent outdoor lights
I have not verified the exact model from the physical controller or Eufy app, and the lights do not appear in the live Home Assistant registry. I will not borrow the current S4 feature list and pretend it describes my roofline. Before turning this into a buying guide, I need the model, installed length, extension layout, power-supply location, repair history, and actual Matter support.
That missing identification is useful information too: there is no honest product link to add yet.
The most expensive failures happen between products
The best example is a ceiling fan with a Bond-controlled RF receiver behind a Caséta wall switch. Every component worked independently. The wall switch could still remove power from the receiver, and Home Assistant could still send an RF command while that receiver was booting. I tried more state tracking before accepting the simpler rule: the receiver needs continuous power if I expect remote control to be reliable.
That story is in Fixing a Bond Fan Behind a Lutron Caséta Switch. It is also the reason my architecture is based on failure modes instead of logos.
How I decide what to buy next
- Start with the physical job. Wall lighting, a loose lamp, a custom LED run, a security camera, and a vacuum should not share one shopping rule.
- Decide what must work without Home Assistant. A permanent light needs an obvious local control. An elaborate scene does not.
- Identify the exact model before checking integration support. Brand-family compatibility is too vague for Eufy, Matter, and even wiring-sensitive Caséta choices.
- Count the second control plane. Vendor apps, bridges, local caches, cloud accounts, maps, firmware, and replacement-part availability all become part of ownership.
- Buy for the primary job, then treat Home Assistant as leverage. I would not buy a flagship vacuum merely because Matter exposes a start button.
If I were starting a compatible new room today, I would begin with the wall-control decision and the standard Caséta hub—not a smart bulb. If I were filling a lamp-sized gap, I would evaluate a Matter bulb. If I needed a made-to-fit LED installation, I would accept the maintenance burden of WLED. My broader Home Assistant hardware I would buy again page collects the purchase decisions that have enough firsthand evidence behind them.
Where local AI fits
The Ollama assistant is an interface experiment, not a new control plane for the house. I have measured Qwen3 on an RTX 5070 Ti and connected the conversation path to Home Assistant, but I keep deterministic automations for things that must happen correctly. A language model can help interpret a request; it should not erase the device state, power path, and permissions underneath it. The current build notes are in Ollama in Home Assistant on an RTX 5070 Ti.
What this page can and cannot prove
The Caséta counts, model labels, Matter inventory, S2 entities, and HomeBase model came from the live Home Assistant configuration and registries reviewed on September 13, 2026. The linked articles contain the individual configurations, sources, and caveats. I did not simulate a whole-house outage for this page, test an installed Matter bulb, identify the outdoor-light model, install a replacement doorbell, or compare every competing ecosystem.
Disclosure: Nothing on this page is sponsored, and there are no affiliate links. Product links will appear only after an account is approved and the exact model is verified.