raulgbcr/lednetwf_ble

Error adding entities for domain light with platform lednetwf_ble

Closed this issue · 3 comments

Thanks for this Integration, i've been sitting on a useless ring led for quite some time! This integration revived it - it worked right out the gate. Unfortunately it stopped doing that at some point. Not sure when and why. At the moment i can add the device via bluetooth mac and it does blink during setup. But afterwards it says no devices and no entities under the chosen name.

I assume i messed something by deleting and readding the device. Any suggestions what to do?

Log says:

Logger: homeassistant.components.light
Source: helpers/entity_platform.py:619
Integration: Licht ([documentation](https://www.home-assistant.io/integrations/light), [issues](https://github.com/home-assistant/core/issues?q=is%3Aissue+is%3Aopen+label%3A%22integration%3A+light%22))
First occurred: 15:28:14 (2 occurrences)
Last logged: 15:28:14

    Error adding entities for domain light with platform lednetwf_ble
    Error while setting up lednetwf_ble platform for light

Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/helpers/entity_platform.py", line 510, in async_add_entities
    await asyncio.gather(*tasks)
  File "/usr/src/homeassistant/homeassistant/helpers/entity_platform.py", line 619, in _async_add_entity
    device = dev_reg.async_get(self.hass).async_get_or_create(
             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
TypeError: homeassistant.helpers.device_registry.DeviceRegistry.async_get_or_create() got multiple values for keyword argument 'config_entry_id'

Hmmm, I have no idea what could be causing that. I would try deleting the integration completely including files and restarting HA, then try to reinstall the integration and reboot HA again to see if it happens again. Seems to me something related to HA in itself got hang up.

About the stopping to work, if it happens to you again don't remove the device so we can take a look too.

I have the same issue.
IMG_2670
IMG_2671
IMG_2672
IMG_2673

Should be fixed on new version, thanks.