The one line that decides a bulb
Home Assistant publishes an IoT class on every integration page, and for lighting it predicts how the house will feel more accurately than lumens or colour gamut do.
Local Push means the device or its hub tells Home Assistant immediately, on your own network. Press a Hue dimmer and the dashboard updates as the light changes. Local Polling means Home Assistant asks on a timer — private and local, but a change made in the vendor app shows up a few seconds late. Cloud Polling routes the question through the maker’s servers, which for a light is the difference between a smart home and a slow one.
Every bulb below is local. They are ranked on how directly local, and on what each route costs you in hardware or in credentials.
Hue: a Bridge, and the reason to want one
The Hue Bridge is the thing people try hardest to avoid buying, and the reason to buy it anyway is on both of Philips Hue’s own pages and Home Assistant’s. Hue describes Zigbee as a dedicated low-power network rather than Wi-Fi, with the Bridge sitting on Ethernet to your router and handling up to 50 lights. Its own FAQ compares the two control routes bluntly: Bluetooth is local-only, roughly ten metres, and up to ten lights, while the Bridge gives you out-of-home access, full automations and that 50-light ceiling.
For Home Assistant the Bridge pays off three more times. It is auto-discovered, so setup is a confirmation rather than a configuration. Hue motion sensors arrive as motion, temperature and light-level entities, which turns a lighting system into a sensor network you did not have to buy twice. And Hue scenes you build in the polished Hue app are imported automatically as scene entities — with the sharp caveat that Home Assistant states creating or editing Hue scenes from Home Assistant is not supported, so scene authoring stays in the Hue app.
One performance note from the same page that is worth building your automations around: Home Assistant recommends calling a Hue scene when you want several lights to change at once, because “a Hue scene sends commands to all lights at once in an optimized way”, whereas controlling each light individually sends each command one by one. If you have ever watched a row of bulbs turn on like a slow domino run, that sentence is the fix.
Hue’s weaknesses are the obvious ones and we will not soften them: it costs more per bulb than anything else here, the Bridge is another box drawing power, and full colour costs more than white-only. If you own four bulbs and no ambitions, it is overkill. Our Philips Hue review goes through that trade in detail.
The Tapo L535E, and the list it is not on
This is the most useful thing on this page, because every other roundup gets it backwards. Home Assistant’s TP-Link integration is excellent — one integration covering Kasa and Tapo, IoT class Local Polling on a five-second cycle, connecting “locally to the devices without going via the TP-Link cloud”. But its supported-bulb list is specific: Tapo L510B, L510E, L530E and L630. The L535E is not there.
It does not need to be. TP-Link publishes Matter certification for the L535E, and Home Assistant’s Matter integration is Local Push, with Home Assistant acting as a Matter controller running its own Matter Server and devices talking over IPv6 on your existing LAN. A Matter bulb therefore skips the vendor integration entirely and answers locally and instantly.
Three conditions you should know before ordering. First, Home Assistant notes that “some vendors may require you to set up an account before you can enable Matter support for some products” — Matter is not always a clean escape from an app. Second, TP-Link publishes 2.4GHz Wi-Fi only for this bulb, so a 5GHz-only network will not do, and our compatibility matrix explains why that band keeps coming up in this category. Third, TP-Link explicitly says not to fit it behind a dimmer switch. At four bulbs a box and a published 1100 lumens — the brightest figure on this page — it is still the most light per dollar we can point at.
The Kasa KL135: on the list, with a condition
If you want the bulb that Home Assistant’s own TP-Link page names, this is it: the supported Kasa bulbs are KL110, KL120, KL125, KL130, KL135, KL50, KL60 and LB110. The KL135 is a plain Wi-Fi multicolour bulb with no bridge and no Matter, and that simplicity is the appeal — screw it in, it appears, done.
The condition is the one we have flagged on every Home Assistant page we have published this month, because Home Assistant states it and almost nobody repeats it: newer Kasa and all Tapo devices “require your TP-Link cloud username and password to authenticate for local access”. The traffic stays on your network; the credential does not come from nowhere. Two more notes from the same page: some firmware requires Third-Party Compatibility to be switched on in the vendor app first, and devices on a different subnet from Home Assistant are not auto-discovered.
There is also a plain-English reason the KL135 ranks third rather than second. It is sold as a single bulb where the L535E comes four to a box, and it is neither Matter-certified nor Apple-Home-listed, so it is the least portable bulb here if you ever change platforms.
The Govee A19 and its second integration
Govee is the interesting case, because Home Assistant ships two Govee paths and only one of them is local. The one to use is Govee lights local, IoT class Local Push, which “integrates Govee lights into Home Assistant using Local API control” — and its published model list includes H6008, which is exactly the A19 multicolour bulb in our registry.
The requirement is a setting, not a purchase: local control has to be switched on for the device first, following Govee’s own instructions, before Home Assistant can take the local route. Get that wrong and you end up on the cloud integration instead, which is the common complaint about Govee in Home Assistant forums and is avoidable. The bulb is also Matter-capable per our registry entry, so you have two local routes to choose between, and it is a single bulb — genuinely useful when you want one colour bulb for a lamp rather than four for a ceiling.
The four bulbs on what Home Assistant publishes
Integration rows are read from Home Assistant's own integration pages on the dates in the sources below; product rows come from the maker's published specs via our registry. 'Not published' means we found no first-party figure — it is not a claim the figure is bad. Integration support lists change release to release; check the current page if one row decides your purchase. | Philips Hue Starter Kit | Tapo L535E | Kasa KL135 | Govee A19 (H6008) |
|---|
| Integration used | Philips Hue | Matter | TP-Link | Govee lights local |
|---|
| IoT class Home Assistant publishes | Local Push | Local Push | Local Polling (5s) | Local Push |
|---|
| Listed by model on that integration page | Bridge-based, by design | No — L510B/L510E/L530E/L630 are | Yes — KL135 named | Yes — H6008 named |
|---|
| Extra hardware required | Hue Bridge (Ethernet) | None | None | None |
|---|
| Cloud credential needed for local access | No | Vendor account may be needed to enable Matter | Yes — TP-Link username and password | No, but local control must be enabled first |
|---|
| Scenes imported into Home Assistant | Yes, from the Hue app | Home Assistant scenes only | Home Assistant scenes only | Home Assistant scenes only |
|---|
| Sensors the integration adds | Motion, temperature, light level | None | None | None |
|---|
| Radio | Zigbee via Bridge; Matter | Wi-Fi 2.4GHz; Matter | Wi-Fi 2.4GHz | Wi-Fi; Matter |
|---|
| Published brightness | Not published per bulb | 1100 lm | Not published | Not published |
|---|
| Bulbs per box | 4 bulbs plus Bridge | 4 | 1 | 1 |
|---|
| Apple Home listed by the maker | Yes | Yes | No | Yes |
|---|
The pattern in that table is the argument of this page. Three of the four bulbs are Local Push, and the one that is not — the Kasa — is also the only one that wants your vendor password to work locally. Hue is the only route that brings sensors and imported scenes with it, which is why it leads despite costing the most.
What about Zigbee bulbs without Hue?
It is the veteran’s answer and we are not going to invent a product to give it. Plenty of people run bare Zigbee bulbs on a coordinator stick and never touch a vendor bridge, and that remains a good setup. Our registry carries the Wi-Fi, Matter and Hue-Zigbee variants, so that is what this page ranks; if a coordinator-based Zigbee lighting build is where you are heading, our Zigbee vs Z-Wave vs Thread guide is the right starting point and the privacy-first hub ranking covers the hardware that runs it.
One last honest note about bulbs in general, which applies to all four picks: any bulb is dead when somebody flips the wall switch off. That is not a defect, it is the shape of the product, and it is why a lighting plan usually ends up involving a smart switch or a plug somewhere. Our main bulb ranking and the Home Assistant plug picks cover the rest of that decision.
