planbnet/livisi_unofficial

Exception in update_reachability when dispatching

Closed this issue · 1 comments

System Health details

System Information

version core-2024.2.5
installation_type Home Assistant OS
dev false
hassio true
docker true
user root
virtualenv false
python_version 3.12.1
os_name Linux
os_version 6.6.16-haos
arch x86_64
timezone Europe/Berlin
config_dir /config
Home Assistant Community Store
GitHub API ok
GitHub Content ok
GitHub Web ok
GitHub API Calls Remaining 5000
Installed Version 1.34.0
Stage running
Available Repositories 1400
Downloaded Repositories 6
Home Assistant Cloud
logged_in false
can_reach_cert_server ok
can_reach_cloud_auth ok
can_reach_cloud ok
Easee EV Charger
component_version 0.9.58
reach_easee_cloud ok
connected2stream true
Home Assistant Supervisor
host_os Home Assistant OS 12.0
update_channel stable
supervisor_version supervisor-2024.04.0
agent_version 1.6.0
docker_version 24.0.7
disk_total 234.0 GB
disk_used 8.6 GB
healthy true
supported true
board generic-x86-64
supervisor_api ok
version_api ok
installed_addons Terminal & SSH (9.13.0), Studio Code Server (5.15.0), Node-RED (17.0.12), evcc (0.125.0)
Dashboards
dashboards 3
resources 4
views 6
mode storage
Recorder
oldest_recorder_run 17. April 2024 um 10:47
current_recorder_run 17. April 2024 um 12:47
estimated_db_size 206.23 MiB
database_engine sqlite
database_version 3.44.2

Checklist

  • I have enabled debug logging for my installation.
  • I have filled out the issue template to the best of my ability.
  • This issue only contains 1 issue (if you have multiple issues, open one issue for each issue).
  • This issue is not a duplicate issue of currently previous issues..

Describe the issue

I upgraded Livisi to the latest version 1.10.0 on April 17, 2024. Since yesterday, the Livisi integration has stopped working twice, almost at the same time of day, with two error messages. I cannot find a corresponding trigger and the message board in the Livisi SHC box shows nothing.
The integration does not recover, so I have to reload it. After reloading, everything works fine.

1st error message:
Error fetching Livisi devices data: Failed to get livisi devices from controller

2nd:
Exception in update_reachability when dispatching 'livisi_reachability_change_23b5b73c04a942328f095e6357196e18'

The last error message says 128 occurrences!!!
This error generates a very large log entry, which I write to an additional text file.
Before reload I have enabled the debug log for Livisi and hope it doesn't blow up my system.
Next time the error occurs, I'll have to load an old version from backup.

Error 202404.txt

Reproduction steps

  1. Reload Livisi integration and wait.

...

Debug logs

See uploaded file

Diagnostics dump

See uploaded file

I close the issue, as I found the cause. It was a failure in the DHCP-System.