MQTT Status im Dashboard anzeigen?

[JB-Braunschweig]

Hi, ich habe hier (ganz neu) MQTT mit einem Hichi Stromzähler im Einsatz.

Jetzt ist der “ausgefallen”, lief aber auf Tasmota. Nach langer Suche bin ich im HA darauf gestoßen, dass MQTT nicht lief (ich glaube er sagte “disabled”, kleines Icon “allgemeines Verbotszeichen”; rund, roter Rand, roter Diagonalbalken). Da ich gestern keine Zeit hatte hat sich jetzt auch der Stromverbrauch “aufgeschaukelt”, so dass für heute im Energy Dashboard keine “vernünftige” Anzeige mehr zu erwarten ist. Kann man da was machen?

Aber mir wichtiger: Ich würde nun gern eine Warnung erstellen, die mir anzeigt, wenn MQTT mehr als fünf Minuten nicht läuft…? Finde aber keine Entity und auch nichts über Internetsuche. Eine Idee?
Edit: Kam mir eben. Optimal natürlich, wenn ich dann im Dashboard gleich per klick MQTT starten könnte…

[Radiocarbonat]

Warum nutzt du nicht den Watchdog des Add-ons? Der startet auch automatisch den Mosquito wieder.

[JB-Braunschweig]

Watchdog war eingeschaltet, aber Mosquito war nicht gestartet. Als ich dann per Hand gestartet habe lief er auf Anhieb.

Ich hatte ja auch gar nicht erwartet, dass es ein Problem mit dem Mosquito Broker sein könnte, aber der Tasmota lief problemlos, las den Stromzähler also aus. Konnte sich aber nicht mit dem HA verbinden. Dann kam ich auf die Idee dort zu gucken

[JB-Braunschweig]

Gestern abend ist MQTT wieder abgeschmiert. Heute morgen versucht neu zu starten, keine Fehlermeldung (gefixt) aber MQTT war nicht gestartet. Beim Versuch dies im Add-On-Fenster zu tun, sagte er mir etwas davon, das Port 1883 bereits in Benutzung sei? Ich habe dann HA neu gestartet (inkl. Rechnerneustart), seitdem läuft es wieder.
Und ja, der Watchdog läuft (angeblich), hilft aber offenbar nicht.

Logger: homeassistant.components.mqtt.client
Source: components/mqtt/client.py:1235
integration: MQTT (documentation, issues)
First occurred: 09:52:16 (1 occurrences)
Last logged: 09:52:16

Error returned from MQTT server: The connection was lost.

Meine Frage also erneut. Kann ich den MQTT Status “überwachen”? Sowohl im Dashboard, wichtiger offenbar als Automation, wenn MQTT nicht läuft? Meine eigenen Versuche in Automatisierung waren erfolglos.
Eine automatisierte Warnung auf mein Handy wenn der “Tasmota MQTT Connect Count” zu “unavailable” wechselt hat leider nicht geholfen (keine Meldung)
Dieser Tage hatte ich bei einem der MQTT Ausfälle, dass sich da HA neu gestartet hat, obwohl es keinen Auslöser dafür gab. Systemcrash durch MQTT?

Gern natürlich zusätzlich Tipps, wie ich herausbekomme, warum MQTT abgrätscht. Ich finde da nicht, wo ich dafür Log-Einträge aktivieren kann und im Log scheinen nur Einträge seit Neustart zu sein?

[RobertoCravallo]

Ich habe mir ein Pop-Up gebastelt, dass hochkommt, wenn einer dieser Ding nicht mehr am Start ist. Im “Erstfall” ist natürlich der Bösewicht farblich gekennzeichnet.

Hatte ich mal eingerichtet weil Z2M gerne mal nicht lief.

Der TRIGGER:

   trigger:
      - condition: or
        conditions:
          - condition: state
            entity: binary_sensor.cloudflared_lauft
            state: "off"
          - condition: state
            entity: binary_sensor.cloudflared_lauft
            state: "off"
          - condition: state
            entity: binary_sensor.zigbee2mqtt_lauft
            state: "off"
          - condition: state
            entity: binary_sensor.zigbee2mqtt_lauft_2
            state: "off"
          - condition: state
            entity: binary_sensor.zigbee2mqtt_lauft_3
            state: "off"
          - condition: state
            entity: binary_sensor.mariadb_running
            state: "off"

[dp20eic]

Moin,

@JB-Braunschweig

dafür Log-Einträge aktivieren kann und im Log scheinen nur Einträge seit Neustart zu sein?

das hast Du korrekt erkannt, HA verschiebt bei jedem Neustart, das alte Log File und erstellt ein neues.
Wenn Du das Advanced ssh & Web Terminal installiert hast, öffne das Terminal und schaue mal in den Ordner, wo auch die configuration.yaml liegt, kannst Du auch mit dem File Editor oder VSC machen.
Da gibt es dann zwei files,

  Home Assistant URL:       http://homeassistant.local:8123
  Observer URL:             http://homeassistant.local:4357
