planbnet/livisi_unofficial

Frequent restart required

Opened this issue · 16 comments

System Health details

System Information

version core-2024.6.3
installation_type Home Assistant OS
dev false
hassio true
docker true
user root
virtualenv false
python_version 3.12.2
os_name Linux
os_version 6.6.28-haos-raspi
arch aarch64
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 1393
Downloaded Repositories 19
HACS Data ok
Home Assistant Cloud
logged_in true
subscription_expiration 4. April 2025 um 02:00
relayer_connected true
relayer_region eu-central-1
remote_enabled true
remote_connected true
alexa_enabled true
google_enabled false
remote_server eu-central-1-0.ui.nabu.casa
certificate_status ready
instance_id c926ddd70c444db29d2122b4feed732f
can_reach_cert_server ok
can_reach_cloud_auth ok
can_reach_cloud ok
Home Assistant Supervisor
host_os Home Assistant OS 12.3
update_channel stable
supervisor_version supervisor-2024.06.0
agent_version 1.6.0
docker_version 25.0.5
disk_total 57.8 GB
disk_used 28.3 GB
healthy true
supported true
host_connectivity true
supervisor_connectivity true
ntp_synchronized true
virtualization
board rpi4-64
supervisor_api ok
version_api ok
installed_addons Studio Code Server (5.15.0), File editor (5.8.0), Terminal & SSH (9.14.0), Mosquitto broker (6.4.1)
Dashboards
dashboards 15
resources 5
views 14
mode storage
Recorder
oldest_recorder_run 13. Juni 2024 um 22:15
current_recorder_run 16. Juni 2024 um 13:49
estimated_db_size 1602.60 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

Since about two weeks I need to regularly reload the integration as devices/ entities are not reachable in Home Assistant anymore. Usually a daily reload is required. After reloading the integration all devices/ entities are available again.
Other users at Facebook report similar issues.

Reproduction steps

The entities automatically lose connection/ are not reachable in Home Assistant anymore usually daily.

Debug logs

Debug logging has just been activated

Diagnostics dump

No response

Ohne weitere Infos oder Debug logs kann ich da leider nichts zu sagen... Ich hab keinerlei Probleme und ich wüsste auch nicht, was sich in den letzten zwei Wochen verändert haben sollte.

Auf der Seite der Integration erscheint dann doch der Button "Debug Logs laden" oder so.. Wichtig ist nur, dass der Fehler auch in den Logs enthalten ist, er muss also aufgetreten sein.

Ok, anbei der Debug Log. Der Fehler sollte in dem Zeitpunkt aufgetreten sein.

home-assistant_livisi_2024-06-21T11-46-33.602Z.zip

aiohttp.client_exceptions.ContentTypeError: 0, message='Attempt to decode JSON with unexpected mimetype: ', url=URL('http://192.168.178.74:8080/capability//state')

There seems to be a missing capability id. unfortunately the stack trace is incomplete here...

Ok, thanks. But can you tell me what that exactly means?

No because I don't know :)
But maybe the next version fixes it...

Please try 1.11.2 (you need to set hacs to download beta versions)

Same issue here and getting worse since the devices won’t reconnect to HA after restarting the integration and/or HomeAssistant.

Can you provide a log with the error created with the latest version. This seems to be a problem with the v1 SHC and I don’t have one so I cannot reproduce this.

Logger: homeassistant.components.cover
Quelle: helpers/entity_platform.py:875
Integration: Abdeckung (Dokumentation, Probleme)
Erstmals aufgetreten: 17:58:19 (5 Vorkommnisse)
Zuletzt protokolliert: 17:58:23

Entity id already exists - ignoring: cover.balkon
Entity id already exists - ignoring: cover.rollo_garage
Entity id already exists - ignoring: cover.untergeschoss_links
Entity id already exists - ignoring: cover.untergeschoss_rechts
Entity id already exists - ignoring: cover.rollo_gastebad

Funfact: The buttons of the devices are supporting their „pressed“ state when they are pressed but the devices themselves remain unavailable.

Can you provide a log with the error created with the latest version. This seems to be a problem with the v1 SHC and I don’t have one so I cannot reproduce this.

If you mean that this is linked to the 1st generation of the SHC ("Zentrale") I can say that at my side the issue appears with the second generation.

Can you provide a log with the error created with the latest version. This seems to be a problem with the v1 SHC and I don’t have one so I cannot reproduce this.

I have this issue with SHC 2.0. Several times during the day I have to restart the integration.

I encounter the problem with v1 SHC

The problem now also occurs with me (SHC2)