[Résolu] Erreur - Miss configuration reports

Forum dédié au plugin ZigBeeForDomoticZ : installation, paramétrage, utilisation, interfaces ...
bartras
Messages : 140
Inscription : 17 mars 2017, 17:44
Localisation : Saint Etienne (42)

[Résolu] Erreur - Miss configuration reports

Message par bartras »

Bonjour,

Hier, j'ai ajouté trois prises connectés Zigbee (de chez Aliexpress).
Aucun souci, tout fonctionne correctement.
Seulement dans le log domoticz, j'ai ces notifications (toutes les secondes ^^):

Code : Tout sélectionner

2023-12-30 13:22:33.253 Status: ZigbeeForDomoticz: ------ We have detected a miss configuration reports for device b9ec on ep 01 and cluster 0b04
2023-12-30 13:22:33.260 Status: ZigbeeForDomoticz: - Attribut 050b request to force a Configure Reporting due to field MinInterval '0000' != '0001'
2023-12-30 13:22:43.231 Status: ZigbeeForDomoticz: ------ We have detected a miss configuration reports for device 9913 on ep 01 and cluster 0b04
2023-12-30 13:22:43.237 Status: ZigbeeForDomoticz: - Attribut 050b request to force a Configure Reporting due to field MinInterval '0000' != '0001'
2023-12-30 13:22:48.282 Status: ZigbeeForDomoticz: ------ We have detected a miss configuration reports for device a7b8 on ep 01 and cluster 0b04
2023-12-30 13:22:48.288 Status: ZigbeeForDomoticz: - Attribut 050b request to force a Configure Reporting due to field MinInterval '0000' != '0001'
J'ai cherché sur le wiki et le forum mais je n'ai pas trouvé d'informations à ce sujet.

J'ai essayé moi même (avec mon peu de connaissance) et j'ai modifié la valeur de MinInterval dans l'onglet "Configuration de la remontée d'infos des objets". Mais quelque soit la valeur que je mets, le message revient sans cesse.

Voici le détail pour la prise b9ec:
Configuration de la remontée d'infos des objets
Configuration de la remontée d'infos des objets
Configuration.png (28.47 Kio) Consulté 401 fois

EDIT: Liste des informations demandées
  • Version de DomoticZ 2023.2
  • Version de Python 3.9.2 (default, Mar 12 2021, 04:06:34) [GCC 10.2.1 20210110]
  • Système sur lequel tourne DomoticZ avec le plugin : RPI3B+
  • Modèle de coordinateur : ITead_Sonoff_Zigbee_3.0_USB_Dongle_Plus
  • Version de coordinateur : USB

Voici le log pour la prise b9ec :

Code : Tout sélectionner

