Yeelight Ceiling Light 650 randomly goes offline after successfully discovery


#1

Hello community,
I’m driving crazy with 2 Yeelight Ceiling Lights 650. Home Assistant can discover correctly these devices, but after some times one of them goes in offline status (not always the same lamp), so I’m not able to ping it anymore from HA. I have also other Yeelight lights like Bulbs, Led strips and Celing Lights 450 who doesn’t suffers by this issue. After powering off/on the lamp, HA is able to ping/discover it again. During the offline issue, the Ceiling Light is still connected to the internet, so I can power on/off using Yeelight App, so it seems the issue is related to HA and Yeelight LAN control.
I updated the netdisco component to the latest version: https://github.com/home-assistant/netdisco and HA is able to identify the Ceiling lights like:
light.yeelight_ceiling4_7811dcxxxxxx
But still got offline :frowning:

I activated the Yeelight debug, and, also during offline status I can see the following for the Ceiling Light (nothing else)

2018-05-27 08:20:58 DEBUG (Thread-17) [yeelight.main] Bulb<192.168.2.27:55443, type=BulbType.Color> > {‘params’: [‘power’, ‘bright’, ‘ct’, ‘rgb’, ‘hue’, ‘sat’, ‘color_mode’, ‘flowing’, ‘delayoff’, ‘music_on’, ‘name’], ‘id’: 64, ‘method’: ‘get_prop’}
2018-05-27 08:21:03 ERROR (Thread-10) [homeassistant.components.light.yeelight] Unable to update bulb status: Bulb closed the connection.

Previously they both work perfect, and never go offline, but I don’t know if the issue was introduced by HA upgrade (I had 0.68.0, now I have 0.69.1) or Ceiling Lights firmware upgrade (I have 1.5.5_0038 and now 1.5.5_0041). I also contacted the Yeelight support, but they said that the issue is related to HA that doesn’t reply to Yeelight devices. Ok, but why other Yeelight devices in my LAN remain connected? Maybe there’s a bug in HA who is not able to handle the specific yeelight_ceiling4?

Could someone help me here?

Thank you
Lucas


#2

Are you able to (icmp) ping the device all the time?


#3

@syssi: Nope, the device goes offline, and I cannot ping nor telnet it from my lan including HA. :frowning:

But I notice something strage, already reported to Yeelight forum. All my device in my wifi network, including mobile phones, notebook, PC, yeelight bulbs, led strips, and Ceiling lights 450, have a low response time (ping from HA), instead, both Ceiling Lights 650 have a very large response time, and this could be the reason for offline issue. The Yeelight devices think the peer is down, and close the connection due to timeout in response. I don’t know if this issue is caused by the new firmware, but for sure is not my local network since, as I wrote, all other devices work perfect and have low response time.

My Ceiling lights have the following firmware: 1.5.5_0041, is there anyone with Ceiling Lights 650 who can check this behaviour??

(Yeelight Bulb):

PING 192.168.2.28 (192.168.2.28) 56(84) bytes of data.
64 bytes from 192.168.2.28: icmp_seq=1 ttl=255 time=3.04 ms
64 bytes from 192.168.2.28: icmp_seq=2 ttl=255 time=6.37 ms
64 bytes from 192.168.2.28: icmp_seq=3 ttl=255 time=6.19 ms
64 bytes from 192.168.2.28: icmp_seq=4 ttl=255 time=7.63 ms

(Yeelight Led Strip):

PING 192.168.2.32 (192.168.2.32) 56(84) bytes of data.
64 bytes from 192.168.2.32: icmp_seq=1 ttl=255 time=3.33 ms
64 bytes from 192.168.2.32: icmp_seq=2 ttl=255 time=5.73 ms
64 bytes from 192.168.2.32: icmp_seq=3 ttl=255 time=4.81 ms
64 bytes from 192.168.2.32: icmp_seq=4 ttl=255 time=9.8 ms
64 bytes from 192.168.2.32: icmp_seq=5 ttl=255 time=2.54 ms

(Ceiling Light 450):

PING 192.168.2.23 (192.168.2.23) 56(84) bytes of data.
64 bytes from 192.168.2.23: icmp_seq=1 ttl=255 time=3.36 ms
64 bytes from 192.168.2.23: icmp_seq=2 ttl=255 time=10.6 ms
64 bytes from 192.168.2.23: icmp_seq=3 ttl=255 time=6.61 ms

Ceiling lights 650 1:

PING 192.168.2.26 (192.168.2.26) 56(84) bytes of data.
64 bytes from 192.168.2.26: icmp_seq=1 ttl=255 time=1159 ms
64 bytes from 192.168.2.26: icmp_seq=2 ttl=255 time=1157 ms
64 bytes from 192.168.2.26: icmp_seq=6 ttl=255 time=1095 ms
64 bytes from 192.168.2.26: icmp_seq=7 ttl=255 time=456.2 ms
64 bytes from 192.168.2.26: icmp_seq=8 ttl=255 time=117 ms
64 bytes from 192.168.2.26: icmp_seq=9 ttl=255 time=1688 ms

Ceiling lights 650 2:

PING 192.168.2.27 (192.168.2.27) 56(84) bytes of data.
64 bytes from 192.168.2.26: icmp_seq=1 ttl=255 time=346.7 ms
64 bytes from 192.168.2.26: icmp_seq=2 ttl=255 time=599 ms
64 bytes from 192.168.2.26: icmp_seq=3 ttl=255 time=608 ms
64 bytes from 192.168.2.26: icmp_seq=7 ttl=255 time=998 ms
64 bytes from 192.168.2.26: icmp_seq=8 ttl=255 time=322.91 ms

#4

Are you sure you are able to control the light by the Yeelight App all the time?


#5

Nope, sometime it goes offline also in Yeelight app, but with low frequency compared with HA.
BTW, I changed the WiFi radio channel from AUTO to 2, then the hotspot reset all WiFi connections. Now, pinging the Ceiling Lights will result in reasonable response time:

PING 192.168.2.27 (192.168.2.27) 56(84) bytes of data.
64 bytes from 192.168.2.27: icmp_seq=1 ttl=255 time=153 ms
64 bytes from 192.168.2.27: icmp_seq=2 ttl=255 time=56.9 ms
64 bytes from 192.168.2.27: icmp_seq=3 ttl=255 time=65.4 ms

PING 192.168.2.26 (192.168.2.26) 56(84) bytes of data.
64 bytes from 192.168.2.26: icmp_seq=1 ttl=255 time=111 ms
64 bytes from 192.168.2.26: icmp_seq=2 ttl=255 time=105 ms
64 bytes from 192.168.2.26: icmp_seq=3 ttl=255 time=127 ms

Unfortunately, again, one Ceiling Light 650 goes offline, this time it tooks long time.
Even I don’t understand why only the Ceiling Lights 650 got the issue. :face_with_symbols_over_mouth: