sander1988 / Indego

Home Assistant Custom Component for Bosch Indego Lawn Mower
Apache License 2.0
95 stars 29 forks source link

Indego fails after update to HA 2023.08 #193

Closed 35aportal closed 1 year ago

35aportal commented 1 year ago

My Indego integration failed after updating HA, so I deleted the integration and reinstalled. After a few hiccups (I'd removed the helper from Chrome), the integration installed without errors, but has "No devices or entities".

My log file shows...

Logger: homeassistant.components.sensor Source: helpers/entity_platform.py:619 Integration: Sensor (documentation, issues) First occurred: 21:50:28 (4 occurrences) Last logged: 21:52:32

Error adding entities for domain sensor with platform indego Error while setting up indego platform for sensor 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: DeviceRegistry.async_get_or_create() got an unexpected keyword argument 'serial_number'

Let me know if anything else is needed to help debug this. Thanks in advance for your help.

Helskov commented 1 year ago

As a temporary solution comment out line 393 (Serial_number) in Custom_components>Indego>init.Py Reboot HA and it should work again.

    device_info = DeviceInfo(
        identifiers={(DOMAIN, self._serial)},
        #serial_number=self._serial,
        manufacturer="Bosch",
        name=self._mower_name,
        model=generic_data.bareToolnumber if generic_data else None,
        sw_version=generic_data.alm_firmware_version if generic_data else None,

Saw a similar problem with EUFY with similar workaround. https://github.com/fuatakgun/eufy_security/issues/855

35aportal commented 1 year ago

Thanks for the advice - this worked.

I'm working again, but I'll leave the issue open as a reminder to get the fix rolled into the next release.

dvdmaz commented 1 year ago

Hello, I have the same problem, the workaround also worked for me. Thanks!

antoinevandenhurk commented 1 year ago

It worked for me too!

RockFlare commented 1 year ago

Confirming that this worked for me too.

jm-73 commented 1 year ago

This fix is included in 5.3.0 (Beta)