There are disconnections after about 24 hours, but they always been. I’m not using Home Assistant, I’ve written my own firmware for esp8266, that controls bulbs and connects them to MQTT.
In case of disconnect, esp8266 reconnects to bulb at once, and it doesn’t bother me.
Without homebridge-yeelight plugin, bulbs always respond by TCP telnet connection to port 55443 (max 4 simultaneous connections, don’t forget).
So, guys, if your bulb doesn’t respond by telnet, first try to shutdown all controlling software and hardware at your network, Smart Home soft, etc. Maybe this software doing something wrong with your bulbs.
Still the same thing here on 0055 as well. Not being able to use my lights normally is getting really frustrating. They stay unavailable until a powercycle which is exactly the same behavior as before.
Yes, very frustrating. In my case all bulbs are manipulated via automation in HA. I don’t use the Yeelight app and my bulbs are all practically useless at the moment. This issue has literally affected and greatly inconvenienced people’s lives.
Some positive news then: upgraded my 8 bulbs (v2, color) to the 0055 firmware and have not experienced any disconnections since. Home Assistant works like a charm again. Thanks Yeelight devs!
If it helps anyone, all my bulbs have static IP’s set in the router and are configured in configuration.yaml as follows:
Hi, could you please add me to the beta group? Can’t see any updates. lights randomly become offline in both Google Home and Yeelight app. Singapore server, mi id 6245070457
The bulb connection issue is over a month since firmware upgrade to 0051. Then no solution after 0054, 0055 … Many other user already post threads about the issue of disconnection of the 0051, but still, no solution at all.
I do believe that people in this thread do use home assistant. It’s meaningless that other software, yeelight app or custom firmware etc can control the bulb. It’s above home assistant. And many people, like me, buy yeelight bulb because it work with home assistant. But since 0051, it won’t work anymore. Should I throw all my bulb away and buy other brands?
At first, this post request to downgrade the firmware. But yeelight staff reject it and said this will ‘harm’ the bulb. I’m not an expert, but I do flash firmware of many different devices many time. I already know that It is a risk of flashing firmware. If I can take the risk of bricking my bulb. (for me, the bulb already is a brick and useless) Can yeelight staff provide firmware downgrade for me??
we are working on this issue as 1st priority now but it’s impossible to reproduce this problem in our lab. we are pushing the chip vendor to check their firmware too, so please have some patience.
Exactly my situation. Bulbs are considered bricked anyway (if you think about it, it’s the upgrade that actually bricked them). No risk at all flashing old firmware. Nothing to lose. f downgrade is not permitted and no working solution is offered, lots of people’s money are wasted.
I realised same thing to mi gateway. So those who haven’t upgraded their firmware please refrain to do so.
I’m looking a way to quit from xiao mi if they can’t solve it in another mth time.
Hello,
.
