Je reinstalle tout de zero (pas de sauvegarde de la SD
[Résolu] Sonoff ZBMINI : retour d'état dans Domoticz
Re: Sonoff ZBMINI : retour d'état dans Domoticz
Les dégâts sur le pi sont plus important que prévu (plus d'accès avec putty).
Je reinstalle tout de zero (pas de sauvegarde de la SD
)
Je reinstalle tout de zero (pas de sauvegarde de la SD
RPI 2 -> Bullseye Lite
DomoticZ -> 2024.7
RFXCom 433E -> Pro1 1041
DongleP - Z-Stack 3.30+ (build 20240710) /Z4D 7.1.025 [7.489]
CC1101 433Mhz "Itron EverBlue Cyble"
PiTInfo v1.4
USB->ùSD = Rpi-clones
DomoticZ -> 2024.7
RFXCom 433E -> Pro1 1041
DongleP - Z-Stack 3.30+ (build 20240710) /Z4D 7.1.025 [7.489]
CC1101 433Mhz "Itron EverBlue Cyble"
PiTInfo v1.4
USB->ùSD = Rpi-clones
Re: Sonoff ZBMINI : retour d'état dans Domoticz
réinstallation complète effectué :
PI B+ Bullseye (Legacy 32b Full)
DomoticZ 2023.2
Z4D 7.1.012 [5.260]
debug activé ( en plus de ceux par défaut)
Input
zclDecoder
Cluster
ZclClusters
Command
WidgetUpdate
zigpyDeconz
toujours impossible d'exporter le pluginZigbee.log depuis le webui ou winSCP ou FileZilla.
J'ai contourné le problème avec "DiskInternals Linux Reader"
PI B+ Bullseye (Legacy 32b Full)
DomoticZ 2023.2
Z4D 7.1.012 [5.260]
debug activé ( en plus de ceux par défaut)
Input
zclDecoder
Cluster
ZclClusters
Command
WidgetUpdate
zigpyDeconz
toujours impossible d'exporter le pluginZigbee.log depuis le webui ou winSCP ou FileZilla.
J'ai contourné le problème avec "DiskInternals Linux Reader"
RPI 2 -> Bullseye Lite
DomoticZ -> 2024.7
RFXCom 433E -> Pro1 1041
DongleP - Z-Stack 3.30+ (build 20240710) /Z4D 7.1.025 [7.489]
CC1101 433Mhz "Itron EverBlue Cyble"
PiTInfo v1.4
USB->ùSD = Rpi-clones
DomoticZ -> 2024.7
RFXCom 433E -> Pro1 1041
DongleP - Z-Stack 3.30+ (build 20240710) /Z4D 7.1.025 [7.489]
CC1101 433Mhz "Itron EverBlue Cyble"
PiTInfo v1.4
USB->ùSD = Rpi-clones
Re: Sonoff ZBMINI : retour d'état dans Domoticz
Bonsoir,
je pre-suppose que tu es sur la branche stable7 tournant la dernière version du plugin.
Dans ces conditions, peux-tu basculer sur la branche fix-cluster-onoff
restart du plugin et voir ce qu'il se passe
je pre-suppose que tu es sur la branche stable7 tournant la dernière version du plugin.
Dans ces conditions, peux-tu basculer sur la branche fix-cluster-onoff
Code : Tout sélectionner
git pull
git checkout fix-cluster-onoffZigbee for Domoticz - Clef zzh-p (electrolama) 45 devices.
Si vous appréciez ce que je fais, vous pouvez contribuer par un don Paypal , ce qui me permettra notamment l'achat d’équipements et de les tester/valider pour le plugin.
Wiki ici
chat sur Keybase.io
Si vous appréciez ce que je fais, vous pouvez contribuer par un don Paypal , ce qui me permettra notamment l'achat d’équipements et de les tester/valider pour le plugin.
Wiki ici
chat sur Keybase.io
Re: Sonoff ZBMINI : retour d'état dans Domoticz
Effectivement, je suis bien sur la dernière stable (précisé dans mon message précédant)
une fois sur la "branche fix-cluster-onoff" , le widget sur domoticz réagit parfaitement en fonction des actions (inter sur S1/S2 du micromodule, le bouton poussoir qui sert aussi pour l'appairage ou le widget de Domoticz).
Me concernant c'est nickel.
Merci beaucoup Pipiche.
une fois sur la "branche fix-cluster-onoff" , le widget sur domoticz réagit parfaitement en fonction des actions (inter sur S1/S2 du micromodule, le bouton poussoir qui sert aussi pour l'appairage ou le widget de Domoticz).
Me concernant c'est nickel.
Merci beaucoup Pipiche.
RPI 2 -> Bullseye Lite
DomoticZ -> 2024.7
RFXCom 433E -> Pro1 1041
DongleP - Z-Stack 3.30+ (build 20240710) /Z4D 7.1.025 [7.489]
CC1101 433Mhz "Itron EverBlue Cyble"
PiTInfo v1.4
USB->ùSD = Rpi-clones
DomoticZ -> 2024.7
RFXCom 433E -> Pro1 1041
DongleP - Z-Stack 3.30+ (build 20240710) /Z4D 7.1.025 [7.489]
CC1101 433Mhz "Itron EverBlue Cyble"
PiTInfo v1.4
USB->ùSD = Rpi-clones
Re: Sonoff ZBMINI : retour d'état dans Domoticz
Excellente nouvelle.
En fait le 01ZBMINI ne remonte pas l'information On/Off avec le Type standard "Booléen". Du coup le plugin ne traitait pas correctement les valeurs.
Merci de ton aide.
J'ai mergé la branche sur la future 7.1.013 donc tu peux ou rester sur la branche ou tu es ou basculer sur wip-stable7-7.1.13
En fait le 01ZBMINI ne remonte pas l'information On/Off avec le Type standard "Booléen". Du coup le plugin ne traitait pas correctement les valeurs.
Merci de ton aide.
J'ai mergé la branche sur la future 7.1.013 donc tu peux ou rester sur la branche ou tu es ou basculer sur wip-stable7-7.1.13
Code : Tout sélectionner
git checkout wip-stable7-7.1.13
git pull
Zigbee for Domoticz - Clef zzh-p (electrolama) 45 devices.
Si vous appréciez ce que je fais, vous pouvez contribuer par un don Paypal , ce qui me permettra notamment l'achat d’équipements et de les tester/valider pour le plugin.
Wiki ici
chat sur Keybase.io
Si vous appréciez ce que je fais, vous pouvez contribuer par un don Paypal , ce qui me permettra notamment l'achat d’équipements et de les tester/valider pour le plugin.
Wiki ici
chat sur Keybase.io
Re: Sonoff ZBMINI : retour d'état dans Domoticz
C'est moi qui te remercie pour ton aide
Je vais basculé sur la wip et j'ajouterai une prise sonoff.
Merci
Edit
le webui m'affiche "Plugin: 7.1.012 [5.260]" alors que je suis bien sur la " 'origin/wip-stable7-7.1.13'."
Je vais basculé sur la wip et j'ajouterai une prise sonoff.
Merci
Edit
le webui m'affiche "Plugin: 7.1.012 [5.260]" alors que je suis bien sur la " 'origin/wip-stable7-7.1.13'."
RPI 2 -> Bullseye Lite
DomoticZ -> 2024.7
RFXCom 433E -> Pro1 1041
DongleP - Z-Stack 3.30+ (build 20240710) /Z4D 7.1.025 [7.489]
CC1101 433Mhz "Itron EverBlue Cyble"
PiTInfo v1.4
USB->ùSD = Rpi-clones
DomoticZ -> 2024.7
RFXCom 433E -> Pro1 1041
DongleP - Z-Stack 3.30+ (build 20240710) /Z4D 7.1.025 [7.489]
CC1101 433Mhz "Itron EverBlue Cyble"
PiTInfo v1.4
USB->ùSD = Rpi-clones
Re: [Résolu] Sonoff ZBMINI : retour d'état dans Domoticz
C'est normal : le changement de 7.1.012 ne sera fait que lorsque la 7.1.013 stable sera sortie. Pour le moment, elle est en préparation. On ne gère pas de numérotation sur les branches de développement.
Comment bien utiliser le forum : Poser une question, Mettre un script, un fichier, une image ou des logs
Mes petits guides : Débuter en programmation, Le débogage, Le choix de matériel, Les sauvegardes
Ma présentation - Mes Tutos
Mes petits guides : Débuter en programmation, Le débogage, Le choix de matériel, Les sauvegardes
Ma présentation - Mes Tutos
Re: [Résolu] Sonoff ZBMINI : retour d'état dans Domoticz
Merci Keros 
RPI 2 -> Bullseye Lite
DomoticZ -> 2024.7
RFXCom 433E -> Pro1 1041
DongleP - Z-Stack 3.30+ (build 20240710) /Z4D 7.1.025 [7.489]
CC1101 433Mhz "Itron EverBlue Cyble"
PiTInfo v1.4
USB->ùSD = Rpi-clones
DomoticZ -> 2024.7
RFXCom 433E -> Pro1 1041
DongleP - Z-Stack 3.30+ (build 20240710) /Z4D 7.1.025 [7.489]
CC1101 433Mhz "Itron EverBlue Cyble"
PiTInfo v1.4
USB->ùSD = Rpi-clones
Re: [Résolu] Sonoff ZBMINI : retour d'état dans Domoticz
Je ne sais pas si il y a un rapport mais le plugin ne semble plus vouloir démarrer
une petite partie du log erreur de domoticz conceranant Z4D
Le plugin essais de redémarrer en boucle.
je suis sur la wip-stable7-7.1.13.
Je vais le laisser tourner cette nuit au cas ou il se décide a repartir...
edit 02/06 a 9h00
un "git add" résoudra peut être le problème
une petite partie du log erreur de domoticz conceranant Z4D
Code : Tout sélectionner
2024-06-01 21:43:23.292 Error: Z4D: forwarder_thread - Error while receiving a Coordinator command
2024-06-01 21:43:23.629 Error: Z4D: Issue in request 018002003cff0000008004000002447b02000004007b440c0d5ec05ee102010010010010ff03, dumping stack: Traceback (most recent call last):
2024-06-01 21:43:23.629 File "/home/pi/domoticz/plugins/Domoticz-Zigbee/Classes/ZigpyTransport/forwarderThread.py", line 42, in forwarder_thread
2024-06-01 21:43:23.629 forward_message(self, message)
2024-06-01 21:43:23.629 File "/home/pi/domoticz/plugins/Domoticz-Zigbee/Classes/ZigpyTransport/instrumentation.py", line 31, in f_out
2024-06-01 21:43:23.629 result = f_in(self, message)
2024-06-01 21:43:23.629 File "/home/pi/domoticz/plugins/Domoticz-Zigbee/Classes/ZigpyTransport/forwarderThread.py", line 58, in forward_message
2024-06-01 21:43:23.629 self.F_out(message)
2024-06-01 21:43:23.629 File "/home/pi/domoticz/plugins/Domoticz-Zigbee/plugin.py", line 744, in processFrame
2024-06-01 21:43:23.629 zigbee_receive_message(self, Devices, Data)
2024-06-01 21:43:23.629 File "/home/pi/domoticz/plugins/Domoticz-Zigbee/Modules/input.py", line 165, in zigbee_receive_message
2024-06-01 21:43:23.629 _decode_message(self, MsgType, Devices, Data, MsgData, MsgLQI)
2024-06-01 21:43:23.629 File "/home/pi/domoticz/plugins/Domoticz-Zigbee/Modules/input.py", line 172, in _decode_message
2024-06-01 21:43:23.629 decoding_method(self, Devices, MsgData, MsgLQI)
2024-06-01 21:43:23.629 File "/home/pi/domoticz/plugins/Domoticz-Zigbee/Z4D_decoders/z4d_decoder_Simple_Descriptor_Rsp.py", line 43, in Decode8043
2024-06-01 21:43:23.629 if 'NbEp' in self.ListOfDevices[MsgDataShAddr] and self.ListOfDevices[MsgDataShAddr]['NbEp'] > '1':
2024-06-01 21:43:23.629 TypeError: '>' not supported between instances of 'int' and 'str'
2024-06-01 21:43:23.629
2024-06-01 21:43:33.264 Error: Z4D: Error at startup 1
2024-06-01 21:43:43.469 Error: Z4D hardware (3) thread seems to have ended unexpectedly
2024-06-01 21:43:57.487 Error: Z4D hardware (3) thread seems to have ended unexpectedly
2024-06-01 21:44:11.494 Error: Z4D hardware (3) thread seems to have ended unexpectedly
2024-06-01 21:44:25.522 Error: Z4D hardware (3) thread seems to have ended unexpectedly
2024-06-01 21:44:39.536 Error: Z4D hardware (3) thread seems to have ended unexpectedly
2024-06-01 21:46:02.078 Error: Z4D: [ 70] I have hard time to get Coordinator Version. Most likely there is a communication issue
2024-06-01 21:46:12.084 Error: Z4D: [ 80] I have hard time to get Coordinator Version. Most likely there is a communication issue
2024-06-01 21:46:22.099 Error: Z4D: [ 90] I have hard time to get Coordinator Version. Most likely there is a communication issue
2024-06-01 21:46:32.103 Error: Z4D: [100] I have hard time to get Coordinator Version. Most likely there is a communication issue
2024-06-01 21:46:42.115 Error: Z4D: [110] I have hard time to get Coordinator Version. Most likely there is a communication issue
2024-06-01 21:46:52.116 Error: Z4D: [120] I have hard time to get Coordinator Version. Most likely there is a communication issue
2024-06-01 21:47:44.033 Error: Z4D: forwarder_thread - Error while receiving a Coordinator command
2024-06-01 21:47:44.377 Error: Z4D: Issue in request 018002003cff0000008004000002447b02000004007b440c0d5ec05ee102010010010010ff03, dumping stack: Traceback (most recent call last):
2024-06-01 21:47:44.377 File "/home/pi/domoticz/plugins/Domoticz-Zigbee/Classes/ZigpyTransport/forwarderThread.py", line 42, in forwarder_thread
2024-06-01 21:47:44.377 forward_message(self, message)
2024-06-01 21:47:44.377 File "/home/pi/domoticz/plugins/Domoticz-Zigbee/Classes/ZigpyTransport/instrumentation.py", line 31, in f_out
2024-06-01 21:47:44.377 result = f_in(self, message)
2024-06-01 21:47:44.377 File "/home/pi/domoticz/plugins/Domoticz-Zigbee/Classes/ZigpyTransport/forwarderThread.py", line 58, in forward_message
2024-06-01 21:47:44.377 self.F_out(message)
2024-06-01 21:47:44.377 File "/home/pi/domoticz/plugins/Domoticz-Zigbee/plugin.py", line 744, in processFrame
2024-06-01 21:47:44.377 zigbee_receive_message(self, Devices, Data)
2024-06-01 21:47:44.377 File "/home/pi/domoticz/plugins/Domoticz-Zigbee/Modules/input.py", line 165, in zigbee_receive_message
2024-06-01 21:47:44.377 _decode_message(self, MsgType, Devices, Data, MsgData, MsgLQI)
2024-06-01 21:47:44.377 File "/home/pi/domoticz/plugins/Domoticz-Zigbee/Modules/input.py", line 172, in _decode_message
2024-06-01 21:47:44.377 decoding_method(self, Devices, MsgData, MsgLQI)
2024-06-01 21:47:44.377 File "/home/pi/domoticz/plugins/Domoticz-Zigbee/Z4D_decoders/z4d_decoder_Simple_Descriptor_Rsp.py", line 43, in Decode8043
2024-06-01 21:47:44.377 if 'NbEp' in self.ListOfDevices[MsgDataShAddr] and self.ListOfDevices[MsgDataShAddr]['NbEp'] > '1':
2024-06-01 21:47:44.377 TypeError: '>' not supported between instances of 'int' and 'str'
2024-06-01 21:47:44.377
2024-06-01 21:47:55.306 Error: Z4D: Error at startup 1
2024-06-01 21:48:09.740 Error: Z4D hardware (3) thread seems to have ended unexpectedly
2024-06-01 21:48:23.747 Error: Z4D hardware (3) thread seems to have ended unexpectedly
2024-06-01 21:48:37.772 Error: Z4D hardware (3) thread seems to have ended unexpectedly
2024-06-01 21:48:51.779 Error: Z4D hardware (3) thread seems to have ended unexpectedly
2024-06-01 21:49:05.786 Error: Z4D hardware (3) thread seems to have ended unexpectedly
2024-06-01 21:50:20.083 Error: Z4D: [ 70] I have hard time to get Coordinator Version. Most likely there is a communication issue
2024-06-01 21:50:30.093 Error: Z4D: [ 80] I have hard time to get Coordinator Version. Most likely there is a communication issue
2024-06-01 21:50:40.105 Error: Z4D: [ 90] I have hard time to get Coordinator Version. Most likely there is a communication issue
2024-06-01 21:50:50.110 Error: Z4D: [100] I have hard time to get Coordinator Version. Most likely there is a communication issue
2024-06-01 21:51:00.072 Error: Z4D: [110] I have hard time to get Coordinator Version. Most likely there is a communication issue
2024-06-01 21:51:10.083 Error: Z4D: [120] I have hard time to get Coordinator Version. Most likely there is a communication issue
2024-06-01 21:52:05.308 Error: Z4D: forwarder_thread - Error while receiving a Coordinator command
2024-06-01 21:52:05.658 Error: Z4D: Issue in request 018002003cff0000008004000002447b02000004007b440c0d5ec05ee102010010010010ff03, dumping stack: Traceback (most recent call last):
2024-06-01 21:52:05.658 File "/home/pi/domoticz/plugins/Domoticz-Zigbee/Classes/ZigpyTransport/forwarderThread.py", line 42, in forwarder_thread
2024-06-01 21:52:05.658 forward_message(self, message)
2024-06-01 21:52:05.658 File "/home/pi/domoticz/plugins/Domoticz-Zigbee/Classes/ZigpyTransport/instrumentation.py", line 31, in f_out
2024-06-01 21:52:05.658 result = f_in(self, message)
2024-06-01 21:52:05.658 File "/home/pi/domoticz/plugins/Domoticz-Zigbee/Classes/ZigpyTransport/forwarderThread.py", line 58, in forward_message
2024-06-01 21:52:05.658 self.F_out(message)
2024-06-01 21:52:05.658 File "/home/pi/domoticz/plugins/Domoticz-Zigbee/plugin.py", line 744, in processFrame
2024-06-01 21:52:05.658 zigbee_receive_message(self, Devices, Data)
2024-06-01 21:52:05.658 File "/home/pi/domoticz/plugins/Domoticz-Zigbee/Modules/input.py", line 165, in zigbee_receive_message
2024-06-01 21:52:05.658 _decode_message(self, MsgType, Devices, Data, MsgData, MsgLQI)
2024-06-01 21:52:05.658 File "/home/pi/domoticz/plugins/Domoticz-Zigbee/Modules/input.py", line 172, in _decode_message
2024-06-01 21:52:05.658 decoding_method(self, Devices, MsgData, MsgLQI)
2024-06-01 21:52:05.658 File "/home/pi/domoticz/plugins/Domoticz-Zigbee/Z4D_decoders/z4d_decoder_Simple_Descriptor_Rsp.py", line 43, in Decode8043
2024-06-01 21:52:05.658 if 'NbEp' in self.ListOfDevices[MsgDataShAddr] and self.ListOfDevices[MsgDataShAddr]['NbEp'] > '1':
2024-06-01 21:52:05.658 TypeError: '>' not supported between instances of 'int' and 'str'
2024-06-01 21:52:05.658
2024-06-01 21:52:13.440 Error: Z4D: Error at startup 1
2024-06-01 21:52:21.944 Error: Z4D hardware (3) thread seems to have ended unexpectedly
2024-06-01 21:52:35.956 Error: Z4D hardware (3) thread seems to have ended unexpectedly
2024-06-01 21:52:49.963 Error: Z4D hardware (3) thread seems to have ended unexpectedly
2024-06-01 21:53:03.992 Error: Z4D hardware (3) thread seems to have ended unexpectedly
2024-06-01 21:53:17.999 Error: Z4D hardware (3) thread seems to have ended unexpectedly
2024-06-01 21:54:39.085 Error: Z4D: [ 70] I have hard time to get Coordinator Version. Most likely there is a communication issue
2024-06-01 21:54:49.089 Error: Z4D: [ 80] I have hard time to get Coordinator Version. Most likely there is a communication issue
2024-06-01 21:54:59.103 Error: Z4D: [ 90] I have hard time to get Coordinator Version. Most likely there is a communication issue
2024-06-01 21:55:09.070 Error: Z4D: [100] I have hard time to get Coordinator Version. Most likely there is a communication issue
2024-06-01 21:55:19.085 Error: Z4D: [110] I have hard time to get Coordinator Version. Most likely there is a communication issue
2024-06-01 21:55:29.088 Error: Z4D: [120] I have hard time to get Coordinator Version. Most likely there is a communication issue
2024-06-01 21:56:25.433 Error: Z4D: Error at startup 1
2024-06-01 21:56:48.193 Error: Z4D hardware (3) thread seems to have ended unexpectedly
2024-06-01 21:57:02.200 Error: Z4D hardware (3) thread seems to have ended unexpectedly
2024-06-01 21:57:16.211 Error: Z4D hardware (3) thread seems to have ended unexpectedly
2024-06-01 21:57:30.275 Error: Z4D hardware (3) thread seems to have ended unexpectedly
2024-06-01 21:57:44.282 Error: Z4D hardware (3) thread seems to have ended unexpectedly
2024-06-01 21:58:55.081 Error: Z4D: [ 70] I have hard time to get Coordinator Version. Most likely there is a communication issue
2024-06-01 21:59:05.093 Error: Z4D: [ 80] I have hard time to get Coordinator Version. Most likely there is a communication issue
2024-06-01 21:59:15.102 Error: Z4D: [ 90] I have hard time to get Coordinator Version. Most likely there is a communication issue
2024-06-01 21:59:25.064 Error: Z4D: [100] I have hard time to get Coordinator Version. Most likely there is a communication issue
2024-06-01 21:59:35.073 Error: Z4D: [110] I have hard time to get Coordinator Version. Most likely there is a communication issue
2024-06-01 21:59:45.089 Error: Z4D: [120] I have hard time to get Coordinator Version. Most likely there is a communication issue
2024-06-01 22:00:41.798 Error: Z4D: forwarder_thread - Error while receiving a Coordinator command
2024-06-01 22:00:42.145 Error: Z4D: Issue in request 018002003cff0000008004000002447b02000004007b440c0d5ec05ee102010010010010ff03, dumping stack: Traceback (most recent call last):
2024-06-01 22:00:42.145 File "/home/pi/domoticz/plugins/Domoticz-Zigbee/Classes/ZigpyTransport/forwarderThread.py", line 42, in forwarder_thread
2024-06-01 22:00:42.145 forward_message(self, message)
2024-06-01 22:00:42.145 File "/home/pi/domoticz/plugins/Domoticz-Zigbee/Classes/ZigpyTransport/instrumentation.py", line 31, in f_out
2024-06-01 22:00:42.145 result = f_in(self, message)
2024-06-01 22:00:42.145 File "/home/pi/domoticz/plugins/Domoticz-Zigbee/Classes/ZigpyTransport/forwarderThread.py", line 58, in forward_message
2024-06-01 22:00:42.145 self.F_out(message)
2024-06-01 22:00:42.145 File "/home/pi/domoticz/plugins/Domoticz-Zigbee/plugin.py", line 744, in processFrame
2024-06-01 22:00:42.145 zigbee_receive_message(self, Devices, Data)
2024-06-01 22:00:42.145 File "/home/pi/domoticz/plugins/Domoticz-Zigbee/Modules/input.py", line 165, in zigbee_receive_message
2024-06-01 22:00:42.145 _decode_message(self, MsgType, Devices, Data, MsgData, MsgLQI)
2024-06-01 22:00:42.145 File "/home/pi/domoticz/plugins/Domoticz-Zigbee/Modules/input.py", line 172, in _decode_message
2024-06-01 22:00:42.145 decoding_method(self, Devices, MsgData, MsgLQI)
2024-06-01 22:00:42.145 File "/home/pi/domoticz/plugins/Domoticz-Zigbee/Z4D_decoders/z4d_decoder_Simple_Descriptor_Rsp.py", line 43, in Decode8043
2024-06-01 22:00:42.145 if 'NbEp' in self.ListOfDevices[MsgDataShAddr] and self.ListOfDevices[MsgDataShAddr]['NbEp'] > '1':
2024-06-01 22:00:42.145 TypeError: '>' not supported between instances of 'int' and 'str'
2024-06-01 22:00:42.145
2024-06-01 22:00:49.674 Error: Z4D: Error at startup 1
2024-06-01 22:01:00.493 Error: Z4D hardware (3) thread seems to have ended unexpectedly
2024-06-01 22:01:14.503 Error: Z4D hardware (3) thread seems to have ended unexpectedly
2024-06-01 22:01:28.510 Error: Z4D hardware (3) thread seems to have ended unexpectedly
2024-06-01 22:01:42.575 Error: Z4D hardware (3) thread seems to have ended unexpectedly
2024-06-01 22:01:56.592 Error: Z4D hardware (3) thread seems to have ended unexpectedly
© 2012-2024 Domoticz | WWje suis sur la wip-stable7-7.1.13.
Je vais le laisser tourner cette nuit au cas ou il se décide a repartir...
edit 02/06 a 9h00
un "git add" résoudra peut être le problème
RPI 2 -> Bullseye Lite
DomoticZ -> 2024.7
RFXCom 433E -> Pro1 1041
DongleP - Z-Stack 3.30+ (build 20240710) /Z4D 7.1.025 [7.489]
CC1101 433Mhz "Itron EverBlue Cyble"
PiTInfo v1.4
USB->ùSD = Rpi-clones
DomoticZ -> 2024.7
RFXCom 433E -> Pro1 1041
DongleP - Z-Stack 3.30+ (build 20240710) /Z4D 7.1.025 [7.489]
CC1101 433Mhz "Itron EverBlue Cyble"
PiTInfo v1.4
USB->ùSD = Rpi-clones