Give us the opportunity to come back in 1.4.2_0038 this should not be complicated. because for us it does not work as it should.
3 个赞
I have done some investigation and now I strongly believe that this is an issue with home assistant.
Using the yeelight python library in the doc I am able to discover all my yeelight bulbs running new firmware.
https://yeelight.readthedocs.io/en/stable/
But on the other hand Home assistant using same python library (I believe) is unable to discover the bulbs with new firmware.
There is no issue with Home Assistant! I don’t even using it!
Try to read Yeelight SDK carefully. Yes, you can discover lamps with SSDP using multicast UDP to 239.255.255.250:1982.
But!
On new firmware, there is not connect to lamp TCP port 55443! The lamp doesn’t answer to telnet <lamp_ip> 55443 after a few minutes after enabling Lan Control. So we can’t control our lamps manually.
So I ask you again, Yeelight developers, why such thing started to happen with new firmware and how to fix it?
I don’t know, if you whitelisted my Mi ID, but I don’t see beta firmware update. I’m using German server.
Yeelight team, do some more research, there is no issue with Home Assistant, etc, there is problem with your lamp firmware. I’m glad to see that you don’t have any issues in your test environment, but we DO have issues!
2 个赞
UPDATE:
After more than 24 hours of being connected to and usable from Home Assistant, 7 bulbs have now become UNAVAILABLE in HA. This therefore confirms that build 0054 does NOT fix the issue.
I strongly suggest cooperation between HA and Yeelight devs to get to the bottom of this and once and for all fix the problem. With the gravity of how this issue affects people’s lives the problem should be fixed very soon. Everyone should stop finger pointing and and should instead cooperate and work together to fix the problem. That includes devs from Home Assistant, Yeelight and everyone else affected by this.
Follow Up Comment: Can we please at least be given the option to downgrade to the last working (pre HomeKit) version? PLEASE???
2 个赞
+1 MI ID: 1779114679 (server US)
Hi,
Can you please whitelist by my MI ID: 6175796696 (Server Germany) ?
My 4 bulbs are updated to versio 2.0.6_0051 . They are all not discovered by HA.
Thank you
Using the python yeelight library (YeeLight library — python-yeelight 0.7.13 documentation) I have no issues discovering the devices and no issues in connecting the bulbs with new firmware using telnet and sending commands. This shows discovery function of the bulb works and bulbs are reponsding to commands using telnet. Need to raise with homeassistant as it seems hass is unable to handle the bulbs with multiple discovery protocols.
output of discovery and telnet below.(192.168.0.55 is old version 1 color bulb, rest are all v2 color bulbs with latest firmware)
output of discovery and telnet
user@server~$ python
Python 2.7.16 (default, Jul 9 2019, 16:43:02)
[GCC 8.3.0] on linux2
Type “help”, “copyright”, “credits” or “license” for more information.
from yeelight import discover_bulbs
bulbs = discover_bulbs()
for i in bulbs:
… print(i[“ip”], i[“port”])
…
(u’192.168.0.55’, 55443)
(u’192.168.0.218’, 55443)
(u’192.168.0.56’, 55443)
(u’192.168.0.244’, 55443)
(u’192.168.0.57’, 55443)
(u’192.168.0.58’, 55443)
(u’192.168.0.212’, 55443)
(u’192.168.0.215’, 55443)
user@server~$ telnet 192.168.0.55 55443
Trying 192.168.0.55…
Connected to 192.168.0.55.
Escape character is ‘^]’.
{“id”:1,“method”:“get_prop”,“params”:[“power”, “name”, “bright”]}
{“id”:1, “result”:[“on”,“”,“1”]}
^]q
telnet> q
Connection closed.
user@server~$ telnet 192.168.0.218 55443
Trying 192.168.0.218…
Connected to 192.168.0.218.
Escape character is ‘^]’.
{“id”:1,“method”:“get_prop”,“params”:[“power”, “name”, “bright”]}
{“id”:1,“result”:[“off”,“”,“100”]}
^Q]
{“id”:0, “error”:{“code”:-1, “message”:“invalid command”}}
^]q
telnet> q
Connection closed.
user@server~$ telnet 192.168.0.56 55443
Trying 192.168.0.56…
Connected to 192.168.0.56.
Escape character is ‘^]’.
{“id”:1,“method”:“get_prop”,“params”:[“power”, “name”, “bright”]}
{“id”:1,“result”:[“off”,“”,“100”]}
^]q
telnet> q
Connection closed.
user@server~$ telnet 192.168.0.244 55443
Trying 192.168.0.244…
Connected to 192.168.0.244.
Escape character is ‘^]’.
{“id”:1,“method”:“get_prop”,“params”:[“power”, “name”, “bright”]}
{“id”:1,“result”:[“off”,“”,“100”]}
^]q
telnet> q
Connection closed.
user@server~$ telnet 192.168.0.215 55443
Trying 192.168.0.215…
Connected to 192.168.0.215.
Escape character is ‘^]’.
{“id”:1,“method”:“get_prop”,“params”:[“power”, “name”, “bright”]}
{“id”:1,“result”:[“off”,“”,“21”]}
^]q
telnet> q
Connection closed.
@weiwei Can you please help get the attention of the HA devs so that they can have another look at the issue on their end? Looks like they’re not following or keeping track. Thanks.
For the connectivity issue, could anybody help do more testing by telnet 55443 or any other method to establish a TCP connection with the bulb. Then keep that connection and see if it will break at some point. At the same time, please monitor HA’s status to see if the connection breaks at the same time. If the connection does break, then please try to establish connection again manually and see if it works.
Again, without any further information, we could not fix the issue since we can’t reproduce the problem in our environment.
Downgrade firmware is dangerous and we don’t want to take this risk, so please give some patience and help us do some debugging instead of saying something that is meaningless (before this issue, we never know HA supports Yeelight and we didn’t even know who did the integration for Yeelight device in HA, so theoretically, we are doing something that is not promised).
What’s the error when you telnet to the bulb? It doesn’t work even after you power on/off your bulb?
I have added a bulb to the home assistant and also established a TCP connection using telnet to the same bulb, I will check the status in a few hours and report back. As it is just a basic telnet connection not sure how will i capture the time of telnet disconection if the telnet session terminates.
yeelight:
devices:
192.168.0.215:
name: Hallway
# telnet 192.168.0.215 55443
Trying 192.168.0.215...
Connected to 192.168.0.215.
Escape character is '^]'.
{"id":0, "error":{"code":-1, "message":"invalid command"}}
{"id":0, "error":{"code":-1, "message":"invalid command"}}
{"method":"props","params":{"power":"on"}}
{"method":"props","params":{"power":"off"}}
@weiwei Downgrading the firmware to a working version is no more dangerous than upgrading to a non-working one (as is the case for us) which renders our bulbs useless.
1 个赞
Dude calm down, I think the yeelight team knows better, what is dangerous with their devices and what’s not. They try to fix it, so don’t be rude and wait for a working version.
@weiwei Unfortunately I’m still not whitelisted for the update 
Could you please add me? Thanks!
Already added to whitelist, you should be able to see the testing firmware.
At least your bulb now can connect to the network and emit lights, you don’t want to brick it, right?
Downgrading a software/firmware is never safe, there is persistent data compatibility issue.
1 个赞
When you find HA shows disconnect, just type some character in telnet session and see if there is a response.
There is no error, connection just hangs:
telnet 192.168.1.41 55443
Trying 192.168.1.41…
And this is forever.
If I turn Lan Control for lamp off, then turn it back on, all works for about 3-5 minutes. Than no telnet connection again.
What is your xiaomi ID? When this happened, can you control the bulb from Yeelight app?
My MI ID: 1661243535, German server,
Yes, I always can control the bulbs from Yeelight app, IFTTT, Google Home, etc.