Version: "3"
ZDeviceName: "Frigo sous sol"
Status: "inDB"
SQN: "8a"
Heartbeat: "32691"
RIA: "0"
LQI: 42
Battery: Object {}
Model: "TS011F-plug"
ForceAckCommands: Array[0] []
MacCapa: "8e"
IEEE: "a4c138ac3bd035a0"
Type: "Plug/Power/Meter/Voltage/Ampere"
ProfileID: "0104"
ZDeviceID: "0051"
App Version: 112
Attributes List: Object {}
DeviceType: "FFD"
HW Version: ""
Last Cmds: Array[0] []
LogicalType: "Router"
Manufacturer: "100b"
Manufacturer Name: "_TZ3000_okaz9tjs"
NbEp: "2"
PowerSource: "Main"
ReadAttributes: Object {"Ep":{"01":{"0000":{"TimeStamp":"28/12/2023 16:13:41","iSQN":{"fffe":"00","0004":"06","0000":"06","0001":"06","0005":"06","0007":"06"},"Attributes":{"fffe":"86","0004":"00","0000":"00","0001":"00","0005":"00","0007":"00"},"ZigateRequest":{}},"0702":{"TimeStamp":"30/12/2023 13:33:41","iSQN":{"0000":"03","0300":"0a","0302":"0a","0301":"0a"},"Attributes":{"0000":"00","0300":"00","0302":"00","0301":"00"},"ZigateRequest":{}},"0006":{"TimeStamp":"30/12/2023 13:35:57","iSQN":{"4001":"04","4002":"04","5000":"04","8000":"04","8001":"04","8002":"05","8003":"05","0000":"16"},"Attributes":{"4001":"00","4002":"00","5000":"86","8000":"00","8001":"00","8002":"00","8003":"86","0000":"00"},"ZigateRequest":{}},"0b04":{"TimeStamp":"30/12/2023 13:42:50","iSQN":{"0505":"b7","0508":"b7","050b":"b7"},"Attributes":{"0505":"00","0508":"00","050b":"00"},"ZigateRequest":{}},"e000":{"TimeStamp":"28/12/2023 16:15:49","iSQN":{},"Attributes":{"d001":"00","d002":"00"},"ZigateRequest":{}}}}}
ReceiveOnIdle: "On"
Stack Version: ""
Stamp: Object {"time":1703940170.3789291,"Time":"2023-12-30 13:42:50","MsgType":"8102","LastSeen":"30/12/2023 13:42:50"}
ZCL Version: 3
Health: "Live"
Capability: Array[5] ["Full-Function Device","Main Powered","Receiver during Idle","Standard security","NwkAddr should be allocated"]
ZCLSQN: "c4"
ZDPSQN: "b2"
RollingLQI: Array[11] [42,42,45,45,42,45,45,45,42,45,42]
Param: Object {"PowerOnAfterOffOn":2,"TuyaBackLight":1,"PowerPollingFreq":300}
ConfigSource: "DeviceConf"
Ep: Object {"01":{"0000":{"0004":"_TZ3000_okaz9tjs","0000":3,"0001":112,"0005":"TS011F","0007":1},"0003":{},"0004":{},"0005":{},"0006":{"4001":0,"4002":0,"8000":"00","8001":"1","8002":"0","0000":"01"},"0702":{"0000":1150,"0300":"kW","0302":0,"0301":0},"0b04":{"0505":235,"0508":0.311,"050b":35},"e000":{"d001":"06","d002":"0a"},"e001":{},"000a":{},"0019":{},"Type":"Plug/Power/Meter/Voltage/Ampere","ClusterType":{"132":"Plug","134":"Meter"}},"f2":{"0000":{},"0021":{}}}
WriteAttributes: Object {"Ep":{"01":{"0000":{"TimeStamp":0,"iSQN":{},"Attributes":{},"ZigateRequest":{}},"0003":{"TimeStamp":0,"iSQN":{},"Attributes":{},"ZigateRequest":{}},"0004":{"TimeStamp":0,"iSQN":{},"Attributes":{},"ZigateRequest":{}},"0005":{"TimeStamp":0,"iSQN":{},"Attributes":{},"ZigateRequest":{}},"0006":{"TimeStamp":"29/12/2023 14:50:26","iSQN":{"8001":"81"},"Attributes":{"8001":"00"},"ZigateRequest":{"8001":{"Status":"fullfilled","DataType":"30","EPin":"01","EPout":"01","manuf_id":"0000","manuf_spec":"00","data":"01","ackIsDisabled":false}}},"0702":{"TimeStamp":0,"iSQN":{},"Attributes":{},"ZigateRequest":{}},"0b04":{"TimeStamp":0,"iSQN":{},"Attributes":{},"ZigateRequest":{}},"e000":{"TimeStamp":0,"iSQN":{},"Attributes":{},"ZigateRequest":{}},"e001":{"TimeStamp":0,"iSQN":{},"Attributes":{},"ZigateRequest":{}},"000a":{"TimeStamp":0,"iSQN":{},"Attributes":{},"ZigateRequest":{}},"0019":{"TimeStamp":0,"iSQN":{},"Attributes":{},"ZigateRequest":{}}},"f2":{"0000":{"TimeStamp":0,"iSQN":{},"Attributes":{},"ZigateRequest":{}},"0021":{"TimeStamp":0,"iSQN":{},"Attributes":{},"ZigateRequest":{}}}}}
_rawNodeDescriptor: "100b004200422c00008e424001"
Max Buffer Size: "42"
Max Rx: "0042"
Max Tx: "0042"
macapa: "8e"
bitfield: "4001"
server_mask: "2c00"
descriptor_capability: "00"
Epv2: Object {"01":{"ProfileID":"0104","ZDeviceID":"0051","ClusterIn":{"1000":{},"1888":{},"0000":{},"0003":{},"0004":{},"0005":{},"0006":{},"000a":{},"e000":{},"0702":{},"0b04":{}},"ClusterOut":{"0019":{}}},"f2":{"ProfileID":"a1e0","ZDeviceID":"0061","ClusterOut":{"0021":{}}}}
ZDeviceVersion: "0001"
SQN_000a: "4c"
PairingInProgress: false
PairingTime: 1703776376.1788497
Bind: Object {"01":{"0006":{"Target":"0000","Stamp":"28/12/2023 16:12:56","Phase":"binded","Status":"00","i_sqn":"03"},"0702":{"Target":"0000","Stamp":"28/12/2023 16:14:01","Phase":"binded","Status":"00","i_sqn":"0a"},"0b04":{"Target":"0000","Stamp":"30/12/2023 13:42:33","Phase":"requested","Status":"","i_sqn":"b2"}}}
BindingTable: Object {"SQN":0,"Status":"Success","TimeStamp":"28/12/2023 16:13:01","BindingTableSize":3,"Devices":[{"a4c138ac3bd035a0":{"sourceEp":"01","Cluster":"0006","targetIEEE":"00124b00258d4a55","targetNickName":"Zigbee Coordinator","targetEp":"01"}},{"a4c138ac3bd035a0":{"sourceEp":"01","Cluster":"0702","targetIEEE":"00124b00258d4a55","targetNickName":"Zigbee Coordinator","targetEp":"01"}},{"a4c138ac3bd035a0":{"sourceEp":"01","Cluster":"0b04","targetIEEE":"00124b00258d4a55","targetNickName":"Zigbee Coordinator","targetEp":"01"}}]}
ConfigureReporting: Object {"Ep":{"01":{"0702":{"TimeStamp":"28/12/2023 16:12:56","iSQN":{"0000":"0b"},"Attributes":{"0000":"00"},"ZigateRequest":{}},"0b04":{"TimeStamp":"28/12/2023 16:12:56","iSQN":{"0505":"c4","0508":"c4","050b":"c4"},"Attributes":{"0505":"00","0508":"00","050b":"8d"},"ZigateRequest":{}}}}}
CheckParam: false
CertifiedDevice: true
ReadConfigureReporting: Object {"Ep":{"01":{"0b04":{"0505":{"TimeStamp":"30/12/2023 13:41:45","Status":"00","DataType":"21","MinInterval":"0001","MaxInterval":"012c","Change":"0001"},"0508":{"TimeStamp":"30/12/2023 13:41:45","Status":"00","DataType":"21","MinInterval":"0001","MaxInterval":"012c","Change":"0001"},"050b":{"TimeStamp":"30/12/2023 13:41:45","Status":"00","DataType":"21","MinInterval":"0000","MaxInterval":"044c","Change":"0005"}},"0702":{"0000":{"TimeStamp":"28/12/2023 16:14:03","Status":"00","DataType":"25","MinInterval":"0005","MaxInterval":"012c","Change":"000000000001"}}}},"TimeStamp":"30/12/2023 13:41:45"}
Neighbours: Array[1] [{"SQN":0,"Status":"","TimeStamp":"28/12/2023 16:39:33","Time":"28/12/2023 16:39:33","Devices":[{"a7b8":{"_relationshp":"Parent","_devicetype":"Router","_depth":2,"_lnkqty":145,"_rxonwhenidl":"Rx-On","_IEEE":"a4c1386b06649a21","_permitjnt":"??"}},{"fae8":{"_relationshp":"Sibling","_devicetype":"Router","_depth":0,"_lnkqty":179,"_rxonwhenidl":"Rx-On","_IEEE":"a4c138b125ed0f86","_permitjnt":"??"}},{"37b7":{"_relationshp":"Sibling","_devicetype":"Router","_depth":0,"_lnkqty":154,"_rxonwhenidl":"Rx-On","_IEEE":"a4c1388816198824","_permitjnt":"??"}},{"4e71":{"_relationshp":"Sibling","_devicetype":"Router","_depth":0,"_lnkqty":223,"_rxonwhenidl":"Rx-On","_IEEE":"a4c13881114ec063","_permitjnt":"??"}},{"8673":{"_relationshp":"Sibling","_devicetype":"Router","_depth":0,"_lnkqty":207,"_rxonwhenidl":"Rx-On","_IEEE":"a4c138900aeea911","_permitjnt":"??"}},{"92d6":{"_relationshp":"Sibling","_devicetype":"Router","_depth":0,"_lnkqty":120,"_rxonwhenidl":"Rx-On","_IEEE":"a4c1384671b4d883","_permitjnt":"??"}},{"2959":{"_relationshp":"Sibling","_devicetype":"Router","_depth":0,"_lnkqty":170,"_rxonwhenidl":"Rx-On","_IEEE":"a4c13871c12b264c","_permitjnt":"??"}},{"1682":{"_relationshp":"Sibling","_devicetype":"Router","_depth":0,"_lnkqty":108,"_rxonwhenidl":"Rx-On","_IEEE":"a4c138c1cb0f56be","_permitjnt":"??"}},{"607d":{"_relationshp":"Sibling","_devicetype":"Router","_depth":0,"_lnkqty":250,"_rxonwhenidl":"Rx-On","_IEEE":"e0798dfffe57dc65","_permitjnt":"??"}},{"9913":{"_relationshp":"Sibling","_devicetype":"Router","_depth":0,"_lnkqty":133,"_rxonwhenidl":"Rx-On","_IEEE":"a4c1387f3c6b1693","_permitjnt":"??"}},{"bc40":{"_relationshp":"Sibling","_devicetype":"Router","_depth":0,"_lnkqty":127,"_rxonwhenidl":"Rx-On","_IEEE":"a4c1387cbd3ec273","_permitjnt":"??"}},{"0f56":{"_relationshp":"Sibling","_devicetype":"Router","_depth":0,"_lnkqty":117,"_rxonwhenidl":"Rx-On","_IEEE":"a4c1389a0a6b6848","_permitjnt":"??"}}]}]
RoutingTable: Array[1] [{"Devices":[],"SQN":0,"Status":"","TimeStamp":"28/12/2023 16:39:33","Time":"28/12/2023 16:39:33"}]
NeighbourTableSize: 12
MapLQI: Object {"1682":30,"2959":81,"6782":3,"8673":121,"0000":39,"607d":248,"bc40":45,"37b7":45,"c6f0":0,"0f56":33,"a7b8":142,"92d6":36,"4e71":142}
ParamConfigureReporting: Object {"0702":{"Attributes":{"0000":{"MinInterval":"0005","MaxInterval":"012c","TimeOut":"0000","DataType":"25","Change":"000000000001"}}},"0b04":{"Attributes":{"0505":{"MinInterval":"0001","MaxInterval":"012c","TimeOut":"0000","DataType":"21","Change":"0001"},"0508":{"MinInterval":"0001","MaxInterval":"012c","TimeOut":"0000","DataType":"21","Change":"0001"},"050b":{"MinInterval":"0001","MaxInterval":"012c","TimeOut":"0000","DataType":"29","Change":"0005"}}}}
NwkID: "b9ec"
Dernière modification par bartras le 31 déc. 2023, 18:44, modifié 3 fois.
Keros
Messages : 6638
Inscription : 23 juil. 2019, 20:57

