Massive Updateprobleme HA-Core und HACS

Allgemein
1

Hi!
Da es recht komplex ist (scheint) fange ich einfach mal an mit den Symptomen, vielleicht kann mir jemand helfen bzw. weiß welche konkreten weiteren Infos hilfreich wären. Ich weiß es schlicht nicht, weil mit meinem Latein bin ich am Ende.

Kurz: Ich kann weder HA updaten und HACS ist quasi tot (es läuft alles, aber aktualisieren geht gar nicht mehr).

Es fing so an:
Das Core-Update auf 1.2024.6.2 wollte ich installieren, nachdem ich noch auf 1.2024.5.5 stand. Gesagt getan, er brauchte ewig zum starten, startete offenbar auch gar nicht voll durch sondern nahm den bis zum Zeitpunkt X geladenen Zustand dann irgendwann einfach als gegeben. In der Folge waren natürlich etliche Geräte und Sensoren etc. nicht verfügbar, weil nicht geladen. An welchem Zeitpunkt genau er nicht weiter machte kann ich nicht sagen, weil dieser jedes mal (s.u.) ein anderer war.

Ergo: Nach mehreren Neustarts und manuellem Laden von Integrationen etc. das BackUp von 5.5 einspielen → alles wieder beim Alten UND voll funktionierend.

Auf die nächste Updateversion gewartet, in der Hoffnung, dass es dann läuft. War aber wieder das selbe. Mit der nächsten dann wieder.

Heißt: mit Version 5.5 läuft alles (bis auf die gleich folgende Feststellung) wunderbar, mit ner 6.x überhaupt nicht. In den Dev-Notes gibt es keine einzige Änderung, die ich als relevant für mein System erkenne.
Laut Logs (Und Fehlermeldung) liegt das Problem daran, dass REST und RESTful nicht geladen werden kann… Aber Warum nicht? mit der 5.5 klappt es ja ohne Probleme…

HACS: Da die Coreupdates nicht laufen hab ich irgendwann zumindest mal die HACS-Integrationen und Frontenderweiterungen aktualisieren wollen - an welchem Zeitpunkt der oben beschriebenen “Reise” genau kann ich nicht mehr sagen. Klicke ich jedoch in der Liste der zur Verfügung stehenden Aktualisierungen auf einen Eintrag öffnet sich keines der Fenster, in welchen ich die Aktualisierung starten kann. Lade ich das Browserfenster neu erscheint dieses Fenster manchmal dann doch - aber die Aktualisierung kann ich nicht starten.
HACS neu zu initialisieren brachte nichts. HACS komplett neu einzubringen war mir (wegen der darauf folgenden Neukonfigurationen der Integrationen) bisher noch zu viel Arbeit, deswegen bin ich davor noch zurückgeschreckt.
Dieses Verhalten findet sich nun unter der 5.5 auch wieder, wurde also quasi mitgenommen.

VOR dem ersten Core-Updateversuch lief tatsächlich alles komplett fluffig. Aktuell läuft soweit auch noch alles, aber irgendwann werde ich Dinge (abseits des Sicherheitsthemas) updaten müssen, allein um die Funktion weiter zu gewährleisten. Eine HA-Neuinstallation schließe ich aus, dann würden 1. viele “wertvolle” Daten flöten gehen und 2. hätte ich schlicht keine Lust die Zeit wieder zu investieren. Dann schmeiß ich die Brocken lieber hin.

Ich weiß nicht wie ich das beheben soll. Jemand eine Idee? Jemand Fragen, Anregungen etc.? Ich weiß, ein fremdes System ist komplex und einzigartig, daher ist Support schwierig.

2

Moin,

Das ist weniger, dass Problem, Du sagst leider nicht

  • worauf Dein System läuft,
  • ob es vielleicht Platzprobleme gibt,
  • Du die Logs nicht zeigst, sondern nur nachsprichst.
  • zeigt die Reparatur etwas an, bei der 5.5er und/oder 6er?
    grafik
    grafik1551×719 67 KB

Hoffen, dass ein Backup sauber ist und, dann HAOS neu aufsetzen und Backup zurückspielen.

VG
Bernd

1 „Gefällt mir“
3

Kannst du dich auf GitHub direkt noch anmelden?
Ansonsten gibt es z.Z. mit Esprimos wohl Probleme.
Von daher, wie @dp20eic schon schrieb, braucht es soviel Informationen (Hardware, Software, Integrationen usw.) wie nur möglich, um ein Chance zu habe dir zu helfen.

1 „Gefällt mir“
4

Danke schon mal.
Das System läuft auf nem Raspi 4 mit 8GB RAM.
Speicher ist kein Problem, es sind nur 41% belegt und noch deutlich über 100GB frei.
Reparaturen sind keine verfügbar. Das ist die laufende 5.5er - mit der 6er muss ich das dann am Wochenende schauen. Danke für den Hinweis, den Punkt Reparaturen hab ich bisher immer geflissentlich übersehen.
image

Hier das vollständige (Core-)Log nach Neustart:

