I was only mentioning the error encountered which prevented me from telnet-ing to a bulb.
I am not sure how / why port 23 is relevant (I did / do not expect it to be), but a quick google search showed many results of the same error encountered by others (doing telnet). I didn’t bother investigating the error further.
Any device can have any number of ports ‘open’. Many have reserved port numbers and specific protocols (rules of how to talk to them). 23 is telnet, 80 is http, 443 is https, and many many more.
Yeelight uses port 55443 for their controls. While the Yeelight controls are not telnet protocol, the telnet is a tool available to most people and allows you to connect to 55443 and even send/receive commands with a Yeelight bulb providing the the connection port of 55443 is used.
The error message says it failed on port 23. We know for sure that a Yeelight bulb should not answer on port 23 so that message is completely normal. Since 23 is the default telnet port one would suspect that the telnet command did not see or understand that it should have used 55443.
Yeah, it requires very specific input. If it doesn’t understand it’s unlikely to respond at all. Copy and paste this into your telnet session and the light should toggle (turn on or off depending on if its on already) and you should see a response.
Paste this:
{“id”:1,“method”:“toggle”,“params”:}
Here’s an example from here (I did not include the telnet command because I use a different command on Linux and it would confuse)
Connection to 10.1.0.201 55443 port [tcp/*] succeeded!
{“id”:1,“method”:“toggle”,“params”:}
{“id”:1,“result”:[“ok”]}
{“method”:“props”,“params”:{“power”:“off”}}
How unclear of me. The only input I gave was the one bolded line. The rest came back from the bulb.
Connection to 10.1.0.201 55443 port [tcp/*] succeeded! {“id”:1,“method”:“toggle”,“params”:[]}
{“id”:1,“result”:[“ok”]}
{“method”:“props”,“params”:{“power”:“off”}}
Yep, that’s exactly the error I had seen. Double check that you are on firmware version 2.0.6_0062 just to be sure.
After that perhaps Weiwei or someone from Yeelight might want us to try something or, at least, note this happened to yours. Mine are still fine but time ticks on.
You can do that. Be aware that there is some limit to how many commands you can issue per minute and I think there can only be 4 simultaneous connections but don’t trust my numbers, just know that it will ignore things beyond a certain threshold.
Must importantly we want Yeelight to know it happened. I wish some more folks would check in with their results.
One other thought. After I upgraded I did make a point of power cycling my bulbs once. No one told us to, I just did. Just to mention a possible factor. All still good here.
Updated my 8 bulbs to 0062 about 36 hours ago, no disconnections so far. I enabled notifications in Home Assistant to send me a Telegram message as soon as a bulb goes offline/unavailable, so will post an update here again if that happens!