Re: Miss configuration reports

Message par 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.
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
bartras
Messages : 140
Inscription : 17 mars 2017, 17:44
Localisation : Saint Etienne (42)

Re: Erreur - Miss configuration reports

Message par bartras »

Voila j'ai édité mon message avec ces informations.
bartras
Messages : 140
Inscription : 17 mars 2017, 17:44
Localisation : Saint Etienne (42)

Re: Erreur - Miss configuration reports

Message par bartras »

En fouillant dans la liste RAW, je dirais que la valeur qui pose problème se trouve ici :
piste (Copier).png
piste (Copier).png (46.31 Kio) Consulté 387 fois
Seulement, je ne sais pas comment la basculer sur 0001...
pipiche
Messages : 4677
Inscription : 04 avr. 2018, 16:16
Contact :

Re: Erreur - Miss configuration reports

Message par pipiche »

Fais-une mise à jour du plugin assure-toi d'etre en 7.1.007 [3.169] Le problème devrait disparaitre
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
bartras
Messages : 140
Inscription : 17 mars 2017, 17:44
Localisation : Saint Etienne (42)

Re: Erreur - Miss configuration reports

Message par bartras »

Merci pour le retour.
J'ai fait la mise à jour et j'ai toujours les messages.
Par contre les valeurs ont changées et maxinterval s'est invité :D

