I am using a Xiaomi Yeelight YLDP06YL E27 bulb integrated this way: https://www.home-assistant.io/components/light.yeelight/
The bulb gets unavailable after some time in HASS, but in the Yeelight app it is reachable all the time.
So, when the bulb gets unavailable in HASS, I am still able to control it with the Yeelight app.
After disconnecting the bulb from power en reconnect, most of the times it gets available again in HASS.
What could be the problem?
If youre using discovery maybe try manually configuring them. Do they have a fixed IP address?
They do not have a fixed IP address, but the IP address is not changed since I have added them to HASS. I suppose I have added the light manually by adding this to my configuration.yaml, or do you point to another way?
light:
- platform: yeelight
devices:
192.168.1.168:
name: TV
Make sure you have the lights set to LAN Mode in the Yeelight App.
Yes I did. As described, the Yeelights do work for some time, but then gets unavailable untill a power off/on.
Any solution herE?
Not sure why en how, but I do not have this problem anymore. Sometimes the bulbs sure unavailable for a moment, but they will come back online a minute or so later.
I ended using discovery rather than the static ip address…
I’m using manual configuration as per the integration guide with discovery set to false and fixed the IP. I’m also encountering the bulb connection being disconnected. “Bulb closed the connection”. Is there a way to resolve this?
I’ve also tried to do an hourly update via homeassistant.update_entity service but it still occurs. 
Any idea to keep the lights functioning is greatly appreciated 
If you are having a problem with a second generation bulb. it could be due an firmware issue which has just been fixed by the yeelight devs. More info on it here. So if or when it is available for you, you can try updating to 2.0.6_0065 from within the yeelight app.
Thanks, I will try when the firmware is available (which is not at the moment).
If you want it sooner you can try to add your MI ID to that topic maybe they will still whitelist you for the update depending on how long it takes to release the new firmware.
Thanks @Mister-Espria , the link was very insightful, though I wish that I have read it much earlier… That would save me many hours of troubleshooting. Guess I have to wait patiently for the updated firmware. I’ll try to post there too and see if the yeelight staff could expediate the release of the new firmware.
This morning the 2.0.6_0065 firmware was available for me. Just updated my bulbs and seems to work in HA again Thanks!
I’ve also upgraded my 2nd Gen color bulb to the new …065 firmware, but I can’t for the life of me get Home Assistant to recognise it. I’ve even reset the bulb and restarted Hassio, but it’s like it doesn’t exist.
Anyone else still having this problem? I’ve got other v1 Yeelight bulbs and strips that all work fine on automatic discovery
I am using the manuaal mode with discovery for yeelight disabled. Works fine for me.
Also having this problem. Latest firmware (2.0.6_0065), LAN control enabled, fixed IP address, etc.
They work perfectly fine from the Yeelight app. In Home Assistant they are recognized as Homekit accessories in the Integrations tab, but I’m not a Homekit user, I want to be able to control them directly from Home Assistant.
So discovery doesn’t work and I’ve tried adding them manually about 10 times but nothing seems to work.
A bit lost at the moment. Any sugestions…?
I agree and having the same problems after the firmware update. There is also no way to get the connection code
I am facing exactly the same issue: latest firmware (2.0.6_0065), manually configured, fixed ip address, discovery disabled for yeelight. Bulb works ok with mi home app but in HA is displayed as “unavailable”.
Nothing interesting can be seen in logs, even the fixed ip address is not logged, its simply ignored.
I am thinking to do the same but i have a doubt.
If automatically discovered, the lights need a static IP configured into the router or not?