Continuous Yeelight Telnet connect failed

🛎️ Get Help
1

I've got an issue with my Yeelights currently. I am turning them on with the Yeelight app no issue, but with HE they are uncontrollable. In the logs I am getting these errors constantly:

dev:882019-08-03 02:06:35.120 pm errorTelnet connect failed, trying again in 120 seconds...
dev:832019-08-03 02:06:35.124 pm errorTelnet connect failed, trying again in 120 seconds...
dev:2902019-08-03 02:06:38.106 pm errorTelnet connect failed, trying again in 120 seconds...

Any ideas as this is a HE driver @mike.maxwell ?

2

Did you enable remote access for each bulb in the yeelight app?

3

all 12 bulbs have had LAN control on and been working in HE no issue.
all 12 bulbs can currently be controlled with the Yeelight app - no issue. Some of them (roughly half) can't be controlled by HE.

4

The pair in the living room - same bulbs, both been working flawlessly until my hub lockup today
hub lockups

living room A - heartbeat every 2 hrs no issue
dev:432019-08-03 02:16:38.118 pm debugheartbeat- message sent...
dev:432019-08-03 02:16:38.114 pm debugts- ct:1564805798112, lhb: 1564805678127, age: 119985
dev:432019-08-03 02:16:38.112 pm debuggetReTry- reTryCount:0
dev:432019-08-03 02:14:38.106 pm debugheartbeat- message sent...
dev:432019-08-03 02:14:38.105 pm debugts- ct:1564805678094, lhb: 1564805558118, age: 119976
dev:432019-08-03 02:14:38.098 pm debuggetReTry- reTryCount:0

living room B - is up to 304 retrys to connect.
dev:442019-08-03 02:18:41.126 pm errorTelnet connect failed, trying again in 120 seconds...
dev:442019-08-03 02:18:41.125 pm debuggetReTry- reTryCount:304
dev:442019-08-03 02:18:41.123 pm debuginitialize error: No route to host (Host unreachable)
dev:442019-08-03 02:18:38.122 pm debuggetReTry- reTryCount:303
dev:442019-08-03 02:18:38.120 pm debugts- ct:1564805918116, lhb: 1564787318102, age: 18600014
dev:442019-08-03 02:18:38.119 pm debuggetReTry- reTryCount:302
dev:442019-08-03 02:16:41.138 pm errorTelnet connect failed, trying again in 120 seconds...
dev:442019-08-03 02:16:41.135 pm debuggetReTry- reTryCount:302
dev:442019-08-03 02:16:41.133 pm debuginitialize error: No route to host (Host unreachable)
dev:442019-08-03 02:16:38.128 pm debuggetReTry- reTryCount:301
dev:442019-08-03 02:16:38.127 pm debugts- ct:1564805798125, lhb: 1564787318102, age: 18480023
dev:442019-08-03 02:16:38.125 pm debuggetReTry- reTryCount:300

5

Power cycled the bulb, no change.
Power cycled the wifi router, no change.

A different bulb though has come back by itself, any thoughts how to get them all back @mike.maxwell

dev:882019-08-03 06:50:32.067 pm debugts- ct:1564822232064, lhb: 1564822112091, age: 119973
dev:882019-08-03 06:50:32.064 pm debuggetReTry- reTryCount:0
dev:882019-08-03 06:48:32.075 pm debugheartbeat- message sent...
dev:882019-08-03 06:48:32.072 pm debugts- ct:1564822112071, lhb: 1564822091895, age: 20176
dev:882019-08-03 06:48:32.069 pm debuggetReTry- reTryCount:0
dev:882019-08-03 06:48:12.065 pm infoTelnet connection to Yeelight established
dev:882019-08-03 06:46:35.047 pm errorTelnet connect failed, trying again in 120 seconds...
dev:882019-08-03 06:46:35.045 pm debuggetReTry- reTryCount:589
dev:882019-08-03 06:46:35.043 pm debuginitialize error: No route to host (Host unreachable)

6

Haven't changed anything and a large group of them all just reconnected

dev:472019-08-03 06:48:12.087 pm infoTelnet connection to Yeelight established
dev:882019-08-03 06:48:12.065 pm infoTelnet connection to Yeelight established
dev:832019-08-03 06:48:12.038 pm infoTelnet connection to Yeelight established
dev:462019-08-03 06:48:11.996 pm infoTelnet connection to Yeelight established
dev:442019-08-03 06:48:11.963 pm infoTelnet connection to Yeelight established

7

and they have started dropping again..

dev:462019-08-03 07:10:38.150 pm errorTelnet connection dropped...
dev:472019-08-03 07:10:38.188 pm errorTelnet connection dropped...

8

and back again.. Please help @mike.maxwell

dev:472019-08-03 07:12:38.163 pm debugheartbeat- message sent...

dev:472019-08-03 07:12:38.162 pm debugts- ct:1564823558161, lhb: 1564823439228, age: 118933

dev:472019-08-03 07:12:38.160 pm debuggetReTry- reTryCount:0

*blank stare at screen...

    [dev:41](http://192.168.1.140/logs#dev41)2019-08-03 07:14:38.039 pm [debug](http://192.168.1.140/device/edit/41)getReTry- reTryCount:1

    [dev:41](http://192.168.1.140/logs#dev41)2019-08-03 07:14:38.038 pm [debug](http://192.168.1.140/device/edit/41)ts- ct:1564823678036, lhb: 1564823331896, age: 346140

    [dev:41](http://192.168.1.140/logs#dev41)2019-08-03 07:14:38.037 pm [debug](http://192.168.1.140/device/edit/41)getReTry- reTryCount:0

    [dev:41](http://192.168.1.140/logs#dev41)2019-08-03 07:14:41.046 pm [error](http://192.168.1.140/device/edit/41)Telnet connect failed, trying again in 120 seconds...

    [dev:41](http://192.168.1.140/logs#dev41)2019-08-03 07:14:41.045 pm [debug](http://192.168.1.140/device/edit/41)getReTry- reTryCount:2

    [dev:41](http://192.168.1.140/logs#dev41)2019-08-03 07:14:41.043 pm [debug](http://192.168.1.140/device/edit/41)initialize error: No route to host (Host unreachable)
9

an explanation, but probably not an answer