Ceiling device offline issue


#1

All,

If you have offline issues with your ceiling devices (ceiling, ceiling 450, ceiling 480 and ceiling 650), please update to the latest firmware and have a try. We have released a new firmware to resolved the issue.

Latest firmware version for ceiling device:
Ceiling - 1.5.5_0180
Ceiling SE - 1.5.5_0026
Ceiling 450 and Ceiling 480 - 1.5.5_0034
Ceiling 650 - 1.5.5_0038

Any questions, let us know!

Thanks,
Andy Ding


#2

Thank you, all my Ceiling lights (480/650) are updated with current firmware and I can confirm I have no more offline issue. What about latest firmware versione for Yeelight Bulb? Actually I have 1.4.2_0060.


#3

Thanks for your feedback!

Yes, 1.4.2_0060 is latest firmware for color bulb.


#4

Ok thank you. Just to clarify that I ask for bulbs firmware info only for curiosity, since they don’t suffer offline issue too.


#5

:ok_hand:


#6

Having issues with the ceiling 450 after installation. Worked well for a day but it automatically shuts off after a while now, even after multiple resets and updating to 1.5.5_0034. Is it a hardware issue?


#7

Same problem here


#8

we are working on this issue, it maybe related to chip vendor’s firmware, please stay tuned, will release the firmware as soon as the issue fixed.


#9

Thank you @weiwei for reply. I’m suffering (again) in offline issue ONLY for Ceiling 650, is the fix will be also for that device?
My latest working firmware was 1.5.5_0038, starting from 1.5.5_0039 and now with 1.5.5_0041, my 2 Ceiling 650 goes offline randomly. DAMN! I didn’t have to update! :frowning_face:
Hope Yeelight team will resolve soon that issue, since several times at the day I have to manually switch off/on the ceiling light.


#10

Got it! We will release a major update recently for all ceiling lights. The chip vendor (MTK) fixed several WiFi and stability-related bugs, we are doing test now.


#11

@weiwei Perfect thank you, I’ll wait for the release, and I’m available for beta testing (Mi ID: 1744792246). My Ceilings 650 goes offline at least every hour. But after further investigation I discover that Ceilings are still connected to the internet, so I can command them via Yeelight or Mi apps, and the issue is related to LAN Control. For some reason it becomes unavailable to the local network, so my Home Assistant is not able to see them anymore. All my other Yeelight products (bulbs, Ceiling 450, led strip, etc) are not affect by this issue.


#12

Next time could you try “telnet ‘ip of the ceiling light’ 55443” to see if it is still responsible? It may related to Home Assistant plugins since the ceiling lights use TCP keep-alive mechanism to detect peer shutdown, it Home Assistant didn’t handle that properly, the ceiling lights may think peer is dead and close the connection.


#13

@weiwei thank you for feedback, however, I didn’t have that issue with firmware: 1.5.5_0038, and the ceilings becomes unreachable not only from Home Assistant, but from all the lan. BTW, I’ll try to check my Home Assistant configuration, waiting for firmware update! :wink:


#14

Ok, thanks for you update, we will take a look at the code changes between two release.


#15

@weiwei, my apologies, you had right, the often offline issue was caused by Home Assistant discovery module. I fixed it and now the celinings stay online. However, sometimes (about 1 time per day) goes offline at all, so I’ll wait the firmware update. Thank you for your time!

EDIT: Damn! Still get offline issue only on Ceilings 650. At this point I believe the problem is on device side. Well, will se when the firmware will be updated! :slight_smile:


#16

@weiwei Definitely is a firmware issue. Bulbs, Led strips and Ceiling lights 450 and 650 are all in the same network (I have also other devices like sonoff), but the ping shown low response time from bulbs, led strip, Ceiling light 450, and from all device in the WiFi network. But very long response time only from Ceiling Lights 650, so the TCP keep alive packets will be loosed, and, Ceiling lights think the peer is dead and close the connection. BTW, is there a way to increase the timeout for keep alive as a workaround?
As I said, I don’t have this behaviour with firmware 1.5.5_0038

(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

#17

Interesting, we will take a look at the WiFi performance of Ceiling 650.


#18

Hmm that’s strange… just checked mine, and even though 650 (YL-LIVING in my LAN) is a bit worse, not too much of a difference:

C:>ping YL-STRIP_1

Pinging YL-STRIP_1 [192.168.1.212] with 32 bytes of data:
Reply from 192.168.1.212: bytes=32 time=4ms TTL=255
Reply from 192.168.1.212: bytes=32 time=3ms TTL=255
Reply from 192.168.1.212: bytes=32 time=7ms TTL=255
Reply from 192.168.1.212: bytes=32 time=6ms TTL=255

Ping statistics for 192.168.1.212:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 3ms, Maximum = 7ms, Average = 5ms

C:>ping YL-LAMP_L

Pinging YL-LAMP_L [192.168.1.210] with 32 bytes of data:
Reply from 192.168.1.210: bytes=32 time=2ms TTL=255
Reply from 192.168.1.210: bytes=32 time=3ms TTL=255
Reply from 192.168.1.210: bytes=32 time=3ms TTL=255
Reply from 192.168.1.210: bytes=32 time=3ms TTL=255

Ping statistics for 192.168.1.210:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 2ms, Maximum = 3ms, Average = 2ms

C:>ping YL-LAMP_R

Pinging YL-LAMP_R [192.168.1.211] with 32 bytes of data:
Reply from 192.168.1.211: bytes=32 time=6ms TTL=255
Reply from 192.168.1.211: bytes=32 time=6ms TTL=255
Reply from 192.168.1.211: bytes=32 time=4ms TTL=255
Reply from 192.168.1.211: bytes=32 time=3ms TTL=255

Ping statistics for 192.168.1.211:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 3ms, Maximum = 6ms, Average = 4ms

C:>ping YL-KITCHEN

Pinging YL-KITCHEN [192.168.1.216] with 32 bytes of data:
Reply from 192.168.1.216: bytes=32 time=3ms TTL=255
Reply from 192.168.1.216: bytes=32 time=3ms TTL=255
Reply from 192.168.1.216: bytes=32 time=3ms TTL=255
Reply from 192.168.1.216: bytes=32 time=5ms TTL=255

Ping statistics for 192.168.1.216:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 3ms, Maximum = 5ms, Average = 3ms

C:>ping YL-DINER

Pinging YL-DINER [192.168.1.213] with 32 bytes of data:
Reply from 192.168.1.213: bytes=32 time=7ms TTL=255
Reply from 192.168.1.213: bytes=32 time=2ms TTL=255
Reply from 192.168.1.213: bytes=32 time=8ms TTL=255
Reply from 192.168.1.213: bytes=32 time=3ms TTL=255

Ping statistics for 192.168.1.213:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 2ms, Maximum = 8ms, Average = 5ms

C:>ping YL-LIVING

Pinging YL-LIVING [192.168.1.215] with 32 bytes of data:
Reply from 192.168.1.215: bytes=32 time=4ms TTL=255
Reply from 192.168.1.215: bytes=32 time=9ms TTL=255
Reply from 192.168.1.215: bytes=32 time=48ms TTL=255
Reply from 192.168.1.215: bytes=32 time=3ms TTL=255

Ping statistics for 192.168.1.215:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 3ms, Maximum = 48ms, Average = 16ms

C:>