hey @yeelka, there is a similar issue in Google Home: setting colours via the Assistant will result in Color mode, instead of White, thus making the light less bright (colour also shifts to random bluish-greenish tints). my point is, that the issue does not seem to be HomeKit related, but something else.
also, using SmartThings, i was able to use the lights as intended, however, SmartThings randomly lost my lights (unavailable), and were never able to recover unless relinking the Yeelight service.
Hello @liufei Do you have any news on the beta firmware of the Color4?
Hello @Silvest and @ezcGman I saw that Home Assistant is releasing V1.0 and I saw in their beta 4 changelog something about the yeelight unavailability with rebooting and such. Maybe this will help fix the problems we are having. Release 1.0.0b4 · home-assistant/core · GitHub
Nah, I’ve seen the code, it fixes something else. The actual problem in this thread is firmware + library related.
If you are on the latest beta firmware for color4, the get_prop call doesnt work at all. The HA integration is dependant on this to get all the props. What I fixed is temporarily I just use SSDP as my get_prop calls which works for all my lights now though you’d miss out on ambilight and binary sensor. I might do something like use SSDP as a fallback only if get_prop doesn’t work properly. And also previously in the library, you’d use one socket which if you don’t get any error it would never get closed properly.
The firmware can only handle 4 open TCP connections (Stated in the documentation) so I just close the socket after each action to work around this problem. Since a restart or watever might keep the connection open on the lighting.
And then you’d have to power cycle (on and off) the lights so you’d be able to connect again. You can test how it works by just telnetting and keeping them open, then open another command line (the 5 one would just be refused).
So restart etc or anything could leave the sockets open. Don’t know if the firmware properly garbage collect dangling connections after * amount of time.
The HA integration is dependant of the get_prop calls. It’s in their update loop. All other commands sent to lights work (though some might not always give a response but that doesn’t matter) .
The current color4 beta firmware breaks get_prop, haven’t tested the bslamp2 and ceiling20.
I’ll push an update later today or tomorrow for using SSDP only as a fallback. This should fix the ambilights on ex. ceiling20. Using my library changes my lights have been stable even on the latest beta firmware for ceiling20, bslamp2 and color4 for a week now…
Hi @liufei, I updated the firmware to 2.0.6 0031. The 16 bulbs didn’t go offline for a good 3 days. But they went offline and unreachable via the Yeelight app this morning. I have not been able to connect to the 16 bulbs since this morning. Can you advise next steps, please?
@liufei
A color2 bulb with latest firmware doesn’t work with Google Home. Google Home can see the status of the color2 that is on the latest firmware. Commands sent from google home have no effect on the color2 that is on the latest firmware.
I have another color2 bulb that is still on the firmware that it came originally shipped with, on the same network as the non-functional color2.
The color2 bulb that is still on its original firmware works properly with google home.
Is there anyone else that can add our IDs to the whitelist? 4 days since I asked and still, can’t update my bulbs to the beta FW. Come on guys, help us out!
I know I shouldn’t laugh, but lol 4 days. Some of the issues people have been having are over a year old. Looks like Yeelight disappeared again from this thread. Here’s hoping for a miracle in 2021 and once and for all just have these bulbs not lose connection from routers even… 3 feet away?
Hi all, I was having these problems too with bulbs (going totally offline/unavailable) and strips (unavailable and flickering) but at my place, it was caused by a problem coming from my Shelly devices (I have one Shelly1 and six shelly2.5). Those were running on firmwareversion 1.8.0 and since 2 days those are now running on 1.9.3 and guess what: no single drops anymore on my Yeelight lights, not in Home Assistant and not in the yeelight app.
This was mentioned in the changelog (4th bulletpoint):
Hi @liufei, I have to correct myself.
With the new firmware the problem is reduced but not finally solved. After more than one month I’ve had still several disconnections. I think once every 2/3 days.
I am running the latest version of Home assistant, and I am having issues with this 2.0.6_0031 firmware. Is it possible to either get permission to downgrade, or, get on the beta list for my RGB 1S bulbs (color4)? Thanks.
