Open Tobias1122334 opened 2 weeks ago
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.
Hallo,
ich habe den Debugmodus aktiviert. Gibt es irgendwo eine Anleitung wie ich die Debug logs herunterladen kann?
Ich habe erstmal übergangsweise eine Automatik erstellt, die die Integration ein mal am Tag neu lädt.
Von: Felix Rotthowe @.> Gesendet: Freitag, 21. Juni 2024 13:09 An: planbnet/livisi_unofficial @.> Cc: Tobias1122334 @.>; Author @.> Betreff: Re: [planbnet/livisi_unofficial] Frequent restart required (Issue #130)
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.
— Reply to this email directly, view it on GitHub https://github.com/planbnet/livisi_unofficial/issues/130#issuecomment-2182541361 , or unsubscribe https://github.com/notifications/unsubscribe-auth/BE3VGGXCQMI46QGWYQOEAUDZIQCWNAVCNFSM6AAAAABJOYV4D2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCOBSGU2DCMZWGE . You are receiving this because you authored the thread. https://github.com/notifications/beacon/BE3VGGQ6X5R2U4V4L6Y7RN3ZIQCWNA5CNFSM6AAAAABJOYV4D2WGG33NNVSW45C7OR4XAZNMJFZXG5LFINXW23LFNZ2KUY3PNVWWK3TUL5UWJTUCC3YDC.gif Message ID: @. @.> >
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.
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)
System Health details
System Information
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 | okHome 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 | okHome 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 | storageRecorder
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.2Checklist
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
Diagnostics dump
No response