➜  ~ pwd               
/root
➜  ~ ls -la config/*.log*
-rw-r--r--    1 root     root         26512 Mar 17 11:19 config/home-assistant.log
-rw-r--r--    1 root     root         33446 Mar 17 11:15 config/home-assistant.log.1
..
➜  ~ 

Die Loginformation, vom vor dem Booten findest Du dann im File

-rw-r--r--    1 root     root         33446 Mar 17 11:15 config/home-assistant.log.1

Zudem wenn Du keine Panik schiebst und vor dem Booten in die Logfiles schaust, dann sollten da auch noch die aktuellen angezeigt werden

VG
Bernd

P.S.: zu einer guten Problembeschreibung, gehört auch immer die Konfiguration und auf welcher Hardware, mit welchen Ressourcen alles installiert ist

[JB-Braunschweig]

Okay Bernd. Die Konfig:

Home Assistant
Core 2025.3.3
Supervisor 2025.03.3
Operating System 14.2
Frontend 20250306.0

auf einem Raspberry Pi 3B

Panik eher nicht, aber ja, so langer Ausfall zerschießt mir die Energieanzeige, der ganze Strom der Nacht tauchte gesammelt nach dem Reboot auf.

Die log.1-Datei:

2025-03-16 20:40:14.156 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration spook_inverse 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
2025-03-16 20:40:14.163 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration spook 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
2025-03-16 20:40:14.169 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration lights_app 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
2025-03-16 20:40:14.174 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration scheduler 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
2025-03-16 20:40:14.181 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration bosch_shc 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
2025-03-16 20:40:14.193 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration fontawesome 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
2025-03-16 20:40:14.205 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
2025-03-16 20:40:14.216 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
2025-03-16 20:40:27.921 WARNING (Recorder) [homeassistant.components.recorder.util] The system could not validate that the sqlite3 database at //config/home-assistant_v2.db was shutdown cleanly
2025-03-16 20:40:28.574 WARNING (Recorder) [homeassistant.components.recorder.util] Ended unfinished session (id=156 from 2025-03-14 16:23:59.726466)
2025-03-16 20:41:06.181 WARNING (ImportExecutor_0) [homeassistant.components.zeroconf] ZeroconfServiceInfo was used from bosch_shc, this is a deprecated constant which will be removed in HA Core 2026.2. Use homeassistant.helpers.service_info.zeroconf.ZeroconfServiceInfo instead, please report it to the author of the 'bosch_shc' custom integration
2025-03-16 20:41:09.240 ERROR (MainThread) [homeassistant.config_entries] Error setting up entry shc404727 for bosch_shc
Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/config_entries.py", line 753, in __async_setup_with_context
    result = await component.async_setup_entry(hass, self)
             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/config/custom_components/bosch_shc/__init__.py", line 68, in async_setup_entry
    session: SHCSession = await hass.async_add_executor_job(
                          ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
    ...<6 lines>...
    )
    ^
  File "/usr/local/lib/python3.13/concurrent/futures/thread.py", line 59, in run
    result = self.fn(*self.args, **self.kwargs)
  File "/usr/local/lib/python3.13/site-packages/boschshcpy/session.py", line 52, in __init__
    self._enumerate_all()
    ~~~~~~~~~~~~~~~~~~~^^
  File "/usr/local/lib/python3.13/site-packages/boschshcpy/session.py", line 64, in _enumerate_all
    self.authenticate()
    ~~~~~~~~~~~~~~~~~^^
  File "/usr/local/lib/python3.13/site-packages/boschshcpy/session.py", line 373, in authenticate
    self._shc_information = SHCInformation(api=self._api, zeroconf=self._zeroconf)
                            ~~~~~~~~~~~~~~^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.13/site-packages/boschshcpy/information.py", line 83, in __init__
    self.get_unique_id(zeroconf)
    ~~~~~~~~~~~~~~~~~~^^^^^^^^^^
  File "/usr/local/lib/python3.13/site-packages/boschshcpy/information.py", line 141, in get_unique_id
    self._listener = SHCListener(zeroconf, self.filter)
                     ~~~~~~~~~~~^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.13/site-packages/boschshcpy/information.py", line 40, in __init__
    callback(self.shc_services)
    ~~~~~~~~^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.13/site-packages/boschshcpy/information.py", line 122, in filter
    for info in service_info.values():
                ~~~~~~~~~~~~~~~~~~~^^
RuntimeError: dictionary changed size during iteration
2025-03-16 20:41:18.951 ERROR (MainThread) [homeassistant.components.mqtt.client] Failed to connect to MQTT server due to exception: [Errno -5] Name has no usable address
2025-03-16 20:41:22.755 ERROR (MainThread) [homeassistant.helpers.event] Error while processing template: Template<template=({{ float(states('sensor.tasmota_mt175_e_in')) | round(3) }}) renders=2>
Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/helpers/template.py", line 2365, in forgiving_float
    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 643, in async_render
    render_result = _render_with_context(self.template, compiled, **kwargs)
  File "/usr/src/homeassistant/homeassistant/helpers/template.py", line 2756, in _render_with_context
    return template.render(**kwargs)
           ~~~~~~~~~~~~~~~^^^^^^^^^^
  File "/usr/local/lib/python3.13/site-packages/jinja2/environment.py", line 1295, in render
    self.environment.handle_exception()
    ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~^^
  File "/usr/local/lib/python3.13/site-packages/jinja2/environment.py", line 942, in handle_exception
    raise rewrite_traceback_stack(source=source)
  File "<template>", line 1, in top-level template code
  File "/usr/local/lib/python3.13/site-packages/jinja2/sandbox.py", line 401, in call
    return __context.call(__obj, *args, **kwargs)
           ~~~~~~~~~~~~~~^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/helpers/template.py", line 2368, in forgiving_float
    raise_no_default("float", value)
    ~~~~~~~~~~~~~~~~^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/helpers/template.py", line 1932, in raise_no_default
    raise ValueError(
    ...<2 lines>...
    )
ValueError: Template error: float got invalid input 'unavailable' when rendering template '{{ float(states('sensor.tasmota_mt175_e_in')) | round(3) }}' 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 760, in async_render_to_info
    render_info._result = self.async_render(  # noqa: SLF001
                          ~~~~~~~~~~~~~~~~~^^^^^^^^^^^^^^^^^
        variables, strict=strict, log_fn=log_fn, **kwargs
        ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
    )
    ^
  File "/usr/src/homeassistant/homeassistant/helpers/template.py", line 645, in async_render
    raise TemplateError(err) from err
homeassistant.exceptions.TemplateError: ValueError: Template error: float got invalid input 'unavailable' when rendering template '{{ float(states('sensor.tasmota_mt175_e_in')) | round(3) }}' but no default was specified
2025-03-16 20:41:22.796 ERROR (MainThread) [homeassistant.components.template.template_entity] TemplateError('ValueError: Template error: float got invalid input 'unavailable' when rendering template '{{ float(states('sensor.tasmota_mt175_e_in')) | round(3) }}' but no default was specified') while processing template 'Template<template=({{ float(states('sensor.tasmota_mt175_e_in')) | round(3) }}) renders=4>' for attribute '_attr_native_value' in entity 'sensor.hichi_energy_meter_in'
2025-03-16 20:41:22.800 ERROR (MainThread) [homeassistant.helpers.event] Error while processing template: Template<template=({{ float(states('sensor.tasmota_mt175_e_out')) | round(3) }}) renders=2>
Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/helpers/template.py", line 2365, in forgiving_float
    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 643, in async_render
    render_result = _render_with_context(self.template, compiled, **kwargs)
  File "/usr/src/homeassistant/homeassistant/helpers/template.py", line 2756, in _render_with_context
    return template.render(**kwargs)
           ~~~~~~~~~~~~~~~^^^^^^^^^^
  File "/usr/local/lib/python3.13/site-packages/jinja2/environment.py", line 1295, in render
    self.environment.handle_exception()
    ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~^^
  File "/usr/local/lib/python3.13/site-packages/jinja2/environment.py", line 942, in handle_exception
    raise rewrite_traceback_stack(source=source)
  File "<template>", line 1, in top-level template code
  File "/usr/local/lib/python3.13/site-packages/jinja2/sandbox.py", line 401, in call
    return __context.call(__obj, *args, **kwargs)
           ~~~~~~~~~~~~~~^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/helpers/template.py", line 2368, in forgiving_float
    raise_no_default("float", value)
    ~~~~~~~~~~~~~~~~^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/helpers/template.py", line 1932, in raise_no_default
    raise ValueError(
    ...<2 lines>...
    )
ValueError: Template error: float got invalid input 'unavailable' when rendering template '{{ float(states('sensor.tasmota_mt175_e_out')) | round(3) }}' 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 760, in async_render_to_info
    render_info._result = self.async_render(  # noqa: SLF001
                          ~~~~~~~~~~~~~~~~~^^^^^^^^^^^^^^^^^
        variables, strict=strict, log_fn=log_fn, **kwargs
        ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
    )
    ^
  File "/usr/src/homeassistant/homeassistant/helpers/template.py", line 645, in async_render
    raise TemplateError(err) from err
homeassistant.exceptions.TemplateError: ValueError: Template error: float got invalid input 'unavailable' when rendering template '{{ float(states('sensor.tasmota_mt175_e_out')) | round(3) }}' but no default was specified
2025-03-16 20:41:22.821 ERROR (MainThread) [homeassistant.components.template.template_entity] TemplateError('ValueError: Template error: float got invalid input 'unavailable' when rendering template '{{ float(states('sensor.tasmota_mt175_e_out')) | round(3) }}' but no default was specified') while processing template 'Template<template=({{ float(states('sensor.tasmota_mt175_e_out')) | round(3) }}) renders=4>' for attribute '_attr_native_value' in entity 'sensor.hichi_energy_meter_out'
2025-03-16 20:41:22.824 ERROR (MainThread) [homeassistant.helpers.event] Error while processing template: Template<template=({{ float(states('sensor.tasmota_mt175_p')) | round(3) }}) renders=2>
Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/helpers/template.py", line 2365, in forgiving_float
    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 643, in async_render
    render_result = _render_with_context(self.template, compiled, **kwargs)
  File "/usr/src/homeassistant/homeassistant/helpers/template.py", line 2756, in _render_with_context
    return template.render(**kwargs)
           ~~~~~~~~~~~~~~~^^^^^^^^^^
  File "/usr/local/lib/python3.13/site-packages/jinja2/environment.py", line 1295, in render
    self.environment.handle_exception()
    ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~^^
  File "/usr/local/lib/python3.13/site-packages/jinja2/environment.py", line 942, in handle_exception
    raise rewrite_traceback_stack(source=source)
  File "<template>", line 1, in top-level template code
  File "/usr/local/lib/python3.13/site-packages/jinja2/sandbox.py", line 401, in call
    return __context.call(__obj, *args, **kwargs)
           ~~~~~~~~~~~~~~^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/helpers/template.py", line 2368, in forgiving_float
    raise_no_default("float", value)
    ~~~~~~~~~~~~~~~~^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/helpers/template.py", line 1932, in raise_no_default
    raise ValueError(
    ...<2 lines>...
    )
ValueError: Template error: float got invalid input 'unavailable' when rendering template '{{ float(states('sensor.tasmota_mt175_p')) | round(3) }}' 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 760, in async_render_to_info
    render_info._result = self.async_render(  # noqa: SLF001
                          ~~~~~~~~~~~~~~~~~^^^^^^^^^^^^^^^^^
        variables, strict=strict, log_fn=log_fn, **kwargs
        ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
    )
    ^
  File "/usr/src/homeassistant/homeassistant/helpers/template.py", line 645, in async_render
    raise TemplateError(err) from err
homeassistant.exceptions.TemplateError: ValueError: Template error: float got invalid input 'unavailable' when rendering template '{{ float(states('sensor.tasmota_mt175_p')) | round(3) }}' but no default was specified
2025-03-16 20:41:22.840 ERROR (MainThread) [homeassistant.components.template.template_entity] TemplateError('ValueError: Template error: float got invalid input 'unavailable' when rendering template '{{ float(states('sensor.tasmota_mt175_p')) | round(3) }}' but no default was specified') while processing template 'Template<template=({{ float(states('sensor.tasmota_mt175_p')) | round(3) }}) renders=4>' for attribute '_attr_native_value' in entity 'sensor.hichi_watt_use'
2025-03-16 20:42:16.173 WARNING (MainThread) [homeassistant.helpers.frame] Detected that custom integration 'spook' accessed lovelace_data['dashboards'] instead of lovelace_data.dashboards at custom_components/spook/ectoplasms/lovelace/repairs/unknown_entity_references.py, line 45: self._dashboards = self.hass.data["lovelace"]["dashboards"]. This will stop working in Home Assistant 2026.2, please create a bug report at https://github.com/frenck/spook/issues
2025-03-16 20:42:18.156 WARNING (Recorder) [homeassistant.components.sensor.recorder] Entity sensor.hichi_watt_use from integration template has state class total_increasing, but its state is not strictly increasing. Triggered by state 506.0 (510.0) with last_updated set to 2025-03-16T19:30:08.671145+00:00. Please create a bug report at https://github.com/home-assistant/core/issues?q=is%3Aopen+is%3Aissue+label%3A%22integration%3A+template%22
2025-03-16 20:55:54.929 WARNING (MainThread) [homeassistant.components.websocket_api.http.connection] [546967882048] Alexsandra from 127.0.0.1 (Home Assistant/2025.2 (io.robbie.HomeAssistant; build:2025.1178; iOS 18.3.1)): Disconnected: Received error message during command phase: No PONG received after 27.5 seconds
2025-03-16 21:38:38.925 ERROR (MainThread) [aioshelly.rpc_device.wsrpc] Invalid Message from host 192.168.68.197:80: Received message error
2025-03-16 21:40:46.346 WARNING (MainThread) [habluetooth.scanner] hci0 (B8:27:EB:0F:B8:7F): Bluetooth scanner has gone quiet for 118.68925476074219s, restarting
2025-03-16 21:49:11.075 ERROR (Thread-7) [pychromecast.socket_client] [Alexsandra.TV(192.168.68.212):8009] Failed to connect to service MDNSServiceInfo(name='AI-PONT-DE-1226f2504d15de69ce4ddcc42bda615e._googlecast._tcp.local.'), retrying in 5.0s
2025-03-16 21:52:44.965 ERROR (Thread-7) [pychromecast.socket_client] [Alexsandra.TV(192.168.68.212):8009] Failed to connect to service MDNSServiceInfo(name='AI-PONT-DE-1226f2504d15de69ce4ddcc42bda615e._googlecast._tcp.local.'), retrying in 5.0s
2025-03-16 22:13:10.927 WARNING (MainThread) [homeassistant.components.websocket_api.http.connection] [546970035120] Sonia from 127.0.0.1 (Home Assistant/2025.1.2-14946 (Android 14; moto g54 5G)): Disconnected: Received error message during command phase: No PONG received after 27.5 seconds
2025-03-16 22:13:12.926 WARNING (MainThread) [homeassistant.components.websocket_api.http.connection] [547007347104] Sonia from 127.0.0.1 (Home Assistant/2025.1.2-14946 (Android 14; moto g54 5G)): Disconnected: Received error message during command phase: No PONG received after 27.5 seconds
2025-03-16 22:13:20.927 WARNING (MainThread) [homeassistant.components.websocket_api.http.connection] [547149954016] Sonia from 127.0.0.1 (Mozilla/5.0 (Linux; Android 14; moto g54 5G Build/U1TDS34.94-12-9-10-2; wv) AppleWebKit/537.36 (KHTML, like Gecko) Version/4.0 Chrome/133.0.6943.138 Mobile Safari/537.36 Home Assistant/2025.1.2-14946 (Android 14; moto g54 5G)): Disconnected: Received error message during command phase: No PONG received after 27.5 seconds
2025-03-16 22:21:46.438 WARNING (MainThread) [habluetooth.scanner] hci0 (B8:27:EB:0F:B8:7F): Bluetooth scanner has gone quiet for 93.5836410522461s, restarting
2025-03-16 22:24:22.523 ERROR (Thread-7) [pychromecast.socket_client] [Alexsandra.TV(192.168.68.212):8009] Failed to connect to service MDNSServiceInfo(name='AI-PONT-DE-1226f2504d15de69ce4ddcc42bda615e._googlecast._tcp.local.'), retrying in 5.0s
2025-03-16 22:34:16.460 WARNING (MainThread) [habluetooth.scanner] hci0 (B8:27:EB:0F:B8:7F): Bluetooth scanner has gone quiet for 106.62432861328125s, restarting
2025-03-16 22:50:16.507 WARNING (MainThread) [habluetooth.scanner] hci0 (B8:27:EB:0F:B8:7F): Bluetooth scanner has gone quiet for 116.96150970458984s, restarting
2025-03-16 23:00:46.531 WARNING (MainThread) [habluetooth.scanner] hci0 (B8:27:EB:0F:B8:7F): Bluetooth scanner has gone quiet for 110.71954345703125s, restarting
2025-03-16 23:29:32.904 ERROR (Thread-7) [pychromecast.socket_client] [Alexsandra.TV(192.168.68.212):8009] Failed to connect to service MDNSServiceInfo(name='AI-PONT-DE-1226f2504d15de69ce4ddcc42bda615e._googlecast._tcp.local.'), retrying in 5.0s
2025-03-16 23:33:46.608 WARNING (MainThread) [habluetooth.scanner] hci0 (B8:27:EB:0F:B8:7F): Bluetooth scanner has gone quiet for 113.22522735595703s, restarting
2025-03-17 00:03:46.679 WARNING (MainThread) [habluetooth.scanner] hci0 (B8:27:EB:0F:B8:7F): Bluetooth scanner has gone quiet for 96.65120697021484s, restarting
2025-03-17 00:03:52.153 WARNING (MainThread) [bluetooth_auto_recovery.recover] Could not reset the power state of the Bluetooth adapter hci0 [B8:27:EB:0F:B8:7F] (0) due to timeout after 5 seconds
2025-03-17 00:10:16.696 WARNING (MainThread) [habluetooth.scanner] hci0 (B8:27:EB:0F:B8:7F): Bluetooth scanner has gone quiet for 92.35292053222656s, restarting
2025-03-17 00:33:46.743 WARNING (MainThread) [habluetooth.scanner] hci0 (B8:27:EB:0F:B8:7F): Bluetooth scanner has gone quiet for 113.3721923828125s, restarting
2025-03-17 00:36:16.750 WARNING (MainThread) [habluetooth.scanner] hci0 (B8:27:EB:0F:B8:7F): Bluetooth scanner has gone quiet for 92.38111877441406s, restarting
2025-03-17 00:48:46.426 ERROR (Thread-7) [pychromecast.socket_client] [Alexsandra.TV(192.168.68.212):8009] Failed to connect to service MDNSServiceInfo(name='AI-PONT-DE-1226f2504d15de69ce4ddcc42bda615e._googlecast._tcp.local.'), retrying in 5.0s
2025-03-17 00:51:46.777 WARNING (MainThread) [habluetooth.scanner] hci0 (B8:27:EB:0F:B8:7F): Bluetooth scanner has gone quiet for 99.28348541259766s, restarting
2025-03-17 01:05:40.926 ERROR (MainThread) [aioshelly.rpc_device.wsrpc] Invalid Message from host 192.168.68.195:80: Received message error
2025-03-17 01:12:46.833 WARNING (MainThread) [habluetooth.scanner] hci0 (B8:27:EB:0F:B8:7F): Bluetooth scanner has gone quiet for 97.90762329101562s, restarting
2025-03-17 01:12:58.160 WARNING (MainThread) [bluetooth_auto_recovery.recover] Could not reset the power state of the Bluetooth adapter hci0 [B8:27:EB:0F:B8:7F] (0) due to timeout after 5 seconds
2025-03-17 01:13:00.679 WARNING (MainThread) [bluetooth_auto_recovery.recover] Could not cycle the Bluetooth adapter hci0 [B8:27:EB:0F:B8:7F] (0): [Errno 110] Operation timed out
2025-03-17 01:13:05.683 WARNING (MainThread) [bluetooth_auto_recovery.recover] Could not reset the power state of the Bluetooth adapter hci0 [B8:27:EB:0F:B8:7F] (0) due to timeout after 5 seconds
2025-03-17 01:13:05.749 WARNING (MainThread) [habluetooth.scanner] hci0 (B8:27:EB:0F:B8:7F): Successful fall-back to passive scanning mode after active scanning failed (4/4)
2025-03-17 01:14:46.839 WARNING (MainThread) [habluetooth.scanner] hci0 (B8:27:EB:0F:B8:7F): Bluetooth scanner has gone quiet for 101.08860778808594s, restarting
2025-03-17 01:14:49.421 WARNING (MainThread) [bluetooth_auto_recovery.recover] Could not cycle the Bluetooth adapter hci0 [B8:27:EB:0F:B8:7F] (0): [Errno 110] Operation timed out
2025-03-17 01:14:54.429 WARNING (MainThread) [bluetooth_auto_recovery.recover] Could not reset the power state of the Bluetooth adapter hci0 [B8:27:EB:0F:B8:7F] (0) due to timeout after 5 seconds
2025-03-17 01:14:56.966 WARNING (MainThread) [bluetooth_auto_recovery.recover] Could not cycle the Bluetooth adapter hci0 [B8:27:EB:0F:B8:7F] (0): [Errno 110] Operation timed out
2025-03-17 01:15:01.970 WARNING (MainThread) [bluetooth_auto_recovery.recover] Could not reset the power state of the Bluetooth adapter hci0 [B8:27:EB:0F:B8:7F] (0) due to timeout after 5 seconds
2025-03-17 01:15:01.991 WARNING (MainThread) [habluetooth.scanner] hci0 (B8:27:EB:0F:B8:7F): Successful fall-back to passive scanning mode after active scanning failed (4/4)
2025-03-17 01:16:46.845 WARNING (MainThread) [habluetooth.scanner] hci0 (B8:27:EB:0F:B8:7F): Bluetooth scanner has gone quiet for 104.85358428955078s, restarting
2025-03-17 01:16:49.414 WARNING (MainThread) [bluetooth_auto_recovery.recover] Could not cycle the Bluetooth adapter hci0 [B8:27:EB:0F:B8:7F] (0): [Errno 110] Operation timed out
2025-03-17 01:16:54.418 WARNING (MainThread) [bluetooth_auto_recovery.recover] Could not reset the power state of the Bluetooth adapter hci0 [B8:27:EB:0F:B8:7F] (0) due to timeout after 5 seconds
2025-03-17 01:16:56.966 WARNING (MainThread) [bluetooth_auto_recovery.recover] Could not cycle the Bluetooth adapter hci0 [B8:27:EB:0F:B8:7F] (0): [Errno 110] Operation timed out
2025-03-17 01:17:01.971 WARNING (MainThread) [bluetooth_auto_recovery.recover] Could not reset the power state of the Bluetooth adapter hci0 [B8:27:EB:0F:B8:7F] (0) due to timeout after 5 seconds
2025-03-17 01:17:01.989 WARNING (MainThread) [habluetooth.scanner] hci0 (B8:27:EB:0F:B8:7F): Successful fall-back to passive scanning mode after active scanning failed (4/4)
2025-03-17 01:18:46.849 WARNING (MainThread) [habluetooth.scanner] hci0 (B8:27:EB:0F:B8:7F): Bluetooth scanner has gone quiet for 104.85858154296875s, restarting
2025-03-17 01:18:49.413 WARNING (MainThread) [bluetooth_auto_recovery.recover] Could not cycle the Bluetooth adapter hci0 [B8:27:EB:0F:B8:7F] (0): [Errno 110] Operation timed out
2025-03-17 01:18:54.417 WARNING (MainThread) [bluetooth_auto_recovery.recover] Could not reset the power state of the Bluetooth adapter hci0 [B8:27:EB:0F:B8:7F] (0) due to timeout after 5 seconds
2025-03-17 01:18:56.966 WARNING (MainThread) [bluetooth_auto_recovery.recover] Could not cycle the Bluetooth adapter hci0 [B8:27:EB:0F:B8:7F] (0): [Errno 110] Operation timed out
2025-03-17 01:19:01.970 WARNING (MainThread) [bluetooth_auto_recovery.recover] Could not reset the power state of the Bluetooth adapter hci0 [B8:27:EB:0F:B8:7F] (0) due to timeout after 5 seconds
2025-03-17 01:19:01.986 WARNING (MainThread) [habluetooth.scanner] hci0 (B8:27:EB:0F:B8:7F): Successful fall-back to passive scanning mode after active scanning failed (4/4)
2025-03-17 01:20:46.854 WARNING (MainThread) [habluetooth.scanner] hci0 (B8:27:EB:0F:B8:7F): Bluetooth scanner has gone quiet for 104.8675765991211s, restarting
2025-03-17 01:20:49.414 WARNING (MainThread) [bluetooth_auto_recovery.recover] Could not cycle the Bluetooth adapter hci0 [B8:27:EB:0F:B8:7F] (0): [Errno 110] Operation timed out
2025-03-17 01:20:54.418 WARNING (MainThread) [bluetooth_auto_recovery.recover] Could not reset the power state of the Bluetooth adapter hci0 [B8:27:EB:0F:B8:7F] (0) due to timeout after 5 seconds
2025-03-17 01:20:56.970 WARNING (MainThread) [bluetooth_auto_recovery.recover] Could not cycle the Bluetooth adapter hci0 [B8:27:EB:0F:B8:7F] (0): [Errno 110] Operation timed out
2025-03-17 01:21:01.974 WARNING (MainThread) [bluetooth_auto_recovery.recover] Could not reset the power state of the Bluetooth adapter hci0 [B8:27:EB:0F:B8:7F] (0) due to timeout after 5 seconds
2025-03-17 01:21:01.994 WARNING (MainThread) [habluetooth.scanner] hci0 (B8:27:EB:0F:B8:7F): Successful fall-back to passive scanning mode after active scanning failed (4/4)
2025-03-17 01:22:46.859 WARNING (MainThread) [habluetooth.scanner] hci0 (B8:27:EB:0F:B8:7F): Bluetooth scanner has gone quiet for 104.86457061767578s, restarting
2025-03-17 01:22:49.415 WARNING (MainThread) [bluetooth_auto_recovery.recover] Could not cycle the Bluetooth adapter hci0 [B8:27:EB:0F:B8:7F] (0): [Errno 110] Operation timed out
2025-03-17 01:22:49.555 WARNING (MainThread) [bluetooth_auto_recovery.recover] Bluetooth adapter hci0 [B8:27:EB:0F:B8:7F] (0) successfully turned back ON
2025-03-17 01:29:46.873 WARNING (MainThread) [habluetooth.scanner] hci0 (B8:27:EB:0F:B8:7F): Bluetooth scanner has gone quiet for 111.95453643798828s, restarting
2025-03-17 01:29:58.042 WARNING (MainThread) [bluetooth_auto_recovery.recover] Could not reset the power state of the Bluetooth adapter hci0 [B8:27:EB:0F:B8:7F] (0) due to timeout after 5 seconds
2025-03-17 01:30:00.582 WARNING (MainThread) [bluetooth_auto_recovery.recover] Could not cycle the Bluetooth adapter hci0 [B8:27:EB:0F:B8:7F] (0): [Errno 110] Operation timed out
2025-03-17 01:30:05.586 WARNING (MainThread) [bluetooth_auto_recovery.recover] Could not reset the power state of the Bluetooth adapter hci0 [B8:27:EB:0F:B8:7F] (0) due to timeout after 5 seconds
2025-03-17 01:30:05.605 WARNING (MainThread) [habluetooth.scanner] hci0 (B8:27:EB:0F:B8:7F): Successful fall-back to passive scanning mode after active scanning failed (4/4)
2025-03-17 01:31:46.877 WARNING (MainThread) [habluetooth.scanner] hci0 (B8:27:EB:0F:B8:7F): Bluetooth scanner has gone quiet for 101.27057647705078s, restarting
2025-03-17 01:31:49.446 WARNING (MainThread) [bluetooth_auto_recovery.recover] Could not cycle the Bluetooth adapter hci0 [B8:27:EB:0F:B8:7F] (0): [Errno 110] Operation timed out
2025-03-17 01:31:54.452 WARNING (MainThread) [bluetooth_auto_recovery.recover] Could not reset the power state of the Bluetooth adapter hci0 [B8:27:EB:0F:B8:7F] (0) due to timeout after 5 seconds
2025-03-17 01:31:56.997 WARNING (MainThread) [bluetooth_auto_recovery.recover] Could not cycle the Bluetooth adapter hci0 [B8:27:EB:0F:B8:7F] (0): [Errno 110] Operation timed out
2025-03-17 01:32:02.001 WARNING (MainThread) [bluetooth_auto_recovery.recover] Could not reset the power state of the Bluetooth adapter hci0 [B8:27:EB:0F:B8:7F] (0) due to timeout after 5 seconds
2025-03-17 01:32:02.020 WARNING (MainThread) [habluetooth.scanner] hci0 (B8:27:EB:0F:B8:7F): Successful fall-back to passive scanning mode after active scanning failed (4/4)
2025-03-17 01:33:46.883 WARNING (MainThread) [habluetooth.scanner] hci0 (B8:27:EB:0F:B8:7F): Bluetooth scanner has gone quiet for 104.86356353759766s, restarting
2025-03-17 01:33:49.446 WARNING (MainThread) [bluetooth_auto_recovery.recover] Could not cycle the Bluetooth adapter hci0 [B8:27:EB:0F:B8:7F] (0): [Errno 110] Operation timed out
2025-03-17 01:33:49.588 WARNING (MainThread) [bluetooth_auto_recovery.recover] Bluetooth adapter hci0 [B8:27:EB:0F:B8:7F] (0) successfully turned back ON
2025-03-17 01:34:39.678 ERROR (Thread-7) [pychromecast.socket_client] [Alexsandra.TV(192.168.68.212):8009] Failed to connect to service MDNSServiceInfo(name='AI-PONT-DE-1226f2504d15de69ce4ddcc42bda615e._googlecast._tcp.local.'), retrying in 5.0s
2025-03-17 01:43:16.918 WARNING (MainThread) [habluetooth.scanner] hci0 (B8:27:EB:0F:B8:7F): Bluetooth scanner has gone quiet for 92.54766082763672s, restarting
2025-03-17 02:14:47.000 WARNING (MainThread) [habluetooth.scanner] hci0 (B8:27:EB:0F:B8:7F): Bluetooth scanner has gone quiet for 95.59860229492188s, restarting
2025-03-17 02:14:52.229 WARNING (MainThread) [bluetooth_auto_recovery.recover] Could not reset the power state of the Bluetooth adapter hci0 [B8:27:EB:0F:B8:7F] (0) due to timeout after 5 seconds
2025-03-17 02:24:21.639 ERROR (Thread-7) [pychromecast.socket_client] [Alexsandra.TV(192.168.68.212):8009] Failed to connect to service MDNSServiceInfo(name='AI-PONT-DE-1226f2504d15de69ce4ddcc42bda615e._googlecast._tcp.local.'), retrying in 5.0s
2025-03-17 02:43:25.036 ERROR (Thread-7) [pychromecast.socket_client] [Alexsandra.TV(192.168.68.212):8009] Failed to connect to service MDNSServiceInfo(name='AI-PONT-DE-1226f2504d15de69ce4ddcc42bda615e._googlecast._tcp.local.'), retrying in 5.0s
2025-03-17 02:45:17.077 WARNING (MainThread) [habluetooth.scanner] hci0 (B8:27:EB:0F:B8:7F): Bluetooth scanner has gone quiet for 92.83555603027344s, restarting
2025-03-17 02:55:17.096 WARNING (MainThread) [habluetooth.scanner] hci0 (B8:27:EB:0F:B8:7F): Bluetooth scanner has gone quiet for 92.85883331298828s, restarting
2025-03-17 03:09:47.127 WARNING (MainThread) [habluetooth.scanner] hci0 (B8:27:EB:0F:B8:7F): Bluetooth scanner has gone quiet for 103.42761993408203s, restarting
2025-03-17 03:42:17.262 WARNING (MainThread) [habluetooth.scanner] hci0 (B8:27:EB:0F:B8:7F): Bluetooth scanner has gone quiet for 92.50861358642578s, restarting
2025-03-17 03:49:47.281 WARNING (MainThread) [habluetooth.scanner] hci0 (B8:27:EB:0F:B8:7F): Bluetooth scanner has gone quiet for 103.44357299804688s, restarting
2025-03-17 03:59:46.617 ERROR (Thread-9) [pychromecast.socket_client] [Sonias TV(192.168.68.117):8009] Error reading from socket: socket connection broken
2025-03-17 03:59:46.632 ERROR (Thread-9) [pychromecast.socket_client] [Sonias TV(192.168.68.117):8009] Failed to connect to service HostServiceInfo(host='192.168.68.117', port=8009), retrying in 5.0s
2025-03-17 04:06:03.411 ERROR (Thread-7) [pychromecast.socket_client] [Alexsandra.TV(192.168.68.212):8009] Failed to connect to service MDNSServiceInfo(name='AI-PONT-DE-1226f2504d15de69ce4ddcc42bda615e._googlecast._tcp.local.'), retrying in 5.0s
2025-03-17 04:24:26.583 ERROR (Thread-7) [pychromecast.socket_client] [Alexsandra.TV(192.168.68.212):8009] Failed to connect to service MDNSServiceInfo(name='AI-PONT-DE-1226f2504d15de69ce4ddcc42bda615e._googlecast._tcp.local.'), retrying in 5.0s
2025-03-17 04:49:47.416 WARNING (MainThread) [habluetooth.scanner] hci0 (B8:27:EB:0F:B8:7F): Bluetooth scanner has gone quiet for 103.52964782714844s, restarting
2025-03-17 04:53:17.427 WARNING (MainThread) [habluetooth.scanner] hci0 (B8:27:EB:0F:B8:7F): Bluetooth scanner has gone quiet for 111.35960388183594s, restarting
2025-03-17 05:06:39.303 ERROR (Thread-5) [pychromecast.socket_client] [Sonia.TV(192.168.68.222):8009] Error reading from socket: socket connection broken
2025-03-17 05:06:39.318 ERROR (Thread-5) [pychromecast.socket_client] [Sonia.TV(192.168.68.222):8009] Failed to connect to service HostServiceInfo(host='192.168.68.222', port=8009), retrying in 5.0s
2025-03-17 05:11:17.479 WARNING (MainThread) [habluetooth.scanner] hci0 (B8:27:EB:0F:B8:7F): Bluetooth scanner has gone quiet for 115.29930877685547s, restarting
2025-03-17 05:24:17.540 WARNING (MainThread) [habluetooth.scanner] hci0 (B8:27:EB:0F:B8:7F): Bluetooth scanner has gone quiet for 93.33456420898438s, restarting
2025-03-17 05:24:22.597 WARNING (MainThread) [bluetooth_auto_recovery.recover] Could not reset the power state of the Bluetooth adapter hci0 [B8:27:EB:0F:B8:7F] (0) due to timeout after 5 seconds
2025-03-17 05:24:49.589 ERROR (Thread-7) [pychromecast.socket_client] [Alexsandra.TV(192.168.68.212):8009] Failed to connect to service MDNSServiceInfo(name='AI-PONT-DE-1226f2504d15de69ce4ddcc42bda615e._googlecast._tcp.local.'), retrying in 5.0s
2025-03-17 05:29:17.550 WARNING (MainThread) [habluetooth.scanner] hci0 (B8:27:EB:0F:B8:7F): Bluetooth scanner has gone quiet for 97.83556365966797s, restarting
2025-03-17 05:29:28.735 WARNING (MainThread) [bluetooth_auto_recovery.recover] Could not reset the power state of the Bluetooth adapter hci0 [B8:27:EB:0F:B8:7F] (0) due to timeout after 5 seconds
2025-03-17 05:29:31.270 WARNING (MainThread) [bluetooth_auto_recovery.recover] Could not cycle the Bluetooth adapter hci0 [B8:27:EB:0F:B8:7F] (0): [Errno 110] Operation timed out
2025-03-17 05:29:36.275 WARNING (MainThread) [bluetooth_auto_recovery.recover] Could not reset the power state of the Bluetooth adapter hci0 [B8:27:EB:0F:B8:7F] (0) due to timeout after 5 seconds
2025-03-17 05:29:36.331 WARNING (MainThread) [habluetooth.scanner] hci0 (B8:27:EB:0F:B8:7F): Successful fall-back to passive scanning mode after active scanning failed (4/4)
2025-03-17 05:30:29.047 ERROR (Thread-7) [pychromecast.socket_client] [Alexsandra.TV(192.168.68.212):8009] Failed to connect to service MDNSServiceInfo(name='AI-PONT-DE-1226f2504d15de69ce4ddcc42bda615e._googlecast._tcp.local.'), retrying in 5.0s
2025-03-17 05:31:17.556 WARNING (MainThread) [habluetooth.scanner] hci0 (B8:27:EB:0F:B8:7F): Bluetooth scanner has gone quiet for 101.22354888916016s, restarting
2025-03-17 05:31:20.134 WARNING (MainThread) [bluetooth_auto_recovery.recover] Could not cycle the Bluetooth adapter hci0 [B8:27:EB:0F:B8:7F] (0): [Errno 110] Operation timed out
2025-03-17 05:31:25.138 WARNING (MainThread) [bluetooth_auto_recovery.recover] Could not reset the power state of the Bluetooth adapter hci0 [B8:27:EB:0F:B8:7F] (0) due to timeout after 5 seconds
2025-03-17 05:31:27.686 WARNING (MainThread) [bluetooth_auto_recovery.recover] Could not cycle the Bluetooth adapter hci0 [B8:27:EB:0F:B8:7F] (0): [Errno 110] Operation timed out
2025-03-17 05:31:32.691 WARNING (MainThread) [bluetooth_auto_recovery.recover] Could not reset the power state of the Bluetooth adapter hci0 [B8:27:EB:0F:B8:7F] (0) due to timeout after 5 seconds
2025-03-17 05:31:32.710 WARNING (MainThread) [habluetooth.scanner] hci0 (B8:27:EB:0F:B8:7F): Successful fall-back to passive scanning mode after active scanning failed (4/4)
2025-03-17 05:33:17.562 WARNING (MainThread) [habluetooth.scanner] hci0 (B8:27:EB:0F:B8:7F): Bluetooth scanner has gone quiet for 104.8515396118164s, restarting
2025-03-17 05:33:20.134 WARNING (MainThread) [bluetooth_auto_recovery.recover] Could not cycle the Bluetooth adapter hci0 [B8:27:EB:0F:B8:7F] (0): [Errno 110] Operation timed out
2025-03-17 05:33:25.138 WARNING (MainThread) [bluetooth_auto_recovery.recover] Could not reset the power state of the Bluetooth adapter hci0 [B8:27:EB:0F:B8:7F] (0) due to timeout after 5 seconds
2025-03-17 05:33:27.686 WARNING (MainThread) [bluetooth_auto_recovery.recover] Could not cycle the Bluetooth adapter hci0 [B8:27:EB:0F:B8:7F] (0): [Errno 110] Operation timed out
2025-03-17 05:33:32.690 WARNING (MainThread) [bluetooth_auto_recovery.recover] Could not reset the power state of the Bluetooth adapter hci0 [B8:27:EB:0F:B8:7F] (0) due to timeout after 5 seconds
2025-03-17 05:33:32.709 WARNING (MainThread) [habluetooth.scanner] hci0 (B8:27:EB:0F:B8:7F): Successful fall-back to passive scanning mode after active scanning failed (4/4)
2025-03-17 05:35:17.568 WARNING (MainThread) [habluetooth.scanner] hci0 (B8:27:EB:0F:B8:7F): Bluetooth scanner has gone quiet for 104.85753631591797s, restarting
2025-03-17 05:35:20.134 WARNING (MainThread) [bluetooth_auto_recovery.recover] Could not cycle the Bluetooth adapter hci0 [B8:27:EB:0F:B8:7F] (0): [Errno 110] Operation timed out
2025-03-17 05:35:25.137 WARNING (MainThread) [bluetooth_auto_recovery.recover] Could not reset the power state of the Bluetooth adapter hci0 [B8:27:EB:0F:B8:7F] (0) due to timeout after 5 seconds
2025-03-17 05:35:27.686 WARNING (MainThread) [bluetooth_auto_recovery.recover] Could not cycle the Bluetooth adapter hci0 [B8:27:EB:0F:B8:7F] (0): [Errno 110] Operation timed out
2025-03-17 05:35:27.828 WARNING (MainThread) [bluetooth_auto_recovery.recover] Bluetooth adapter hci0 [B8:27:EB:0F:B8:7F] (0) successfully turned back ON
2025-03-17 06:04:17.627 WARNING (MainThread) [habluetooth.scanner] hci0 (B8:27:EB:0F:B8:7F): Bluetooth scanner has gone quiet for 97.51158142089844s, restarting
2025-03-17 06:24:29.979 ERROR (Thread-7) [pychromecast.socket_client] [Alexsandra.TV(192.168.68.212):8009] Failed to connect to service HostServiceInfo(host='192.168.68.212', port=8009), retrying in 5.0s
2025-03-17 06:29:17.676 WARNING (MainThread) [habluetooth.scanner] hci0 (B8:27:EB:0F:B8:7F): Bluetooth scanner has gone quiet for 97.340576171875s, restarting
2025-03-17 06:29:22.718 WARNING (MainThread) [bluetooth_auto_recovery.recover] Could not reset the power state of the Bluetooth adapter hci0 [B8:27:EB:0F:B8:7F] (0) due to timeout after 5 seconds
2025-03-17 07:03:47.755 WARNING (MainThread) [habluetooth.scanner] hci0 (B8:27:EB:0F:B8:7F): Bluetooth scanner has gone quiet for 104.2967529296875s, restarting
2025-03-17 07:34:18.136 WARNING (MainThread) [habluetooth.scanner] hci0 (B8:27:EB:0F:B8:7F): Bluetooth scanner has gone quiet for 110.76241302490234s, restarting
2025-03-17 07:34:29.277 WARNING (MainThread) [bluetooth_auto_recovery.recover] Could not reset the power state of the Bluetooth adapter hci0 [B8:27:EB:0F:B8:7F] (0) due to timeout after 5 seconds
2025-03-17 07:34:31.814 WARNING (MainThread) [bluetooth_auto_recovery.recover] Could not cycle the Bluetooth adapter hci0 [B8:27:EB:0F:B8:7F] (0): [Errno 110] Operation timed out
2025-03-17 07:34:36.818 WARNING (MainThread) [bluetooth_auto_recovery.recover] Could not reset the power state of the Bluetooth adapter hci0 [B8:27:EB:0F:B8:7F] (0) due to timeout after 5 seconds
2025-03-17 07:34:36.861 WARNING (MainThread) [habluetooth.scanner] hci0 (B8:27:EB:0F:B8:7F): Successful fall-back to passive scanning mode after active scanning failed (4/4)
2025-03-17 07:36:18.141 WARNING (MainThread) [habluetooth.scanner] hci0 (B8:27:EB:0F:B8:7F): Bluetooth scanner has gone quiet for 101.27949523925781s, restarting
2025-03-17 07:36:20.679 WARNING (MainThread) [bluetooth_auto_recovery.recover] Could not cycle the Bluetooth adapter hci0 [B8:27:EB:0F:B8:7F] (0): [Errno 110] Operation timed out
2025-03-17 07:36:25.461 ERROR (Thread-7) [pychromecast.socket_client] [Alexsandra.TV(192.168.68.212):8009] Failed to connect to service MDNSServiceInfo(name='AI-PONT-DE-1226f2504d15de69ce4ddcc42bda615e._googlecast._tcp.local.'), retrying in 5.0s
2025-03-17 07:36:25.683 WARNING (MainThread) [bluetooth_auto_recovery.recover] Could not reset the power state of the Bluetooth adapter hci0 [B8:27:EB:0F:B8:7F] (0) due to timeout after 5 seconds
2025-03-17 07:36:28.229 WARNING (MainThread) [bluetooth_auto_recovery.recover] Could not cycle the Bluetooth adapter hci0 [B8:27:EB:0F:B8:7F] (0): [Errno 110] Operation timed out
2025-03-17 07:36:28.370 WARNING (MainThread) [bluetooth_auto_recovery.recover] Bluetooth adapter hci0 [B8:27:EB:0F:B8:7F] (0) successfully turned back ON
2025-03-17 07:41:51.971 ERROR (Thread-7) [pychromecast.socket_client] [Alexsandra.TV(192.168.68.212):8009] Failed to connect to service MDNSServiceInfo(name='AI-PONT-DE-1226f2504d15de69ce4ddcc42bda615e._googlecast._tcp.local.'), retrying in 5.0s
2025-03-17 07:42:08.928 WARNING (MainThread) [homeassistant.components.websocket_api.http.connection] [546967895872] Alexsandra from 127.0.0.1 (Home Assistant/2025.2 (io.robbie.HomeAssistant; build:2025.1178; iOS 18.3.1)): Disconnected: Received error message during command phase: No PONG received after 27.5 seconds
2025-03-17 07:55:48.177 WARNING (MainThread) [habluetooth.scanner] hci0 (B8:27:EB:0F:B8:7F): Bluetooth scanner has gone quiet for 114.0445327758789s, restarting
2025-03-17 08:23:51.926 WARNING (MainThread) [homeassistant.components.websocket_api.http.connection] [547076106720] Sonia from 127.0.0.1 (Mozilla/5.0 (Linux; Android 14; moto g54 5G Build/U1TDS34.94-12-9-10-2; wv) AppleWebKit/537.36 (KHTML, like Gecko) Version/4.0 Chrome/133.0.6943.138 Mobile Safari/537.36 Home Assistant/2025.1.2-14946 (Android 14; moto g54 5G)): Disconnected: Received error message during command phase: No PONG received after 27.5 seconds
2025-03-17 08:24:24.927 WARNING (MainThread) [homeassistant.components.websocket_api.http.connection] [546969290208] Sonia from 127.0.0.1 (Home Assistant/2025.1.2-14946 (Android 14; moto g54 5G)): Disconnected: Received error message during command phase: No PONG received after 27.5 seconds
2025-03-17 08:27:08.052 ERROR (MainThread) [homeassistant.components.hassio] Failed to to call /addons/core_mosquitto/start - Port '1883' is already in use by something else on the host.
2025-03-17 08:27:55.512 ERROR (Thread-7) [pychromecast.socket_client] [Alexsandra.TV(192.168.68.212):8009] Failed to connect. No retries.

Ich glaube das Problem fängt in Zeile 47 an…

Nur der Vollständigkeit halber, in der configuration.yaml (analog zu Simon’s Info)

# - Hichi Energy Meter --
template:
  # ------- Hichi Energy Meter IN -------
  - sensor:
    - name: "Hichi Energy Meter in"
      unique_id: "TotalEnergyfromGrid"
      unit_of_measurement: 'kWh'
      device_class: "energy"
      state_class: "total_increasing"
      state: >-
        {{ float(states('sensor.tasmota_mt175_e_in')) | round(3) }}
  # ------- Hichi Energy Meter OUT -------
  - sensor:
    - name: "Hichi Energy Meter out"
      unique_id: "TotalEnergytoGrid"
      unit_of_measurement: 'kWh'
      device_class: "energy"
      state_class: "total_increasing"
      state: >-
          {{ float(states('sensor.tasmota_mt175_e_out')) | round(3) }}
  # ------- Hichi Energy Watt Usage -------
  - sensor:
    - name: "Hichi Watt Use"
      unique_id: "WattUsed"
      unit_of_measurement: 'W'
      device_class: "energy"
      state_class: "total_increasing"
      state: >-
          {{ float(states('sensor.tasmota_mt175_p')) | round(3) }}

[dp20eic]

Moin,

@JB-Braunschweig

Die Konfig:

Ok, das sind die Versionen, der HA Komponenten, da bist Du aktuell.
Ich meinte aber die Konfiguration des MQTT Add-ons, am besten als Code in Code-Tags, bekommst Du, wenn Du im Add-on, im Konfiguration-Tab bist, dann oben rechts auf die drei Punkte und auf yaml gehen.

Zum Log:

2025-03-16 20:40:14.156 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration spook_inverse 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
2025-03-16 20:40:14.163 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration spook 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
2025-03-16 20:40:14.169 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration lights_app 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
2025-03-16 20:40:14.174 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration scheduler 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
2025-03-16 20:40:14.181 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration bosch_shc 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
2025-03-16 20:40:14.193 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration fontawesome 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
2025-03-16 20:40:14.205 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
2025-03-16 20:40:14.216 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

Das sind normale Warnungen, bekommt jeder, der sich, HACS installiert hat und daraus etwas hinzugefügt hat.

2025-03-16 20:40:27.921 WARNING (Recorder) [homeassistant.components.recorder.util] The system could not validate that the sqlite3 database at //config/home-assistant_v2.db was shutdown cleanly
2025-03-16 20:40:28.574 WARNING (Recorder) [homeassistant.components.recorder.util] Ended unfinished session (id=156 from 2025-03-14 16:23:59.726466)

Das kommt davon, wenn man ein System nicht sauber herunterfährt und einfach den Stecker zieht.
Deine Datenbank, scheint kaputt zu sein, HA versucht das, beim nächsten Start, wieder zu bereinigen, das dauert, bei Deiner Hardware, aber vielleicht zu lange, der RasPI ist da eher eine Rennschnecke.

2025-03-16 20:41:06.181 WARNING (ImportExecutor_0) [homeassistant.components.zeroconf] ZeroconfServiceInfo was used from bosch_shc, this is a deprecated constant which will be removed in HA Core 2026.2. Use homeassistant.helpers.service_info.zeroconf.ZeroconfServiceInfo instead, please report it to the author of the 'bosch_shc' custom integration

Das ist eine Warnung, dass eine bestimmte Funktion nicht mehr zu verwenden ist, das muss der Entwickler der Erweiterung bosch_shc bereinigen.
Nutzt Du da eine Erweiterung von Bosch, denn die schmeißt ein Error

2025-03-16 20:41:09.240 ERROR (MainThread) [homeassistant.config_entries] Error setting up entry shc404727 for bosch_shc

Da solltest Du mal schauen, ob das alles korrekt eingerichtet ist, ansonsten mal dies Integration deaktivieren.

2025-03-16 20:41:18.951 ERROR (MainThread) [homeassistant.components.mqtt.client] Failed to connect to MQTT server due to exception: [Errno -5] Name has no usable address

Hier kann HA den MQTT Server nicht mehr erreichen, Error Code -5 deutet auf einen Authentication Error hin

MQTT Client Error Codes

Error code

(Decimal) Error code	(Hex)	Meaning
0	0x0	No Error
1	0x1	Connection Refused: Unacceptable protocol version
10	0xa	Timeout waiting for SUBACK
11	0xb	Timeout waiting for UNSUBACK
12	0xc	Timeout waiting for PINGRESP
13	0xd	Malformed Remaining Length
14	0xe	Problem with the underlying communication port
15	0xf	Address could not be parsed
16	0x10	Malformed received MQTT packet
17	0x11	Subscription failure
18	0x12	Payload decoding failure
19	0x13	Failed to compile a Decoder
2	0x2	Connection Refused: Identifier rejected
20	0x14	The received MQTT packet type is not supported on this client
21	0x15	Timeout waiting for PUBACK
22	0x16	Timeout waiting for PUBREC
23	0x17	Timeout waiting for PUBCOMP
3	0x3	Connection Refused: Server Unavailable
4	0x4	Connection Refused: Bad username or password
5	0x5	Connection Refused: Authorization error
6	0x6	Connection lost or bad
7	0x7	Timeout waiting for Length bytes
8	0x8	Timeout waiting for Payload
9	0x9	Timeout waiting for CONNACK

2025-03-16 20:41:22.755 ERROR (MainThread) [homeassistant.helpers.event] Error while processing template: Template<template=({{ float(states('sensor.tasmota_mt175_e_in')) | round(3) }}) renders=2>

Alle Errors, die mit etwas wie Tamplate haben, sind dann Folgefehler, weil der MQTT Broker keine Daten mehr liefert.

2025-03-16 20:42:16.173 WARNING (MainThread) [homeassistant.helpers.frame] Detected that custom integration 'spook' accessed lovelace_data['dashboards'] instead of lovelace_data.dashboards at custom_components/spook/ectoplasms/lovelace/repairs/unknown_entity_references.py, line 45: self._dashboards = self.hass.data["lovelace"]["dashboards"]. This will stop working in Home Assistant 2026.2, please create a bug report at https://github.com/frenck/spook/issues

Diese Warnung, betrifft Spook, da muss der Entwickler wohl was machen.

2025-03-16 20:42:18.156 WARNING (Recorder) [homeassistant.components.sensor.recorder] Entity sensor.hichi_watt_use from integration template has state class total_increasing, but its state is not strictly increasing. Triggered by state 506.0 (510.0) with last_updated set to 2025-03-16T19:30:08.671145+00:00. Please create a bug report at https://github.com/home-assistant/core/issues?q=is%3Aopen+is%3Aissue+label%3A%22integration%3A+template%22

Das würde ich auch als ein Folgefehler ansehen.

2025-03-16 20:55:54.929 WARNING (MainThread) [homeassistant.components.websocket_api.http.connection] [546967882048] Alexsandra from 127.0.0.1 (Home Assistant/2025.2 (io.robbie.HomeAssistant; build:2025.1178; iOS 18.3.1)): Disconnected: Received error message during command phase: No PONG received after 27.5 seconds

Das ist eine Warnung, die ich nicht beurteilen kann, da ist etwas von Alexandra, iOS und robbie, keine Ahnung, musst Du dich mal schauen.

2025-03-16 21:38:38.925 ERROR (MainThread) [aioshelly.rpc_device.wsrpc] Invalid Message from host 192.168.68.197:80: Received message error

Auch keine Ahnung, was sich hinter der IP verbirgt, scheint etwas von Shelly zu sein.

2025-03-16 21:40:46.346 WARNING (MainThread) [habluetooth.scanner] hci0 (B8:27:EB:0F:B8:7F): Bluetooth scanner has gone quiet for 118.68925476074219s, restarting

Da scheint sich auch beim Bluetooth etwas aufzuschaukeln und muss dann neu gestartet werden, da würde ich sagen, dass alles andere mit Bluetooth auch Folgefehler sind.

2025-03-16 21:49:11.075 ERROR (Thread-7) [pychromecast.socket_client] [Alexsandra.TV(192.168.68.212):8009] Failed to connect to service MDNSServiceInfo(name='AI-PONT-DE-1226f2504d15de69ce4ddcc42bda615e._googlecast._tcp.local.'), retrying in 5.0s
2025-03-16 21:52:44.965 ERROR (Thread-7) [pychromecast.socket_client] [Alexsandra.TV(192.168.68.212):8009] Failed to connect to service MDNSServiceInfo(name='AI-PONT-DE-1226f2504d15de69ce4ddcc42bda615e._googlecast._tcp.local.'), retrying in 5.0s

Hier wieder etwas von Alexandra und TV, das sind Dinge, die ich nicht beurteilen kann, warum die ein Error schmeißen.

2025-03-16 22:13:10.927 WARNING (MainThread) [homeassistant.components.websocket_api.http.connection] [546970035120] Sonia from 127.0.0.1 (Home Assistant/2025.1.2-14946 (Android 14; moto g54 5G)): Disconnected: Received error message during command phase: No PONG received after 27.5 seconds
2025-03-16 22:13:12.926 WARNING (MainThread) [homeassistant.components.websocket_api.http.connection] [547007347104] Sonia from 127.0.0.1 (Home Assistant/2025.1.2-14946 (Android 14; moto g54 5G)): Disconnected: Received error message during command phase: No PONG received after 27.5 seconds
2025-03-16 22:13:20.927 WARNING (MainThread) [homeassistant.components.websocket_api.http.connection] [547149954016] Sonia from 127.0.0.1 (Mozilla/5.0 (Linux; Android 14; moto g54 5G Build/U1TDS34.94-12-9-10-2; wv) AppleWebKit/537.36 (KHTML, like Gecko) Version/4.0 Chrome/133.0.6943.138 Mobile Safari/537.36 Home Assistant/2025.1.2-14946 (Android 14; moto g54 5G)): Disconnected: Received error message during command phase: No PONG received after 27.5 seconds

Das ist jetzt mal Android, auch das ist mir unbekannt, was dahinter steckt.

@JB-Braunschweig

Nur der Vollständigkeit halber, in der configuration.yaml (analog zu Simon’s Info)

Das ist für den Fehler eher uninteressant, da das nur die Sensoren betrifft, und natürlich die Template Folgefehler, die durch das nicht erreichen des MQTT entstehen.

@JB-Braunschweig

auf einem Raspberry Pi 3B

Keine Ahnung, was Du alles installiert hast, aber vielleicht solltest Du da mal in etwas performanteres und mit mehr Speicher investieren, auch eine Stabiele Stromversorgung ist für RasPIs ganz wichtig.

Ich würde jetzt mal, aus dem Bauchheraus sagen, dass der kleine auf dem letzten Loch pfeift.
Dann betreibst Du das ganze mit SD-Kart, die kann auch eine macke haben, sodass das zum Ausfall führen kann.

Wie oben ja schon geschrieben, erkennt HA, das die Datenbank nicht ordentlich heruntergefahren wurde, installiere Dir mal, das Add-on SQLite Web und schaue nach, ob die Datenbank sauber ist, dazu das in das Query Feld einfügen und Execute, dann gedult, das kann etwas dauern.

PRAGMA integrity_check

Wenn alles ok, dann sieht das so aus

VG
Bernd

[JB-Braunschweig]

Danke für das umfangreiche Feedback!!

Was performanteres: Ein HA Green steht schon auf dem Wunschzettel, ich hab aber einen ungenutzten Orbsmart AW-10, auf dem ich mal probieren wollte, ob sich HA installieren lässt - kam noch nicht dazu…

logins: []
require_certificate: false
certfile: fullchain.pem
keyfile: privkey.pem
customize:
  active: false
  folder: mosquitto

Ports sind Standard.

Herunterfahren: Wir sind hier Baustelle, da fliegt gelegentlich auch die Sicherung raus, weshalb das die Großbaustelle für Sommer ist (inkl. PV).

Datenbank. Danke für den Tipp, er ist in letzter Zeit “langsamer” geworden.
Gleich SQLite Web installiert (nutze sonst MySQL/MariaDB, also nix allzu fremdes). Bei Eingabe in Query bekomme ich aber “Bad Gateway” (502)
Das Log:

[16:51:50] INFO: Service SQLite Web exited with code 256 (by signal 9)
[16:51:52] INFO: Starting SQLite Web...
[16:51:58] INFO: Service SQLite Web exited with code 256 (by signal 9)
[16:52:00] INFO: Starting SQLite Web...
WARNING: This is a development server. Do not use it in a production deployment. Use a production WSGI server instead.
 * Running on http://127.0.0.1:8080
Press CTRL+C to quit
 * Serving Flask app 'sqlite_web.sqlite_web'
 * Debug mode: off
2025/03/17 16:53:30 [error] 220#220: *16 upstream prematurely closed connection while reading response header from upstream, client: 172.30.32.2, server: a0d7b954-sqlite-web, request: "POST /query/ HTTP/1.1", upstream: "http://127.0.0.1:8080//api/hassio_ingress/fDkwGDM7xG0hUWgPbRF-BLWB0EMVeWHE4mf_-Z6krZ8/query/", host: "homeassistant.local:8123", referrer: "http://homeassistant.local:8123/api/hassio_ingress/fDkwGDM7xG0hUWgPbRF-BLWB0EMVeWHE4mf_-Z6krZ8/"
[16:53:34] INFO: Service SQLite Web exited with code 256 (by signal 9)
[16:53:38] INFO: Starting SQLite Web...
[16:53:51] INFO: Service SQLite Web exited with code 256 (by signal 9)
[16:53:55] INFO: Starting SQLite Web...
 * Serving Flask app 'sqlite_web.sqlite_web'
 * Debug mode: off
WARNING: This is a development server. Do not use it in a production deployment. Use a production WSGI server instead.
 * Running on http://127.0.0.1:8080
Press CTRL+C to quit
[16:54:10] INFO: Service SQLite Web exited with code 256 (by signal 9)
[16:54:11] INFO: Starting SQLite Web...
 * Serving Flask app 'sqlite_web.sqlite_web'
 * Debug mode: off
WARNING: This is a development server. Do not use it in a production deployment. Use a production WSGI server instead.
 * Running on http://127.0.0.1:8080
Press CTRL+C to quit
[16:54:40] INFO: Service SQLite Web exited with code 256 (by signal 9)
[16:54:42] INFO: Starting SQLite Web...
[16:54:49] INFO: Service SQLite Web exited with code 256 (by signal 9)
[16:54:51] INFO: Starting SQLite Web...
WARNING: This is a development server. Do not use it in a production deployment. Use a production WSGI server instead.
 * Running on http://127.0.0.1:8080
Press CTRL+C to quit
 * Serving Flask app 'sqlite_web.sqlite_web'
 * Debug mode: off

Ich fürchte, ich muss da das Projekt Orbsmart priorisieren… Gucken ob das funzt. Im Moment nehme ich “instabiles HA” in Kauf und melde mich, falls es hinterher wieder Probleme gibt. Im Moment schiebe ich es mal auf Raspberry 3B.

DANKE, das hilft mir natürlich sehr, auch wenn das Orbsmart Projekt mir grad’ eigentlich gar nicht reinpasst

Edit: P.S.: Integrity Check nach Neustart “ok”

[dp20eic]

Moin,

@JB-Braunschweig

Bei Eingabe in Query bekomme ich aber “Bad Gateway” (502)

ich kann mir gut vorstellen, dass da schon der RasPI am Limit ist, da müsste man erst mal schauen was da alles läuft und mal einiges anhlten, damit das Add-on starten kann.
Denn so sieht es normal aus

[18:04:08] INFO: Starting SQLite Web...
s6-rc: info: service legacy-services successfully started
 * Serving Flask app 'sqlite_web.sqlite_web'
 * Debug mode: off
WARNING: This is a development server. Do not use it in a production deployment. Use a production WSGI server instead.
 * Running on http://127.0.0.1:8080
Press CTRL+C to quit
[18:04:09] INFO: Starting NGINX...
127.0.0.1 - - [17/Mar/2025 18:04:10] "GET /api/hassio_ingress/Qy1e2EXq05aSjV36IUHULcyrEOE9CKqhx6UG4VgGPFQ/ HTTP/1.1" 200 -
127.0.0.1 - - [17/Mar/2025 18:04:10] "GET /api/hassio_ingress/Qy1e2EXq05aSjV36IUHULcyrEOE9CKqhx6UG4VgGPFQ/static/css/bootstrap.min.css HTTP/1.1" 304 -
127.0.0.1 - - [17/Mar/2025 18:04:10] "GET /api/hassio_ingress/Qy1e2EXq05aSjV36IUHULcyrEOE9CKqhx6UG4VgGPFQ/static/css/syntax-highlight.css HTTP/1.1" 304 -
127.0.0.1 - - [17/Mar/2025 18:04:10] "GET /api/hassio_ingress/Qy1e2EXq05aSjV36IUHULcyrEOE9CKqhx6UG4VgGPFQ/static/css/sqlbrowse.css HTTP/1.1" 304 -
127.0.0.1 - - [17/Mar/2025 18:04:10] "GET /api/hassio_ingress/Qy1e2EXq05aSjV36IUHULcyrEOE9CKqhx6UG4VgGPFQ/static/js/jquery-1.11.0.min.js HTTP/1.1" 304 -
127.0.0.1 - - [17/Mar/2025 18:04:10] "GET /api/hassio_ingress/Qy1e2EXq05aSjV36IUHULcyrEOE9CKqhx6UG4VgGPFQ/static/js/bootstrap.bundle.min.js HTTP/1.1" 304 -
127.0.0.1 - - [17/Mar/2025 18:04:10] "GET /api/hassio_ingress/Qy1e2EXq05aSjV36IUHULcyrEOE9CKqhx6UG4VgGPFQ/static/js/app.js HTTP/1.1" 304 -

@JB-Braunschweig

Edit: P.S.: Integrity Check nach Neustart “ok”

Ja, denn wenn er das nicht versuchen würde, könnte er nicht mehr auf die Datenbank und dann steht das System in einem undefiniertem Zustand aus dem Du dann nicht herauskommst.

Du kannst Dir auch das SQLite Datenbank File auf einen anderen Rechner ziehen und dor mit einem geeigneten Tool öffnen, ich nutze dazu DBeaver, dann kannst Du die Query auch dort durchführen
https://dbeaver.io/

VG
Bernd

[JB-Braunschweig]

Aaaaalso. Und DANKE @dp20eic (Bernd). Ja, das Problem war wohl die Hardware, wusste nicht, dass MQTT offenbar solchen Stress für diese bedeutet. Hab jetzt alles mit weitgehender Hilfe von Simons Anleitung auf einen Mini-PC (Orbsmart AW-10 Pro) verschoben. Heute lief MQTT stabil durch.

Trotzdem denke ich wäre es gut, wenn man in HA eine Automatisierung einrichten könnte, die als zusätzlicher Watchdog fungiert. Beim Ansatz von @RobertoCravallo fehlen mir da die Trigger, wo die herkommen. Scheint ja nicht nur mal bei MQTT zu passieren, dass was trotz Watchdog abschmiert?

Bei mir hat’s jedenfalls das (für mich neue) Energie-Dashboard jedesmal schön “zerschossen”, wenn da stundenlang nix ausgelesen wurde (s.u. Bild)und dann der halbe tägliche Verbrauch in einem Rutsch in der Electricity Usage angezeigt wurde/wird. Nervt doch sicher nicht nur mich, selbst wenn der Verursacher hier ein Hardwareproblem war?

Hier einfach mal das Beispiel der letzten beiden Tage, seit heute Mittag (ca. 11:30) läuft HA auf dem x86… Abgestürzt ist MQTT jeweils abends als Familienzeit die IT links liegen liess. Eine Warnung hätte mich dann sicher veranlasst, MQTT (oder ganz HA) wieder zu starten.

[RobertoCravallo]

@JB-Braunschweig

@RobertoCravallo fehlen mir da die Trigger, wo die herkommen.

Sehe eben einen Fehler in meinem Code, der MOSQUITO wurde nicht abgefangen.

        conditions:
          - condition: state
            entity: binary_sensor.mosquitto_broker_running
            state: "off"
          - condition: state
            entity: binary_sensor.cloudflared_lauft
            state: "off"
          - condition: state
            entity: binary_sensor.zigbee2mqtt_lauft
            state: "off"
          - condition: state
            entity: binary_sensor.zigbee2mqtt_lauft_2
            state: "off"
          - condition: state
            entity: binary_sensor.zigbee2mqtt_lauft_3
            state: "off"
          - condition: state
            entity: binary_sensor.mariadb_running
            state: "off"

Wenn Du folgendes eingibst, siehst Du die Entitäten. Bei Dir können die ja auch anders sein.

[dp20eic]

Moin,

@JB-Braunschweig

Trotzdem denke ich wäre es gut, wenn man in HA eine Automatisierung einrichten könnte, die als zusätzlicher Watchdog fungiert. Beim Ansatz von @RobertoCravallo fehlen mir da die Trigger, wo die herkommen. Scheint ja nicht nur mal bei MQTT zu passieren, dass was trotz Watchdog abschmiert?

in Deinem Fall beißt sich da die Katze in den Schwanz, der Rechner geht in die Knie, er stoppt etwas, um wieder Luft zu bekommen, aber Deine Automation startet es dann wieder, um das Ding wieder in die Knie zu zwingen und das Spiel beginnt von neuem.

Watchdog, können helfen, sollten aber nach zwei, maximal drei versuchen, nicht weiter versuchen, etwas das Crasht wieder zu starten, man belastet damit nur unnötig das System.
Man sollte lieber regelmäßig über die Logfiles schauen und sich um die Fehler kümmern, die auftauchen.
An einigen kann man nichts selbst machen, da kann man dann nur Issues beim Projekt aufmachen.
Zum anderen lernt man sein System kennen

VG
Bernd

[JB-Braunschweig]

Nur zur Klarstellung, der zusätzlich Watchdog soll mich informieren, damit ich Abhilfe (ad hoc oder besser dauerhaft) schaffen kann. Ich halte wenig davon, einen Watchdog auf was loszulassen, was schon einen eigenen hat. Er soll nur laut bellen, wenn der andere Hund pennt.

[JB-Braunschweig]

Also ich finde da leider nur mosquitto broker update. Sicher ein Grund, warum ich nicht weiterkomme. Wo kommen diese Entitäten her? … AHHHH

Die sind standardmäßig deaktiviert!
Unter Devices nach Mosquitto gucken (nicht nach MQTT)
Anklicken. 5 disbled entities

Dann aber bleibe ich hängen, weil conditions sind ja and if?

Also die gesamte Automation sähe bei mir so aus:

alias: MQTT Crash Warning
description: ""
triggers:
  - trigger: state
    entity_id:
      - binary_sensor.mosquitto_broker_running
    to: "off"
actions:
  - action: notify.mobile_app_jurgens_smartphone
    metadata: {}
    data:
      message: MQTT Crash
mode: single

Kann ich da irgendwie anhängen, dass der bspw. mehr als fünf Sekunden “off” sein soll? Denn eigentlich kann’s ja sein, dass der Watchdog greift. Aber wenn ich “Status wechselt zu off” verwende, wechselt der ja nicht fünf Sekunden lang, sondern bleibt dann eben off. Oder geht (Danke Watchdog?) wieder on …?

[dp20eic]

Moin,

@JB-Braunschweig

Watchdog

das ist dann kein Watchdog

Schau mal in den Thread, das scheint genau das zu sein, was Du suchst.

Überwachung mit Uptime Kuma

Ich betreibe mein HA als VM mit unraid und den Docker Container Uptime Kuma installiert. Es gibt dort verschiedenste Monitore, um den Status per http, Docker, mqtt, usw. zu überwachen. [image] Auch die Benachrichtigungswege sind vielfältig. Ich selber nutze Mail und Telegram. Das Ganze gibt es auch als HA AddOn - habe ich aber nicht ausprobiert. Gerade die Überwachung von zigbee Geräte per mqtt-Status finde ich klasse. So habe ich einige wichtige Gerätschaften im Blick. Hier eine Auszug me…

VG
Bernd