Core: Unable to update bulb status: A socket error occurred when sending the command.

[vpomax]

I'm runnng last versione on Home Assistant and Hassio I've 4 yeelight rgb bulbs all working fine but I receive errors

Home Assistant 0.65.6
Hassio 0.99

Description of problem: errors in home-assistant.log

2018-03-25 19:55:36 ERROR (SyncWorker_16) [homeassistant.components.light.yeelight] Unable to update bulb status: A socket error occurred when sending the command.
2018-03-25 19:55:36 ERROR (SyncWorker_5) [homeassistant.components.light.yeelight] Unable to update bulb status: A socket error occurred when sending the command.

[syssi]

Could you try to update the firmware of your yeelights?

[mfabiani53]

I have the same errors and have the latest firmware...
I have tons of those errors that make my logfile actually 4.8 MB big.

[syssi]

Unfortunately it looks like a network issue. Please make sure there is no network component which drops the connection.

[freekeys]

I have this issue too... @syssi please can you provide more detailed instructions on how to check this? Thanks!

[syssi]

There is a tcp connection between HA and your bulb. If the connection drops the socket error occurs. You could capture your network traffic by tcpdump (on your HA host) and check the tcp connection in detail.

[trimethia]

Same here using 0.69.0 and yeelight bulbs.

[balloobbot]

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 :+1:

[trimethia]

Still happening with 0.74.

[syssi]

@trimethia Could you try to setup a small wifi (bulb <-> accesspoint <-> homeassistant) network just for testing. Please use another accesspoint as the current one.

[patrickjane]

I am facing the same. I set up the yeelight some months ago, and in the beginning it worked. But still I observed that the connection would be totally lost after 1-2 weeks, and I had to factory reset the yeelight and connect it to the WLAN again, for it to be connected to HA again.
I also tried to change channels on the wifi access point with no success.

And right now, for some weeks now, I am unable to get it working again at all - it will totally refuse to work within HA.

I will experiment again with access point settings, and also try to use the MiHome app, although I am quite certain that the lamp is working when using the MiHome app.

This is what I see in the HA log after a HA restart:

2018-07-30 14:38:24 ERROR (Thread-8) [homeassistant.components.light.yeelight] Failed to connect to bulb 10.0.0.10, Nachttischlampe: A socket error occurred when sending the command.

This is the only error message related to the yeelight, no more messages are shown (this probably also means that no reconnect is attempted).
BTW I am having a xiaomi mi bedside lamp w/ WIFI (https://www.mi.com/us/mi-bedside-lamp/).

[patrickjane]

Yesterday I retried with different access point settings, until I found a channel on which the bedside lamp can connect without problems. I factory reset the bedside lamp, connected it to the wifi via bluetooth, and now I can control it via the mi home app (screenshot from just now: https://imgur.com/a/jbACaO1).

However, home assistant still claims the device is unavailable, with the same error message as above:

Jul 31 08:13:45 pi3HA hass[2028]: 2018-07-31 08:13:45 ERROR (Thread-5) [homeassistant.components.light.yeelight] Failed to connect to bulb 10.0.0.10, Nachttischlampe: A socket error occurred when sending the command.

I really don't know what to do, because the lamp is definitely reachable on the network :(

[syssi]

Is the developer mode still enabled? Are you able to ping the bulb?

[patrickjane]

Sure, I can ping it, as I can also connect to it via Wi-Fi using the MiHome app. I checked the MiHome app, but there is no such option, so I am unsure what the developer mode is.

Also, I am quite sure that I have never enabled such a mode in the past, and yet it used to work, some couple of weeks/months ago?

[syssi]

Are you sure? The mode must be enabled with the yeelight app also called "LAN mode": https://www.home-assistant.io/components/light.yeelight/

[patrickjane]

Ok I see, I didnt check the yeelight app, just the MiHome app. I cannot try this out in the office now via VPN, since the yeelight app cannot connect to existing lamps, and instead wants to couple again via bluetooth. I'm going to try in the evening when back home, and report if this got me any further.

[patrickjane]

Okay I was able to enable the LAN mode in the yeelight app, and in fact HA is now able to connect to the lamp and control it.
I have not done this before, and was not aware I should do it, but now everything seems to work again.

So please just disregard my previous posts. Sorry for the confusion.

[cgarwood]

Closing since it looks like this is working now? Please open a new issue if that's not the case.

[Kreuger]

Hi all. Can we have this issue reopened? I'm having the same problem now. Yesterday I set up a lightstrip and colour 1s bulb. They both worked the first few times I played around with them. Now the lightstrip is having this issue. Everything is up to date and I am able to user the Yeelight app itself to control it just fine. It appears that the issue is with HA.

Edit: It turns out the IP address on the device changed. I'm not sure why but I guess I will need to go into my router and force a static one.