Yeelight led ceiling light compatible with HA

Hardware
365

Okay got it, I glad to see the sensor of the nightlight, Im using it now at 0.92.1 build of HA.

366

i got an error when using yeelight.set_mode

Unable to set the power mode: {ā€˜codeā€™: -5000, ā€˜messageā€™: ā€˜general errorā€™}

whatā€™s the problem?
is simple as that:

  - service: yeelight.set_mode
    data:
      entity_id: light.room
      mode: color_flow
367

Do you use the most recent firmware?

368

indeed i am, just checked today

369

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?

370

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.

371

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!

372

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?

373

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

374

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.

375

I managed to install yeecli on my ubuntu, and I can toggle the light using this command:

yee --ip 192.168.2.199 toggle

376

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
377

Thanks. Hereā€™s the log https://paste.ubuntu.com/p/SnxmVYKKBj/

378

@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.

379

They do not show up in my entity list.

380

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

381

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
382

Change config to yeelight component

yeelight:
  devices:
    ...
383

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

384

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.