search

peribeir / homeassistant-rademacher

This custom integration provides access to Rademacher Devices connected to a HomePilot (or Start2Smart) bridge.
GNU General Public License v3.0
58 stars 11 forks source link

Upgrade to 1.3.1 from 1.3.0 fails #9

Closed hklages closed 2 years ago

hklages commented 2 years ago

Hi thanks for this great integration. It replaces a lot of my "REST API calls" /sensor templates.

The update to 1.3.0 did work fine (I removed the old integration and folder manually), then used HACS to install 1.3.0

Today I tried to update via HACS from 1.3.0 to 1.3.1 but the update failed an all my covers were unavailable. Unfortunately I can not provide you with any log messages. Sorry for that. I had to restore a full backup because I accidentally deleted important HA files as I tried to get the covers work again. :-(

So this is just a "heads up" message. Would be interesting whether others also had the issues.

Installation with newest software:
HomePilot 2

peribeir commented 2 years ago

Hi,

I'm sorry to hear that it failed :(

I'll try to reproduce the issue (downgrade then upgrade) to see if it happens to me too.

One question, after the upgrade, did you try to remove the integration and then add again?

kauthmbt commented 2 years ago

@peribeir Having the same problem too. According to the logs it seems to be related to the following line added to several files: devices: bool = entry[2][CONF_DEVICES]

2022-01-18 10:26:43 ERROR (MainThread) [homeassistant.components.cover] Error while setting up rademacher platform for cover
Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/helpers/entity_platform.py", line 249, in _async_setup_platform
    await asyncio.shield(task)
  File "/config/custom_components/rademacher/cover.py", line 35, in async_setup_entry
    devices: bool = entry[2][CONF_DEVICES]
KeyError: 'devices'

Also effecting _button, switch, binarysensor, sensor components

peribeir commented 2 years ago

I think I found the problem. Indeed it is related to a new variable that I added to the setup forms.

And if the integration is already deployed it will be empty. I'll do the correction during the next hours.