Home Assistant Community Store
GitHub API | ok
-- | --
GitHub Content | ok
GitHub Web | ok
GitHub API Calls Remaining | 4505
Installed Version | 1.34.0
Stage | running
Available Repositories | 1393
Downloaded Repositories | 27
Home Assistant Cloud
logged_in | false
-- | --
can_reach_cert_server | ok
can_reach_cloud_auth | ok
can_reach_cloud | ok
Home Assistant Supervisor
host_os | Home Assistant OS 11.5
-- | --
update_channel | stable
supervisor_version | supervisor-2024.01.1
agent_version | 1.6.0
docker_version | 24.0.7
disk_total | 109.3 GB
disk_used | 16.7 GB
healthy | true
supported | true
board | rpi4-64
supervisor_api | ok
version_api | ok
installed_addons | Grafana (9.1.3), Studio Code Server (5.15.0), MariaDB (2.6.1), TasmoAdmin (0.29.1), AdGuard Home (5.0.3), Advanced SSH & Web Terminal (17.1.0), ESPHome (2023.12.9), Frigate Proxy (1.4), Mosquitto broker (6.4.0), Matter Server (5.1.2), Duck DNS (1.15.0), NGINX Home Assistant SSL proxy (3.8.0), Glances (0.21.0)
Dashboards
dashboards | 2
-- | --
resources | 13
views | 15
mode | storage
Recorder
oldest_recorder_run | 10. Februar 2024 um 20:47
-- | --
current_recorder_run | 13. Februar 2024 um 11:21
estimated_db_size | 627.69 MiB
database_engine | mysql
database_version | 10.6.12
Checklist
[X] I have enabled debug logging for my installation.
[X] I have filled out the issue template to the best of my ability.
[X] This issue only contains 1 issue (if you have multiple issues, open one issue for each issue).
[X] This issue is not a duplicate issue of currently previous issues..
Describe the issue
upgrading to 1.75/1.7.6 causes integration not to start up on my SHC.
Reverting back to 1.7.4 is the temporary fix.
Reproduction steps
1.
2.
3.
...
Debug logs
Dieser Fehler wurde von einer benutzerdefinierten Integration verursacht
Logger: custom_components.livisi
Source: helpers/update_coordinator.py:313
Integration: Livisi Unofficial (documentation, issues)
First occurred: 11:21:33 (6 occurrences)
Last logged: 11:26:34
Unexpected error fetching Livisi devices data: LivisiConnection.__init__() takes 1 positional argument but 2 were given
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/helpers/update_coordinator.py", line 313, in _async_refresh
self.data = await self._async_update_data()
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/config/custom_components/livisi/coordinator.py", line 84, in _async_update_data
return await self.async_get_devices()
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/config/custom_components/livisi/coordinator.py", line 104, in async_get_devices
devices = await self.aiolivisi.async_get_devices()
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/config/custom_components/livisi/livisi_connector.py", line 207, in async_get_devices
raise LivisiConnection("Livisi controller is not active")
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
TypeError: LivisiConnection.__init__() takes 1 positional argument but 2 were given
System Health details
System Information
Home Assistant Community Store
GitHub API | ok -- | -- GitHub Content | ok GitHub Web | ok GitHub API Calls Remaining | 4505 Installed Version | 1.34.0 Stage | running Available Repositories | 1393 Downloaded Repositories | 27Home Assistant Cloud
logged_in | false -- | -- can_reach_cert_server | ok can_reach_cloud_auth | ok can_reach_cloud | okHome Assistant Supervisor
host_os | Home Assistant OS 11.5 -- | -- update_channel | stable supervisor_version | supervisor-2024.01.1 agent_version | 1.6.0 docker_version | 24.0.7 disk_total | 109.3 GB disk_used | 16.7 GB healthy | true supported | true board | rpi4-64 supervisor_api | ok version_api | ok installed_addons | Grafana (9.1.3), Studio Code Server (5.15.0), MariaDB (2.6.1), TasmoAdmin (0.29.1), AdGuard Home (5.0.3), Advanced SSH & Web Terminal (17.1.0), ESPHome (2023.12.9), Frigate Proxy (1.4), Mosquitto broker (6.4.0), Matter Server (5.1.2), Duck DNS (1.15.0), NGINX Home Assistant SSL proxy (3.8.0), Glances (0.21.0)Dashboards
dashboards | 2 -- | -- resources | 13 views | 15 mode | storageRecorder
oldest_recorder_run | 10. Februar 2024 um 20:47 -- | -- current_recorder_run | 13. Februar 2024 um 11:21 estimated_db_size | 627.69 MiB database_engine | mysql database_version | 10.6.12Checklist
Describe the issue
upgrading to 1.75/1.7.6 causes integration not to start up on my SHC. Reverting back to 1.7.4 is the temporary fix.
Reproduction steps
1. 2. 3. ...
Debug logs
Diagnostics dump
No response