Homey Community Forum

[APP] Yeelights

1 of my 4 devices is also unreachable, also after reinstall

v1.0.3 - 2019-12-01

Small fixes to improve pairing process and avoid crashes when removing Yeelight devices.

1 Like

Reporting what works for me here in case anyone experienced the same…

After removing the Yeelight led strip from the Xiaomi app, I also couldn’t add them back in via the Yeelight app. Tried ptp on homey, restarted all the respective apps and reboot didn’t work.
What worked, was to physically power off and on the Yeelight light itself to force a reconnection to wifi before the homey Yeelight app detected it.
All the while, the iOS Yeelight app is working with the Yeelights but somehow homey just couldn’t detect it…

Hi, today all my Yeelights were off - 8d3b8c2d-04a6-44ec-8261-283464f46d23 , yet again working fine in the original app.

Below is a big part of the log. It seems the connection is reset and the lights become unreachable. I already catch these events and don’t know what else to do. It just seems an unstable connection between Homey and the lights.

log] [ManagerDrivers] [yeelight] [2] Yeelight - error on socket: Error: read ECONNRESET
2019-12-06 02:51:34 [log] [ManagerDrivers] [yeelight] [2] Yeelight - trying to reconnect in 6 seconds.
2019-12-06 02:51:42 [log] [ManagerDrivers] [yeelight] [5] Yeelight - error on socket: Error: read ECONNRESET
2019-12-06 02:51:42 [log] [ManagerDrivers] [yeelight] [5] Yeelight - trying to reconnect in 6 seconds.
2019-12-06 02:52:18 [log] [ManagerDrivers] [yeelight] [0] Yeelight - error on socket: Error: read ECONNRESET
2019-12-06 02:52:18 [log] [ManagerDrivers] [yeelight] [0] Yeelight - trying to reconnect in 6 seconds.
2019-12-06 02:52:28 [log] [ManagerDrivers] [yeelight] [6] Yeelight - error on socket: Error: read ECONNRESET
2019-12-06 02:52:28 [log] [ManagerDrivers] [yeelight] [6] Yeelight - trying to reconnect in 6 seconds.
2019-12-06 02:52:28 [log] [ManagerDrivers] [yeelight] [4] Yeelight - error on socket: Error: read ECONNRESET
2019-12-06 02:52:28 [log] [ManagerDrivers] [yeelight] [4] Yeelight - trying to reconnect in 6 seconds.
2019-12-06 02:52:49 [log] [ManagerDrivers] [yeelight] [7] Yeelight - error on socket: Error: read ECONNRESET
2019-12-06 02:52:49 [log] [ManagerDrivers] [yeelight] [7] Yeelight - trying to reconnect in 6 seconds.
2019-12-06 03:00:25 [log] [ManagerDrivers] [yeelight] [6] Yeelight - error on socket: Error: read ECONNRESET
2019-12-06 03:00:25 [log] [ManagerDrivers] [yeelight] [6] Yeelight - trying to reconnect in 6 seconds.
2019-12-06 03:00:25 [log] [ManagerDrivers] [yeelight] [4] Yeelight - error on socket: Error: read ECONNRESET
2019-12-06 03:00:25 [log] [ManagerDrivers] [yeelight] [4] Yeelight - trying to reconnect in 6 seconds.
2019-12-06 03:00:45 [log] [ManagerDrivers] [yeelight] [7] Yeelight - error on socket: Error: read ECONNRESET
2019-12-06 03:00:45 [log] [ManagerDrivers] [yeelight] [7] Yeelight - trying to reconnect in 6 seconds.
2019-12-06 03:00:55 [log] [ManagerDrivers] [yeelight] [5] Yeelight - error on socket: Error: read ECONNRESET
2019-12-06 03:00:55 [log] [ManagerDrivers] [yeelight] [5] Yeelight - trying to reconnect in 6 seconds.
2019-12-06 03:00:55 [log] [ManagerDrivers] [yeelight] [3] Yeelight - error on socket: Error: read ECONNRESET
2019-12-06 03:00:55 [log] [ManagerDrivers] [yeelight] [3] Yeelight - trying to reconnect in 6 seconds.
2019-12-06 03:01:08 [log] [ManagerDrivers] [yeelight] [8] Yeelight - error on socket: Error: read ECONNRESET
2019-12-06 03:01:08 [log] [ManagerDrivers] [yeelight] [8] Yeelight - trying to reconnect in 6 seconds.
2019-12-06 03:01:26 [log] [ManagerDrivers] [yeelight] [1] Yeelight - error on socket: Error: read ECONNRESET
2019-12-06 03:01:26 [log] [ManagerDrivers] [yeelight] [1] Yeelight - trying to reconnect in 6 seconds.
2019-12-06 03:01:31 [log] [ManagerDrivers] [yeelight] [0] Yeelight - error on socket: Error: read ECONNRESET
2019-12-06 03:01:31 [log] [ManagerDrivers] [yeelight] [0] Yeelight - trying to reconnect in 6 seconds.
2019-12-06 03:02:07 [log] [ManagerDrivers] [yeelight] [2] Yeelight - error on socket: Error: read ECONNRESET
2019-12-06 03:02:07 [log] [ManagerDrivers] [yeelight] [2] Yeelight - trying to reconnect in 6 seconds.
2019-12-06 04:51:02 [log] [ManagerDrivers] [yeelight] [8] Yeelight - error on socket: Error: read ECONNRESET
2019-12-06 04:51:02 [log] [ManagerDrivers] [yeelight] [8] Yeelight - trying to reconnect in 6 seconds.
2019-12-06 04:51:07 [log] [ManagerDrivers] [yeelight] [1] Yeelight - error on socket: Error: read ECONNRESET
2019-12-06 04:51:07 [log] [ManagerDrivers] [yeelight] [1] Yeelight - trying to reconnect in 6 seconds.
2019-12-06 04:51:07 [log] [ManagerDrivers] [yeelight] [5] Yeelight - error on socket: Error: read ECONNRESET
2019-12-06 04:51:07 [log] [ManagerDrivers] [yeelight] [5] Yeelight - trying to reconnect in 6 seconds.
2019-12-06 04:51:07 [log] [ManagerDrivers] [yeelight] [3] Yeelight - error on socket: Error: read ECONNRESET
2019-12-06 04:51:07 [log] [ManagerDrivers] [yeelight] [3] Yeelight - trying to reconnect in 6 seconds.
2019-12-06 04:51:08 [log] [ManagerDrivers] [yeelight] [7] Yeelight - error on socket: Error: read ECONNRESET
2019-12-06 04:51:08 [log] [ManagerDrivers] [yeelight] [7] Yeelight - trying to reconnect in 6 seconds.
2019-12-06 04:51:11 [log] [ManagerDrivers] [yeelight] [6] Yeelight - error on socket: Error: read ECONNRESET
2019-12-06 04:51:11 [log] [ManagerDrivers] [yeelight] [6] Yeelight - trying to reconnect in 6 seconds.
2019-12-06 04:51:12 [log] [ManagerDrivers] [yeelight] [4] Yeelight - error on socket: Error: read ECONNRESET
2019-12-06 04:51:12 [log] [ManagerDrivers] [yeelight] [4] Yeelight - trying to reconnect in 6 seconds.
2019-12-06 04:51:12 [log] [ManagerDrivers] [yeelight] [0] Yeelight - error on socket: Error: read ECONNRESET
2019-12-06 04:51:12 [log] [ManagerDrivers] [yeelight] [0] Yeelight - trying to reconnect in 6 seconds.
2019-12-06 04:51:13 [log] [ManagerDrivers] [yeelight] [2] Yeelight - error on socket: Error: read ECONNRESET
2019-12-06 04:51:13 [log] [ManagerDrivers] [yeelight] [2] Yeelight - trying to reconnect in 6 seconds.
2019-12-06 04:51:16 [log] [ManagerDrivers] [yeelight] [1] Yeelight - error on socket: Error: connect EHOSTUNREACH 10.0.0.142:55443
2019-12-06 04:51:17 [log] [ManagerDrivers] [yeelight] [7] Yeelight - error on socket: Error: connect EHOSTUNREACH 10.0.0.141:55443
2019-12-06 04:51:20 [log] [ManagerDrivers] [yeelight] [6] Yeelight - error on socket: Error: connect EHOSTUNREACH 10.0.0.145:55443
2019-12-06 04:51:21 [log] [ManagerDrivers] [yeelight] [4] Yeelight - error on socket: Error: connect EHOSTUNREACH 10.0.0.155:55443
2019-12-06 04:51:21 [log] [ManagerDrivers] [yeelight] [0] Yeelight - error on socket: Error: connect EHOSTUNREACH 10.0.0.144:55443
2019-12-06 04:51:43 [log] [ManagerDrivers] [yeelight] [8] Yeelight - error on socket: Error: connect EHOSTUNREACH 10.0.0.191:55443
2019-12-06 04:51:54 [log] [ManagerDrivers] [yeelight] [2] Yeelight - error on socket: Error: connect EHOSTUNREACH 10.0.0.157:55443
2019-12-06 04:52:05 [log] [ManagerDrivers] [yeelight] [2] Yeelight - error on socket: Error: connect EHOSTUNREACH 10.0.0.157:55443
2019-12-06 04:52:08 [log] [ManagerDrivers] [yeelight] [2] Yeelight - error on socket: Error: connect EHOSTUNREACH 10.0.0.157:55443
2019-12-06 04:52:21 [log] [ManagerDrivers] [yeelight] [5] Yeelight - error on socket: Error: connect EHOSTUNREACH 10.0.0.143:55443
2019-12-06 04:52:21 [log] [ManagerDrivers] [yeelight] [3] Yeelight - error on socket: Error: connect EHOSTUNREACH 10.0.0.120:55443
"ECONNRESET" means the other side of the TCP conversation abruptly closed its end of the connection. This is most probably due to one or more application protocol errors.
1 Like

