Forum Domoticz en français

Bonjour,
depuis plusieurs semaines j'ai des crash régulier de domoticz, parfois plusieurs fois par jour, parfois 1 à 2 fois pas semaine.
ma conf: raspberry 4, domoticz en beta à jour.
En plugin particulier ZigbeeForDomoticz
Je loggue et j'ai peu de symptôme, lorsque Domoticz crash j'ai un beau:
"Error: WebServer:8080 thread seems to have ended unexpectedly (last update 691.000000 seconds ago)", le last update changeant
dans les logs on voit que domoticz continue à travailler il y a des remontées, mais, je n'ai plus accès à l'interface web:

2025-06-27 10:54:18.513 RFX: Temp + Humidity (Bureau)
2025-06-27 10:54:21.816 RFX: Temp + Humidity (Temp Chambre 2)
2025-06-27 10:54:21.829 RFX: Temp + Humidity (Temp Entree)
2025-06-27 10:54:21.959 Error: WebServer:8080 thread seems to have ended unexpectedly (last update 972.000000 seconds ago)
2025-06-27 10:54:25.697 RFX: Temp + Humidity (Temp chambre)

Dans les remontées j'ai encore ce qui vient du RFX mais plus rien qui ne vienne de mon réseau Zigbee.

Seule solution, un restart de domoticz.
Je n'ai pas d'idée pour augmenter le niveau de log ou chercher des infos ailleurs.
Je suis preneur de toutes pistes.
Merci

Il y a des sujets dans la section du plugin ZigBeeForDomoticZ à propos de problématiques de mémoires. Tu peux regarder si tu n'aurais pas les mêmes symptômes ? Si oui, je déplacerai ce sujet dans la section du plugin (ne réponds pas sur un post déjà ouvert / en cours).

Sujet déplacé dans la section dédiée au plugin ZigBeeForDomoticZ.

je reprend et surtout je complète mon messages suite aux déplacements dans la section ZigbeeForDomoticz

