@weiwei
Could I please get added to beta group?
ID: 1893497806
thanks!
Hello,
I am experiencing the same issue as described. Could you please add me as well?
MI ID: 1778359741
Thanks!
Could I please get added to beta group?
ID: 4166283871
china mainland
thanks!
Surprisingly, upgrading the bulbs to the beta firmware not only fixed the issue with these bulbs but also my light strip is working again without issues (still stock firmware).
Maybe helpful to know…
Please add me to beta group.
MI ID 1637842657
China Mainland
could you please add me also to the beta group?
ID: 1540760970
Please add me to beta group.
ID: 1819852929
Could you also add me to the beta group?
ID: 1607797253
Server: Germany
Thank you very much 
@Alacrity Is this still working for you? Please report back if still no disconnection after 48+ hours. Could be Homebridge plugin/Homekit component conflicting with Yeelight component. Thanks.
Could you also add me to the beta group?
MI ID: 1724344162
Server Continental China
Thank you!
I am also experiencing disconnected bulbs in HomeAssistant after a few hours, with “Bulb closed connection” showing in the logs as described in other posts.
What’s interesting is that I moved from OpenHab to HomeAssistant today because I was experiencing exactly the same issue in OpenHab. Bulbs worked fine for a while, but then suddenly disconnected. I thought moving to HA would fix it, but it seems that it is indeed an issue with the firmware then.
Could you please also add me to the whitelist for the updated firmware? My ID is 1872381185 and I’m on the German server. Thank you for your support, it is much appreciated.
Many reply already reported that the issue didn’t fix after updated firmware to 0054.
The problem is, all my yeelight bulbs failed to work with home assistant, unavailable issue nearly a month. The yeelight available if I manually turn on and off the power switch and it appear for few minutes or hours then unavailable again. The bulb failed to response to home assistant ‘get_prop’ request.
I know this problem is reported to home assistant team but so far, no solution from home assistant team yet.
I do suggest yeelight team to contact home assistant team to cop with the problem.
2 个赞
Hi, could you please add me to the beta group? Can’t see any updates for neither upgrading nor downgrading, lights randomly become offline in both Google Home and Yeelight app. Singapore server, mi id 6245070457.
Hi, everyone. Today we fixed a bug where the bulb went unresponsible to new local tcp connections or homekit directions after working normally for a while. The firmware version 2.0.6_0055 contains the patch. The boost in network stability is significant for most cases, while there’s still some issue with AC+AP setup (we are working on it).
All account in this thread have been whitelisted. Please try the new version (2.0.6_0055) out and feedback in case of any kind of failures.
2 个赞
Didn’t see beta updates
I was submit my MI id before
16133807 (China Mainland)
Maybe you guys missing.
@liufei I upgraded to FW build 0055 and after a few minutes my bulbs (9) became unavailable. Build 0054 was better my bulbs could stay available for several hours. Build 0055 made the disconnection issue worse in my case.
Please whitelist me
ID 1909449581 Singapore server
Thanks.
Please whitelist me for the beta updates
ID 1768357071 (China Mainland)
Updated to fw 0055 and problem still exist.
The bulb disconnect from home assistant after several hours. After it disconnected from home assistant, bulb doesn’t response to telnet too. I send the command {“id”:1,“method”:“get_prop”,“params”:[“power”, “not_exist”, “bright”]} and nothing happened, no error code as all, it just hang.
If I turn off and on the light switch, it work (both in home assistant and telnet) for several hours and disconnect again after several hours. If it is disconnected, only yeelight app can control the bulb. I don’t know what protocol is used in yeelight app to communicate with the bulb, but obviously, there is bug in the TCP/Telnet.