Thank you - around 3AM I’m rebooting my router each day - yet the connection always when tested it’s fine in the original Yeelights app. Also no other devices (non-Yeeligght yet Wifi devices) have this problem at my home yet Yeelights seems not to be able to reconnect.
Not sure what happened at 4:51 however. It looks to me it gave up and refuse to reconnect after while anymore.

The issue with your Yeelights being offline is not caused around 02:52 or 3AM. It just reconnects the lights around that time due to connection lost. The issue is around 04:51, the connetion is lost but upon trying to reconnect the host is unreachable (perhaps because of flaky Wifi adapter of Homey?!?). It then appearantly fails to reconnect or keep trying to reconnect.

You can not compare the Yeelight smartphone app with Homey. Homey needs to maintain a constant connecting where the Yeelight app will reconnect with the lights when started up.

Although I have a mechanism that reconnects when the connection is lost perhaps there are cases where this does not work and the light stays offline until powered down or the Yeelights app is rebooted. I’ll check it and see if I can improve it.

1 Like

Thank you for explanation. Actually I have another type of problematic devices - Chromecasts, those are loosing randomly connectivity even each hour (based on feedbacks on App Store, I’m not alone). But all the rest is fine (Tasmota Sonoff, Philips Wifi lights, TPLink power sockets and then yours Xiaomi supported - Roborocks, Phillips downlights) and none of them have those problems like Yeelights. I guess if there would be Wifi adapter problem, it would influence even those). BTW, would Xiaomi debug help ? If so : db3c53a8-7032-42fd-8a85-1299a29ba85a.