Code : Tout sélectionner

2023-12-30 20:10:03.220 Status: ZigbeeForDomoticz: ------ We have detected a miss configuration reports for device a7b8 on ep 01 and cluster 0b04
2023-12-30 20:10:03.227 Status: ZigbeeForDomoticz: - Attribut 050b request to force a Configure Reporting due to field MaxInterval '044c' != '012C'
2023-12-30 20:10:03.312 Status: ZigbeeForDomoticz: ------ We have detected a miss configuration reports for device 9913 on ep 01 and cluster 0b04
2023-12-30 20:10:03.319 Status: ZigbeeForDomoticz: - Attribut 050b request to force a Configure Reporting due to field MaxInterval '044c' != '012C'
2023-12-30 20:10:33.269 Status: ZigbeeForDomoticz: ------ We have detected a miss configuration reports for device b9ec on ep 01 and cluster 0b04
2023-12-30 20:10:33.276 Status: ZigbeeForDomoticz: - Attribut 050b request to force a Configure Reporting due to field MinInterval '0000' != '000a'
bartras
Messages : 140
Inscription : 17 mars 2017, 17:44
Localisation : Saint Etienne (42)

Re: Erreur - Miss configuration reports

Message par bartras »

Si je comprends bien ça doit venir d'ici :

Code : Tout sélectionner

ParamConfigureReporting:
0702: Object {"Attributes":{"0000":{"MinInterval":"0005","MaxInterval":"012c","TimeOut":"0000","DataType":"25","Change":"000000000001"}}}
0b04:
Attributes:
0505:
MinInterval: "0001"
MaxInterval: "012c"
TimeOut: "0000"
DataType: "21"
Change: "0001"
0508:
MinInterval: "0001"
MaxInterval: "012c"
TimeOut: "0000"
DataType: "21"
Change: "0001"
050b:
MinInterval: "000a"
MaxInterval: "012c"
TimeOut: "0000"
DataType: "29"
Change: "0005"
macapa: "8e"
pipiche
Messages : 4677
Inscription : 04 avr. 2018, 16:16
Contact :

Re: Erreur - Miss configuration reports

Message par pipiche »

Elle vient d'où cette prise ? EN fait ces prises ?

de plus ca semble changer.

peux-tu nous donner l'enesemble du fichier log ainsi qu'un export.json
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
bartras
Messages : 140
Inscription : 17 mars 2017, 17:44
Localisation : Saint Etienne (42)

Re: Erreur - Miss configuration reports

Message par bartras »

Les prises viennent d'Aliexpress. Voici le lien.

Ca a changé lorsque j'ai fait la mises à jour ZigbeeForDomoticz.
Avant la mise à jour en 3.169, le log Domoticz renvoyait toujours le même message sur le MinInterval (pour les trois prises).
Suite à la mise à jour en 3.169, le log Domoticz renvoie ça :

Code : Tout sélectionner

2023-12-31 15:18:46.261 Status: ZigbeeForDomoticz: ------ We have detected a miss configuration reports for device 9913 on ep 01 and cluster 0b04
2023-12-31 15:18:46.268 Status: ZigbeeForDomoticz: - Attribut 050b request to force a Configure Reporting due to field MaxInterval '044c' != '012C'
2023-12-31 15:19:26.255 Status: ZigbeeForDomoticz: ------ We have detected a miss configuration reports for device b9ec on ep 01 and cluster 0b04
2023-12-31 15:19:26.258 Status: ZigbeeForDomoticz: - Attribut 050b request to force a Configure Reporting due to field MinInterval '0000' != '000a'
2023-12-31 15:19:41.429 Status: ZigbeeForDomoticz: ------ We have detected a miss configuration reports for device a7b8 on ep 01 and cluster 0b04
2023-12-31 15:19:41.436 Status: ZigbeeForDomoticz: - Attribut 050b request to force a Configure Reporting due to field MaxInterval '044c' != '012C'

Voici l'export JSON de ZigbeeForDomoticz.
export.json
(247.79 Kio) Téléchargé 46 fois


Ce que tu appelles l'ensemble du fichier log c'est celui de Domoticz ?
Si oui, voici le log complet suite à un démarrage de Domoticz.

Code : Tout sélectionner