2024-06-25 10:29:30.488 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration hacs which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant
2024-06-25 10:29:30.492 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration goecharger_mqtt which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant
2024-06-25 10:29:30.495 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration electrolux_status which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant
2024-06-25 10:29:30.497 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration alarmo which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant
2024-06-25 10:29:30.500 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration measureit which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant
2024-06-25 10:29:30.502 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration ui_lovelace_minimalist which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant
2024-06-25 10:29:30.507 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration tapo_control which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant
2024-06-25 10:29:30.510 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration sunspec which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant
2024-06-25 10:29:30.512 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration roborock which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant
2024-06-25 10:29:30.514 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration teamtracker which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant
2024-06-25 10:29:30.517 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration govee_lan which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant
2024-06-25 10:29:30.519 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration govee which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant
2024-06-25 10:29:30.521 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration waste_collection_schedule which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant
2024-06-25 10:29:30.523 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration meross_cloud which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant
2024-06-25 10:29:30.526 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration presence_simulation which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant
2024-06-25 10:29:36.638 WARNING (MainThread) [homeassistant.util.loop] Detected blocking call to import_module inside the event loop by custom integration 'waste_collection_schedule' at custom_components/waste_collection_schedule/waste_collection_schedule/source_shell.py, line 188: source_module = importlib.import_module( (offender: /config/custom_components/waste_collection_schedule/waste_collection_schedule/source_shell.py, line 188: source_module = importlib.import_module(), please report it to the author of the 'waste_collection_schedule' custom integration
2024-06-25 10:29:36.890 ERROR (MainThread) [homeassistant.components.rest.data] Error fetching data: http://127.0.0.1:5000/charge_control?vin=VXEVZZKXZPZ043454 failed with All connection attempts failed
2024-06-25 10:29:36.891 ERROR (MainThread) [homeassistant.components.rest.data] Error fetching data: http://127.0.0.1:5000/get_vehicleinfo/VXEVZZKXZPZ043454 failed with All connection attempts failed
2024-06-25 10:29:36.927 ERROR (MainThread) [homeassistant.components.rest.data] Error fetching data: http://127.0.0.1:5000/charge_control?vin=VXEVZZKXZPZ043454 failed with All connection attempts failed
2024-06-25 10:29:36.927 ERROR (MainThread) [homeassistant.components.rest.data] Error fetching data: http://127.0.0.1:5000/get_vehicleinfo/VXEVZZKXZPZ043454 failed with All connection attempts failed
2024-06-25 10:29:36.931 WARNING (MainThread) [homeassistant.components.sensor] Platform rest not ready yet: All connection attempts failed; Retrying in background in 30 seconds
2024-06-25 10:29:36.932 WARNING (MainThread) [homeassistant.components.sensor] Platform rest not ready yet: All connection attempts failed; Retrying in background in 30 seconds
2024-06-25 10:29:37.016 WARNING (MainThread) [homeassistant.components.modbus.validators] `retries`: is deprecated and will be removed in version 2024.7
2024-06-25 10:29:38.247 WARNING (MainThread) [homeassistant.components.sensor] Entity sensor.stromkosten_jahr (<class 'homeassistant.components.template.sensor.SensorTemplate'>) is using state class 'total_increasing' which is impossible considering device class ('monetary') it is using; expected None or one of 'total'; Please update your configuration if your entity is manually configured, otherwise create a bug report at https://github.com/home-assistant/core/issues?q=is%3Aopen+is%3Aissue+label%3A%22integration%3A+template%22
2024-06-25 10:29:38.248 WARNING (MainThread) [homeassistant.components.sensor] Entity sensor.stromkosten_tag (<class 'homeassistant.components.template.sensor.SensorTemplate'>) is using state class 'total_increasing' which is impossible considering device class ('monetary') it is using; expected None or one of 'total'; Please update your configuration if your entity is manually configured, otherwise create a bug report at https://github.com/home-assistant/core/issues?q=is%3Aopen+is%3Aissue+label%3A%22integration%3A+template%22
2024-06-25 10:29:41.844 INFO (SyncWorker_0) [fritzconnection] Unable to retrieve resource 'http://192.168.178.31:49000/igddesc.xml' from the device.
2024-06-25 10:29:41.862 INFO (SyncWorker_6) [fritzconnection] Unable to retrieve resource 'http://192.168.178.33:49000/igddesc.xml' from the device.
2024-06-25 10:29:41.867 INFO (SyncWorker_8) [fritzconnection] Unable to retrieve resource 'http://192.168.178.95:49000/igddesc.xml' from the device.
2024-06-25 10:29:41.896 INFO (SyncWorker_16) [fritzconnection] Unable to retrieve resource 'http://192.168.178.140:49000/igddesc.xml' from the device.
2024-06-25 10:29:51.355 WARNING (MainThread) [homeassistant.helpers.frame] Detected that custom integration 'hacs' accesses hass.components.frontend. This is deprecated and will stop working in Home Assistant 2024.9, it should be updated to import functions used from frontend directly at custom_components/hacs/frontend.py, line 68: hass.components.frontend.async_register_built_in_panel(, please create a bug report at https://github.com/hacs/integration/issues
2024-06-25 10:29:55.099 WARNING (MainThread) [custom_components.meross_cloud] Skip MQTT cert validation option set to: True
2024-06-25 10:29:55.100 WARNING (MainThread) [custom_components.meross_cloud] Returned/Stored DOMAIN within existing credentials is <https://iot.meross.com>. Patching the stored credentials with the correct value right away.
2024-06-25 10:29:55.257 WARNING (MainThread) [custom_components.meross_cloud] 
===============================
Meross Cloud Custom component
Developed by Alberto Geniola
Low level library version: 0.4.7.2b3
-------------------------------
This custom component is under development and not yet ready for production use.
In case of errors/misbehave, please report it here: 
https://github.com/albertogeniola/meross-homeassistant/issues

If you like this extension and you want to support it, please consider donating.
-------------------------------
List of devices reported by HTTP API:
- Smart Plug (mss210) - OnlineStatus.ONLINE
- topdownplug (mss620r) - OnlineStatus.ONLINE
- Smart Plug (mss210) - OnlineStatus.ONLINE
- Schlafzimmer Vorne (mrs100) - OnlineStatus.ONLINE
- Opti (mss210) - OnlineStatus.ONLINE
- Hanna Fenster (mrs100) - OnlineStatus.ONLINE
- Garagentor (msg100) - OnlineStatus.ONLINE
- Smart Plug (mss210) - OnlineStatus.ONLINE
- Smart Ambient Light (msl420) - OnlineStatus.ONLINE
- Smart Plug (mss120b) - OnlineStatus.ONLINE
- Vordach (mss210) - OnlineStatus.ONLINE
- Nora Garten (mrs100) - OnlineStatus.ONLINE
- Nora Straße (mrs100) - OnlineStatus.ONLINE
- GrillBrunnen (mss620) - OnlineStatus.ONLINE
===============================
2024-06-25 10:30:02.036 WARNING (MainThread) [homeassistant.setup] Setup of telegram_bot is taking over 10 seconds.
2024-06-25 10:30:06.048 WARNING (MainThread) [homeassistant.components.calendar] Setup of calendar platform caldav is taking over 10 seconds.
2024-06-25 10:30:06.325 WARNING (MainThread) [homeassistant.components.light] None (<class 'custom_components.govee_lan.light.GoveLightEntity'>) sets invalid supported color modes {<ColorMode.COLOR_TEMP: 'color_temp'>, <ColorMode.BRIGHTNESS: 'brightness'>, <ColorMode.RGB: 'rgb'>}, this will stop working in Home Assistant Core 2025.3, please create a bug report at https://github.com/wez/govee-lan-hass/issues
2024-06-25 10:30:06.326 WARNING (MainThread) [homeassistant.components.light] None (<class 'custom_components.govee_lan.light.GoveLightEntity'>) sets invalid supported color modes {<ColorMode.COLOR_TEMP: 'color_temp'>, <ColorMode.BRIGHTNESS: 'brightness'>, <ColorMode.RGB: 'rgb'>}, this will stop working in Home Assistant Core 2025.3, please create a bug report at https://github.com/wez/govee-lan-hass/issues
2024-06-25 10:30:06.328 WARNING (MainThread) [homeassistant.components.light] None (<class 'custom_components.govee_lan.light.GoveLightEntity'>) sets invalid supported color modes {<ColorMode.COLOR_TEMP: 'color_temp'>, <ColorMode.BRIGHTNESS: 'brightness'>, <ColorMode.RGB: 'rgb'>}, this will stop working in Home Assistant Core 2025.3, please create a bug report at https://github.com/wez/govee-lan-hass/issues
2024-06-25 10:30:06.794 ERROR (MainThread) [meross_iot.manager] Timeout occurred while waiting a response for message b'{"header":{"from":"/app/756017-b9080411ed1ee3b606745a75093bd7a6/subscribe","messageId":"6f3cac51472da864655b5c7972311c75","method":"GET","namespace":"Appliance.System.Ability","payloadVersion":1,"sign":"7daa52a5c350f3766d5a14040c0642ed","timestamp":1719304197,"triggerSrc":"Android","uuid":"2004234441425451850648e1e91ac61b"},"payload":{}}' sent to device uuid 2004234441425451850648e1e91ac61b. Timeout was: 10.000000 seconds. Mqtt Host: mqtt-eu-4.meross.com:443.
2024-06-25 10:30:06.794 WARNING (MainThread) [meross_iot.manager] Device Smart Plug (2004234441425451850648e1e91ac61b) is online, but timeout occurred when fetching its abilities. 
2024-06-25 10:30:06.811 ERROR (MainThread) [meross_iot.manager] Timeout occurred while waiting a response for message b'{"header":{"from":"/app/756017-b9080411ed1ee3b606745a75093bd7a6/subscribe","messageId":"3ce88d042a4f52d5d8d8cd085f38aef1","method":"GET","namespace":"Appliance.System.Ability","payloadVersion":1,"sign":"6ad03e5f2e33c6e15c93bf03af999f06","timestamp":1719304197,"triggerSrc":"Android","uuid":"2006287592740090816348e1e920fb15"},"payload":{}}' sent to device uuid 2006287592740090816348e1e920fb15. Timeout was: 10.000000 seconds. Mqtt Host: mqtt-eu-4.meross.com:443.
2024-06-25 10:30:06.811 WARNING (MainThread) [meross_iot.manager] Device Smart Plug (2006287592740090816348e1e920fb15) is online, but timeout occurred when fetching its abilities. 
2024-06-25 10:30:07.877 ERROR (MainThread) [meross_iot.manager] Timeout occurred while waiting a response for message b'{"header":{"from":"/app/756017-b9080411ed1ee3b606745a75093bd7a6/subscribe","messageId":"b3577913418e1896daffd1f3544eb7a3","method":"GET","namespace":"Appliance.System.Ability","payloadVersion":1,"sign":"1782ad8fd8d1ad362cbf0a9503718361","timestamp":1719304198,"triggerSrc":"Android","uuid":"2006287592740090816348e1e920fb15"},"payload":{}}' sent to device uuid 2006287592740090816348e1e920fb15. Timeout was: 10.000000 seconds. Mqtt Host: mqtt-eu-4.meross.com:443.
2024-06-25 10:30:07.878 WARNING (MainThread) [meross_iot.manager] Device Smart Plug (2006287592740090816348e1e920fb15) is online, but timeout occurred when fetching its abilities. 
2024-06-25 10:30:08.660 WARNING (MainThread) [aioesphomeapi.reconnect_logic] Can't connect to ESPHome API for m5stack-atom-echo-b83010 @ 192.168.178.120: Error connecting to [AddrInfo(family=<AddressFamily.AF_INET: 2>, type=<SocketKind.SOCK_STREAM: 1>, proto=6, sockaddr=IPv4Sockaddr(address='192.168.178.120', port=6053))]: [Errno 113] Connect call failed ('192.168.178.120', 6053) (SocketAPIError)
2024-06-25 10:30:14.213 WARNING (MainThread) [zigpy.application] Zigbee channel 15 utilization is 99.67%!
2024-06-25 10:30:14.214 WARNING (MainThread) [zigpy.application] If you are having problems joining new devices, are missing sensor updates, or have issues keeping devices joined, ensure your coordinator is away from interference sources such as USB 3.0 devices, SSDs, WiFi routers, etc.
2024-06-25 10:30:17.573 ERROR (MainThread) [meross_iot.manager] Timeout occurred while waiting a response for message b'{"header":{"from":"/app/756017-b9080411ed1ee3b606745a75093bd7a6/subscribe","messageId":"a6c35ea88a716a0cf2386ca7b7fb591c","method":"GET","namespace":"Appliance.System.Ability","payloadVersion":1,"sign":"00a98f4ec44c1d6a7a7583c55e0ff4a3","timestamp":1719304208,"triggerSrc":"Android","uuid":"2006287592740090816348e1e920fb15"},"payload":{}}' sent to device uuid 2006287592740090816348e1e920fb15. Timeout was: 10.000000 seconds. Mqtt Host: mqtt-eu-4.meross.com:443.
2024-06-25 10:30:17.574 WARNING (MainThread) [meross_iot.manager] Device Smart Plug (2006287592740090816348e1e920fb15) is online, but timeout occurred when fetching its abilities. 
2024-06-25 10:30:17.581 ERROR (MainThread) [meross_iot.manager] Timeout occurred while waiting a response for message b'{"header":{"from":"/app/756017-b9080411ed1ee3b606745a75093bd7a6/subscribe","messageId":"c612adbf8a6fbb658b1b16543aa92b73","method":"GET","namespace":"Appliance.System.Ability","payloadVersion":1,"sign":"f01312b6a2882f2311f7fb1d456c5a4a","timestamp":1719304208,"triggerSrc":"Android","uuid":"2012102503141851853348e1e93f6509"},"payload":{}}' sent to device uuid 2012102503141851853348e1e93f6509. Timeout was: 10.000000 seconds. Mqtt Host: mqtt-eu-4.meross.com:443.
2024-06-25 10:30:17.581 WARNING (MainThread) [meross_iot.manager] Device Opti (2012102503141851853348e1e93f6509) is online, but timeout occurred when fetching its abilities. 
2024-06-25 10:30:17.977 ERROR (MainThread) [meross_iot.manager] Timeout occurred while waiting a response for message b'{"header":{"from":"/app/756017-b9080411ed1ee3b606745a75093bd7a6/subscribe","messageId":"1a8a7986660ec9a5d99a4142353bb054","method":"GET","namespace":"Appliance.System.Ability","payloadVersion":1,"sign":"6bc838cb9d09e6648eb0b5b07cf93add","timestamp":1719304208,"triggerSrc":"Android","uuid":"2012102503141851853348e1e93f6509"},"payload":{}}' sent to device uuid 2012102503141851853348e1e93f6509. Timeout was: 10.000000 seconds. Mqtt Host: mqtt-eu-4.meross.com:443.
2024-06-25 10:30:17.977 WARNING (MainThread) [meross_iot.manager] Device Opti (2012102503141851853348e1e93f6509) is online, but timeout occurred when fetching its abilities. 
2024-06-25 10:30:27.589 ERROR (MainThread) [meross_iot.manager] Timeout occurred while waiting a response for message b'{"header":{"from":"/app/756017-b9080411ed1ee3b606745a75093bd7a6/subscribe","messageId":"b8e0d8b80e6d8b0234f6d2eaae5b3f92","method":"GET","namespace":"Appliance.System.Ability","payloadVersion":1,"sign":"400bf0615612c5cb7363c8fe7cdaabdf","timestamp":1719304218,"triggerSrc":"Android","uuid":"2012109611902951853348e1e93f2c1f"},"payload":{}}' sent to device uuid 2012109611902951853348e1e93f2c1f. Timeout was: 10.000000 seconds. Mqtt Host: mqtt-eu-4.meross.com:443.
2024-06-25 10:30:27.590 WARNING (MainThread) [meross_iot.manager] Device Smart Plug (2012109611902951853348e1e93f2c1f) is online, but timeout occurred when fetching its abilities. 
2024-06-25 10:30:27.837 ERROR (MainThread) [meross_iot.manager] Timeout occurred while waiting a response for message b'{"header":{"from":"/app/756017-b9080411ed1ee3b606745a75093bd7a6/subscribe","messageId":"bc2b16fccff09c6f1c675884f0266a78","method":"GET","namespace":"Appliance.System.Ability","payloadVersion":1,"sign":"5c9928b9eb7b2ac588ae83fb71c960d2","timestamp":1719304218,"triggerSrc":"Android","uuid":"2012109611902951853348e1e93f2c1f"},"payload":{}}' sent to device uuid 2012109611902951853348e1e93f2c1f. Timeout was: 10.000000 seconds. Mqtt Host: mqtt-eu-4.meross.com:443.
2024-06-25 10:30:27.837 WARNING (MainThread) [meross_iot.manager] Device Smart Plug (2012109611902951853348e1e93f2c1f) is online, but timeout occurred when fetching its abilities. 
2024-06-25 10:30:28.472 ERROR (MainThread) [meross_iot.manager] Timeout occurred while waiting a response for message b'{"header":{"from":"/app/756017-b9080411ed1ee3b606745a75093bd7a6/subscribe","messageId":"db4194c94bf594c032d7e6b8e4e4f66e","method":"GET","namespace":"Appliance.System.Ability","payloadVersion":1,"sign":"b1dd02eb9d375dc12dc42c7aa7b3d62c","timestamp":1719304218,"triggerSrc":"Android","uuid":"2004234441425451850648e1e91ac61b"},"payload":{}}' sent to device uuid 2004234441425451850648e1e91ac61b. Timeout was: 10.000000 seconds. Mqtt Host: mqtt-eu-4.meross.com:443.
2024-06-25 10:30:28.473 WARNING (MainThread) [meross_iot.manager] Device Smart Plug (2004234441425451850648e1e91ac61b) is online, but timeout occurred when fetching its abilities. 
2024-06-25 10:30:37.058 WARNING (MainThread) [homeassistant.bootstrap] Waiting on integrations to complete setup: {('fritzbox', '5ff5ab3a1436d2a7fa78339e5c7d7550'): 553396.74538518, ('meross_cloud', '68483f6458faf406a1659a0160df8824'): 553400.676410426, ('caldav', '547376368192'): 553401.491144928}
2024-06-25 10:30:37.838 ERROR (MainThread) [meross_iot.manager] Timeout occurred while waiting a response for message b'{"header":{"from":"/app/756017-b9080411ed1ee3b606745a75093bd7a6/subscribe","messageId":"23d8d93f92b2d328037d99c9b60cf9aa","method":"GET","namespace":"Appliance.System.Ability","payloadVersion":1,"sign":"6862fa426c175f58fccdb36cbe0e14df","timestamp":1719304228,"triggerSrc":"Android","uuid":"2004234441425451850648e1e91ac61b"},"payload":{}}' sent to device uuid 2004234441425451850648e1e91ac61b. Timeout was: 10.000000 seconds. Mqtt Host: mqtt-eu-4.meross.com:443.
2024-06-25 10:30:37.839 WARNING (MainThread) [meross_iot.manager] Device Smart Plug (2004234441425451850648e1e91ac61b) is online, but timeout occurred when fetching its abilities. 
2024-06-25 10:30:38.216 ERROR (MainThread) [meross_iot.manager] Timeout occurred while waiting a response for message b'{"header":{"from":"/app/756017-b9080411ed1ee3b606745a75093bd7a6/subscribe","messageId":"be963d985413656f9411507dae98510d","method":"GET","namespace":"Appliance.System.Ability","payloadVersion":1,"sign":"8d4a3a89b03a5e442e9cd6a2834092c4","timestamp":1719304228,"triggerSrc":"Android","uuid":"2012102503141851853348e1e93f6509"},"payload":{}}' sent to device uuid 2012102503141851853348e1e93f6509. Timeout was: 10.000000 seconds. Mqtt Host: mqtt-eu-4.meross.com:443.
2024-06-25 10:30:38.217 WARNING (MainThread) [meross_iot.manager] Device Opti (2012102503141851853348e1e93f6509) is online, but timeout occurred when fetching its abilities. 
2024-06-25 10:30:38.608 ERROR (MainThread) [meross_iot.manager] Timeout occurred while waiting a response for message b'{"header":{"from":"/app/756017-b9080411ed1ee3b606745a75093bd7a6/subscribe","messageId":"5767623d852bc4ab8647fbf81647640a","method":"GET","namespace":"Appliance.System.Ability","payloadVersion":1,"sign":"45ea1082438ff6d17274b4c8941edc8b","timestamp":1719304229,"triggerSrc":"Android","uuid":"2012109611902951853348e1e93f2c1f"},"payload":{}}' sent to device uuid 2012109611902951853348e1e93f2c1f. Timeout was: 10.000000 seconds. Mqtt Host: mqtt-eu-4.meross.com:443.
2024-06-25 10:30:38.609 WARNING (MainThread) [meross_iot.manager] Device Smart Plug (2012109611902951853348e1e93f2c1f) is online, but timeout occurred when fetching its abilities. 
2024-06-25 10:30:38.730 WARNING (MainThread) [meross_iot.manager] Found a new device topdownplug (mss620r, HW 4.5.0, FW 4.1.34, class: mss620r:4.5.0:4.1.34) that has become online while we were offline.
2024-06-25 10:30:38.732 WARNING (MainThread) [meross_iot.manager] Found a new device Vordach (mss210, HW 4.0.0, FW 4.2.9, class: mss210:4.0.0:4.2.9) that has become online while we were offline.
2024-06-25 10:30:38.737 WARNING (MainThread) [meross_iot.manager] Found a new device Nora Garten (mrs100, HW 7.0.0, FW 7.6.14, class: mrs100:7.0.0:7.6.14) that has become online while we were offline.
2024-06-25 10:30:38.739 WARNING (MainThread) [meross_iot.manager] Found a new device Nora Straße (mrs100, HW 7.0.0, FW 7.6.14, class: mrs100:7.0.0:7.6.14) that has become online while we were offline.
2024-06-25 10:30:38.740 WARNING (MainThread) [meross_iot.manager] Found a new device Schlafzimmer Vorne (mrs100, HW 7.0.0, FW 7.6.14, class: mrs100:7.0.0:7.6.14) that has become online while we were offline.
2024-06-25 10:30:38.740 WARNING (MainThread) [meross_iot.manager] Found a new device Smart Ambient Light (msl420, HW 4.0.0, FW 4.2.5, class: msl420:4.0.0:4.2.5) that has become online while we were offline.
2024-06-25 10:30:38.744 WARNING (MainThread) [meross_iot.manager] Found a new device Hanna Fenster (mrs100, HW 7.0.0, FW 7.6.14, class: mrs100:7.0.0:7.6.14) that has become online while we were offline.
2024-06-25 10:30:38.744 WARNING (MainThread) [meross_iot.manager] Found a new device Garagentor (msg100, HW 4.0.0, FW 4.2.12, class: msg100:4.0.0:4.2.12) that has become online while we were offline.
2024-06-25 10:30:38.746 WARNING (MainThread) [meross_iot.manager] Found a new device GrillBrunnen (mss620, HW 4.0.0, FW 4.1.32, class: mss620:4.0.0:4.1.32) that has become online while we were offline.
2024-06-25 10:30:38.749 WARNING (MainThread) [meross_iot.manager] Found a new device Smart Plug (mss210, HW 4.0.0, FW 4.2.9, class: mss210:4.0.0:4.2.9) that has become online while we were offline.
2024-06-25 10:30:40.821 WARNING (MainThread) [meross_iot.manager] Found a new device Vordach (mss210, HW 4.0.0, FW 4.2.9, class: mss210:4.0.0:4.2.9) that has become online while we were offline.
2024-06-25 10:30:40.821 WARNING (MainThread) [meross_iot.manager] Found a new device Nora Garten (mrs100, HW 7.0.0, FW 7.6.14, class: mrs100:7.0.0:7.6.14) that has become online while we were offline.
2024-06-25 10:30:40.822 WARNING (MainThread) [meross_iot.manager] Found a new device Nora Straße (mrs100, HW 7.0.0, FW 7.6.14, class: mrs100:7.0.0:7.6.14) that has become online while we were offline.
2024-06-25 10:30:40.822 WARNING (MainThread) [meross_iot.manager] Found a new device Schlafzimmer Vorne (mrs100, HW 7.0.0, FW 7.6.14, class: mrs100:7.0.0:7.6.14) that has become online while we were offline.
2024-06-25 10:30:40.822 WARNING (MainThread) [meross_iot.manager] Found a new device Smart Ambient Light (msl420, HW 4.0.0, FW 4.2.5, class: msl420:4.0.0:4.2.5) that has become online while we were offline.
2024-06-25 10:30:40.823 WARNING (MainThread) [meross_iot.manager] Found a new device Hanna Fenster (mrs100, HW 7.0.0, FW 7.6.14, class: mrs100:7.0.0:7.6.14) that has become online while we were offline.
2024-06-25 10:30:40.823 WARNING (MainThread) [meross_iot.manager] Found a new device Garagentor (msg100, HW 4.0.0, FW 4.2.12, class: msg100:4.0.0:4.2.12) that has become online while we were offline.
2024-06-25 10:30:40.823 WARNING (MainThread) [meross_iot.manager] Found a new device GrillBrunnen (mss620, HW 4.0.0, FW 4.1.32, class: mss620:4.0.0:4.1.32) that has become online while we were offline.
2024-06-25 10:30:40.824 WARNING (MainThread) [meross_iot.manager] Found a new device Smart Plug (mss210, HW 4.0.0, FW 4.2.9, class: mss210:4.0.0:4.2.9) that has become online while we were offline.
2024-06-25 10:30:40.825 WARNING (MainThread) [meross_iot.manager] Updating status for device topdownplug (mss620r, HW 4.5.0, FW 4.1.34, class: mss620r:4.5.0:4.1.34)
2024-06-25 10:30:55.916 ERROR (MainThread) [homeassistant.components.calendar] Setup of platform caldav is taking longer than 60 seconds. Startup will proceed without waiting any longer.
2024-06-25 10:30:56.067 ERROR (MainThread) [homeassistant.helpers.event] Error while processing template: Template<template=({{ (float(states('sensor.battery_charging_power'))) - (float(states('sensor.battery_discharging_power'))) }}) renders=2>
Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/helpers/template.py", line 2214, in forgiving_float
    return float(value)
           ^^^^^^^^^^^^
ValueError: could not convert string to float: 'unknown'

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/helpers/template.py", line 585, in async_render
    render_result = _render_with_context(self.template, compiled, **kwargs)
                    ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/helpers/template.py", line 2600, in _render_with_context
    return template.render(**kwargs)
           ^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.12/site-packages/jinja2/environment.py", line 1304, in render
    self.environment.handle_exception()
  File "/usr/local/lib/python3.12/site-packages/jinja2/environment.py", line 939, in handle_exception
    raise rewrite_traceback_stack(source=source)
  File "<template>", line 1, in top-level template code
  File "/usr/local/lib/python3.12/site-packages/jinja2/sandbox.py", line 394, in call
    return __context.call(__obj, *args, **kwargs)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/helpers/template.py", line 2217, in forgiving_float
    raise_no_default("float", value)
  File "/usr/src/homeassistant/homeassistant/helpers/template.py", line 1849, in raise_no_default
    raise ValueError(
ValueError: Template error: float got invalid input 'unknown' when rendering template '{{ (float(states('sensor.battery_charging_power'))) - (float(states('sensor.battery_discharging_power'))) }}' but no default was specified

The above exception was the direct cause of the following exception:

Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/helpers/template.py", line 713, in async_render_to_info
    render_info._result = self.async_render(
                          ^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/helpers/template.py", line 587, in async_render
    raise TemplateError(err) from err
homeassistant.exceptions.TemplateError: ValueError: Template error: float got invalid input 'unknown' when rendering template '{{ (float(states('sensor.battery_charging_power'))) - (float(states('sensor.battery_discharging_power'))) }}' but no default was specified
2024-06-25 10:30:56.089 ERROR (MainThread) [homeassistant.components.template.template_entity] TemplateError('ValueError: Template error: float got invalid input 'unknown' when rendering template '{{ (float(states('sensor.battery_charging_power'))) - (float(states('sensor.battery_discharging_power'))) }}' but no default was specified') while processing template 'Template<template=({{ (float(states('sensor.battery_charging_power'))) - (float(states('sensor.battery_discharging_power'))) }}) renders=4>' for attribute '_attr_native_value' in entity 'sensor.batterieleistung_aktuell'
2024-06-25 10:30:56.095 ERROR (MainThread) [homeassistant.helpers.event] Error while processing template: Template<template=({{ (int(states('sensor.total_dc_power', rounded=True))) + (int(states('sensor.garagensolar_power', rounded=True))) + (int(states('sensor.battery_discharging_power', rounded=True))) - (int(states('sensor.battery_charging_power', rounded=True))) + (int(states('sensor.strom_eg_aktuell', rounded=True)))  }}) renders=2>
Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/helpers/template.py", line 585, in async_render
    render_result = _render_with_context(self.template, compiled, **kwargs)
                    ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/helpers/template.py", line 2600, in _render_with_context
    return template.render(**kwargs)
           ^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.12/site-packages/jinja2/environment.py", line 1304, in render
    self.environment.handle_exception()
  File "/usr/local/lib/python3.12/site-packages/jinja2/environment.py", line 939, in handle_exception
    raise rewrite_traceback_stack(source=source)
  File "<template>", line 1, in top-level template code
  File "/usr/local/lib/python3.12/site-packages/jinja2/sandbox.py", line 394, in call
    return __context.call(__obj, *args, **kwargs)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/helpers/template.py", line 2235, in forgiving_int
    raise_no_default("int", value)
  File "/usr/src/homeassistant/homeassistant/helpers/template.py", line 1849, in raise_no_default
    raise ValueError(
ValueError: Template error: int got invalid input 'unknown' when rendering template '{{ (int(states('sensor.total_dc_power', rounded=True))) + (int(states('sensor.garagensolar_power', rounded=True))) + (int(states('sensor.battery_discharging_power', rounded=True))) - (int(states('sensor.battery_charging_power', rounded=True))) + (int(states('sensor.strom_eg_aktuell', rounded=True)))  }}' but no default was specified

The above exception was the direct cause of the following exception:

Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/helpers/template.py", line 713, in async_render_to_info
    render_info._result = self.async_render(
                          ^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/helpers/template.py", line 587, in async_render
    raise TemplateError(err) from err
homeassistant.exceptions.TemplateError: ValueError: Template error: int got invalid input 'unknown' when rendering template '{{ (int(states('sensor.total_dc_power', rounded=True))) + (int(states('sensor.garagensolar_power', rounded=True))) + (int(states('sensor.battery_discharging_power', rounded=True))) - (int(states('sensor.battery_charging_power', rounded=True))) + (int(states('sensor.strom_eg_aktuell', rounded=True)))  }}' but no default was specified
2024-06-25 10:30:56.100 ERROR (MainThread) [homeassistant.components.template.template_entity] TemplateError('ValueError: Template error: int got invalid input 'unknown' when rendering template '{{ (int(states('sensor.total_dc_power', rounded=True))) + (int(states('sensor.garagensolar_power', rounded=True))) + (int(states('sensor.battery_discharging_power', rounded=True))) - (int(states('sensor.battery_charging_power', rounded=True))) + (int(states('sensor.strom_eg_aktuell', rounded=True)))  }}' but no default was specified') while processing template 'Template<template=({{ (int(states('sensor.total_dc_power', rounded=True))) + (int(states('sensor.garagensolar_power', rounded=True))) + (int(states('sensor.battery_discharging_power', rounded=True))) - (int(states('sensor.battery_charging_power', rounded=True))) + (int(states('sensor.strom_eg_aktuell', rounded=True)))  }}) renders=4>' for attribute '_attr_native_value' in entity 'sensor.hausverbrauch_berechnet'
2024-06-25 10:30:56.113 ERROR (MainThread) [homeassistant.helpers.event] Error while processing template: Template<template=({{ states.sensor.psa.attributes["energy"][0]["charging"]["status"] }}) renders=2>
Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/helpers/template.py", line 585, in async_render
    render_result = _render_with_context(self.template, compiled, **kwargs)
                    ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/helpers/template.py", line 2600, in _render_with_context
    return template.render(**kwargs)
           ^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.12/site-packages/jinja2/environment.py", line 1304, in render
    self.environment.handle_exception()
  File "/usr/local/lib/python3.12/site-packages/jinja2/environment.py", line 939, in handle_exception
    raise rewrite_traceback_stack(source=source)
  File "<template>", line 1, in top-level template code
  File "/usr/local/lib/python3.12/site-packages/jinja2/sandbox.py", line 304, in getitem
    return obj[argument]
           ~~~^^^^^^^^^^
jinja2.exceptions.UndefinedError: 'homeassistant.util.read_only_dict.ReadOnlyDict object' has no attribute 'energy'

The above exception was the direct cause of the following exception:

Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/helpers/template.py", line 713, in async_render_to_info
    render_info._result = self.async_render(
                          ^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/helpers/template.py", line 587, in async_render
    raise TemplateError(err) from err
homeassistant.exceptions.TemplateError: UndefinedError: 'homeassistant.util.read_only_dict.ReadOnlyDict object' has no attribute 'energy'
2024-06-25 10:30:56.120 ERROR (MainThread) [homeassistant.components.template.template_entity] TemplateError('UndefinedError: 'homeassistant.util.read_only_dict.ReadOnlyDict object' has no attribute 'energy'') while processing template 'Template<template=({{ states.sensor.psa.attributes["energy"][0]["charging"]["status"] }}) renders=4>' for attribute '_attr_native_value' in entity 'sensor.psa_charging_status'
2024-06-25 10:30:56.121 ERROR (MainThread) [homeassistant.helpers.template] Template variable error: None has no element 0 when rendering '{{ state_attr('sensor.psa', 'energy')[0].level }}'
2024-06-25 10:30:56.121 ERROR (MainThread) [homeassistant.helpers.event] Error while processing template: Template<template=({{ state_attr('sensor.psa', 'energy')[0].level }}) renders=2>
Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/helpers/template.py", line 585, in async_render
    render_result = _render_with_context(self.template, compiled, **kwargs)
                    ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/helpers/template.py", line 2600, in _render_with_context
    return template.render(**kwargs)
           ^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.12/site-packages/jinja2/environment.py", line 1304, in render
    self.environment.handle_exception()
  File "/usr/local/lib/python3.12/site-packages/jinja2/environment.py", line 939, in handle_exception
    raise rewrite_traceback_stack(source=source)
  File "<template>", line 1, in top-level template code
  File "/usr/local/lib/python3.12/site-packages/jinja2/sandbox.py", line 327, in getattr
    value = getattr(obj, attribute)
            ^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/helpers/template.py", line 2632, in _fail_with_undefined_error
    return super()._fail_with_undefined_error(*args, **kwargs)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
jinja2.exceptions.UndefinedError: None has no element 0

The above exception was the direct cause of the following exception:

Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/helpers/template.py", line 713, in async_render_to_info
    render_info._result = self.async_render(
                          ^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/helpers/template.py", line 587, in async_render
    raise TemplateError(err) from err
homeassistant.exceptions.TemplateError: UndefinedError: None has no element 0
2024-06-25 10:30:56.127 ERROR (MainThread) [homeassistant.helpers.template] Template variable error: None has no element 0 when rendering '{{ state_attr('sensor.psa', 'energy')[0].level }}'
2024-06-25 10:30:56.128 ERROR (MainThread) [homeassistant.components.template.template_entity] TemplateError('UndefinedError: None has no element 0') while processing template 'Template<template=({{ state_attr('sensor.psa', 'energy')[0].level }}) renders=4>' for attribute '_attr_native_value' in entity 'sensor.psa_battery_level'
2024-06-25 10:30:56.129 ERROR (MainThread) [homeassistant.helpers.event] Error while processing template: Template<template=({{ states.sensor.psa.attributes["timed_odometer"]["mileage"] }}) renders=2>
Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/helpers/template.py", line 585, in async_render
    render_result = _render_with_context(self.template, compiled, **kwargs)
                    ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/helpers/template.py", line 2600, in _render_with_context
    return template.render(**kwargs)
           ^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.12/site-packages/jinja2/environment.py", line 1304, in render
    self.environment.handle_exception()
  File "/usr/local/lib/python3.12/site-packages/jinja2/environment.py", line 939, in handle_exception
    raise rewrite_traceback_stack(source=source)
  File "<template>", line 1, in top-level template code
  File "/usr/local/lib/python3.12/site-packages/jinja2/sandbox.py", line 304, in getitem
    return obj[argument]
           ~~~^^^^^^^^^^
jinja2.exceptions.UndefinedError: 'homeassistant.util.read_only_dict.ReadOnlyDict object' has no attribute 'timed_odometer'

The above exception was the direct cause of the following exception:

Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/helpers/template.py", line 713, in async_render_to_info
    render_info._result = self.async_render(
                          ^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/helpers/template.py", line 587, in async_render
    raise TemplateError(err) from err
homeassistant.exceptions.TemplateError: UndefinedError: 'homeassistant.util.read_only_dict.ReadOnlyDict object' has no attribute 'timed_odometer'
2024-06-25 10:30:56.136 ERROR (MainThread) [homeassistant.components.template.template_entity] TemplateError('UndefinedError: 'homeassistant.util.read_only_dict.ReadOnlyDict object' has no attribute 'timed_odometer'') while processing template 'Template<template=({{ states.sensor.psa.attributes["timed_odometer"]["mileage"] }}) renders=4>' for attribute '_attr_native_value' in entity 'sensor.psa_mileage'
2024-06-25 10:30:56.138 ERROR (MainThread) [homeassistant.helpers.event] Error while processing template: Template<template=({{ states.sensor.psa.attributes["energy"][0]["autonomy"] }}) renders=2>
Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/helpers/template.py", line 585, in async_render
    render_result = _render_with_context(self.template, compiled, **kwargs)
                    ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/helpers/template.py", line 2600, in _render_with_context
    return template.render(**kwargs)
           ^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.12/site-packages/jinja2/environment.py", line 1304, in render
    self.environment.handle_exception()
  File "/usr/local/lib/python3.12/site-packages/jinja2/environment.py", line 939, in handle_exception
    raise rewrite_traceback_stack(source=source)
  File "<template>", line 1, in top-level template code
  File "/usr/local/lib/python3.12/site-packages/jinja2/sandbox.py", line 304, in getitem
    return obj[argument]
           ~~~^^^^^^^^^^
jinja2.exceptions.UndefinedError: 'homeassistant.util.read_only_dict.ReadOnlyDict object' has no attribute 'energy'

The above exception was the direct cause of the following exception:

Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/helpers/template.py", line 713, in async_render_to_info
    render_info._result = self.async_render(
                          ^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/helpers/template.py", line 587, in async_render
    raise TemplateError(err) from err
homeassistant.exceptions.TemplateError: UndefinedError: 'homeassistant.util.read_only_dict.ReadOnlyDict object' has no attribute 'energy'
2024-06-25 10:30:56.143 ERROR (MainThread) [homeassistant.components.template.template_entity] TemplateError('UndefinedError: 'homeassistant.util.read_only_dict.ReadOnlyDict object' has no attribute 'energy'') while processing template 'Template<template=({{ states.sensor.psa.attributes["energy"][0]["autonomy"] }}) renders=4>' for attribute '_attr_native_value' in entity 'sensor.psa_range'
2024-06-25 10:30:56.145 ERROR (MainThread) [homeassistant.helpers.template] Template variable error: 'None' has no attribute 'air_conditioning' when rendering '{{ state_attr('sensor.psa', 'preconditionning').air_conditioning.status }}'
2024-06-25 10:30:56.146 ERROR (MainThread) [homeassistant.helpers.event] Error while processing template: Template<template=({{ state_attr('sensor.psa', 'preconditionning').air_conditioning.status }}) renders=2>
Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/helpers/template.py", line 585, in async_render
    render_result = _render_with_context(self.template, compiled, **kwargs)
                    ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/helpers/template.py", line 2600, in _render_with_context
    return template.render(**kwargs)
           ^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.12/site-packages/jinja2/environment.py", line 1304, in render
    self.environment.handle_exception()
  File "/usr/local/lib/python3.12/site-packages/jinja2/environment.py", line 939, in handle_exception
    raise rewrite_traceback_stack(source=source)
  File "<template>", line 1, in top-level template code
  File "/usr/local/lib/python3.12/site-packages/jinja2/sandbox.py", line 327, in getattr
    value = getattr(obj, attribute)
            ^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/helpers/template.py", line 2632, in _fail_with_undefined_error
    return super()._fail_with_undefined_error(*args, **kwargs)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
jinja2.exceptions.UndefinedError: 'None' has no attribute 'air_conditioning'

The above exception was the direct cause of the following exception:

Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/helpers/template.py", line 713, in async_render_to_info
    render_info._result = self.async_render(
                          ^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/helpers/template.py", line 587, in async_render
    raise TemplateError(err) from err
homeassistant.exceptions.TemplateError: UndefinedError: 'None' has no attribute 'air_conditioning'
2024-06-25 10:30:56.151 ERROR (MainThread) [homeassistant.helpers.template] Template variable error: 'None' has no attribute 'air_conditioning' when rendering '{{ state_attr('sensor.psa', 'preconditionning').air_conditioning.status }}'
2024-06-25 10:30:56.152 ERROR (MainThread) [homeassistant.components.template.template_entity] TemplateError('UndefinedError: 'None' has no attribute 'air_conditioning'') while processing template 'Template<template=({{ state_attr('sensor.psa', 'preconditionning').air_conditioning.status }}) renders=4>' for attribute '_attr_native_value' in entity 'sensor.psa_preconditioning_status'
2024-06-25 10:30:56.153 ERROR (MainThread) [homeassistant.helpers.template] Template variable error: None has no element 0 when rendering '{{ state_attr('sensor.psa', 'energy')[0].charging.charging_mode }}'
2024-06-25 10:30:56.153 ERROR (MainThread) [homeassistant.helpers.event] Error while processing template: Template<template=({{ state_attr('sensor.psa', 'energy')[0].charging.charging_mode }}) renders=2>
Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/helpers/template.py", line 585, in async_render
    render_result = _render_with_context(self.template, compiled, **kwargs)
                    ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/helpers/template.py", line 2600, in _render_with_context
    return template.render(**kwargs)
           ^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.12/site-packages/jinja2/environment.py", line 1304, in render
    self.environment.handle_exception()
  File "/usr/local/lib/python3.12/site-packages/jinja2/environment.py", line 939, in handle_exception
    raise rewrite_traceback_stack(source=source)
  File "<template>", line 1, in top-level template code
  File "/usr/local/lib/python3.12/site-packages/jinja2/sandbox.py", line 327, in getattr
    value = getattr(obj, attribute)
            ^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/helpers/template.py", line 2632, in _fail_with_undefined_error
    return super()._fail_with_undefined_error(*args, **kwargs)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
jinja2.exceptions.UndefinedError: None has no element 0

The above exception was the direct cause of the following exception:

Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/helpers/template.py", line 713, in async_render_to_info
    render_info._result = self.async_render(
                          ^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/helpers/template.py", line 587, in async_render
    raise TemplateError(err) from err
homeassistant.exceptions.TemplateError: UndefinedError: None has no element 0
2024-06-25 10:30:56.158 ERROR (MainThread) [homeassistant.helpers.template] Template variable error: None has no element 0 when rendering '{{ state_attr('sensor.psa', 'energy')[0].charging.charging_mode }}'
2024-06-25 10:30:56.159 ERROR (MainThread) [homeassistant.components.template.template_entity] TemplateError('UndefinedError: None has no element 0') while processing template 'Template<template=({{ state_attr('sensor.psa', 'energy')[0].charging.charging_mode }}) renders=4>' for attribute '_attr_native_value' in entity 'sensor.psa_charging_mode'
2024-06-25 10:30:56.160 ERROR (MainThread) [homeassistant.helpers.template] Template variable error: None has no element 0 when rendering '{{ state_attr('sensor.psa', 'energy')[0].charging.charging_rate }}'
2024-06-25 10:30:56.161 ERROR (MainThread) [homeassistant.helpers.event] Error while processing template: Template<template=({{ state_attr('sensor.psa', 'energy')[0].charging.charging_rate }}) renders=2>
Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/helpers/template.py", line 585, in async_render
    render_result = _render_with_context(self.template, compiled, **kwargs)
                    ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/helpers/template.py", line 2600, in _render_with_context
    return template.render(**kwargs)
           ^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.12/site-packages/jinja2/environment.py", line 1304, in render
    self.environment.handle_exception()
  File "/usr/local/lib/python3.12/site-packages/jinja2/environment.py", line 939, in handle_exception
    raise rewrite_traceback_stack(source=source)
  File "<template>", line 1, in top-level template code
  File "/usr/local/lib/python3.12/site-packages/jinja2/sandbox.py", line 327, in getattr
    value = getattr(obj, attribute)
            ^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/helpers/template.py", line 2632, in _fail_with_undefined_error
    return super()._fail_with_undefined_error(*args, **kwargs)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
jinja2.exceptions.UndefinedError: None has no element 0

The above exception was the direct cause of the following exception:

Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/helpers/template.py", line 713, in async_render_to_info
    render_info._result = self.async_render(
                          ^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/helpers/template.py", line 587, in async_render
    raise TemplateError(err) from err
homeassistant.exceptions.TemplateError: UndefinedError: None has no element 0
2024-06-25 10:30:56.165 ERROR (MainThread) [homeassistant.helpers.template] Template variable error: None has no element 0 when rendering '{{ state_attr('sensor.psa', 'energy')[0].charging.charging_rate }}'
2024-06-25 10:30:56.166 ERROR (MainThread) [homeassistant.components.template.template_entity] TemplateError('UndefinedError: None has no element 0') while processing template 'Template<template=({{ state_attr('sensor.psa', 'energy')[0].charging.charging_rate }}) renders=4>' for attribute '_attr_native_value' in entity 'sensor.psa_charge_rate'
2024-06-25 10:30:56.170 ERROR (MainThread) [homeassistant.helpers.template] Template variable error: None has no element 0 when rendering '{{ state_attr('sensor.psa', 'energy')[0].charging.plugged }}'
2024-06-25 10:30:56.170 ERROR (MainThread) [homeassistant.helpers.event] Error while processing template: Template<template=({{ state_attr('sensor.psa', 'energy')[0].charging.plugged }}) renders=2>
Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/helpers/template.py", line 585, in async_render
    render_result = _render_with_context(self.template, compiled, **kwargs)
                    ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/helpers/template.py", line 2600, in _render_with_context
    return template.render(**kwargs)
           ^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.12/site-packages/jinja2/environment.py", line 1304, in render
    self.environment.handle_exception()
  File "/usr/local/lib/python3.12/site-packages/jinja2/environment.py", line 939, in handle_exception
    raise rewrite_traceback_stack(source=source)
  File "<template>", line 1, in top-level template code
  File "/usr/local/lib/python3.12/site-packages/jinja2/sandbox.py", line 327, in getattr
    value = getattr(obj, attribute)
            ^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/helpers/template.py", line 2632, in _fail_with_undefined_error
    return super()._fail_with_undefined_error(*args, **kwargs)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
jinja2.exceptions.UndefinedError: None has no element 0

The above exception was the direct cause of the following exception:

Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/helpers/template.py", line 713, in async_render_to_info
    render_info._result = self.async_render(
                          ^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/helpers/template.py", line 587, in async_render
    raise TemplateError(err) from err
homeassistant.exceptions.TemplateError: UndefinedError: None has no element 0
2024-06-25 10:30:56.180 ERROR (MainThread) [homeassistant.helpers.template] Template variable error: None has no element 0 when rendering '{{ state_attr('sensor.psa', 'energy')[0].charging.plugged }}'
2024-06-25 10:30:56.180 ERROR (MainThread) [homeassistant.components.template.template_entity] TemplateError('UndefinedError: None has no element 0') while processing template 'Template<template=({{ state_attr('sensor.psa', 'energy')[0].charging.plugged }}) renders=4>' for attribute '_state' in entity 'binary_sensor.psa_plugged_in'
2024-06-25 10:30:56.182 WARNING (MainThread) [homeassistant.helpers.template] Template variable warning: 'None' has no attribute 'moving' when rendering '{{ state_attr('sensor.psa', 'kinetic').moving }}'
2024-06-25 10:30:56.182 ERROR (MainThread) [homeassistant.helpers.template] Template variable error: 'None' has no attribute 'geometry' when rendering '{{ state_attr('sensor.psa', 'last_position').geometry.coordinates[1] }}'
2024-06-25 10:30:56.183 ERROR (MainThread) [homeassistant.helpers.event] Error while processing template: Template<template=({{ state_attr('sensor.psa', 'last_position').geometry.coordinates[1] }}) renders=2>
Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/helpers/template.py", line 585, in async_render
    render_result = _render_with_context(self.template, compiled, **kwargs)
                    ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/helpers/template.py", line 2600, in _render_with_context
    return template.render(**kwargs)
           ^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.12/site-packages/jinja2/environment.py", line 1304, in render
    self.environment.handle_exception()
  File "/usr/local/lib/python3.12/site-packages/jinja2/environment.py", line 939, in handle_exception
    raise rewrite_traceback_stack(source=source)
  File "<template>", line 1, in top-level template code
  File "/usr/local/lib/python3.12/site-packages/jinja2/sandbox.py", line 327, in getattr
    value = getattr(obj, attribute)
            ^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/helpers/template.py", line 2632, in _fail_with_undefined_error
    return super()._fail_with_undefined_error(*args, **kwargs)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
jinja2.exceptions.UndefinedError: 'None' has no attribute 'geometry'

The above exception was the direct cause of the following exception:

Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/helpers/template.py", line 713, in async_render_to_info
    render_info._result = self.async_render(
                          ^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/helpers/template.py", line 587, in async_render
    raise TemplateError(err) from err
homeassistant.exceptions.TemplateError: UndefinedError: 'None' has no attribute 'geometry'
2024-06-25 10:30:56.188 ERROR (MainThread) [homeassistant.helpers.template] Template variable error: 'None' has no attribute 'geometry' when rendering '{{ state_attr('sensor.psa', 'last_position').geometry.coordinates[0] }}'
2024-06-25 10:30:56.189 ERROR (MainThread) [homeassistant.helpers.event] Error while processing template: Template<template=({{ state_attr('sensor.psa', 'last_position').geometry.coordinates[0] }}) renders=2>
Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/helpers/template.py", line 585, in async_render
    render_result = _render_with_context(self.template, compiled, **kwargs)
                    ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/helpers/template.py", line 2600, in _render_with_context
    return template.render(**kwargs)
           ^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.12/site-packages/jinja2/environment.py", line 1304, in render
    self.environment.handle_exception()
  File "/usr/local/lib/python3.12/site-packages/jinja2/environment.py", line 939, in handle_exception
    raise rewrite_traceback_stack(source=source)
  File "<template>", line 1, in top-level template code
  File "/usr/local/lib/python3.12/site-packages/jinja2/sandbox.py", line 327, in getattr
    value = getattr(obj, attribute)
            ^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/helpers/template.py", line 2632, in _fail_with_undefined_error
    return super()._fail_with_undefined_error(*args, **kwargs)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
jinja2.exceptions.UndefinedError: 'None' has no attribute 'geometry'

The above exception was the direct cause of the following exception:

Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/helpers/template.py", line 713, in async_render_to_info
    render_info._result = self.async_render(
                          ^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/helpers/template.py", line 587, in async_render
    raise TemplateError(err) from err
homeassistant.exceptions.TemplateError: UndefinedError: 'None' has no attribute 'geometry'
2024-06-25 10:30:56.193 WARNING (MainThread) [homeassistant.helpers.template] Template variable warning: 'None' has no attribute 'moving' when rendering '{{ state_attr('sensor.psa', 'kinetic').moving }}'
2024-06-25 10:30:56.194 ERROR (MainThread) [homeassistant.helpers.template] Template variable error: 'None' has no attribute 'geometry' when rendering '{{ state_attr('sensor.psa', 'last_position').geometry.coordinates[1] }}'
2024-06-25 10:30:56.195 ERROR (MainThread) [homeassistant.helpers.template] Template variable error: 'None' has no attribute 'geometry' when rendering '{{ state_attr('sensor.psa', 'last_position').geometry.coordinates[0] }}'
2024-06-25 10:30:56.196 ERROR (MainThread) [homeassistant.components.template.template_entity] TemplateError('UndefinedError: 'None' has no attribute 'geometry'') while processing template 'Template<template=({{ state_attr('sensor.psa', 'last_position').geometry.coordinates[1] }}) renders=4>' for attribute 'latitude' in entity 'binary_sensor.psa_position'
2024-06-25 10:30:56.196 ERROR (MainThread) [homeassistant.components.template.template_entity] TemplateError('UndefinedError: 'None' has no attribute 'geometry'') while processing template 'Template<template=({{ state_attr('sensor.psa', 'last_position').geometry.coordinates[0] }}) renders=4>' for attribute 'longitude' in entity 'binary_sensor.psa_position'
2024-06-25 10:30:56.283 ERROR (MainThread) [homeassistant.helpers.event] Error while processing template: Template<template=({{ (states('sensor.total_imported_energy_cost')) | float |round(2) }}) renders=2>
Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/helpers/template.py", line 2224, in forgiving_float_filter
    return float(value)
           ^^^^^^^^^^^^
ValueError: could not convert string to float: 'unavailable'

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/helpers/template.py", line 585, in async_render
    render_result = _render_with_context(self.template, compiled, **kwargs)
                    ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/helpers/template.py", line 2600, in _render_with_context
    return template.render(**kwargs)
           ^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.12/site-packages/jinja2/environment.py", line 1304, in render
    self.environment.handle_exception()
  File "/usr/local/lib/python3.12/site-packages/jinja2/environment.py", line 939, in handle_exception
    raise rewrite_traceback_stack(source=source)
  File "<template>", line 1, in top-level template code
  File "/usr/src/homeassistant/homeassistant/helpers/template.py", line 2227, in forgiving_float_filter
    raise_no_default("float", value)
  File "/usr/src/homeassistant/homeassistant/helpers/template.py", line 1849, in raise_no_default
    raise ValueError(
ValueError: Template error: float got invalid input 'unavailable' when rendering template '{{ (states('sensor.total_imported_energy_cost')) | float |round(2) }}' but no default was specified

The above exception was the direct cause of the following exception:

Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/helpers/template.py", line 713, in async_render_to_info
    render_info._result = self.async_render(
                          ^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/helpers/template.py", line 587, in async_render
    raise TemplateError(err) from err
homeassistant.exceptions.TemplateError: ValueError: Template error: float got invalid input 'unavailable' when rendering template '{{ (states('sensor.total_imported_energy_cost')) | float |round(2) }}' but no default was specified
2024-06-25 10:30:56.287 ERROR (MainThread) [homeassistant.components.template.template_entity] TemplateError('ValueError: Template error: float got invalid input 'unavailable' when rendering template '{{ (states('sensor.total_imported_energy_cost')) | float |round(2) }}' but no default was specified') while processing template 'Template<template=({{ (states('sensor.total_imported_energy_cost')) | float |round(2) }}) renders=4>' for attribute '_attr_native_value' in entity 'sensor.daily_imported_energy_cost'
2024-06-25 10:30:56.289 ERROR (MainThread) [homeassistant.helpers.event] Error while processing template: Template<template=({{ (states('sensor.total_exported_energy_compensation')) | float |round(2) }}) renders=2>
Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/helpers/template.py", line 2224, in forgiving_float_filter
    return float(value)
           ^^^^^^^^^^^^
ValueError: could not convert string to float: 'unavailable'

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/helpers/template.py", line 585, in async_render
    render_result = _render_with_context(self.template, compiled, **kwargs)
                    ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/helpers/template.py", line 2600, in _render_with_context
    return template.render(**kwargs)
           ^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.12/site-packages/jinja2/environment.py", line 1304, in render
    self.environment.handle_exception()
  File "/usr/local/lib/python3.12/site-packages/jinja2/environment.py", line 939, in handle_exception
    raise rewrite_traceback_stack(source=source)
  File "<template>", line 1, in top-level template code
  File "/usr/src/homeassistant/homeassistant/helpers/template.py", line 2227, in forgiving_float_filter
    raise_no_default("float", value)
  File "/usr/src/homeassistant/homeassistant/helpers/template.py", line 1849, in raise_no_default
    raise ValueError(
ValueError: Template error: float got invalid input 'unavailable' when rendering template '{{ (states('sensor.total_exported_energy_compensation')) | float |round(2) }}' but no default was specified

The above exception was the direct cause of the following exception:

Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/helpers/template.py", line 713, in async_render_to_info
    render_info._result = self.async_render(
                          ^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/helpers/template.py", line 587, in async_render
    raise TemplateError(err) from err
homeassistant.exceptions.TemplateError: ValueError: Template error: float got invalid input 'unavailable' when rendering template '{{ (states('sensor.total_exported_energy_compensation')) | float |round(2) }}' but no default was specified
2024-06-25 10:30:56.294 ERROR (MainThread) [homeassistant.components.template.template_entity] TemplateError('ValueError: Template error: float got invalid input 'unavailable' when rendering template '{{ (states('sensor.total_exported_energy_compensation')) | float |round(2) }}' but no default was specified') while processing template 'Template<template=({{ (states('sensor.total_exported_energy_compensation')) | float |round(2) }}) renders=4>' for attribute '_attr_native_value' in entity 'sensor.daily_exported_energy_compensation_2'
2024-06-25 10:30:56.353 WARNING (MainThread) [homeassistant.helpers.frame] Detected that custom integration 'hacs' accesses hass.helpers.event. This is deprecated and will stop working in Home Assistant 2024.11, it should be updated to import functions used from event directly at custom_components/hacs/base.py, line 630: self.hass.helpers.event.async_track_time_interval(, please create a bug report at https://github.com/hacs/integration/issues
2024-06-25 10:31:11.297 WARNING (MainThread) [homeassistant.core] Something is blocking Home Assistant from wrapping up the start up phase. We're going to continue anyway. Please report the following info at https://github.com/home-assistant/core/issues: zha.binary_sensor, tag, media_source, xiaomi_ble.binary_sensor, person, energy.sensor, update, goecharger_mqtt.switch, calendar, history, shelly.event, tankerkoenig, sun.sensor, weather, tradfri.switch, homekit_controller.light, remote, fritz, homeassistant, raspberry_pi, dlna_dmr, tuya.button, utility_meter, siren, template.sensor, min_max, brother, fritz.button, apple_tv, ipp.sensor, fritzbox.light, esphome.light, websocket_api, tradfri.fan, automation, homekit_controller.sensor, influxdb, tuya, intent, dlna_dmr.media_player, hue.light, sonos.switch, apple_tv.media_player, zha.switch, trace, zone, tasmota.binary_sensor, sonos.binary_sensor, meross_cloud.humidifier, hardware, tuya.switch, tradfri.cover, waste_collection_schedule, electrolux_status, tuya.select, shelly, fritzbox.climate, frontend, shelly.light, goecharger_mqtt, webostv.notify, input_boolean, alarm_control_panel, telegram_bot, number, image_upload, usb, shelly.sensor, zha.climate, timer, zha.button, workday, rest.sensor, zha.number, homekit, input_datetime, system_health, light, min_max.sensor, esphome.update, script, tuya.camera, tradfri.sensor, workday.binary_sensor, mobile_app.binary_sensor, switch, panel_custom, teamtracker, zha.light, electrolux_status.number, template.binary_sensor, mqtt.lock, hassio, homeassistant_hardware, input_select, hue.switch, lock, bluetooth, hue.binary_sensor, select, hassio.binary_sensor, zha.update, waste_collection_schedule.calendar, zha.cover, hue.sensor, met, hassio.update, alarmo, webostv.media_player, default_config, device_tracker, homekit_controller.select, fritzbox.sensor, lovelace, govee_lan.light, xiaomi_ble.event, zha, waste_collection_schedule.sensor, tuya.scene, samsungtv.remote, picnic.todo, ssdp, fan, apple_tv.remote, persistent_notification, tuya.number, logger, upnp.sensor, tuya.vacuum, counter, diagnostics, stream, met.weather, group, sonos.number, button, cloud.tts, switch_as_x.light, application_credentials, eufylife_ble.sensor, ffmpeg, tuya.light, goecharger_mqtt.number, bring.todo, tasmota.switch, goecharger_mqtt.binary_sensor, notify, logbook, homeassistant_alerts, analytics, electrolux_status.sensor, xiaomi_ble, electrolux_status.switch, tasmota.sensor, meross_cloud.switch, file_upload, zha.alarm_control_panel, fritz.device_tracker, modbus.sensor, meross_cloud.light, webhook, zeroconf, search, google_translate, webostv, tankerkoenig.binary_sensor, bluetooth_adapters, conversation, mqtt.binary_sensor, onboarding, shelly.button, samsungtv, goecharger_mqtt.select, xiaomi_ble.sensor, sensor, energy, picnic.sensor, system_log, tasmota.light, event, config, upnp.binary_sensor, homeassistant_sky_connect, electrolux_status.binary_sensor, goecharger_mqtt.sensor, shelly.valve, tuya.fan, fritz.image, media_player, shelly.binary_sensor, fritzbox.switch, http, fritz.binary_sensor, hue.event, climate, electrolux_status.button, homeassistant.scene, valve, input_number, shelly.switch, tuya.humidifier, fritz.update, repairs, homekit_controller, fritzbox.button, homekit_controller.fan, sonos.sensor, fritzbox, tankerkoenig.sensor, mqtt.sensor, rest, fritz.sensor, meross_cloud.sensor, samsungtv.media_player, sonos, brother.sensor, esphome.button, zha.fan, tradfri, wyoming.stt, rpi_power.binary_sensor, map, assist_pipeline, mobile_app, mobile_app.notify, shelly.update, telegram.notify, zha.sensor, tuya.cover, presence_simulation, image, wake_word, meross_cloud.cover, forecast_solar.sensor, fritzbox.cover, ipp, shelly.cover, hue, esphome.switch, zha.device_tracker, input_button, sun, rest_command, local_todo.todo, backup, wyoming, tasmota, modbus, device_automation, template, tuya.alarm_control_panel, goecharger_mqtt.button, cover, meross_cloud.climate, fritz.switch, tuya.binary_sensor, binary_sensor, mobile_app.device_tracker, wyoming.tts, fritzbox.binary_sensor, vacuum, scene, google_translate.tts, cloud, upnp, mqtt.button, humidifier, teamtracker.sensor, tuya.sensor, homekit_controller.switch, hacs.sensor, zha.siren, local_todo, zha.lock, recorder, my, hacs, schedule, tradfri.light, eufylife_ble, tuya.siren, sonos.media_player, auth, tts, electrolux_status.select, thread, homekit_controller.button, tuya.climate, mobile_app.sensor, forecast_solar, radio_browser, input_text, bring, dhcp, switch_as_x, tasmota.fan, todo, meross_cloud, zha.select, api, esphome.binary_sensor, utility_meter.sensor, stt, presence_simulation.switch, hue.scene, picnic, mqtt, alarmo.alarm_control_panel, hassio.sensor, govee_lan, rpi_power, camera, network, blueprint, tasmota.cover, group.light, esphome The system is waiting for tasks: {<Task pending name='Task-3239' coro=<HacsBase.startup_tasks() running at /config/custom_components/hacs/base.py:695> wait_for=<_GatheringFuture pending cb=[Task.task_wakeup()]> cb=[set.remove()]>}
2024-06-25 10:31:11.684 ERROR (MainThread) [homeassistant.components.rest.data] Error fetching data: http://127.0.0.1:5000/charge_control?vin=VXEVZZKXZPZ043454 failed with All connection attempts failed
2024-06-25 10:31:11.685 ERROR (MainThread) [homeassistant.components.rest.data] Error fetching data: http://127.0.0.1:5000/get_vehicleinfo/VXEVZZKXZPZ043454 failed with All connection attempts failed
2024-06-25 10:31:11.743 WARNING (MainThread) [homeassistant.components.homekit] The bridge HASS Bridge Olli has entity media_player.samsung_tv. For best performance, and to prevent unexpected unavailability, create and pair a separate HomeKit instance in accessory mode for this entity
2024-06-25 10:31:26.761 WARNING (MainThread) [homeassistant.helpers.entity] Updating state for sensor.go_echarger_230375_nrg_5 (<class 'custom_components.goecharger_mqtt.sensor.GoEChargerSensor'>) took 0.943 seconds. Please create a bug report at https://github.com/syssi/homeassistant-goecharger-mqtt/issues
2024-06-25 10:31:41.424 ERROR (MainThread) [homeassistant.components.homeassistant_alerts] Timeout fetching homeassistant_alerts data
2024-06-25 10:31:58.424 WARNING (MainThread) [custom_components.hacs] A timeout of 60! seconds was encountered while downloading https://raw.githubusercontent.com/thomasloven/lovelace-card-tools/11/info.md, using over 60 seconds to download a single file is not normal. This is not a problem with HACS but how your host communicates with GitHub. Retrying up to 5 times to mask/hide your host/network problems to stop the flow of issues opened about it. Tries left 4
2024-06-25 10:31:58.426 WARNING (MainThread) [custom_components.hacs] A timeout of 60! seconds was encountered while downloading https://raw.githubusercontent.com/piitaya/lovelace-mushroom-themes/v0.0.9/README.md, using over 60 seconds to download a single file is not normal. This is not a problem with HACS but how your host communicates with GitHub. Retrying up to 5 times to mask/hide your host/network problems to stop the flow of issues opened about it. Tries left 4
2024-06-25 10:31:59.425 WARNING (MainThread) [custom_components.hacs] A timeout of 60! seconds was encountered while downloading https://raw.githubusercontent.com/nielsfaber/alarmo-card/v1.5.2/README.md, using over 60 seconds to download a single file is not normal. This is not a problem with HACS but how your host communicates with GitHub. Retrying up to 5 times to mask/hide your host/network problems to stop the flow of issues opened about it. Tries left 4
2024-06-25 10:31:59.427 WARNING (MainThread) [custom_components.hacs] A timeout of 60! seconds was encountered while downloading https://raw.githubusercontent.com/humbertogontijo/homeassistant-roborock/1.0.13/info.md, using over 60 seconds to download a single file is not normal. This is not a problem with HACS but how your host communicates with GitHub. Retrying up to 5 times to mask/hide your host/network problems to stop the flow of issues opened about it. Tries left 4
2024-06-25 10:32:11.935 ERROR (MainThread) [homeassistant.components.rest.data] Error fetching data: http://127.0.0.1:5000/charge_control?vin=VXEVZZKXZPZ043454 failed with All connection attempts failed
2024-06-25 10:32:11.936 ERROR (MainThread) [homeassistant.components.rest.data] Error fetching data: http://127.0.0.1:5000/get_vehicleinfo/VXEVZZKXZPZ043454 failed with All connection attempts failed
2024-06-25 10:32:48.772 ERROR (MainThread) [meross_iot.manager] Timeout occurred while waiting a response for message b'{"header":{"from":"/app/756017-b9080411ed1ee3b606745a75093bd7a6/subscribe","messageId":"86584c56bb7fc755957d3cb0d3105c43","method":"GET","namespace":"Appliance.System.Ability","payloadVersion":1,"sign":"95d76c258f3fcee912ebf74e57ec3494","timestamp":1719304359,"triggerSrc":"Android","uuid":"2006287592740090816348e1e920fb15"},"payload":{}}' sent to device uuid 2006287592740090816348e1e920fb15. Timeout was: 10.000000 seconds. Mqtt Host: mqtt-eu-4.meross.com:443.
2024-06-25 10:32:48.772 WARNING (MainThread) [meross_iot.manager] Device Smart Plug (2006287592740090816348e1e920fb15) is online, but timeout occurred when fetching its abilities. 
2024-06-25 10:32:58.783 ERROR (MainThread) [meross_iot.manager] Timeout occurred while waiting a response for message b'{"header":{"from":"/app/756017-b9080411ed1ee3b606745a75093bd7a6/subscribe","messageId":"a9a9812386ab144d246c3414ae2fc8a5","method":"GET","namespace":"Appliance.System.Ability","payloadVersion":1,"sign":"00b9cf2ee71ad31bf66d40d847727225","timestamp":1719304369,"triggerSrc":"Android","uuid":"2004234441425451850648e1e91ac61b"},"payload":{}}' sent to device uuid 2004234441425451850648e1e91ac61b. Timeout was: 10.000000 seconds. Mqtt Host: mqtt-eu-4.meross.com:443.
2024-06-25 10:32:58.783 WARNING (MainThread) [meross_iot.manager] Device Smart Plug (2004234441425451850648e1e91ac61b) is online, but timeout occurred when fetching its abilities. 
2024-06-25 10:33:00.424 WARNING (MainThread) [custom_components.hacs] A timeout of 60! seconds was encountered while downloading https://raw.githubusercontent.com/piitaya/lovelace-mushroom-themes/v0.0.9/README.md, using over 60 seconds to download a single file is not normal. This is not a problem with HACS but how your host communicates with GitHub. Retrying up to 5 times to mask/hide your host/network problems to stop the flow of issues opened about it. Tries left 3
2024-06-25 10:33:00.425 WARNING (MainThread) [custom_components.hacs] A timeout of 60! seconds was encountered while downloading https://raw.githubusercontent.com/thomasloven/lovelace-card-tools/11/info.md, using over 60 seconds to download a single file is not normal. This is not a problem with HACS but how your host communicates with GitHub. Retrying up to 5 times to mask/hide your host/network problems to stop the flow of issues opened about it. Tries left 3
2024-06-25 10:33:01.423 WARNING (MainThread) [custom_components.hacs] A timeout of 60! seconds was encountered while downloading https://raw.githubusercontent.com/humbertogontijo/homeassistant-roborock/1.0.13/info.md, using over 60 seconds to download a single file is not normal. This is not a problem with HACS but how your host communicates with GitHub. Retrying up to 5 times to mask/hide your host/network problems to stop the flow of issues opened about it. Tries left 3
2024-06-25 10:33:01.425 WARNING (MainThread) [custom_components.hacs] A timeout of 60! seconds was encountered while downloading https://raw.githubusercontent.com/nielsfaber/alarmo-card/v1.5.2/README.md, using over 60 seconds to download a single file is not normal. This is not a problem with HACS but how your host communicates with GitHub. Retrying up to 5 times to mask/hide your host/network problems to stop the flow of issues opened about it. Tries left 3
2024-06-25 10:33:08.788 ERROR (MainThread) [meross_iot.manager] Timeout occurred while waiting a response for message b'{"header":{"from":"/app/756017-b9080411ed1ee3b606745a75093bd7a6/subscribe","messageId":"0bfcc159f70a00aeffcae8d3d465ac0d","method":"GET","namespace":"Appliance.System.Ability","payloadVersion":1,"sign":"235cab3b4603993240e306a36352d42f","timestamp":1719304379,"triggerSrc":"Android","uuid":"2012109611902951853348e1e93f2c1f"},"payload":{}}' sent to device uuid 2012109611902951853348e1e93f2c1f. Timeout was: 10.000000 seconds. Mqtt Host: mqtt-eu-4.meross.com:443.
2024-06-25 10:33:08.789 WARNING (MainThread) [meross_iot.manager] Device Smart Plug (2012109611902951853348e1e93f2c1f) is online, but timeout occurred when fetching its abilities. 
2024-06-25 10:33:18.797 ERROR (MainThread) [meross_iot.manager] Timeout occurred while waiting a response for message b'{"header":{"from":"/app/756017-b9080411ed1ee3b606745a75093bd7a6/subscribe","messageId":"f611ad77087d42ea862867eaee15745f","method":"GET","namespace":"Appliance.System.Ability","payloadVersion":1,"sign":"6edf87d8253198af6440ef622cde170b","timestamp":1719304389,"triggerSrc":"Android","uuid":"2012102503141851853348e1e93f6509"},"payload":{}}' sent to device uuid 2012102503141851853348e1e93f6509. Timeout was: 10.000000 seconds. Mqtt Host: mqtt-eu-4.meross.com:443.
2024-06-25 10:33:18.798 WARNING (MainThread) [meross_iot.manager] Device Opti (2012102503141851853348e1e93f6509) is online, but timeout occurred when fetching its abilities. 
2024-06-25 10:33:41.952 ERROR (MainThread) [homeassistant.components.rest.data] Error fetching data: http://127.0.0.1:5000/charge_control?vin=VXEVZZKXZPZ043454 failed with All connection attempts failed
2024-06-25 10:33:41.953 ERROR (MainThread) [homeassistant.components.rest.data] Error fetching data: http://127.0.0.1:5000/get_vehicleinfo/VXEVZZKXZPZ043454 failed with All connection attempts failed
2024-06-25 10:34:02.424 WARNING (MainThread) [custom_components.hacs] A timeout of 60! seconds was encountered while downloading https://raw.githubusercontent.com/thomasloven/lovelace-card-tools/11/info.md, using over 60 seconds to download a single file is not normal. This is not a problem with HACS but how your host communicates with GitHub. Retrying up to 5 times to mask/hide your host/network problems to stop the flow of issues opened about it. Tries left 2
2024-06-25 10:34:02.425 WARNING (MainThread) [custom_components.hacs] A timeout of 60! seconds was encountered while downloading https://raw.githubusercontent.com/piitaya/lovelace-mushroom-themes/v0.0.9/README.md, using over 60 seconds to download a single file is not normal. This is not a problem with HACS but how your host communicates with GitHub. Retrying up to 5 times to mask/hide your host/network problems to stop the flow of issues opened about it. Tries left 2
2024-06-25 10:34:03.424 WARNING (MainThread) [custom_components.hacs] A timeout of 60! seconds was encountered while downloading https://raw.githubusercontent.com/nielsfaber/alarmo-card/v1.5.2/README.md, using over 60 seconds to download a single file is not normal. This is not a problem with HACS but how your host communicates with GitHub. Retrying up to 5 times to mask/hide your host/network problems to stop the flow of issues opened about it. Tries left 2
2024-06-25 10:34:03.426 WARNING (MainThread) [custom_components.hacs] A timeout of 60! seconds was encountered while downloading https://raw.githubusercontent.com/humbertogontijo/homeassistant-roborock/1.0.13/info.md, using over 60 seconds to download a single file is not normal. This is not a problem with HACS but how your host communicates with GitHub. Retrying up to 5 times to mask/hide your host/network problems to stop the flow of issues opened about it. Tries left 2
2024-06-25 10:34:48.757 ERROR (MainThread) [meross_iot.manager] Timeout occurred while waiting a response for message b'{"header":{"from":"/app/756017-b9080411ed1ee3b606745a75093bd7a6/subscribe","messageId":"0c829b37ea558023d04d81dd0985707d","method":"GET","namespace":"Appliance.System.Ability","payloadVersion":1,"sign":"7edbe16669a8c12f6938031f1e4fdc68","timestamp":1719304479,"triggerSrc":"Android","uuid":"2006287592740090816348e1e920fb15"},"payload":{}}' sent to device uuid 2006287592740090816348e1e920fb15. Timeout was: 10.000000 seconds. Mqtt Host: mqtt-eu-4.meross.com:443.
2024-06-25 10:34:48.757 WARNING (MainThread) [meross_iot.manager] Device Smart Plug (2006287592740090816348e1e920fb15) is online, but timeout occurred when fetching its abilities. 
2024-06-25 10:34:58.763 ERROR (MainThread) [meross_iot.manager] Timeout occurred while waiting a response for message b'{"header":{"from":"/app/756017-b9080411ed1ee3b606745a75093bd7a6/subscribe","messageId":"03c32883daf069098e8eef42c4a460c0","method":"GET","namespace":"Appliance.System.Ability","payloadVersion":1,"sign":"5446422cb551c9e875128d1661e45f70","timestamp":1719304489,"triggerSrc":"Android","uuid":"2012102503141851853348e1e93f6509"},"payload":{}}' sent to device uuid 2012102503141851853348e1e93f6509. Timeout was: 10.000000 seconds. Mqtt Host: mqtt-eu-4.meross.com:443.
2024-06-25 10:34:58.764 WARNING (MainThread) [meross_iot.manager] Device Opti (2012102503141851853348e1e93f6509) is online, but timeout occurred when fetching its abilities. 
2024-06-25 10:35:04.424 WARNING (MainThread) [custom_components.hacs] A timeout of 60! seconds was encountered while downloading https://raw.githubusercontent.com/thomasloven/lovelace-card-tools/11/info.md, using over 60 seconds to download a single file is not normal. This is not a problem with HACS but how your host communicates with GitHub. Retrying up to 5 times to mask/hide your host/network problems to stop the flow of issues opened about it. Tries left 1
2024-06-25 10:35:04.427 WARNING (MainThread) [custom_components.hacs] A timeout of 60! seconds was encountered while downloading https://raw.githubusercontent.com/piitaya/lovelace-mushroom-themes/v0.0.9/README.md, using over 60 seconds to download a single file is not normal. This is not a problem with HACS but how your host communicates with GitHub. Retrying up to 5 times to mask/hide your host/network problems to stop the flow of issues opened about it. Tries left 1
2024-06-25 10:35:05.427 WARNING (MainThread) [custom_components.hacs] A timeout of 60! seconds was encountered while downloading https://raw.githubusercontent.com/nielsfaber/alarmo-card/v1.5.2/README.md, using over 60 seconds to download a single file is not normal. This is not a problem with HACS but how your host communicates with GitHub. Retrying up to 5 times to mask/hide your host/network problems to stop the flow of issues opened about it. Tries left 1
2024-06-25 10:35:05.433 WARNING (MainThread) [custom_components.hacs] A timeout of 60! seconds was encountered while downloading https://raw.githubusercontent.com/humbertogontijo/homeassistant-roborock/1.0.13/info.md, using over 60 seconds to download a single file is not normal. This is not a problem with HACS but how your host communicates with GitHub. Retrying up to 5 times to mask/hide your host/network problems to stop the flow of issues opened about it. Tries left 1
2024-06-25 10:35:08.767 ERROR (MainThread) [meross_iot.manager] Timeout occurred while waiting a response for message b'{"header":{"from":"/app/756017-b9080411ed1ee3b606745a75093bd7a6/subscribe","messageId":"36a59031d31302197202afac055dc11f","method":"GET","namespace":"Appliance.System.Ability","payloadVersion":1,"sign":"491b141d27302a469c9d75bd445753a9","timestamp":1719304499,"triggerSrc":"Android","uuid":"2012109611902951853348e1e93f2c1f"},"payload":{}}' sent to device uuid 2012109611902951853348e1e93f2c1f. Timeout was: 10.000000 seconds. Mqtt Host: mqtt-eu-4.meross.com:443.
2024-06-25 10:35:08.768 WARNING (MainThread) [meross_iot.manager] Device Smart Plug (2012109611902951853348e1e93f2c1f) is online, but timeout occurred when fetching its abilities. 
2024-06-25 10:35:18.772 ERROR (MainThread) [meross_iot.manager] Timeout occurred while waiting a response for message b'{"header":{"from":"/app/756017-b9080411ed1ee3b606745a75093bd7a6/subscribe","messageId":"2f1432514ded168c539c52f90cd7d81c","method":"GET","namespace":"Appliance.System.Ability","payloadVersion":1,"sign":"07c3fd8a00cb6220ef5d3a044ca7dfb7","timestamp":1719304509,"triggerSrc":"Android","uuid":"2004234441425451850648e1e91ac61b"},"payload":{}}' sent to device uuid 2004234441425451850648e1e91ac61b. Timeout was: 10.000000 seconds. Mqtt Host: mqtt-eu-4.meross.com:443.
2024-06-25 10:35:18.773 WARNING (MainThread) [meross_iot.manager] Device Smart Plug (2004234441425451850648e1e91ac61b) is online, but timeout occurred when fetching its abilities. 
2024-06-25 10:35:41.974 ERROR (MainThread) [homeassistant.components.rest.data] Error fetching data: http://127.0.0.1:5000/charge_control?vin=VXEVZZKXZPZ043454 failed with All connection attempts failed
2024-06-25 10:35:41.975 ERROR (MainThread) [homeassistant.components.rest.data] Error fetching data: http://127.0.0.1:5000/get_vehicleinfo/VXEVZZKXZPZ043454 failed with All connection attempts failed
2024-06-25 10:36:06.424 WARNING (MainThread) [custom_components.hacs] A timeout of 60! seconds was encountered while downloading https://raw.githubusercontent.com/piitaya/lovelace-mushroom-themes/v0.0.9/README.md, using over 60 seconds to download a single file is not normal. This is not a problem with HACS but how your host communicates with GitHub. Retrying up to 5 times to mask/hide your host/network problems to stop the flow of issues opened about it. Tries left 0
2024-06-25 10:36:06.427 WARNING (MainThread) [custom_components.hacs] A timeout of 60! seconds was encountered while downloading https://raw.githubusercontent.com/thomasloven/lovelace-card-tools/11/info.md, using over 60 seconds to download a single file is not normal. This is not a problem with HACS but how your host communicates with GitHub. Retrying up to 5 times to mask/hide your host/network problems to stop the flow of issues opened about it. Tries left 0
2024-06-25 10:36:07.424 WARNING (MainThread) [custom_components.hacs] A timeout of 60! seconds was encountered while downloading https://raw.githubusercontent.com/nielsfaber/alarmo-card/v1.5.2/README.md, using over 60 seconds to download a single file is not normal. This is not a problem with HACS but how your host communicates with GitHub. Retrying up to 5 times to mask/hide your host/network problems to stop the flow of issues opened about it. Tries left 0
2024-06-25 10:36:07.426 WARNING (MainThread) [custom_components.hacs] A timeout of 60! seconds was encountered while downloading https://raw.githubusercontent.com/humbertogontijo/homeassistant-roborock/1.0.13/info.md, using over 60 seconds to download a single file is not normal. This is not a problem with HACS but how your host communicates with GitHub. Retrying up to 5 times to mask/hide your host/network problems to stop the flow of issues opened about it. Tries left 0
2024-06-25 10:36:48.781 ERROR (MainThread) [meross_iot.manager] Timeout occurred while waiting a response for message b'{"header":{"from":"/app/756017-b9080411ed1ee3b606745a75093bd7a6/subscribe","messageId":"20b59d511e9d9c312c169d8702e608e2","method":"GET","namespace":"Appliance.System.Ability","payloadVersion":1,"sign":"6d3b9f1b80428b3d4b0b69cb0673c01b","timestamp":1719304599,"triggerSrc":"Android","uuid":"2004234441425451850648e1e91ac61b"},"payload":{}}' sent to device uuid 2004234441425451850648e1e91ac61b. Timeout was: 10.000000 seconds. Mqtt Host: mqtt-eu-4.meross.com:443.
2024-06-25 10:36:48.782 WARNING (MainThread) [meross_iot.manager] Device Smart Plug (2004234441425451850648e1e91ac61b) is online, but timeout occurred when fetching its abilities. 
2024-06-25 10:36:58.785 ERROR (MainThread) [meross_iot.manager] Timeout occurred while waiting a response for message b'{"header":{"from":"/app/756017-b9080411ed1ee3b606745a75093bd7a6/subscribe","messageId":"c24a5f2bce988524c7d343706024e8a8","method":"GET","namespace":"Appliance.System.Ability","payloadVersion":1,"sign":"2c27295ac3a703d22f050e0936507624","timestamp":1719304609,"triggerSrc":"Android","uuid":"2006287592740090816348e1e920fb15"},"payload":{}}' sent to device uuid 2006287592740090816348e1e920fb15. Timeout was: 10.000000 seconds. Mqtt Host: mqtt-eu-4.meross.com:443.
2024-06-25 10:36:58.786 WARNING (MainThread) [meross_iot.manager] Device Smart Plug (2006287592740090816348e1e920fb15) is online, but timeout occurred when fetching its abilities. 
2024-06-25 10:37:08.795 ERROR (MainThread) [meross_iot.manager] Timeout occurred while waiting a response for message b'{"header":{"from":"/app/756017-b9080411ed1ee3b606745a75093bd7a6/subscribe","messageId":"8bf706251d53bb95609bed701fef4d51","method":"GET","namespace":"Appliance.System.Ability","payloadVersion":1,"sign":"1309669216ab4928273775283e06b7b9","timestamp":1719304619,"triggerSrc":"Android","uuid":"2012102503141851853348e1e93f6509"},"payload":{}}' sent to device uuid 2012102503141851853348e1e93f6509. Timeout was: 10.000000 seconds. Mqtt Host: mqtt-eu-4.meross.com:443.
2024-06-25 10:37:08.796 WARNING (MainThread) [meross_iot.manager] Device Opti (2012102503141851853348e1e93f6509) is online, but timeout occurred when fetching its abilities. 
2024-06-25 10:37:18.804 ERROR (MainThread) [meross_iot.manager] Timeout occurred while waiting a response for message b'{"header":{"from":"/app/756017-b9080411ed1ee3b606745a75093bd7a6/subscribe","messageId":"dfe2b3d7ad07cbef6588bbca50761d95","method":"GET","namespace":"Appliance.System.Ability","payloadVersion":1,"sign":"2dbc014a84f92558839889a176043bb4","timestamp":1719304629,"triggerSrc":"Android","uuid":"2012109611902951853348e1e93f2c1f"},"payload":{}}' sent to device uuid 2012109611902951853348e1e93f2c1f. Timeout was: 10.000000 seconds. Mqtt Host: mqtt-eu-4.meross.com:443.
2024-06-25 10:37:18.804 WARNING (MainThread) [meross_iot.manager] Device Smart Plug (2012109611902951853348e1e93f2c1f) is online, but timeout occurred when fetching its abilities. 
2024-06-25 10:38:12.000 ERROR (MainThread) [homeassistant.components.rest.data] Error fetching data: http://127.0.0.1:5000/charge_control?vin=VXEVZZKXZPZ043454 failed with All connection attempts failed
2024-06-25 10:38:12.001 ERROR (MainThread) [homeassistant.components.rest.data] Error fetching data: http://127.0.0.1:5000/get_vehicleinfo/VXEVZZKXZPZ043454 failed with All connection attempts failed
2024-06-25 10:38:48.813 ERROR (MainThread) [meross_iot.manager] Timeout occurred while waiting a response for message b'{"header":{"from":"/app/756017-b9080411ed1ee3b606745a75093bd7a6/subscribe","messageId":"36ccb23dfdfaae5f40776d9063a687da","method":"GET","namespace":"Appliance.System.Ability","payloadVersion":1,"sign":"a8f92070efb532ccd83a7a3c6f7e468c","timestamp":1719304719,"triggerSrc":"Android","uuid":"2012109611902951853348e1e93f2c1f"},"payload":{}}' sent to device uuid 2012109611902951853348e1e93f2c1f. Timeout was: 10.000000 seconds. Mqtt Host: mqtt-eu-4.meross.com:443.
2024-06-25 10:38:48.813 WARNING (MainThread) [meross_iot.manager] Device Smart Plug (2012109611902951853348e1e93f2c1f) is online, but timeout occurred when fetching its abilities. 
2024-06-25 10:38:58.820 ERROR (MainThread) [meross_iot.manager] Timeout occurred while waiting a response for message b'{"header":{"from":"/app/756017-b9080411ed1ee3b606745a75093bd7a6/subscribe","messageId":"a8a190c639a3fd632fba9dfa2d23fa08","method":"GET","namespace":"Appliance.System.Ability","payloadVersion":1,"sign":"ecdaf02a005e3e42f00d188931149029","timestamp":1719304729,"triggerSrc":"Android","uuid":"2006287592740090816348e1e920fb15"},"payload":{}}' sent to device uuid 2006287592740090816348e1e920fb15. Timeout was: 10.000000 seconds. Mqtt Host: mqtt-eu-4.meross.com:443.
2024-06-25 10:38:58.821 WARNING (MainThread) [meross_iot.manager] Device Smart Plug (2006287592740090816348e1e920fb15) is online, but timeout occurred when fetching its abilities. 
2024-06-25 10:39:08.828 ERROR (MainThread) [meross_iot.manager] Timeout occurred while waiting a response for message b'{"header":{"from":"/app/756017-b9080411ed1ee3b606745a75093bd7a6/subscribe","messageId":"32115a2a839bb4f85e8ad841ea422aa1","method":"GET","namespace":"Appliance.System.Ability","payloadVersion":1,"sign":"2a40782e80ebea24f2797aad6b11d767","timestamp":1719304739,"triggerSrc":"Android","uuid":"2004234441425451850648e1e91ac61b"},"payload":{}}' sent to device uuid 2004234441425451850648e1e91ac61b. Timeout was: 10.000000 seconds. Mqtt Host: mqtt-eu-4.meross.com:443.
2024-06-25 10:39:08.828 WARNING (MainThread) [meross_iot.manager] Device Smart Plug (2004234441425451850648e1e91ac61b) is online, but timeout occurred when fetching its abilities. 
2024-06-25 10:39:18.832 ERROR (MainThread) [meross_iot.manager] Timeout occurred while waiting a response for message b'{"header":{"from":"/app/756017-b9080411ed1ee3b606745a75093bd7a6/subscribe","messageId":"172072685cc4d983622abae8c53abe03","method":"GET","namespace":"Appliance.System.Ability","payloadVersion":1,"sign":"546229087614fc4d6311b1357f970555","timestamp":1719304749,"triggerSrc":"Android","uuid":"2012102503141851853348e1e93f6509"},"payload":{}}' sent to device uuid 2012102503141851853348e1e93f6509. Timeout was: 10.000000 seconds. Mqtt Host: mqtt-eu-4.meross.com:443.
2024-06-25 10:39:18.833 WARNING (MainThread) [meross_iot.manager] Device Opti (2012102503141851853348e1e93f6509) is online, but timeout occurred when fetching its abilities.
5

Ja, der Githubzugang funktioniert

6

Du könntest mal von der Konsole ha core check eingeben und dann abwarten, ob etwas angezeigt wird. Der Vorgang kann sehr lange dauern!

7

Hab ich getan. Kann ich irgendwo die Results sehen?

8

Auf irgendwas auf Port 5000 kann er offensichtlich nicht zugreifen. Und die Verbindung zu GitHub scheint ein Problem zu sein.

Kannst Du aus der Maschine bzw. aus HA heraus GitHub bzw. die fehlschlagende Domain erreichen?

1 „Gefällt mir“
9

Ja, auf dem Bildschirm. Wenn dir dort nichts weiter angezeigt wird, sollte zumindest dir Konfiguration ok sein.

1 „Gefällt mir“
10

Alles klar, genau so war es. Er ratterte und sagte dann nur noch, dass er fertig sei.

11

Danke, das mit dem 5000er Port hab ich hinbekommen.

Wie erreiche ich aus HA heraus Github? Anpingen?

12

Wäre mein Vorschlag, ja. Bin nicht sicher in wie fern curl oder wget verfügbar sind.

13

Moin,

bin aus dem Kurzurlaub zurück.

ich schaue mir das Log mal an, habe da schon einiges gefunden, dass Du Dir auf jeden Fall anschauen musst.

Ok, dann wäre es angebracht noch einmal ein Log zu zeigen, ob und was keine Folgefehler sind/waren.

VG
Bernd

14

Sorry, so lange keine Zeit gehabt.

Es scheint so, als hätte es bei mir nur am DNS oder DHCP gelegen - wobei ich das Systemupdate noch machen muss, aber alles andere läuft mittlerweile.

Ich hatte sowohl im Router als auch in HomeAssistant eine feste IP vergeben für den Raspi. Stimmte auch alles von den Angaben her, also keine Fehlkonfiguration.

Nun hab ich HomeAssistant die IP dynamisch ziehen lassen (wobei der Router nach wie vor immer die selbe zuweisen soll und auch zuweist) und es klappt. Warum? Keine Ahnung, aber mit dem Umstand kann ich leben.

Wenn ich das Systemupdate auch drauf hab berichte ich nach.

15

Hallo,
ich habe ziemlich genau das gleiche Problem wie Du: seit der Version 2024.5.5 kann ich keine neue Version von Home Assistant Core installieren. Wenn ich den Update starte scheint es, dass das Update zwar eingespielt wird, aber der anschließende Neustart schlägt fehl, da sich das System beim runterfahren scheinbar irgendwie aufhängt. Ich muss Vbox “mit Gewalt” stoppen und dann neu booten. Dabei wird scheinbar das letzte Backup wieder eingespielt und damit bin ich wieder bei Version 2024.5.5.
Unabhängig vom Update kann ich aber generell nicht mehr runterfahren. Das System (HA oder Vbox?) scheint sich dabei immer aufzuhängen.
Ein Problem mit dynamischer bzw. statischer IP-Vergabe habe ich aber nicht. Ich arbeite in meinem Neztwerk schon immer mit dynamischen IPs und die Fritzbox vergibt für den HA immer die selbe IP.
Hat hier jemand einen heißen Tipp für mich?

1 „Gefällt mir“
16

Hast du vielleicht noch ein paar Infos zu deinem System?
Das ist doch recht sparsam:

Hast du noch genug freien Speicher in der HA VM?

LG

17

Bei solch massiven Problemen würde ich selber tatsächlich ganz neu installieren und ein HA Backup einspielen.

18

Ganz plump, nach meiner geschilderten Erfahrung:
Setzt in HA die IP mal auf statisch und dann wieder auf dynamisch zurück :man_shrugging:t2:

19

Mein System ist ein x86 System (N100) mit Ubuntu 22.04 und einer Headless installation von HAOS auf Virtualbox. Speicher ist ausreichend vorhanden (Ram und SSD).

20

Zwischen der Einstellung auf statisch und dem Zurückstellen auf dynamisch irgendetwas unternehmen? Ggfs. neu booten?