I still continue to have these errors about yeelight bulb… They are making the logfile grow too much (actually 4.8Mb).
2018-04-25 18:46:47 ERROR (Thread-19) [homeassistant.components.light.yeelight] Unable to update bulb status: A socket error occurred when sending the command.
2018-04-25 18:46:47 ERROR (Thread-14) [homeassistant.components.light.yeelight] Unable to update bulb status: A socket error occurred when sending the command.
2018-04-25 18:47:15 ERROR (Thread-3) [homeassistant.components.light.yeelight] Unable to update bulb status: A socket error occurred when sending the command.
2018-04-25 18:47:16 ERROR (Thread-14) [homeassistant.components.light.yeelight] Unable to update bulb status: A socket error occurred when sending the command.
2018-04-25 18:47:16 ERROR (Thread-10) [homeassistant.components.light.yeelight] Unable to update bulb status: A socket error occurred when sending the command.
2018-04-25 18:48:11 ERROR (Thread-13) [homeassistant.components.light.yeelight] Unable to update bulb status: Bulb closed the connection.
2018-04-25 18:48:11 ERROR (Thread-9) [homeassistant.components.light.yeelight] Unable to update bulb status: A socket error occurred when sending the command.
2018-04-25 18:48:11 ERROR (Thread-3) [homeassistant.components.light.yeelight] Unable to update bulb status: A socket error occurred when sending the command.
2018-04-25 18:48:11 ERROR (Thread-14) [homeassistant.components.light.yeelight] Unable to update bulb status: A socket error occurred when sending the command.
2018-04-25 18:48:11 ERROR (Thread-10) [homeassistant.components.light.yeelight] Unable to update bulb status: A socket error occurred when sending the command.
Randomly they go to unavailable mode for some seconds and thenthey turn to available but in the logfile the errors is still there… I am using discovery mode as the bulbs are in the same network of HA.
Edit: I also noticed that automations with yeelight bulbs work, but in the frontend the light are still off after the automations trigger…
I tried some days ago this, but after restart i had for every bulb two entries (maybe i must exclude lights from the discovery option?) and then turned back to discovery mode.
Hmmm… sincerely i really don’t know what i am using with discovery… I leave it as default since the first days of HA… do you know what can be discovered other than yeelight?
The error log gives very little info on the actual error. It seems to be a network issue or a wifi issue.
Music mode has given people issues in the past. It is not clear if it is on or off when discovery is used. See the docs on music mode
The idea is to take options away that could cause the error to trouble shoot. Not knowing your network setup or HA setup in general its really hard to troubleshoot from a few lines of generic error log.
Edit: I am also using what I use and has been rock solid for over a year. The only time my bulbs are unavailable is when someone throws the switch.
Same as before also after manually configuring bulbs:
2018-04-25 21:05:00 ERROR (Thread-12) [homeassistant.components.light.yeelight] Unable to update bulb status: A socket error occurred when sending the command.
2018-04-25 21:05:29 ERROR (Thread-6) [homeassistant.components.light.yeelight] Unable to update bulb status: A socket error occurred when sending the command.
2018-04-25 21:06:00 ERROR (Thread-5) [homeassistant.components.light.yeelight] Unable to update bulb status: A socket error occurred when sending the command.