[Résolu] startup en boucle

[bartras]

Bonjour,

Je débute avec ce nouveau plugin.
Ma question porte sur les logs du Zigate status.
Quand je regarde je vois des startup en boucle... Je ne trouve pas ça bien normal.
Mais lorsque je vais dans les log domoticz je n'ai pas d'erreur.



Pourrait on m'aider ?
Merci.

[Deufo]

Bonjour,
Regarder dans le repertoire du plugin dans Logs/
Cela pourrait aider pour comprendre.

[bartras]

Merci, j'ai été voir et j'ai les fichiers suivants:

PluginZigbee_02.log
PluginZigbee_02.log.2022-12-07
PluginZigbee_02.log.2022-12-08
PluginZigbee_log_error_history.json

Dans

PluginZigbee_02.log

j'ai :

Code : Tout sélectionner

2022-12-09 00:00:03,492 INFO    : [ MainThread 21570] onDisconnect - Closing Name: 'Zigate Server Connection', Transport: 'TCP/IP', Protocol: 'HTTP', Address: '', Port: '9440', Baud: -1, Timeout: 0, Connected: False, Parent: 'None'
2022-12-09 00:00:03,497 INFO    : [ MainThread 21570] onStop called
2022-12-09 00:00:03,498 INFO    : [ MainThread 21570] onStop calling (1) domoticzDb DeviceStatus closed
2022-12-09 00:00:03,499 INFO    : [ MainThread 21570] onStop calling (3) Transport off
2022-12-09 00:00:03,499 INFO    : [ MainThread 21570] Shuting down co-routine
2022-12-09 00:00:03,501 INFO    : [ZigpyForwarder_2 21606] ZigpyTransport: thread_processing_and_sending Thread stop.
2022-12-09 00:00:03,544 INFO    : [ ZigpyCom_2 21605] worker_loop: Exiting Worker loop. Semaphore : 7
2022-12-09 00:00:03,546 INFO    : [ ZigpyCom_2 21605] worker_loop:      Semaphore[00:12:4b:00:25:8d:4a:55]
2022-12-09 00:00:03,547 INFO    : [ ZigpyCom_2 21605] worker_loop:      Semaphore[a4:c1:38:e4:96:8b:d5:e6]
2022-12-09 00:00:03,548 INFO    : [ ZigpyCom_2 21605] worker_loop:      Semaphore[a4:c1:38:b1:25:ed:0f:86]
2022-12-09 00:00:03,548 INFO    : [ ZigpyCom_2 21605] worker_loop:      Semaphore[a4:c1:38:28:49:72:38:21]
2022-12-09 00:00:03,555 INFO    : [ ZigpyCom_2 21605] worker_loop:      Semaphore[a4:c1:38:df:02:22:d1:6e]
2022-12-09 00:00:03,557 INFO    : [ ZigpyCom_2 21605] worker_loop:      Semaphore[00:12:4b:00:24:c2:e9:78]
2022-12-09 00:00:03,558 INFO    : [ ZigpyCom_2 21605] worker_loop:      Semaphore[a4:c1:38:23:35:6c:4e:06]
2022-12-09 00:00:18,656 INFO    : [ ZigpyCom_2 21605] Coordinator backup is available: /home/pi/domoticz/plugins/Domoticz-Zigbee/Data//Coordinator-02.backup
2022-12-09 00:00:20,700 INFO    : [ MainThread 21570] onStop calling (4) WebServer off
2022-12-09 00:00:20,702 INFO    : [ MainThread 21570] onStop called (4) WebServer off
2022-12-09 00:00:20,709 INFO    : [ MainThread 21570] onStop calling (5) Plugin Database saved
2022-12-09 00:00:20,999 INFO    : [ MainThread 21570] onStop called (5) Plugin Database saved
2022-12-09 00:00:21,002 INFO    : [ MainThread 21570] onStop calling (6) Close Logging Management
2022-12-09 00:00:31,643 INFO    : [ MainThread 22056] Zigbee for Domoticz (z4d) plugin stable6-6.3.007 started
2022-12-09 00:00:31,681 ERROR   : [       MainThread] domoticz_request - wrong URL toget access to Domoticz JSON/API: http://192.168.1.101:8080/json.htm?type=hardware
2022-12-09 00:00:31,703 ERROR   : [       MainThread] domoticz_request - wrong URL toget access to Domoticz JSON/API: http://192.168.1.101:8080/json.htm?type=hardware
2022-12-09 00:00:31,737 INFO    : [ MainThread 22056] Plugin Database: DeviceList-2.txt
2022-12-09 00:00:31,739 INFO    : [ MainThread 22056] DeviceConf loaded - 22 confs loaded
2022-12-09 00:00:32,258 INFO    : [ MainThread 22056] DeviceConf loaded - 369 confs loaded
2022-12-09 00:00:32,259 INFO    : [ MainThread 22056] load ListOfDevice
2022-12-09 00:00:32,833 INFO    : [ MainThread 22056] 18 Entries loaded from /home/pi/domoticz/plugins/Domoticz-Zigbee/Data/DeviceList-2.txt
2022-12-09 00:00:32,967 INFO    : [ MainThread 22056] Transport mode: ZigpyZNP
2022-12-09 00:00:36,654 DEBUG   :Using selector: EpollSelector
2022-12-09 00:00:36,657 INFO    : [ MainThread 22056] Start Zigpy Transport on ZNP
2022-12-09 00:00:36,698 INFO    : [ MainThread 22056] ZigpyTransport __init__
2022-12-09 00:00:36,707 INFO    : [ ZigpyCom_2 22082] Starting radio znp port: /dev/serial/by-id/usb-ITead_Sonoff_Zigbee_3.0_USB_Dongle_Plus_c4e39f672f1aec11b0b37fe5f01c6278-if00-port0
2022-12-09 00:00:36,712 INFO    : [ZigpyForwarder_2 22083] ZigpyTransport: thread_processing_and_sending Thread start.
2022-12-09 00:00:36,714 INFO    : [ MainThread 22056] Start Web Server connection
2022-12-09 00:00:36,801 INFO    : [ MainThread 22056] Web backend for Web User Interface started on port: 9440
2022-12-09 00:00:36,803 INFO    : [ MainThread 22056] Domoticz Widgets usage is at 9.0 % (232 units free)
2022-12-09 00:00:37,599 INFO    : [ ZigpyCom_2 22082] Started radio znp port: /dev/serial/by-id/usb-ITead_Sonoff_Zigbee_3.0_USB_Dongle_Plus_c4e39f672f1aec11b0b37fe5f01c6278-if00-port0
2022-12-09 00:00:45,995 INFO    : [ ZigpyCom_2 22082] ZNP Radio register default Ep
2022-12-09 00:00:46,020 INFO    : [ ZigpyCom_2 22082] ZNP Radio register any additional/specific Ep
2022-12-09 00:00:46,244 INFO    : [ ZigpyCom_2 22082] device_initialized (0x0000 00:12:4b:00:25:8d:4a:55)
2022-12-09 00:00:46,248 INFO    : [ ZigpyCom_2 22082] ZNP Configuration {'device': {'path': '/dev/serial/by-id/usb-ITead_Sonoff_Zigbee_3.0_USB_Dongle_Plus_c4e39f672f1aec11b0b37fe5f01c6278-if00-port0', 'flow_control': None, 'baudrate': 1>
2022-12-09 00:01:00,739 INFO    : [ZigpyForwarder_2 22083] Number of devices recently active in Zigate = 19
2022-12-09 00:01:00,746 INFO    : [ZigpyForwarder_2 22083] [00] DevID: 00 Network addr: 152d IEEE: a4c138c083df2759 LQI: 000 power: ff not found in plugin database!
2022-12-09 00:01:00,757 INFO    : [ZigpyForwarder_2 22083] [01] DevID: 00 Network addr: d454 IEEE: a4c138c1cb0f56be LQI: 000 power: ff Model: TS0001 ( Radiateur salle )
2022-12-09 00:01:00,771 INFO    : [ZigpyForwarder_2 22083] [02] DevID: 00 Network addr: a4c1 IEEE: 38c083df2759152d LQI: 000 power: ff not found in plugin database!
2022-12-09 00:01:00,779 INFO    : [ZigpyForwarder_2 22083] [03] DevID: 00 Network addr: 0f56 IEEE: a4c1389a0a6b6848 LQI: 000 power: ff Model: TS0001 ( Radiateur couloir )
2022-12-09 00:01:00,790 INFO    : [ZigpyForwarder_2 22083] [04] DevID: 00 Network addr: 6782 IEEE: a4c1382849723821 LQI: 000 power: ff Model: TS0001 ( Radiateur cuisine )
2022-12-09 00:01:00,792 INFO    : [ZigpyForwarder_2 22083] [05] DevID: 00 Network addr: 37b7 IEEE: a4c1388816198824 LQI: 000 power: ff Model: TS0001 ( Radiateur entrée )
2022-12-09 00:01:00,794 INFO    : [ZigpyForwarder_2 22083] [06] DevID: 00 Network addr: bc40 IEEE: a4c1387cbd3ec273 LQI: 000 power: ff Model: TS0001 ( Radiateur chambre sohan )
2022-12-09 00:01:00,796 INFO    : [ZigpyForwarder_2 22083] [07] DevID: 00 Network addr: 92d6 IEEE: a4c1384671b4d883 LQI: 000 power: ff Model: TS0001 ( Radiateur chambre parents )
2022-12-09 00:01:00,798 INFO    : [ZigpyForwarder_2 22083] [08] DevID: 00 Network addr: 397f IEEE: a4c1385db0285afe LQI: 000 power: ff Model: TS0001 ( Radiateur salle eau )
2022-12-09 00:01:00,805 INFO    : [ZigpyForwarder_2 22083] [09] DevID: 00 Network addr: fae8 IEEE: a4c138b125ed0f86 LQI: 000 power: ff Model: TS0601-_TZE200_nklqjk62 ( Porte de garage )
2022-12-09 00:01:00,812 INFO    : [ZigpyForwarder_2 22083] [10] DevID: 00 Network addr: 1adf IEEE: 00124b0024c2e978 LQI: 000 power: ff Model: 01MINIZB ( Chauffe eau )
2022-12-09 00:01:00,819 INFO    : [ ZigpyCom_2 22082] ZNP Radio manufacturer: Texas Instruments
2022-12-09 00:01:00,827 INFO    : [ ZigpyCom_2 22082] ZNP Radio board model: CC1352/CC2652, Z-Stack 3.30+ (build 20210708)
2022-12-09 00:01:00,834 INFO    : [ ZigpyCom_2 22082] ZNP Radio version: 3.3
2022-12-09 00:01:00,839 INFO    : [ ZigpyCom_2 22082] Network settings
2022-12-09 00:01:00,842 INFO    : [ ZigpyCom_2 22082]   Channel: 15

Et dans

PluginZigbee_log_error_history.json

:

Code : Tout sélectionner

{"LastLog": 63, "59": {"LastLog": 0, "StartTime": 1670615131, "FirmwareVersion": "0708", "FirmwareMajorVersion": "21", "PluginVersion": ["stable6-6.3.007"], "0": {"Time": 1670615183, "Module": "Input", "nwkid": "None", "PluginHealth": "Ready", "message": "Decode 8041 - Receive an IEEE: a4c138c083df2759 with a NwkId: 152d, seems not known by the plugin", "PermitToJoin": {"Duration": 0, "Starttime": 1670615171}, "Thread": "ZigpyForwarder_2"}}, "60": {"LastLog": 0, "StartTime": 1670615431, "FirmwareVersion": "0708", "FirmwareMajorVersion": "21", "PluginVersion": ["stable6-6.3.007"], "0": {"Time": 1670615483, "Module": "Input", "nwkid": "None", "PluginHealth": "Ready", "message": "Decode 8041 - Receive an IEEE: a4c138c083df2759 with a NwkId: 152d, seems not known by the plugin", "PermitToJoin": {"Duration": 0, "Starttime": 1670615471}, "Thread": "ZigpyForwarder_2"}}, "61": {"LastLog": 4, "StartTime": 1670616631, "FirmwareVersion": "0708", "FirmwareMajorVersion": "21", "PluginVersion": ["stable6-6.3.007"], "0": {"Time": 1670616685, "Module": "Input", "nwkid": "None", "PluginHealth": "Ready", "message": "Decode 8041 - Receive an IEEE: a4c138c083df2759 with a NwkId: 152d, seems not known by the plugin", "PermitToJoin": {"Duration": 0, "Starttime": 1670616670}, "Thread": "ZigpyForwarder_2"}, "1": {"Time": 1670616688, "Module": "Input", "nwkid": "None", "PluginHealth": "Ready", "message": "Decode 8041 - Receive an IEEE: a4c138c083df2759 with a NwkId: 152d, seems not known by the plugin", "PermitToJoin": {"Duration": 0, "Starttime": 1670616670}, "Thread": "ZigpyForwarder_2"}, "2": {"Time": 1670616795, "Module": "Input", "nwkid": "None", "PluginHealth": "Ready", "message": "Decode 8041 - Receive an IEEE: a4c138e0409d7976 with a NwkId: 7ebf, seems not known by the plugin", "PermitToJoin": {"Duration": 0, "Starttime": 1670616670}, "Thread": "ZigpyForwarder_2"}, "3": {"Time": 1670616798, "Module": "Input", "nwkid": "None", "PluginHealth": "Ready", "message": "Decode 8041 - Receive an IEEE: a4c138e0409d7976 with a NwkId: 7ebf, seems not known by the plugin", "PermitToJoin": {"Duration": 0, "Starttime": 1670616670}, "Thread": "ZigpyForwarder_2"}, "4": {"Time": 1670616801, "Module": "Input", "nwkid": "None", "PluginHealth": "Ready", "message": "Decode 8041 - Receive an IEEE: a4c138e0409d7976 with a NwkId: 7ebf, seems not known by the plugin", "PermitToJoin": {"Duration": 0, "Starttime": 1670616670}, "Thread": "ZigpyForwarder_2"}}, "62": {"LastLog": 0, "StartTime": 1670617231, "FirmwareVersion": "0708", "FirmwareMajorVersion": "21", "PluginVersion": ["stable6-6.3.007"], "0": {"Time": 1670617284, "Module": "Input", "nwkid": "None", "PluginHealth": "Ready", "message": "Decode 8041 - Receive an IEEE: a4c138c083df2759 with a NwkId: 152d, seems not known by the plugin", "PermitToJoin": {"Duration": 0, "Starttime": 1670617271}, "Thread": "ZigpyForwarder_2"}}, "63": {"LastLog": 0, "StartTime": 1670617531, "FirmwareVersion": "0708", "FirmwareMajorVersion": "21", "PluginVersion": ["stable6-6.3.007"], "0": {"Time": 1670617582, "Module": "Input", "nwkid": "None", "PluginHealth": "Ready", "message": "Decode 8041 - Receive an IEEE: a4c138c083df2759 with a NwkId: 152d, seems not known by the plugin", "PermitToJoin": {"Duration": 0, "Starttime": 1670617783}, "Thread": "ZigpyForwarder_2"}}}

Je dois reconnaitre ne pas tout comprendre...

[Keros]

Nous avons regroupé dans le sujet [A lire avant de poster] Guide pour bien formuler une demande une première liste d’informations qui nous sont utiles pour commencer à analyser les demandes. En complétant tes informations, nous pourrons t’apporter plus rapidement des réponses pertinentes. Merci.

[bartras]

Mea culpa, j'ai trouvé ce qui n'allait pas...

C'est le coup de la périodicité de 5min qui m'a mis la puce à l'oreille.

J'ai mis un script dans crontab pour vérifier que domoticz tourne et si ce n'est pas le cas, de le relancer.

Code : Tout sélectionner

#!/bin/bash
# Script qui vérifie l'état de domoticz et qui relance si off

now=$(date) #récupération de la date et heure pour les logs

#Récupération du retour de la commande de status
domoticz=$(sudo service domoticz.sh status)

echo $domoticz

if [[ "$domoticz" = *"exited"* ]] # Si le service n'est pas running
then
 echo "on relance"
 relance=$(sudo service domoticz.sh restart) #On le relance
 echo "$now relance : $relance" #On log la lancement
# curl "https://api.telegram.org/botXXXXXXXXXXX/sendMessage?chat_id=XXXXXXX&text=Domoticz offline, Domoticz vient d'être redémarré!"
else
 echo "$now Domoticz lancé" #On log l'état normal
fi

exit 0

Je l'ai désactivé et depuis plus de reboot.

Par contre, si je peux me permettre, je veux bien un conseil sur la raison du reboot alors que domoticz tournait correctement.
Peut être clore ce sujet et en ouvrir un autre dans une section du forum plus adapté ?

Merci pour l'aide.

[Keros]

Tant mieux que tu aies trouvé.

Oui, tu peux indiquer ce sujet en [Résolu] en modifiant ton premier message (petit icône en haut à droite) et en ouvrir un autre dans la section Linux, pas de soucis

[pipiche]

faudrait plus voir avec les spécialistes des scripts, mais si je comprends bien ton code, si il y la chaine

Code : Tout sélectionner

"exited"

dans le résultat de la commande

Code : Tout sélectionner

 service domoticz.status

alors tu restart.
Je suis pas certain que ce soit la meilleure façon car la chaine "exited" peut se trouver dans la multitude de message de log que tu vas avoir .

il y a un outil qui fait ca: https://mmonit.com/monit/

[Deufo]

https://www.domoticz.com/wiki/Monitoring_domoticz

C'est top monit !