Yeelight integration. Socket error every 3h 20m.

[FeromonDE]

The problem

Hi, I have 2 yeelight lamps connected via integrations. The problem is that every 3 hours 20 minutes the connection is disconnected for 30 seconds.

Environment

• Home Assistant Core release with the issue: 0.115.6
• Last working Home Assistant Core release (if known): ---
• Operating environment (OS/Container/Supervised/Core): HA Core in Docker
• Integration causing this issue: Yeelight
• Link to integration documentation on our website: https://www.home-assistant.io/integrations/yeelight/

Problem-relevant configuration.yaml

Traceback/Error logs

2020-10-03 06:58:40 ERROR (SyncWorker_33) [homeassistant.components.yeelight] Unable to update device 192.168.2.37, yeelight_lamp4_0x0000000010: A socket error occurred when sending the command.
2020-10-03 06:58:40 ERROR (SyncWorker_17) [homeassistant.components.yeelight] Unable to update device 192.168.2.29, yeelight_ceiling10_0x0000000010: A socket error occurred when sending the command.
2020-10-03 10:19:10 ERROR (SyncWorker_27) [homeassistant.components.yeelight] Unable to update device 192.168.2.29, yeelight_ceiling10_0x0000000010: A socket error occurred when sending the command.
2020-10-03 10:19:40 ERROR (SyncWorker_44) [homeassistant.components.yeelight] Unable to update device 192.168.2.37, yeelight_lamp4_0x0000000010: A socket error occurred when sending the command.
2020-10-03 13:39:41 ERROR (SyncWorker_2) [homeassistant.components.yeelight] Unable to update device 192.168.2.29, yeelight_ceiling10_0x0000000010: A socket error occurred when sending the command.
2020-10-03 13:40:11 ERROR (SyncWorker_17) [homeassistant.components.yeelight] Unable to update device 192.168.2.37, yeelight_lamp4_0x0000000010: A socket error occurred when sending the command.

Additional information

[springstan]

Please fill out the issue template, you can find it by clicking on New Issue and then selecting Report a bug with Home Assistant. Copy and paste the provided template into this already created issue, click preview to take a look at the empty template and then fill out as much as you can. Any additional information can be helpful!

Thanks for understanding :)

[FeromonDE]

I have provided enough information.
There is still a problem after upgrading to 0.116.2. I tried pinging the lamp before and after the error appeared in the log:
2020-10-13 10:42:01 ERROR (SyncWorker_16) [homeassistant.components.yeelight] Unable to update device 192.168.2.37, yeelight_lamp4_0x00000000102fef6c: A socket error occurred when sending the command.

And the ping was lossless:

--- 192.168.2.37 ping statistics ---
281 packets transmitted, 280 received, 0% packet loss, time 280429ms
rtt min / avg / max / mdev = 3.767 / 12.627 / 205.768 / 19.227 ms

Similar issue

esphome/issues#1196

[alesoft73]

Home assistant 116.4

My all yeelight lamp. (all lamp have static ip)

2020-10-19 05:09:49 ERROR (SyncWorker_59) [homeassistant.components.yeelight] Unable to update device 192.168.1.204, yeelight_bslamp2_0x000000000655037f: A socket error occurred when sending the command.
2020-10-19 07:55:04 ERROR (SyncWorker_35) [homeassistant.components.yeelight] Unable to update device 192.168.1.203, Antibagno: A socket error occurred when sending the command.
2020-10-19 05:04:19 ERROR (SyncWorker_46) [homeassistant.components.yeelight] Unable to update device 192.168.1.206, yeelight_bslamp1_0x00000000066a1275: A socket error occurred when sending the command.
2020-10-19 08:16:39 ERROR (SyncWorker_9) [homeassistant.components.yeelight] Unable to update device 192.168.1.199,
Bambini: Bulb closed the connection.

But only 2 bslamp don't return to work in home assistant.
The lamp is all on line and work with mi home app. (lan mode is on)

Many thanks.

[marcandre83]

I have the same problem in two locations with various yeelight lamps. It sometimes gets better after a router reset, so I suspect it has to do with some network issues on the code since all other apps that communicate with yeelights (homekit, xiaomi app) work flawlessly.

[FeromonDE]

Any Updates?

[github-actions]

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates.
Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍
This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.