How to Connect Yeelight Bulbs to Home Assistant

This post may contain affiliate links. As an Amazon Associate we earn from qualifying purchases. Disclosure.

Yeelight makes some of the best-value smart bulbs you can buy. A 1S color bulb runs about $18, puts out 800 lumens, and covers the full RGB range. The catch is the app. By default, every command routes through Yeelight's cloud servers, which adds latency and a privacy question mark. Learning to connect them through a proper local Home Assistant setup fixes both problems at once.

TL;DR: Yeelight Wi-Fi bulbs support fully local control through Home Assistant once you flip the LAN Control toggle in the Yeelight app. HA auto-discovers them over the network, no cloud account required. Setup takes about ten minutes. Bluetooth-only Yeelight models won't work this way. After that, response times drop to near-instant and automations keep running offline.

Why bother when the Yeelight app already works? Because local control means the lights respond in milliseconds instead of the half-second cloud round trip, and they don't stop working the moment your internet does. That reliability difference matters more than the spec sheet suggests. I've had the same four Yeelight bulbs running locally for two years now, and the number of times they've failed because of a cloud outage is exactly zero.

What You Need Before You Start

You need three things. A running Home Assistant instance, a Yeelight Wi-Fi bulb already added to the Yeelight app, and both devices sitting on the same network subnet. That last point trips people up constantly. If your bulbs live on a separate IoT VLAN, discovery won't work until you allow mDNS traffic between the segments.

You want a server that stays on 24/7, because the whole point is that it's always there to catch your commands. An HA Green at $99 or a Raspberry Pi 4 at around $55 both handle a house full of bulbs without strain. Neither is fussy about the number of Yeelight devices you throw at it.

Not every Yeelight product plays this game, so check before you buy:

One honest warning: the Yeelight app itself is clunky and the account signup is annoying. You still need it for the initial pairing and to enable LAN Control. After that, you can more or less ignore it forever. Don't uninstall it though, you'll want it again the next time you add a bulb or a firmware update misbehaves.

Enabling LAN Control (the Step Everyone Misses)

This is the single most important step, and it's turned off by default. Open the Yeelight app, tap the bulb you want to control, open its settings, and find the LAN Control toggle. Switch it on.

Without this, Home Assistant simply cannot see the bulb, no matter how many times you restart the integration. I wasted a good twenty minutes on my first bulb before realizing the toggle existed. If you have several bulbs, you have to enable it on each one individually, there's no bulk option. Budget an extra minute per bulb for this, and do it while you're still holding your phone rather than after you've walked back to the computer.

Why is it off by default? Yeelight wants your commands going through its servers, that's how the company collects usage data and keeps you inside its app. Flipping the toggle opts you out of that arrangement. Nothing about the bulb breaks, you just take back control of where the data goes.

Adding Yeelight to Home Assistant

Home Assistant usually discovers Yeelight devices automatically. Head to Settings, then Devices and Services. If a Yeelight card shows up under Discovered, click Configure and you're basically done.

If nothing appears, add it manually. Click Add Integration, search for Yeelight, and either let it scan the network or type the bulb's IP address directly. Pinning a static IP or a DHCP reservation for each bulb is worth the effort here, because a bulb that changes IP address after a router reboot will drop out of Home Assistant until it's rediscovered. Set the reservations in your router once and forget about it.

Once added, each bulb shows up as a light entity with full brightness, color temperature, and RGB control. You'll also get a few extra switches for features like the bulb's built-in music mode and its power-on default state. If you run a mix of protocols, the Zigbee device pairing guide covers the parallel process for mesh gear, though Yeelight itself is pure Wi-Fi and never touches a Zigbee coordinator.

A quick sanity check before you move on: toggle the bulb from the Home Assistant dashboard and watch how fast it reacts. Local control should feel instant. If there's still a noticeable delay, the integration is probably still routing through the cloud, which usually means LAN Control didn't actually save. Go back and confirm the toggle. It's also worth renaming each entity right away, the default names are just the model number and an IP address, which becomes a mess the moment you have more than three bulbs and start writing automations that reference them by name.

Automations That Actually Earn Their Keep

Here's where local control pays off. A few setups I run and recommend:

• Circadian lighting. Shift color temperature warm in the evening and cool during the day. Yeelight bulbs handle the full 1700K to 6500K range, so the effect is genuinely noticeable.
• Motion-triggered hallway lights at 15% brightness after midnight, so a 2am trip to the kitchen doesn't blind you.
• Sunset sync. Fade the living room bulbs up as the sun goes down, using Home Assistant's built-in sun sensor rather than a fixed clock time.
• Flash on alert. Turn a bulb red for three seconds when a door or leak sensor trips. It's a surprisingly effective silent notification.
• Wake-up ramp. Slowly raise brightness over 20 minutes before your alarm. It's gentler than a buzzer and genuinely easier to wake up to.

None of these need the cloud. They run entirely on your HA server, which is exactly why they keep working during an outage. If you want more ideas to copy, the smart home automation ideas roundup has dozens you can adapt to Yeelight in an afternoon.

Picking the right bulbs for each room matters too. Yeelight covers color and tunable white, but not every fixture wants an RGB bulb, some just need warm, dimmable white. The smart light selection guide breaks down where color is worth paying for and where it's wasted. And if you're still on the fence about the whole category, the honest take in are smart lights worth it is worth five minutes before you spend a cent.

When Yeelight Local Control Falls Short

I'll be straight about the limits. Bluetooth-only Yeelight products, some of the cheaper candle bulbs and a few lamps, don't expose the LAN protocol. Those need a Bluetooth proxy or they stay stuck in the app. Firmware updates have also, on rare occasions, reset the LAN Control toggle, so if a bulb suddenly disappears after an update, check that setting first before you reinstall anything.

There's also the discontinuation risk that hangs over any cloud-linked device. Yeelight has shuffled its app and account systems more than once. Going local through Home Assistant is partly insurance against that. Your bulbs keep working even if the company changes direction, because the local architecture doesn't depend on their servers staying online. This is the same reason tunable, locally-controlled lighting keeps showing up in every forecast about where smart lighting is heading: ownership beats rental.

If you're building out a full room, don't stop at bulbs. Wall controls matter just as much, and the best smart switches for Home Assistant pair cleanly with Yeelight so a physical press and an automation both do the right thing. Nothing feels worse than a guest flipping a dumb wall switch and cutting power to a bulb your automations expect to be online.

Is It Worth the Ten Minutes?

Over 1 million homes now run Home Assistant according to the Nabu Casa State of the Smart Home survey (2024), and cheap, controllable bulbs like Yeelight are a big reason people start. The math is simple. You spend ten minutes per bulb enabling LAN Control and confirming discovery, and in exchange you get lighting that responds faster, keeps your usage data at home, and survives an internet outage without blinking.

There's a quieter benefit too. Once your bulbs are local entities in Home Assistant, they stop being isolated gadgets and start being building blocks. A Yeelight bulb can react to a temperature sensor, a door contact, or the time of sunrise, all without you touching the Yeelight app again. That composability is the real reward. The bulb is cheap, but the system you drop it into is what makes it feel expensive.

For a single lamp, maybe that's not worth the fuss. For a whole house of bulbs that you'll live with for years, it absolutely is. Do the setup once, and Yeelight stops being a cloud gadget and becomes a proper part of your local smart home. That's the difference between owning smart lighting and merely renting it, and it's the whole reason to bring these bulbs under local control in the first place.