Unable to start Livisi intetration

[bbr111]

The problem

After entering IP and password the Integration is not starting up. Error see log.

What version of Home Assistant Core has the issue?

2023.4.1

What was the last working version of Home Assistant Core?

No response

What type of installation are you running?

Home Assistant OS

Integration causing the issue

Livisi

Link to integration documentation on our website

No response

Diagnostics information

No response

Example YAML snippet

No response

Anything in the logs that might be useful for us?

2023-04-08 11:37:28.448 ERROR (MainThread) [homeassistant.components.livisi] Unexpected error fetching Livisi devices data: 'type'
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/helpers/update_coordinator.py", line 250, in _async_refresh
self.data = await self._async_update_data()
File "/usr/src/homeassistant/homeassistant/components/livisi/coordinator.py", line 58, in _async_update_data
return await self.async_get_devices()
File "/usr/src/homeassistant/homeassistant/components/livisi/coordinator.py", line 92, in async_get_devices
return await self.aiolivisi.async_get_devices()
File "/usr/local/lib/python3.10/site-packages/aiolivisi/aiolivisi.py", line 157, in async_get_devices
capability_map[device_id][capability["type"]] = (
KeyError: 'type'
2023-04-08 11:37:28.452 ERROR (MainThread) [homeassistant.config_entries] Error setting up entry SHC Classic for livisi
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/config_entries.py", line 383, in async_setup
result = await component.async_setup_entry(hass, self)
File "/usr/src/homeassistant/homeassistant/components/livisi/__init__.py", line 43, in async_setup_entry
await coordinator.async_config_entry_first_refresh()
File "/usr/src/homeassistant/homeassistant/helpers/update_coordinator.py", line 215, in async_config_entry_first_refresh
await self._async_refresh(
File "/usr/src/homeassistant/homeassistant/helpers/update_coordinator.py", line 341, in _async_refresh
self.async_update_listeners()
File "/usr/src/homeassistant/homeassistant/helpers/update_coordinator.py", line 142, in async_update_listeners
update_callback()
File "/usr/src/homeassistant/homeassistant/components/livisi/binary_sensor.py", line 34, in handle_coordinator_update
for device in shc_devices:
TypeError: 'NoneType' object is not iterable
2023-04-08 11:38:02.644 ERROR (MainThread) [homeassistant.config_entries] Error setting up entry SHC Classic for binary_sensor
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/config_entries.py", line 383, in async_setup
result = await component.async_setup_entry(hass, self)
File "/usr/src/homeassistant/homeassistant/components/binary_sensor/__init__.py", line 169, in async_setup_entry
return await component.async_setup_entry(entry)
File "/usr/src/homeassistant/homeassistant/helpers/entity_component.py", line 169, in async_setup_entry
raise ValueError("Config entry has already been setup!")
ValueError: Config entry has already been setup!
2023-04-08 11:38:02.652 ERROR (MainThread) [homeassistant.config_entries] Error setting up entry SHC Classic for climate
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/config_entries.py", line 383, in async_setup
result = await component.async_setup_entry(hass, self)
File "/usr/src/homeassistant/homeassistant/components/climate/__init__.py", line 195, in async_setup_entry
return await component.async_setup_entry(entry)
File "/usr/src/homeassistant/homeassistant/helpers/entity_component.py", line 169, in async_setup_entry
raise ValueError("Config entry has already been setup!")
ValueError: Config entry has already been setup!
2023-04-08 11:38:02.655 ERROR (MainThread) [homeassistant.config_entries] Error setting up entry SHC Classic for switch
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/config_entries.py", line 383, in async_setup
result = await component.async_setup_entry(hass, self)
File "/usr/src/homeassistant/homeassistant/components/switch/__init__.py", line 83, in async_setup_entry
return await component.async_setup_entry(entry)
File "/usr/src/homeassistant/homeassistant/helpers/entity_component.py", line 169, in async_setup_entry
raise ValueError("Config entry has already been setup!")
ValueError: Config entry has already been setup!
2023-04-08 11:38:07.932 ERROR (MainThread) [homeassistant.components.livisi] Unexpected error fetching Livisi devices data: 'type'
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/helpers/update_coordinator.py", line 250, in _async_refresh
self.data = await self._async_update_data()
File "/usr/src/homeassistant/homeassistant/components/livisi/coordinator.py", line 58, in _async_update_data
return await self.async_get_devices()
File "/usr/src/homeassistant/homeassistant/components/livisi/coordinator.py", line 92, in async_get_devices
return await self.aiolivisi.async_get_devices()
File "/usr/local/lib/python3.10/site-packages/aiolivisi/aiolivisi.py", line 157, in async_get_devices
capability_map[device_id][capability["type"]] = (
KeyError: 'type'

Additional information

No response

[home-assistant[bot]]

Hey there @stefaniacoblivisi, @planbnet, mind taking a look at this issue as it has been labeled with an integration (livisi) you are listed as a code owner for? Thanks!

Code owner commands

Code owners of livisi can trigger bot actions by commenting:

• @home-assistant close Closes the issue.
• @home-assistant rename Awesome new title Renames the issue.
• @home-assistant reopen Reopen the issue.
• @home-assistant unassign livisi Removes the current integration label and assignees on the issue, add the integration domain after the command.

_{^{(message by CodeOwnersMention)}}

---

livisi documentation livisi source _{^{(message by IssueLinks)}}

[bbr111]

@planbnet how can i test it in my local system using hass os in proxmox vm?

[issue-triage-workflows[bot]]

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍 This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.

[bbr111]

@planbnet @StefanIacobLivisi Any update here?

[planbnet]

I don’t know - @StefanIacobLivisi is maintaining the aiolisi lib (which contains the root cause of this bug and a pr from me to fix it) but he’s unresponsive and the lib seems abandoned.

[Gonzo1973]

Hi! Thanks for posting current status. I've the same problem and was hoping every month the solution might have been incorporated. So not incorporated yet.

[Alex-Home-Git]

hi all unfortunately I can the LIVISI Smart Home system nihct in my HA intigriren I get the following error displayed can someone help me?

Thanks!

What version of Home Assistant Core has the issue? Core 2023.11.0 Supervisor 2023.10.1 Operating System 11.1 Frontend 20231030.1

Error setting up entry SHC Classic for binary_sensor Logger: homeassistant.config_entries Source: config_entries.py:402 First occurred: 19:27:59 (6 occurrences) Last logged: 19:28:10

Error setting up entry SHC Classic for binary_sensor Error setting up entry SHC Classic for climate Error setting up entry SHC Classic for switch Traceback (most recent call last): File "/usr/src/homeassistant/homeassistant/config_entries.py", line 402, in async_setup result = await component.async_setup_entry(hass, self) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/src/homeassistant/homeassistant/components/binary_sensor/init.py", line 169, in async_setup_entry return await component.async_setup_entry(entry) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/src/homeassistant/homeassistant/helpers/entity_component.py", line 187, in async_setup_entry raise ValueError("Config entry has already been setup!") ValueError: Config entry has already been setup!

Unexpected error fetching Livisi devices data: 'type' Logger: homeassistant.components.livisi Source: helpers/update_coordinator.py:290 Integration: LIVISI Smart Home (documentation, issues) First occurred: 19:24:15 (6 occurrences) Last logged: 19:28:15

Unexpected error fetching Livisi devices data: 'type' Traceback (most recent call last): File "/usr/src/homeassistant/homeassistant/helpers/update_coordinator.py", line 290, in _async_refresh self.data = await self._async_update_data() ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/src/homeassistant/homeassistant/components/livisi/coordinator.py", line 58, in _async_update_data return await self.async_get_devices() ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/src/homeassistant/homeassistant/components/livisi/coordinator.py", line 92, in async_get_devices return await self.aiolivisi.async_get_devices() ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/local/lib/python3.11/site-packages/aiolivisi/aiolivisi.py", line 157, in async_get_devices capability_map[device_id][capability["type"]] = ( ~~~~~~~~~~^^^^^^^^ KeyError: 'type'

[lemmilemkoe]

Gibt es hier schon eine Lösung, da ich vor der selben Herausforderung stehe

[planbnet]

As the aiolivisi lib is unmaintained and this integration depends on it, there won’t be any fixes without a major rewrite I guess. I can just guide you to my unofficial integration which I think is stable now and integrates all the other device types (besides not having all the bugs of the official integration). See https://github.com/planbnet/livisi_unofficial

[issue-triage-workflows[bot]]

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍 This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.