indeed i am, just checked today
I use the custom component since April and I like it, but there are many “Unable to update device” warning from HA 0.96. Is the official version handling the nightlights now?
By handling nightlighs, you mean 2 light entities per light ? Its not yet supported in official versions. I will work on it when I have some time but it will be few weeks for sure.
Yes, I mean 2 light entities per light. I guess it is very useful either at automations and simply switching. Thank you for your efforts!
As of a few days ago I’ve “lost” 3 of my lights in HA. One is the strip and the other two are bulbs, the white ones (YLDP06YL). I think there’s something wrong with the firmware, or integration, because it happened after I’ve upgraded my yeelights to fw 2.0.6.
I still have two other bulbs, older version (gray ones), that still work.
I’ve tried resetting the bulbs, reconnecting the to the gateways, reenable the LAN control, nothing helped so far.
Is anyone else experiencing problems with the yeelight bulbs?
It’s possible the firmware update broke the protocol / has changed the format of the messages. In this case you should file an issue here: https://gitlab.com/stavros/python-yeelight/issues
I would, but my python knowledge is less then 0. So I can’t offer logs, debugging, etc.
If anyone is willing to help with this, I really appreciate it.
I managed to install yeecli on my ubuntu, and I can toggle the light using this command:
yee --ip 192.168.2.199 toggle
Please enable the debug logging of the component and underlying library by:
logger:
default: warn
logs:
yeelight: debug
homeassistant.components.yeelight: debug
homeassistant.components.yeelight.light: debug
And provide some logs (HA startup + toggle the light if possible).
1 Like
@joem From log it looks like you are using autodiscovery for yeelight ? I think lights could change its entity id, because of removing some old legacy code in one of the refactor. From logs it looks like they are being recognized and queried for properties ok. Take a look at entities in states view, to see if they are there, but with different entity_id.
They do not show up in my entity list.
Try to add them by ip in the config. Looks like autodiscovery only sees 2 bulbs 192.168.2.14 and 192.168.2.15
I have them by IP in my config:
- platform: yeelight
devices:
192.168.2.13:
name: Kitchen Door
transition: 1000
192.168.2.12:
name: Kitchen Piano
transition: 1000
192.168.2.15:
name: Hallway back
transition: 1000
192.168.2.14:
name: Hallway front
transition: 1000
192.168.2.199:
name: Yee strip
transition: 1000
Change config to yeelight component
yeelight:
devices:
...
I’ve changed it. My two older bulbs are the only ones that are recognized (IPs ending with 14 and 15).
12, 13 and 199 are still not showing up.
Log here https://paste.ubuntu.com/p/sXk6H9tWqh/
I think there’s something to do with this: type=BulbType.Unknown, since 14 and 15 are recognized as type=BulbType.Color
They are unknown because devices doesn’t respond to get_prop request. Looks like something is wrong with devices, or network firewall / routing ?
2019-08-22 01:21:45 DEBUG (SyncWorker_12) [yeelight.main] Bulb<192.168.2.13:55443, type=BulbType.Unknown> > {'id': 0, 'method': 'get_prop', 'params': ['power', 'main_power', 'bright', 'ct', 'rgb', 'hue', 'sat', 'color_mode', 'bg_power', 'bg_lmode', 'bg_flowing', 'bg_ct', 'bg_bright', 'bg_hue', 'bg_sat', 'bg_rgb', 'nl_br', 'active_mode']}
2019-08-22 01:21:45 DEBUG (SyncWorker_10) [yeelight.main] Bulb<192.168.2.12:55443, type=BulbType.Unknown> > {'id': 0, 'method': 'get_prop', 'params': ['power', 'main_power', 'bright', 'ct', 'rgb', 'hue', 'sat', 'color_mode', 'bg_power', 'bg_lmode', 'bg_flowing', 'bg_ct', 'bg_bright', 'bg_hue', 'bg_sat', 'bg_rgb', 'nl_br', 'active_mode']}
2019-08-22 01:21:45 DEBUG (SyncWorker_18) [yeelight.main] Bulb<192.168.2.15:55443, type=BulbType.Unknown> > {'id': 0, 'method': 'get_prop', 'params': ['power', 'main_power', 'bright', 'ct', 'rgb', 'hue', 'sat', 'color_mode', 'bg_power', 'bg_lmode', 'bg_flowing', 'bg_ct', 'bg_bright', 'bg_hue', 'bg_sat', 'bg_rgb', 'nl_br', 'active_mode']}
2019-08-22 01:21:45 DEBUG (SyncWorker_19) [yeelight.main] Bulb<192.168.2.14:55443, type=BulbType.Unknown> > {'id': 0, 'method': 'get_prop', 'params': ['power', 'main_power', 'bright', 'ct', 'rgb', 'hue', 'sat', 'color_mode', 'bg_power', 'bg_lmode', 'bg_flowing', 'bg_ct', 'bg_bright', 'bg_hue', 'bg_sat', 'bg_rgb', 'nl_br', 'active_mode']}
2019-08-22 01:21:45 DEBUG (SyncWorker_14) [yeelight.main] Bulb<192.168.2.199:55443, type=BulbType.Unknown> > {'id': 0, 'method': 'get_prop', 'params': ['power', 'main_power', 'bright', 'ct', 'rgb', 'hue', 'sat', 'color_mode', 'bg_power', 'bg_lmode', 'bg_flowing', 'bg_ct', 'bg_bright', 'bg_hue', 'bg_sat', 'bg_rgb', 'nl_br', 'active_mode']}
2019-08-22 01:21:45 DEBUG (SyncWorker_19) [yeelight.main] Bulb<192.168.2.14:55443, type=BulbType.Unknown> < {'id': 0, 'result': ['off', '', '58', '2028', '16737024', '23', '100', '1', '', '', '', '', '', '', '', '', '', '']}
2019-08-22 01:21:45 DEBUG (SyncWorker_18) [yeelight.main] Bulb<192.168.2.15:55443, type=BulbType.Unknown> < {'id': 0, 'result': ['off', '', '58', '4000', '16737024', '23', '100', '1', '', '', '', '', '', '', '', '', '', '']}
All devices are being queried for params, but only 2 responds.
All the bulbs are on the same wireless network, and I didn’t change anything on my router lately.
The only thing that changed is the firmware of the bulbs/strip. Upgraded from 1.x to 2.0.6.
14 and 15 are older bulbs, and didn’t receive (yet?) the fw upgrade.
I wonder if it could be an issue with the python-yeelight, like @syssi mentioned in the post #373
It might be possible, but changning get_prop query from yeelight API seems a bit unexpected. Maybe try to check if LAN mode is still on, after FW update ?
I’ve reset the bulbs multiple times, and toggled ON/OFF/ON the LAN mode.
python-yeelight can’t control nor see the status of the bulbs.
hassio@hassiodev:~/.local/bin$ ./yee --ip 192.168.2.12 status
Bulb parameters:
Traceback (most recent call last):
File "./yee", line 11, in <module>
sys.exit(cli())
File "/home/hassio/.local/lib/python2.7/site-packages/click/core.py", line 764, in __call__
return self.main(*args, **kwargs)
File "/home/hassio/.local/lib/python2.7/site-packages/click/core.py", line 717, in main
rv = self.invoke(ctx)
File "/home/hassio/.local/lib/python2.7/site-packages/click/core.py", line 1137, in invoke
return _process_result(sub_ctx.command.invoke(sub_ctx))
File "/home/hassio/.local/lib/python2.7/site-packages/click/core.py", line 956, in invoke
return ctx.invoke(self.callback, **ctx.params)
File "/home/hassio/.local/lib/python2.7/site-packages/click/core.py", line 555, in invoke
return callback(*args, **kwargs)
File "/home/hassio/.local/lib/python2.7/site-packages/yeecli/cli.py", line 301, in status
for key, value in bulb.get_properties().items():
File "/home/hassio/.local/lib/python2.7/site-packages/yeelight/main.py", line 359, in get_properties
response = self.send_command("get_prop", requested_properties)
File "/home/hassio/.local/lib/python2.7/site-packages/yeelight/main.py", line 399, in send_command
raise_from(BulbException("A socket error occurred when sending the command."), ex)
File "/home/hassio/.local/lib/python2.7/site-packages/future/utils/__init__.py", line 456, in raise_from
raise e
yeelight.main.BulbException: A socket error occurred when sending the command.
It seems like it doesn’t recognize LAN mode anymore.