depuis plusieurs semaines j'ai des crash régulier de domoticz, parfois plusieurs fois par jour.
ma conf: raspberry 4, domoticz en beta à jour.
ZigbeeForDomoticz à jour (mise à jour en stable cette semaine mais ça n'a pas réglé le problème).
2 contrôleurs SLZB-06M
Pour le premier contrôleur: une vingtaine d'objet des NODON SDIN 4-2-2, des prises connectées NOUS, des thermomètres..
Pour le second: 5 objets, 1 NODON SIN 4-2-2, une prise connectée, un thermométre...

Je loggue et j'ai peu de symptôme, lorsque Domoticz crash j'ai un beau:

Error: WebServer:8080 thread seems to have ended unexpectedly (last update 691.000000 seconds ago)

le last update changeant
dans les logs on voit que domoticz continue à travailler il y a des remontées, mais, je n'ai plus accès à l'interface web:

2025-06-27 10:54:18.513 RFX: Temp + Humidity (Bureau)
2025-06-27 10:54:21.816 RFX: Temp + Humidity (Temp Chambre 2)
2025-06-27 10:54:21.829 RFX: Temp + Humidity (Temp Entree)
2025-06-27 10:54:21.959 Error: WebServer:8080 thread seems to have ended unexpectedly (last update 972.000000 seconds ago)
2025-06-27 10:54:25.697 RFX: Temp + Humidity (Temp chambre)

Dans les remontées j'ai encore ce qui vient du RFX mais plus rien qui ne vienne de mon réseau Zigbee.

Dans ces situations, un restart de domoticz ne suffit souvent pas, quand je redémarre domoticz, au start il me dit que des ports ne sont pas libérés, même si le process domoticz est arrêté.
Dans ces cas là (la plupart du temps), il faut que je reboot.
Je n'arrive pas à avoir plus d'info dans les logs.
Quand domoticz est planté, la CPU du rapsberry n'est pas chargé outre mesure.

Comme test hier, j'ai désactivé dans l'onglet matériel le contrôleur le plus chargé et laissé le moins chargé, au bout de 5h domoticz s'est planté.
J'ai ensuite désactivé les 2 contrôleurs dans l'onglet matériel, et domoticz n'a toujours pas planté. Il est donc resté vivant environ 24h sans le plugin ZigbeeForDomoticz, on peut raisonnablement penser que le problème se trouve autour de mon réseau Zigbee!

Merci pour votre aide et pout toutes pistes possibles pour isoler le problème...

et je rajoute des élèments...
Après avoir remis mes deux contrôleurs actifs, crash de domoticz 1h après.
Lorsque j'essaye d'attendre le premier contrôleur (le plus chargé) http://@ip_domoticz:9440 (port 9440) ça me dit que le site est inaccessible
Lorsque j'essaye d'attendre le second contrôleur (le moins chargé) http://@ip_domoticz:9470 (port 9470), j'atteins bien l'interface de contrôle
mais je ne vois rien au niveau des logs sur le sujet zigbee

#sudo tail -f /tmp/domoticz.txt
2025-06-29 10:46:37.914 RFX: Temp + Humidity (Temp Chambre Ami)
2025-06-29 10:46:40.058 RFX: Temp + Humidity (Temp Entree)
2025-06-29 10:46:42.093 Error: WebServer:8080 thread seems to have ended unexpectedly (last update 2758.000000 seconds ago)
...
2025-06-29 10:47:30.483 Enphase: General/kWh (Enphase kWh Production)
2025-06-29 10:47:30.489 Enphase: General/kWh (Enphase total-consumption)
2025-06-29 10:47:30.495 Enphase: General/kWh (Enphase net-consumption)
2025-06-29 10:47:31.649 RFX: Temp + Humidity (Unknown)
2025-06-29 10:47:32.225 RFX: Temp + Humidity (Temp chambre)

Si ton coordinateur est un Texas Instrument en mode ZNP, peux-tu essayer de basculer sur la branche rc-7.1.023

Code : Tout sélectionner

git pull
git checkout rc-7.1.023
git pull

Code : Tout sélectionner

sudo python3 -m pip install -r requirements.txt --upgrade

restart de Domoticz

Il serait intéressant que tu nous donnes les logs (Domoticz et plugin pour avoir le context)

Merci pour l'aide.
je suis partie de là: https://easydomoticz.com/forum/viewtopi ... 57#p124357
et pour mes deux SLZB-06M, ça semble plutôt être du SiliconLabs alors EZSP.
J'ai tout de même essayé de passer en rc-7.1.023 pour voir
Pour Domoticz que veux tu comme log? il y en a beaucoup...
et par contre, je ne sais pas comme récupérer les logs du plugin.

Bonjour,
Dans le webui du plugin, les trois barres en haut à droite droite, outils/outils/ puis clic sur log du plugin.
Attend un peu et le téléchargement du log va commencer (ça peut être long des fois).

Merci!
je suis allé cherché là où ça semble partir en sucette avec un plantage vers 10h et un redemerrage à 10:49
, dite moi si vous voulez tous les logs:

Code : Tout sélectionner

2025-06-29 09:59:58,180 INFO    :b'UpdateDevice - (ZAmperage6 - PompePiscine) 0:2.76'
2025-06-29 09:59:59,246 INFO    :b'UpdateDevice - (ZAmperage6 - PompePiscine) 0:2.77'
2025-06-29 10:00:00,131 WARNING :Executing <Task pending name='Task-1' coro=<start_zigpy_task() running at /home/pi/domoticz/plugins/Domoticz-Zigbee/Classes/ZigpyTransport/zigpyThread.py:162> wait_for=<Future pending cb=[Task.__wakeup()] created at /usr/lib/python3.11/asyncio/base_events.py:427> cb=[_run_until_complete_cb() at /usr/lib/python3.11/asyncio/base_events.py:180] created at /usr/lib/python3.11/asyncio/tasks.py:670> took 0.239 seconds
2025-06-29 10:00:00,180 INFO    :b'UpdateDevice - (ZAmperage6 - PompePiscine) 0:2.76'
2025-06-29 10:00:16,326 WARNING :+ Connection to the radio was lost: <class 'bellows.ash.NcpFailure'> <NcpFailure(code=<NcpResetCode.ERROR_EXCEEDED_MAXIMUM_ACK_TIMEOUT_COUNT: 81>)>
2025-06-29 10:00:16,327 ERROR   :NCP reset due to exceeded maximum ACK timeout count, plugin restart required
2025-06-29 10:00:22,936 ERROR   : [ZigpyCom_64 1441498] [           Plugin] Connection lost with coordinator, restarting plugin
2025-06-29 10:00:44,780 DEBUG   :Starting new HTTPS connection (1): z4d.pipiche.net:443
2025-06-29 10:00:44,787 INFO    :b'UpdateDevice - (ZAmperage6 - PompePiscine) 0:2.77'
2025-06-29 10:00:45,001 INFO    :b'UpdateDevice - (ZAmperage6 - PompePiscine) 0:2.76'
2025-06-29 10:00:45,653 DEBUG   :https://z4d.pipiche.net:443 "GET /matomo.php?idsite=9&rec=1&apiv=1&action_name=Plugin+Action&uid=d9d05611dd812fd6f3357f8c1e1f51d288fec96d6fafda82c7637ca1ad8b574f&e_c=Plugin&e_a=Restart&e_n=Plugin+Restart HTTP/1.1" 200 43
2025-06-29 10:00:46,039 WARNING :Executing <Handle ThreadsafeProxy.__getattr__.<locals>.func_wrapper.<locals>.check_result_wrapper() at /home/pi/Domoticz_Python_Environment/bellows/thread.py:110 created at /home/pi/Domoticz_Python_Environment/bellows/thread.py:120> took 29.713 seconds
2025-06-29 10:00:46,052 WARNING :+ Connection to the radio was lost: <class 'bellows.ash.NcpFailure'> <NcpFailure(code=<NcpResetCode.ERROR_EXCEEDED_MAXIMUM_ACK_TIMEOUT_COUNT: 81>)>
2025-06-29 10:00:46,080 WARNING :+ shutdown or restart in progress
2025-06-29 10:00:46,080 WARNING :+ Connection to the radio was lost: <class 'bellows.ash.NcpFailure'> <NcpFailure(code=<NcpResetCode.ERROR_EXCEEDED_MAXIMUM_ACK_TIMEOUT_COUNT: 81>)>
2025-06-29 10:00:46,081 WARNING :+ shutdown or restart in progress
2025-06-29 10:00:46,086 WARNING :+ Connection to the radio was lost: <class 'bellows.ash.NcpFailure'> <NcpFailure(code=<NcpResetCode.ERROR_EXCEEDED_MAXIMUM_ACK_TIMEOUT_COUNT: 81>)>
2025-06-29 10:00:46,087 WARNING :+ shutdown or restart in progress
2025-06-29 10:00:46,098 WARNING :+ Connection to the radio was lost: <class 'bellows.ash.NcpFailure'> <NcpFailure(code=<NcpResetCode.ERROR_EXCEEDED_MAXIMUM_ACK_TIMEOUT_COUNT: 81>)>
2025-06-29 10:00:46,098 WARNING :+ shutdown or restart in progress
2025-06-29 10:00:46,099 WARNING :+ Connection to the radio was lost: <class 'bellows.ash.NcpFailure'> <NcpFailure(code=<NcpResetCode.ERROR_EXCEEDED_MAXIMUM_ACK_TIMEOUT_COUNT: 81>)>
2025-06-29 10:00:46,172 WARNING :+ shutdown or restart in progress
2025-06-29 10:00:46,172 WARNING :+ Connection to the radio was lost: <class 'bellows.ash.NcpFailure'> <NcpFailure(code=<NcpResetCode.ERROR_EXCEEDED_MAXIMUM_ACK_TIMEOUT_COUNT: 81>)>
2025-06-29 10:00:46,173 WARNING :+ shutdown or restart in progress
2025-06-29 10:00:46,173 WARNING :+ Connection to the radio was lost: <class 'bellows.ash.NcpFailure'> <NcpFailure(code=<NcpResetCode.ERROR_EXCEEDED_MAXIMUM_ACK_TIMEOUT_COUNT: 81>)>
2025-06-29 10:00:46,173 WARNING :+ shutdown or restart in progress
2025-06-29 10:00:46,173 WARNING :+ Connection to the radio was lost: <class 'bellows.ash.NcpFailure'> <NcpFailure(code=<NcpResetCode.ERROR_EXCEEDED_MAXIMUM_ACK_TIMEOUT_COUNT: 81>)>
2025-06-29 10:00:46,174 WARNING :+ shutdown or restart in progress
2025-06-29 10:00:46,196 INFO    :b'UpdateDevice - (ZAmperage6 - PompePiscine) 0:2.77'
2025-06-29 10:00:46,250 INFO    :b'UpdateDevice - (ZAmperage6 - PompePiscine) 0:2.76'
2025-06-29 10:00:46,303 INFO    :b'UpdateDevice - (ZAmperage6 - PompePiscine) 0:2.77'
2025-06-29 10:00:46,310 INFO    :b'UpdateDevice - (ZAmperage6 - PompePiscine) 0:2.76'
2025-06-29 10:00:46,454 DEBUG   :Starting new HTTPS connection (1): z4d.pipiche.net:443
2025-06-29 10:00:46,464 WARNING :Executing <Task pending name='_unicast_command-zcl_raw_default_response-<Device model=None manuf=None nwk=0x9EFE ieee=a4:c1:38:00:a0:84:3c:a7 is_initialized=False>-0-106' coro=<measure_execution_time.<locals>.wrapper() running at /home/pi/domoticz/plugins/Domoticz-Zigbee/Classes/ZigpyTransport/zigpyThread.py:748> wait_for=<Future pending cb=[Task.__wakeup()] created at /usr/lib/python3.11/asyncio/base_events.py:427> created at /usr/lib/python3.11/asyncio/tasks.py:374> took 0.138 seconds
2025-06-29 10:00:46,493 WARNING :Watchdog failure
Traceback (most recent call last):
  File "/home/pi/Domoticz_Python_Environment/zigpy/application.py", line 661, in _watchdog_loop
    await self.watchdog_feed()
  File "/home/pi/Domoticz_Python_Environment/zigpy/application.py", line 647, in watchdog_feed
    await self._watchdog_feed()
  File "/home/pi/Domoticz_Python_Environment/bellows/zigbee/application.py", line 1004, in _watchdog_feed
    current_counters = await self._ezsp.read_counters()
                       ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/home/pi/Domoticz_Python_Environment/bellows/ezsp/v4/__init__.py", line 191, in read_counters
    (res,) = await self.readCounters()
             ^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/home/pi/Domoticz_Python_Environment/bellows/ezsp/protocol.py", line 129, in command
    await self._gw.send_data(data)
  File "/usr/lib/python3.11/asyncio/futures.py", line 287, in __await__
    yield self  # This tells Task to wait for completion.
    ^^^^^^^^^^
  File "/usr/lib/python3.11/asyncio/tasks.py", line 339, in __wakeup
    future.result()
  File "/usr/lib/python3.11/asyncio/futures.py", line 203, in result
    raise self._exception.with_traceback(self._exception_tb)
  File "/usr/lib/python3.11/asyncio/tasks.py", line 269, in __step
    result = coro.throw(exc)
             ^^^^^^^^^^^^^^^
  File "/home/pi/Domoticz_Python_Environment/bellows/uart.py", line 31, in send_data
    await self._transport.send_data(data)
  File "/home/pi/Domoticz_Python_Environment/bellows/ash.py", line 708, in send_data
    await asyncio.shield(
  File "/usr/lib/python3.11/asyncio/futures.py", line 287, in __await__
    yield self  # This tells Task to wait for completion.
    ^^^^^^^^^^
  File "/usr/lib/python3.11/asyncio/tasks.py", line 339, in __wakeup
    future.result()
  File "/usr/lib/python3.11/asyncio/futures.py", line 203, in result
    raise self._exception.with_traceback(self._exception_tb)
  File "/usr/lib/python3.11/asyncio/tasks.py", line 267, in __step
    result = coro.send(None)
             ^^^^^^^^^^^^^^^
  File "/home/pi/Domoticz_Python_Environment/bellows/ash.py", line 633, in _send_data_frame
    raise NcpFailure(
bellows.ash.NcpFailure: NcpResetCode.ERROR_EXCEEDED_MAXIMUM_ACK_TIMEOUT_COUNT
2025-06-29 10:00:46,945 WARNING :+ Connection to the radio was lost: <class 'bellows.ash.NcpFailure'> <NcpFailure(code=<NcpResetCode.ERROR_EXCEEDED_MAXIMUM_ACK_TIMEOUT_COUNT: 81>)>
2025-06-29 10:00:46,946 WARNING :+ shutdown or restart in progress
2025-06-29 10:00:46,946 WARNING :Executing <Task finished name='watchdog_loop' coro=<ControllerApplication._watchdog_loop() done, defined at /home/pi/Domoticz_Python_Environment/bellows/zigbee/application.py:985> result=None created at /usr/lib/python3.11/asyncio/tasks.py:374> took 0.454 seconds
2025-06-29 10:00:46,952 INFO    :b"Warning while submitting - rawaps_read_attribute_req a4:c1:38:00:a0:84:3c:a7/0x9efe 0x104 0xB04 payload: b'\\x10I\\x00\\x05\\x05\\x08\\x05\\x0b\\x05' AckIsDisable: True extended_timeout: False Attempt: 1 Exception: 'NcpResetCode.ERROR_EXCEEDED_MAXIMUM_ACK_TIMEOUT_COUNT' (NcpFailure)"
2025-06-29 10:00:46,959 INFO    :b"Warning while submitting - rawaps_read_attribute_req a4:c1:38:b0:34:d1:5a:f3/0x59c1 0x104 0xB04 payload: b'\\x10$\\x00\\x05\\x05\\x08\\x05\\x0b\\x05' AckIsDisable: True extended_timeout: False Attempt: 1 Exception: 'NcpResetCode.ERROR_EXCEEDED_MAXIMUM_ACK_TIMEOUT_COUNT' (NcpFailure)"
2025-06-29 10:00:46,965 INFO    :b"Warning while submitting - zcl_raw_default_response a4:c1:38:00:a0:84:3c:a7/0x9efe 0x104 0x0 payload: b'\\x08j\\x0b\\n\\x00' AckIsDisable: True extended_timeout: False Attempt: 1 Exception: 'NcpResetCode.ERROR_EXCEEDED_MAXIMUM_ACK_TIMEOUT_COUNT' (NcpFailure)"
2025-06-29 10:00:46,974 INFO    :b"Warning while submitting - zcl_raw_default_response a4:c1:38:00:a0:84:3c:a7/0x9efe 0x104 0x0 payload: b'\\x08j\\x0b\\n\\x00' AckIsDisable: True extended_timeout: False Attempt: 1 Exception: 'NcpResetCode.ERROR_EXCEEDED_MAXIMUM_ACK_TIMEOUT_COUNT' (NcpFailure)"
2025-06-29 10:00:46,982 INFO    :b"Warning while submitting - zcl_raw_default_response a4:c1:38:00:a0:84:3c:a7/0x9efe 0x104 0x0 payload: b'\\x08j\\x0b\\n\\x00' AckIsDisable: True extended_timeout: False Attempt: 1 Exception: 'NcpResetCode.ERROR_EXCEEDED_MAXIMUM_ACK_TIMEOUT_COUNT' (NcpFailure)"
2025-06-29 10:00:46,990 INFO    :b"Warning while submitting - zcl_raw_default_response a4:c1:38:00:a0:84:3c:a7/0x9efe 0x104 0x0 payload: b'\\x08j\\x0b\\n\\x00' AckIsDisable: True extended_timeout: False Attempt: 1 Exception: 'NcpResetCode.ERROR_EXCEEDED_MAXIMUM_ACK_TIMEOUT_COUNT' (NcpFailure)"
2025-06-29 10:00:46,996 INFO    :b"Warning while submitting - zcl_raw_default_response a4:c1:38:00:a0:84:3c:a7/0x9efe 0x104 0x0 payload: b'\\x08j\\x0b\\n\\x00' AckIsDisable: True extended_timeout: False Attempt: 1 Exception: 'NcpResetCode.ERROR_EXCEEDED_MAXIMUM_ACK_TIMEOUT_COUNT' (NcpFailure)"
2025-06-29 10:00:47,010 INFO    :b"Warning while submitting - zcl_raw_default_response a4:c1:38:00:a0:84:3c:a7/0x9efe 0x104 0x0 payload: b'\\x08j\\x0b\\n\\x00' AckIsDisable: True extended_timeout: False Attempt: 1 Exception: 'NcpResetCode.ERROR_EXCEEDED_MAXIMUM_ACK_TIMEOUT_COUNT' (NcpFailure)"
2025-06-29 10:00:47,017 INFO    :b"Warning while submitting - zcl_raw_default_response a4:c1:38:00:a0:84:3c:a7/0x9efe 0x104 0x0 payload: b'\\x08j\\x0b\\n\\x00' AckIsDisable: True extended_timeout: False Attempt: 1 Exception: 'NcpResetCode.ERROR_EXCEEDED_MAXIMUM_ACK_TIMEOUT_COUNT' (NcpFailure)"
2025-06-29 10:00:47,024 INFO    :b"Warning while submitting - zcl_raw_default_response a4:c1:38:00:a0:84:3c:a7/0x9efe 0x104 0x0 payload: b'\\x08j\\x0b\\n\\x00' AckIsDisable: True extended_timeout: False Attempt: 1 Exception: 'NcpResetCode.ERROR_EXCEEDED_MAXIMUM_ACK_TIMEOUT_COUNT' (NcpFailure)"
2025-06-29 10:00:47,033 DEBUG   :https://z4d.pipiche.net:443 "GET /matomo.php?idsite=9&rec=1&apiv=1&action_name=Plugin+Action&uid=d9d05611dd812fd6f3357f8c1e1f51d288fec96d6fafda82c7637ca1ad8b574f&e_c=Plugin&e_a=Shutdown&e_n=Plugin+Shutdown HTTP/1.1" 200 43
2025-06-29 10:00:47,050 INFO    :b"Warning while submitting - zcl_raw_default_response a4:c1:38:00:a0:84:3c:a7/0x9efe 0x104 0x0 payload: b'\\x08j\\x0b\\n\\x00' AckIsDisable: True extended_timeout: False Attempt: 1 Exception: 'NcpResetCode.ERROR_EXCEEDED_MAXIMUM_ACK_TIMEOUT_COUNT' (NcpFailure)"
2025-06-29 10:00:47,084 DEBUG   :Starting new HTTPS connection (1): z4d.pipiche.net:443
2025-06-29 10:00:47,138 INFO    :b"Warning while submitting - zcl_raw_default_response a4:c1:38:00:a0:84:3c:a7/0x9efe 0x104 0x0 payload: b'\\x08j\\x0b\\n\\x00' AckIsDisable: True extended_timeout: False Attempt: 1 Exception: 'NcpResetCode.ERROR_EXCEEDED_MAXIMUM_ACK_TIMEOUT_COUNT' (NcpFailure)"
2025-06-29 10:00:47,175 INFO    :b"Warning while submitting - zcl_raw_default_response a4:c1:38:00:a0:84:3c:a7/0x9efe 0x104 0x0 payload: b'\\x08j\\x0b\\n\\x00' AckIsDisable: True extended_timeout: False Attempt: 1 Exception: 'NcpResetCode.ERROR_EXCEEDED_MAXIMUM_ACK_TIMEOUT_COUNT' (NcpFailure)"
2025-06-29 10:00:47,192 INFO    :b"Warning while submitting - zcl_raw_default_response a4:c1:38:00:a0:84:3c:a7/0x9efe 0x104 0x0 payload: b'\\x08j\\x0b\\n\\x00' AckIsDisable: True extended_timeout: False Attempt: 1 Exception: 'NcpResetCode.ERROR_EXCEEDED_MAXIMUM_ACK_TIMEOUT_COUNT' (NcpFailure)"
2025-06-29 10:00:47,218 INFO    :b"Warning while submitting - zcl_raw_default_response a4:c1:38:00:a0:84:3c:a7/0x9efe 0x104 0x0 payload: b'\\x08j\\x0b\\n\\x00' AckIsDisable: True extended_timeout: False Attempt: 1 Exception: 'NcpResetCode.ERROR_EXCEEDED_MAXIMUM_ACK_TIMEOUT_COUNT' (NcpFailure)"
2025-06-29 10:00:47,240 INFO    :b"Warning while submitting - zcl_raw_default_response a4:c1:38:00:a0:84:3c:a7/0x9efe 0x104 0x0 payload: b'\\x08j\\x0b\\n\\x00' AckIsDisable: True extended_timeout: False Attempt: 1 Exception: 'NcpResetCode.ERROR_EXCEEDED_MAXIMUM_ACK_TIMEOUT_COUNT' (NcpFailure)"
2025-06-29 10:00:47,256 DEBUG   :https://z4d.pipiche.net:443 "GET /matomo.php?idsite=9&rec=1&apiv=1&action_name=Z4DPluginInfos&uid=d9d05611dd812fd6f3357f8c1e1f51d288fec96d6fafda82c7637ca1ad8b574f&dimension1=2025.1+build+16729&dimension2=Unknown+Silicon+Labs&dimension3=7.1.022&dimension4=UNK+-+7.3.1.0+build+176&dimension5=Medium&dimension6=6.466&dimension7=Debian+GNU+Linux+12&dimension8=python+3.11.2+arch+64bit+machine+aarch64+processor&dimension9=1+day&dimension11=Raspberry+Pi+4+Model+B+Rev+1.1 HTTP/1.1" 200 43
2025-06-29 10:00:47,276 INFO    :b'Flushing plugin database onto disk'
2025-06-29 10:00:47,279 INFO    :b"Warning while submitting - zcl_raw_default_response a4:c1:38:00:a0:84:3c:a7/0x9efe 0x104 0x0 payload: b'\\x08j\\x0b\\n\\x00' AckIsDisable: True extended_timeout: False Attempt: 1 Exception: 'NcpResetCode.ERROR_EXCEEDED_MAXIMUM_ACK_TIMEOUT_COUNT' (NcpFailure)"
2025-06-29 10:00:47,338 INFO    :b'onStop called'
2025-06-29 10:00:47,506 INFO    :b'Shutding down zigpy thread'
2025-06-29 10:00:47,763 WARNING :Executing <Task pending name='Task-1' coro=<start_zigpy_task() running at /home/pi/domoticz/plugins/Domoticz-Zigbee/Classes/ZigpyTransport/zigpyThread.py:179> wait_for=<Future pending cb=[_chain_future.<locals>._call_check_cancel() at /usr/lib/python3.11/asyncio/futures.py:387, Task.__wakeup()] created at /usr/lib/python3.11/asyncio/base_events.py:427> cb=[_run_until_complete_cb() at /usr/lib/python3.11/asyncio/base_events.py:180] created at /usr/lib/python3.11/asyncio/tasks.py:670> took 0.259 seconds
2025-06-29 10:00:47,765 WARNING :Failed to create backup
2025-06-29 10:00:47,771 WARNING :+ Connection to the radio was lost: <class 'NoneType'> None
2025-06-29 10:00:47,772 WARNING :+ shutdown or restart in progress
2025-06-29 10:00:48,810 INFO    :b'Cancelling 0 outstanding tasks'
2025-06-29 10:00:49,814 DEBUG   :Close <_UnixSelectorEventLoop running=False closed=False debug=True>
2025-06-29 10:00:50,542 INFO    :b'Event loop closed successfully in zigpy_thread.'
2025-06-29 10:00:58,931 INFO    :b'Closing all client connections...'
2025-06-29 10:00:58,931 INFO    :b'++ WebUI - server stopped'
2025-06-29 10:00:58,942 INFO    :b'WebUI shutdown completed'
2025-06-29 10:00:59,085 INFO    :b'Closing Logging Management'
2025-06-29 10:49:19,482 INFO    :b'Z4D is starting with stable7-7.1.022'
2025-06-29 10:49:19,489 INFO    :b"Z4D Multi-instances detected. Enabling 'asyncio' workaround"
2025-06-29 10:49:19,495 INFO    :b'Z4D Database found: DeviceList-64.txt'
2025-06-29 10:49:19,495 INFO    :b'Z4D Certified devices database /home/pi/Domoticz_Python_Environment/z4d_certified_devices/'
2025-06-29 10:49:19,496 INFO    :b'Z4D loads ZCL Cluster definitions'
2025-06-29 10:49:19,538 INFO    :b'Z4D loaded 16 configuration from legacy database.'
2025-06-29 10:49:19,539 INFO    :b'Z4D loads 0 configuration from the local certified Db.'
2025-06-29 10:49:20,045 INFO    :b'Z4D loads 644 certified devices from repository version [6.466]'
2025-06-29 10:49:20,046 INFO    :b'Z4D loading plugin database'
2025-06-29 10:49:20,408 INFO    :b'Z4D loads 22 entries from /home/pi/domoticz/plugins/Domoticz-Zigbee/Data/DeviceList-64.txt'
2025-06-29 10:49:20,449 INFO    :b"Z4D is starting transport Mode: 'ZigpyEZSP' Serial: '/dev/serial1' IP: '192.168.0.97 'Port: '6640'"
2025-06-29 10:49:23,574 INFO    :b'Z4D starting EZSP'

ca ressemble à un problème hardware ... essayes de débrancher ta clef puis de la rebrancher

Forum Domoticz en français

Crash domoticz Error: WebServer:8080 thread seems to have ended unexpectedly

Crash domoticz Error: WebServer:8080 thread seems to have ended unexpectedly

Re: Crash domoticz Error: WebServer:8080 thread seems to have ended unexpectedly

Modération

Re: Crash domoticz Error: WebServer:8080 thread seems to have ended unexpectedly

Re: Crash domoticz Error: WebServer:8080 thread seems to have ended unexpectedly

Re: Crash domoticz Error: WebServer:8080 thread seems to have ended unexpectedly

Re: Crash domoticz Error: WebServer:8080 thread seems to have ended unexpectedly

Re: Crash domoticz Error: WebServer:8080 thread seems to have ended unexpectedly

Re: Crash domoticz Error: WebServer:8080 thread seems to have ended unexpectedly

Re: Crash domoticz Error: WebServer:8080 thread seems to have ended unexpectedly