2023-12-31 15:32:50.645 Sunrise: 08:23:00 SunSet: 17:10:00
2023-12-31 15:32:50.645 Day length: 08:47:00 Sun at south: 12:46:00
2023-12-31 15:32:50.645 Civil twilight start: 07:49:00 Civil twilight end: 17:44:00
2023-12-31 15:32:50.645 Nautical twilight start: 07:11:00 Nautical twilight end: 18:21:00
2023-12-31 15:32:50.645 Astronomical twilight start: 06:36:00 Astronomical twilight end: 18:57:00
2023-12-31 15:32:50.789 Active notification Subsystems: (0/13)
2023-12-31 15:32:50.830 Starting shared server on: :::6144
2023-12-31 15:32:52.832 ZigbeeForDomoticz: Worker thread started.
2023-12-31 15:32:52.832 Linky: Worker thread started.
2023-12-31 15:32:53.667 Linky: Heures creuses mises à 22h00-6h00
2023-12-31 15:32:53.667 Linky: Consommation à montrer sur le tableau de bord mis à value_day / peak_day
2023-12-31 15:32:53.667 Linky: Nombre de jours à récupérer pour la vue par heures mis à 7
2023-12-31 15:32:53.667 Linky: Nombre de jours à récupérer pour les autres vues mis à 7
2023-12-31 15:32:53.667 Linky: Nombre de jours à récupérer pour le calcul du pic mis à 1
2023-12-31 15:32:53.667 Linky: Debug mis à 0
2023-12-31 15:32:53.721 Linky: Cache chargé depuis le disque
2023-12-31 15:32:53.721 Linky: Si vous ne voyez pas assez de données dans la vue par heures, augmentez le paramètre Log des capteurs qui se trouve dans Réglages / Paramètres / Historique des logs
2023-12-31 15:32:57.969 Météo: Temp + Humidity + Baro (Météo)
2023-12-31 15:32:57.987 Météo: UV (UV Index)
2023-12-31 15:32:58.001 Météo: General/Percentage (Clouds %)
2023-12-31 15:32:58.032 Météo: Rain (Précipitation)
2023-12-31 15:33:00.661 ZigbeeForDomoticz: load PluginConf
2023-12-31 15:33:00.666 ZigbeeForDomoticz: Loading PluginConf - from Domoticz sqlite Db
2023-12-31 15:33:00.689 ZigbeeForDomoticz: Plugin data loaded where saved on Thursday, 2023-03-16 10:38:05
2023-12-31 15:33:00.689 ZigbeeForDomoticz: /home/pi/domoticz/plugins/Domoticz-Zigbee/Conf/PluginConf-02.json timestamp is 1703939717.0741518
2023-12-31 15:33:00.690 ZigbeeForDomoticz: Dz PluginConf is older than Json Dz: 1678959485.506258 Json: 1703939717.0741518
2023-12-31 15:33:00.697 ZigbeeForDomoticz: Installing plugin custom page /home/pi/domoticz/www/templates/ZigbeeForDomoticz.html
2023-12-31 15:33:00.698 ZigbeeForDomoticz: Starting LoggingManagement thread
2023-12-31 15:33:00.705 ZigbeeForDomoticz: start_logging_thread
2023-12-31 15:33:00.706 ZigbeeForDomoticz: logging_thread - listening
2023-12-31 15:33:00.913 Status: ZigbeeForDomoticz: - ZCL Cluster 0b04 - (V1) Electrical Measurement loaded
2023-12-31 15:33:00.918 Status: ZigbeeForDomoticz: - ZCL Cluster 0b05 - (V1) Diagnostics loaded
2023-12-31 15:33:00.920 Status: ZigbeeForDomoticz: - ZCL Cluster e000 - (V1) Tuya E000 Private Cluster loaded
2023-12-31 15:33:00.922 Status: ZigbeeForDomoticz: - ZCL Cluster e001 - (V1) Tuya E001 Private Cluster loaded
2023-12-31 15:33:00.925 Status: ZigbeeForDomoticz: - ZCL Cluster e002 - (V1) Tuya E002 Private Cluster loaded
2023-12-31 15:33:00.928 Status: ZigbeeForDomoticz: - ZCL Cluster fcc0 - (V1) LUMI Private Cluster loaded
2023-12-31 15:33:00.932 Status: ZigbeeForDomoticz: - ZCL Cluster ff66 - (V1) Lixee Zlinky private cluster loaded
2023-12-31 15:33:00.946 Status: ZigbeeForDomoticz: DeviceConf loaded - 16 confs loaded
2023-12-31 15:33:00.956 Status: ZigbeeForDomoticz: Local-Device conf loaded - 19 confs loaded
2023-12-31 15:33:02.097 Status: ZigbeeForDomoticz: Certified Devices loaded - 541 confs loaded
2023-12-31 15:33:02.108 Status: Linky: Récupération des données avec l'historique court
2023-12-31 15:33:02.114 Status: Linky: Traitement pour le point de livraison 17933285093465
2023-12-31 15:33:02.158 Status: ZigbeeForDomoticz: load ListOfDevice
2023-12-31 15:33:04.624 Status: ZigbeeForDomoticz: 37 Entries loaded from /home/pi/domoticz/plugins/Domoticz-Zigbee/Data/DeviceList-2.txt
2023-12-31 15:33:05.379 Status: ZigbeeForDomoticz: Transport mode: ZigpyZNP
2023-12-31 15:33:08.088 Status: EventSystem: Script event triggered: 2_Compteur_HP_HC
2023-12-31 15:33:10.544 Status: ZigbeeForDomoticz: Start Zigpy Transport on ZNP
2023-12-31 15:33:10.563 Status: ZigbeeForDomoticz: Starting radio znp port: /dev/serial/by-id/usb-ITead_Sonoff_Zigbee_3.0_USB_Dongle_Plus_c4e39f672f1aec11b0b37fe5f01c6278-if00-port0
2023-12-31 15:33:10.565 Status: ZigbeeForDomoticz: ZigpyTransport: thread_processing_and_sending Thread start.
2023-12-31 15:33:10.570 Status: ZigbeeForDomoticz: Start Web Server connection
2023-12-31 15:33:10.666 Status: ZigbeeForDomoticz: Web backend for Web User Interface started on port: 9440
2023-12-31 15:33:11.416 Status: ZigbeeForDomoticz: Plugin looks to upgrade the Certified Device package
2023-12-31 15:33:11.779 Status: ZigbeeForDomoticz: Started radio znp port: /dev/serial/by-id/usb-ITead_Sonoff_Zigbee_3.0_USB_Dongle_Plus_c4e39f672f1aec11b0b37fe5f01c6278-if00-port0
2023-12-31 15:33:12.464 Status: Linky: Prochaine connexion : 2024-01-01 08:10:02
2023-12-31 15:33:20.605 Status: ZigbeeForDomoticz: ZNP Radio register default Ep
2023-12-31 15:33:20.634 Status: ZigbeeForDomoticz: ZNP Radio register any additional/specific Ep
2023-12-31 15:33:22.012 Status: ZigbeeForDomoticz: Domoticz Widgets usage is at 19.2 % (206 units free)
2023-12-31 15:33:23.955 Error: ZigbeeForDomoticz: ReadCluster - Error/unknow 809d/01 Cluster: e000 Attribute: d003 Status: 00 DataType: 42 DataSize: 0004 Data: 41414141
2023-12-31 15:33:33.226 Status: User: toto (IP: 192.168.1.175) initiated a switch command (15/Porte de garage/Off)
2023-12-31 15:33:37.784 Status: EventSystem: Script event triggered: 2_Compteur_HP_HC
2023-12-31 15:33:39.349 Status: ZigbeeForDomoticz: ZNP Radio manufacturer: Texas Instruments
2023-12-31 15:33:39.351 Status: ZigbeeForDomoticz: ZNP Radio board model: CC2652
2023-12-31 15:33:39.353 Status: ZigbeeForDomoticz: ZNP Radio version: Z-Stack 20210708
2023-12-31 15:33:39.359 Status: ZigbeeForDomoticz: Network settings
2023-12-31 15:33:39.369 Status: ZigbeeForDomoticz: Number of devices recently active in Coordinator = 39
2023-12-31 15:33:39.372 Status: ZigbeeForDomoticz: [00] DevID: 00 Network addr: be32 IEEE: a4c138c083df2759 LQI: 000 power: ff Model: TS0201 ( T°C Ext. Sud )
2023-12-31 15:33:39.376 Status: ZigbeeForDomoticz: [01] DevID: 00 Network addr: 1682 IEEE: a4c138c1cb0f56be LQI: 000 power: ff Model: TS0001 ( Radiateur salle )
2023-12-31 15:33:39.381 Status: ZigbeeForDomoticz: [02] DevID: 00 Network addr: 0f56 IEEE: a4c1389a0a6b6848 LQI: 000 power: ff Model: TS0001 ( Radiateur couloir )
2023-12-31 15:33:39.384 Status: ZigbeeForDomoticz: [03] DevID: 00 Network addr: 6782 IEEE: a4c1382849723821 LQI: 000 power: ff Model: TS0001 ( Radiateur cuisine )
2023-12-31 15:33:39.389 Status: ZigbeeForDomoticz: [04] DevID: 00 Network addr: 37b7 IEEE: a4c1388816198824 LQI: 000 power: ff Model: TS0001 ( Radiateur entrée )
2023-12-31 15:33:39.393 Status: ZigbeeForDomoticz: [05] DevID: 00 Network addr: bc40 IEEE: a4c1387cbd3ec273 LQI: 000 power: ff Model: TS0001 ( Radiateur chambre sohan )
2023-12-31 15:33:39.397 Status: ZigbeeForDomoticz: [06] DevID: 00 Network addr: 92d6 IEEE: a4c1384671b4d883 LQI: 000 power: ff Model: TS0001 ( Radiateur chambre parents )
2023-12-31 15:33:39.402 Status: ZigbeeForDomoticz: [07] DevID: 00 Network addr: 397f IEEE: a4c1385db0285afe LQI: 000 power: ff Model: TS0001 ( Radiateur salle eau )
2023-12-31 15:33:39.404 Status: ZigbeeForDomoticz: Device IEEE: 00:12:4b:00:25:8d:4a:55
2023-12-31 15:33:39.409 Status: ZigbeeForDomoticz: Device NWK: 0x0000
2023-12-31 15:33:39.411 Status: ZigbeeForDomoticz: [08] DevID: 00 Network addr: fae8 IEEE: a4c138b125ed0f86 LQI: 000 power: ff Model: TS0601-_TZE200_nklqjk62 ( Porte de garage )
2023-12-31 15:33:39.414 Status: ZigbeeForDomoticz: Network Update Id: 0x0000
2023-12-31 15:33:39.419 Status: ZigbeeForDomoticz: PAN ID: 0x5A14
2023-12-31 15:33:39.422 Status: ZigbeeForDomoticz: [09] DevID: 00 Network addr: 1adf IEEE: 00124b0024c2e978 LQI: 000 power: ff not found in plugin database!
2023-12-31 15:33:39.425 Status: ZigbeeForDomoticz: Extended PAN ID: 20:ce:a7:9d:1c:ee:0f:7f
2023-12-31 15:33:39.427 Status: ZigbeeForDomoticz: [10] DevID: 00 Network addr: 1edc IEEE: a4c1388406494c64 LQI: 000 power: ff Model: TS0201 ( T°C bureau )
2023-12-31 15:33:39.431 Status: ZigbeeForDomoticz: Channel: 15
2023-12-31 15:33:39.436 Status: ZigbeeForDomoticz: [11] DevID: 00 Network addr: 5c79 IEEE: a4c138e0409d7976 LQI: 000 power: ff Model: TS0601-temphumi-2 ( Tuya num. )
2023-12-31 15:33:39.443 Status: ZigbeeForDomoticz: [12] DevID: 00 Network addr: 8567 IEEE: a4c138e4968bd5e6 LQI: 000 power: ff Model: TS0201 ( T°C Séjour )
2023-12-31 15:33:39.450 Status: ZigbeeForDomoticz: [13] DevID: 00 Network addr: d707 IEEE: a4c138df0222d16e LQI: 000 power: ff Model: TS0201 ( T°C Ext. Nord )
2023-12-31 15:33:39.458 Status: ZigbeeForDomoticz: [14] DevID: 00 Network addr: d7b3 IEEE: a4c13823356c4e06 LQI: 000 power: ff Model: TS0201 ( T°C Salle de bain )
2023-12-31 15:33:39.465 Status: ZigbeeForDomoticz: [15] DevID: 00 Network addr: c2eb IEEE: a4c138c22dde7735 LQI: 000 power: ff Model: TS0201 ( T°C Chambre Sohan )
2023-12-31 15:33:39.472 Status: ZigbeeForDomoticz: [16] DevID: 00 Network addr: 67aa IEEE: a4c13801f40baf0d LQI: 000 power: ff Model: TS0201 ( T°C Chambre Parents )
2023-12-31 15:33:39.479 Status: ZigbeeForDomoticz: [17] DevID: 00 Network addr: 6b0c IEEE: a4c138cc093422e6 LQI: 000 power: ff Model: TS0201 ( T°C Salle eau )
2023-12-31 15:33:39.485 Status: ZigbeeForDomoticz: [18] DevID: 00 Network addr: 4e71 IEEE: a4c13881114ec063 LQI: 000 power: ff Model: TS011F-plug ( Lave linge )
2023-12-31 15:33:39.497 Status: ZigbeeForDomoticz: [19] DevID: 00 Network addr: 91cb IEEE: a4c138e4910b93f8 LQI: 000 power: ff not found in plugin database!
2023-12-31 15:33:39.508 Status: ZigbeeForDomoticz: [20] DevID: 00 Network addr: 0739 IEEE: a4c138920ece7dcb LQI: 000 power: ff Model: TS0001 ( Tampon portail )
2023-12-31 15:33:39.518 Status: ZigbeeForDomoticz: [21] DevID: 00 Network addr: c6f0 IEEE: a4c1384ae539b897 LQI: 000 power: ff Model: TS0601-_TZE200_nklqjk62 ( Portail )
2023-12-31 15:33:39.525 Status: ZigbeeForDomoticz: [22] DevID: 00 Network addr: 2290 IEEE: a4c1381e934f492a LQI: 000 power: ff Model: TS0201 ( T°C Étage )
2023-12-31 15:33:39.543 Status: ZigbeeForDomoticz: [23] DevID: 00 Network addr: 8673 IEEE: a4c138900aeea911 LQI: 000 power: ff Model: TS0001 ( VMC sous sol )
2023-12-31 15:33:39.551 Status: ZigbeeForDomoticz: [24] DevID: 00 Network addr: 2959 IEEE: a4c13871c12b264c LQI: 000 power: ff Model: TS0001 ( Pompe puit )
2023-12-31 15:33:39.565 Status: ZigbeeForDomoticz: [25] DevID: 00 Network addr: 98d8 IEEE: a4c13875365b1da5 LQI: 000 power: ff Model: TS0201 ( T°C Sous Sol )
2023-12-31 15:33:39.568 Status: ZigbeeForDomoticz: [26] DevID: 00 Network addr: 7d2d IEEE: a4c1387133539200 LQI: 000 power: ff Model: TS0201 ( T°C Puit )
2023-12-31 15:33:39.570 Status: ZigbeeForDomoticz: [27] DevID: 00 Network addr: 83eb IEEE: a4c1385192a966db LQI: 000 power: ff Model: TS0201 ( T°C Buanderie )
2023-12-31 15:33:39.572 Status: ZigbeeForDomoticz: [28] DevID: 00 Network addr: 3b74 IEEE: a4c1383af582a736 LQI: 000 power: ff Model: TS0041 ( Bouton )
2023-12-31 15:33:39.582 Status: ZigbeeForDomoticz: [29] DevID: 00 Network addr: 7038 IEEE: a4c138132cd90422 LQI: 000 power: ff Model: TS0001 ( Test verrière )
2023-12-31 15:33:39.590 Status: ZigbeeForDomoticz: [30] DevID: 00 Network addr: 7761 IEEE: a4c138f5152683bf LQI: 000 power: ff Model: TS0202 ( Boite aux lettres )
2023-12-31 15:33:39.597 Status: ZigbeeForDomoticz: [31] DevID: 00 Network addr: 607d IEEE: e0798dfffe57dc65 LQI: 000 power: ff Model: TS011F-din ( Chauffe eau )
2023-12-31 15:33:39.605 Status: ZigbeeForDomoticz: [32] DevID: 00 Network addr: a7b8 IEEE: a4c1386b06649a21 LQI: 000 power: ff Model: TS011F-plug ( Reset_volets )
2023-12-31 15:33:39.613 Status: ZigbeeForDomoticz: [33] DevID: 00 Network addr: 9913 IEEE: a4c1387f3c6b1693 LQI: 000 power: ff Model: TS011F-plug ( Lave vaisselle )
2023-12-31 15:33:39.620 Status: ZigbeeForDomoticz: [34] DevID: 00 Network addr: b9ec IEEE: a4c138ac3bd035a0 LQI: 000 power: ff Model: TS011F-plug ( Frigo sous sol )
2023-12-31 15:33:39.628 Status: ZigbeeForDomoticz: [35] DevID: 00 Network addr: 322b IEEE: e0798dfffec36709 LQI: 000 power: ff Model: TS011F-din ( Plaque induction )
2023-12-31 15:33:39.635 Status: ZigbeeForDomoticz: [36] DevID: 00 Network addr: 093d IEEE: 84b4dbfffec0986a LQI: 000 power: ff Model: TS011F-din ( Four )
2023-12-31 15:33:39.643 Status: ZigbeeForDomoticz: [37] DevID: 00 Network addr: 809d IEEE: 84b4dbfffec0986b LQI: 000 power: ff Model: TS011F-din ( Frigo RDC )
2023-12-31 15:33:39.650 Status: ZigbeeForDomoticz: [38] DevID: 00 Network addr: a4c1 IEEE: 38e4968bd5e68567 LQI: 000 power: ff not found in plugin database!
2023-12-31 15:33:39.667 Status: ZigbeeForDomoticz: CC1352/CC2652, Z-Stack 3.30+ (znp)
2023-12-31 15:33:39.674 Status: ZigbeeForDomoticz: Installer Version Number: Z-Stack 3.30+ (build 20210708)
2023-12-31 15:33:39.681 Status: ZigbeeForDomoticz: Branch Version: ==> CC1352/CC2652, Z-Stack 3.30+ (znp) <==
2023-12-31 15:33:39.728 Status: ZigbeeForDomoticz: Zigbee Coordinator ieee: 00124b00258d4a55 , short addr: 0000
2023-12-31 15:33:39.737 Status: ZigbeeForDomoticz: Network state UP, PANID: 5a14 extPANID: 0x20cea79d1cee0f7f Channel: 15
2023-12-31 15:33:46.083 Status: ZigbeeForDomoticz: Request Disabling Accepting new Hardware
2023-12-31 15:33:46.139 Status: ZigbeeForDomoticz: Accepting new Hardware: Disable (Off)
2023-12-31 15:33:51.096 Status: ZigbeeForDomoticz: coordinator set to Certification : 1/CE -> CE
2023-12-31 15:33:52.255 Status: ZigbeeForDomoticz: ota_scan_folder Following Firmware have been loaded
2023-12-31 15:33:52.256 Status: ZigbeeForDomoticz: Plugin with Zigpy, Coordinator CC1352/CC2652, Z-Stack 3.30+ (znp) firmware Z-Stack 3.30+ (build 20210708) correctly initialized
2023-12-31 15:34:07.812 Status: EventSystem: Script event triggered: 2_Compteur_HP_HC
2023-12-31 15:34:13.490 Status: User: toto (IP: 192.168.1.101) initiated a switch command (70/Portail/Toggle)
2023-12-31 15:34:30.689 Activating Scene/Group: [/radiateurs chambre parents]
2023-12-31 15:34:30.694 Activating Scene/Group Device: /radiateur chambre parents (On)
2023-12-31 15:34:30.671 Status: EventSystem: Script event triggered: 1_Chauffage_chambres_device
2023-12-31 15:34:37.777 Status: EventSystem: Script event triggered: 2_Compteur_HP_HC
2023-12-31 15:34:56.217 Status: ZigbeeForDomoticz: ------ We have detected a miss configuration reports for device b9ec on ep 01 and cluster 0b04
2023-12-31 15:34:56.224 Status: ZigbeeForDomoticz: - Attribut 050b request to force a Configure Reporting due to field MaxInterval '044c' != '012c'
2023-12-31 15:35:07.774 Status: EventSystem: Script event triggered: 2_Compteur_HP_HC
2023-12-31 15:35:11.248 Status: ZigbeeForDomoticz: ------ We have detected a miss configuration reports for device a7b8 on ep 01 and cluster 0b04
2023-12-31 15:35:11.254 Status: ZigbeeForDomoticz: - Attribut 050b request to force a Configure Reporting due to field MaxInterval '044c' != '012C'
2023-12-31 15:35:16.243 Status: ZigbeeForDomoticz: ------ We have detected a miss configuration reports for device 9913 on ep 01 and cluster 0b04
2023-12-31 15:35:16.249 Status: ZigbeeForDomoticz: - Attribut 050b request to force a Configure Reporting due to field MaxInterval '044c' != '012c'
2023-12-31 15:35:37.780 Status: EventSystem: Script event triggered: 2_Compteur_HP_HC
2023-12-31 15:35:56.412 Status: ZigbeeForDomoticz: ------ We have detected a miss configuration reports for device b9ec on ep 01 and cluster 0b04
2023-12-31 15:35:56.413 Status: ZigbeeForDomoticz: - Attribut 050b request to force a Configure Reporting due to field MaxInterval '044c' != '012c'
2023-12-31 15:36:00.581 Status: EventSystem: Script event triggered: 3_Bandeau_rouge
2023-12-31 15:36:07.780 Status: EventSystem: Script event triggered: 2_Compteur_HP_HC
2023-12-31 15:36:11.227 Status: ZigbeeForDomoticz: ------ We have detected a miss configuration reports for device a7b8 on ep 01 and cluster 0b04
2023-12-31 15:36:11.234 Status: ZigbeeForDomoticz: - Attribut 050b request to force a Configure Reporting due to field MaxInterval '044c' != '012C'
2023-12-31 15:36:16.221 Status: ZigbeeForDomoticz: ------ We have detected a miss configuration reports for device 9913 on ep 01 and cluster 0b04
2023-12-31 15:36:16.228 Status: ZigbeeForDomoticz: - Attribut 050b request to force a Configure Reporting due to field MaxInterval '044c' != '012c'
2023-12-31 15:36:37.782 Status: EventSystem: Script event triggered: 2_Compteur_HP_HC


De plus j'ai une autre prise du même type mais pas même marque. Voici le lien..
Et avec celle là je n'ai pas le message dans le log Domoticz.


Pour récapituler avec les shorts ID de ZigbeeForDomoticz:
  • 4e71 ---> Prise Aubess --> Pas de message dans le log
  • a7b8 & 9913 & b9ec ---> Prises Elivco--> Message dans le log
pipiche
Messages : 4677
Inscription : 04 avr. 2018, 16:16
Contact :

Re: Erreur - Miss configuration reports

Message par pipiche »

A priori elles ne sont pas standard, car il y a un data type qui n'est pas correct.
Du coup il faut que tu récupères la dernière version de la base des objets certifiés [3.173]

Code : Tout sélectionner

sudo python3 -m pip install -r requirements.txt --upgrade
Il faudra que tu supprimes toutes les prises Elivco et que tu refasses un appairage from scratch
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
Répondre