I can over night/day monitor my Homey connectivity, to see if Homey really loose connectivity.

v1.0.5 - 2019-12-16

Fixed a bug where certain ceiling lights (ceiling4 and ceiling10) did not get the right capabilities during pairing. Please re-pair if you are missing color settings.

1 Like

Apologies but where can I found I have these lights type (? I mean what is the factory name. In the https://developer.athom.com/tools/devices I don’t see any of that category, I was thinking about XML community backup search but I guess it’s little bit overkill.

The ceiling4 is the Yeelight Jiaoyue and the ceiling10 is the Yeelight Meteorite.

1 Like

I have an problem.

One yeelight color bulb was always working but now I see a red error and device is unreachable.
Get the message. There is something wrong, try it later again.

Did restart the app en reconnect but didn’t work

Did you assign a static IP for the light in your router? Perhaps it’s IP address has changed.

And if the light working in the Yeelight smartphone app? I noticed that sometimes the light becomes completely unreachable and needs a full reset (powering on and off five times in a row)

Yes has een static IP in the yeelight app the light works.
I trying to reset

After resetting the lamp it still not work ?

Did you re-pair it as well and if so, was it able to discover the light?

Yes repair it in Homey with the app and after reconnect I got the same error

Hmmm, do you know how to run the app from the command line? It would give me more information on why this is happening.

Any idea what has changed that might cause this. My app has not been updated recently so there must be some other factor that causes the issue.

More lights stop working.

If I reset and will add them it don’t work
The won’t come in the list.
Remote management is on.
Weird

Hi. I was trying to set up a toggle functionality for a key press: if all of the 6 Yeelights in the fixture are on, turn all 6 off, else turn them all on. The turn on part works always, but the turn off part fails because the lights are reported to Homey with the incorrect status. The Yeelight app consistently shows the correct status, but the lights statuses in Homey (under Devices) are seemingly random for different lights, despite being controllable from Homey.
Does the app poll/update the lights status regularly? Moreover, ii’s still random even if the lights are only controlled by Homey.
I mean, the on flow just turned them ON (visibly), but pressing Test in the flow editor to toggle them to off fails and shows one or several lights as still off in the And… condition.

Also, the relative dim function does not seem to work. If set to “-20%” for example, the lights turn off completely instead of dimming. Unless I misunderstood that feature’s functionality.