Apparaige equipement fait planter Zigbee2mqtt

Plugins Protocole domotique
,
1

Bonsoir,

Je suis sous ZigbeeLinker (configuration zigbee2mqtt + client MQTT), mon serveur mqtt est géré via le #plugin-mqtt2

Je n’avais pas fait d’inclusion depuis un moment et là, je constate qu’une inclusion (appairage d’un nouvel équipement fait planter le serveur zigbee2mqtt).
tests fait avec une prose OSRAM et une télécommande EGLO, meme resultat

message dans le centre de messages : ##### Le service zigbee2mqtt s'est arrêté #####

j’ai réessayé de remettre à jour les dépendances, et du coup, je suis en plus passé en 1.25.0
J’ai restauré un 1.24.0, mais pb identique

les logs de demarrage de Z2M en mode debug :

> zigbee2mqtt@1.24.0 start /opt/zigbee2mqtt
> node index.js
e[34mZigbee2MQTT:debuge[39m 2022-04-04 23:05:00: Loaded state from file /var/www/html/plugins/zigbee2mqtt/data/zigbee2mqtt/state.json
e[32mZigbee2MQTT:info e[39m 2022-04-04 23:05:00: Logging to console and directory: '/var/www/html/plugins/zigbee2mqtt/data/zigbee2mqtt/log/2022-04-04.23-04-58' filename: log.txt
e[34mZigbee2MQTT:debuge[39m 2022-04-04 23:05:00: Removing old log directory '/var/www/html/plugins/zigbee2mqtt/data/zigbee2mqtt/log/2022-04-04.17-06-17'
e[32mZigbee2MQTT:info e[39m 2022-04-04 23:05:00: Starting Zigbee2MQTT version 1.24.0 (commit #unknown)
e[32mZigbee2MQTT:info e[39m 2022-04-04 23:05:00: Starting zigbee-herdsman (0.14.20)
e[34mZigbee2MQTT:debuge[39m 2022-04-04 23:05:00: Using zigbee-herdsman with settings: '{"adapter":{"concurrent":null,"delay":null,"disableLED":false},"backupPath":"/var/www/html/plugins/zigbee2mqtt/data/zigbee2mqtt/coordinator_backup.json","databaseBackupPath":"/var/www/html/plugins/zigbee2mqtt/data/zigbee2mqtt/database.db.backup","databasePath":"/var/www/html/plugins/zigbee2mqtt/data/zigbee2mqtt/database.db","network":{"channelList":[11],"extendedPanID":[221,221,221,221,221,221,221,221],"networkKey":"HIDDEN","panID":6754},"serialPort":{"adapter":"deconz"}}'
2022-04-04T21:05:01.135Z zigbee-herdsman:adapter No path provided, auto detecting path
2022-04-04T21:05:01.357Z zigbee-herdsman:adapter Auto detected path '/dev/ttyACM0' from adapter 'DeconzAdapter'
2022-04-04T21:05:01.359Z zigbee-herdsman:deconz:driver Set delay to 0
CREATED DECONZ ADAPTER
2022-04-04T21:05:01.361Z zigbee-herdsman:controller:log Starting with options '{"network":{"networkKeyDistribute":false,"networkKey":[1,3,5,7,9,11,13,15,0,2,4,6,8,10,12,13],"panID":6754,"extendedPanID":[221,221,221,221,221,221,221,221],"channelList":[11]},"serialPort":{"path":"/dev/ttyACM0","adapter":"deconz"},"databasePath":"/var/www/html/plugins/zigbee2mqtt/data/zigbee2mqtt/database.db","databaseBackupPath":"/var/www/html/plugins/zigbee2mqtt/data/zigbee2mqtt/database.db.backup","backupPath":"/var/www/html/plugins/zigbee2mqtt/data/zigbee2mqtt/coordinator_backup.json","adapter":{"disableLED":false,"concurrent":null,"delay":null}}'
2022-04-04T21:05:01.362Z zigbee-herdsman:deconz:driver Opening with /dev/ttyACM0
2022-04-04T21:05:01.371Z zigbee-herdsman:deconz:driver Serialport opened
2022-04-04T21:05:01.372Z zigbee-herdsman:controller:log Started with result 'resumed'
2022-04-04T21:05:01.372Z zigbee-herdsman:controller:log Injected database: true, adapter: true
2022-04-04T21:05:01.373Z zigbee-herdsman:deconz:driver send read parameter request from queue. seqNr: 1 paramId: 1
2022-04-04T21:05:01.380Z zigbee-herdsman:deconz:frameParser DEVICE_STATE changed: 10101010
2022-04-04T21:05:01.380Z zigbee-herdsman:deconz:driver networkstate: 2 apsDataConfirm: 0 apsDataIndication: 1 configChanged: 0 apsRequestFreeSlots: 1
2022-04-04T21:05:01.380Z zigbee-herdsman:deconz:frameParser DEVICE_STATE changed: 10101010
2022-04-04T21:05:01.381Z zigbee-herdsman:deconz:driver networkstate: 2 apsDataConfirm: 0 apsDataIndication: 1 configChanged: 0 apsRequestFreeSlots: 1
2022-04-04T21:05:01.381Z zigbee-herdsman:deconz:frameParser DEVICE_STATE changed: 10101010
2022-04-04T21:05:01.381Z zigbee-herdsman:deconz:driver networkstate: 2 apsDataConfirm: 0 apsDataIndication: 1 configChanged: 0 apsRequestFreeSlots: 1
2022-04-04T21:05:01.382Z zigbee-herdsman:deconz:driver query aps data indication
2022-04-04T21:05:01.384Z zigbee-herdsman:deconz:frameParser MAC: 0x00212effff060dcc
2022-04-04T21:05:01.384Z zigbee-herdsman:deconz:driver send read parameter request from queue. seqNr: 3 paramId: 7
2022-04-04T21:05:01.387Z zigbee-herdsman:deconz:frameParser NWKADDR: 0
e[32mZigbee2MQTT:info e[39m 2022-04-04 23:05:01: zigbee-herdsman started (resumed)
2022-04-04T21:05:01.396Z zigbee-herdsman:deconz:driver DATA_INDICATION - sending read data request - SeqNr. 2
2022-04-04T21:05:01.396Z zigbee-herdsman:deconz:driver send read firmware version request from queue. seqNr: 4
2022-04-04T21:05:01.399Z zigbee-herdsman:deconz:frameParser DATA_INDICATION RESPONSE - seqNr. 2 srcAddr: 0xe5af destAddr: 0x0 profile id: 0x104 cluster id: 0x0 lqi: 255
2022-04-04T21:05:01.400Z zigbee-herdsman:deconz:frameParser response payload: 24,127,10,1,0,32,64,226,255,32,22
2022-04-04T21:05:01.406Z zigbee-herdsman:controller:log Received 'zcl' data '{"frame":{"Header":{"frameControl":{"frameType":0,"manufacturerSpecific":false,"direction":1,"disableDefaultResponse":true,"reservedBits":0},"transactionSequenceNumber":127,"manufacturerCode":null,"commandIdentifier":10},"Payload":[{"attrId":1,"dataType":32,"attrData":64},{"attrId":65506,"dataType":32,"attrData":22}],"Command":{"ID":10,"name":"report","parameters":[{"name":"attrId","type":33},{"name":"dataType","type":32},{"name":"attrData","type":1000}]}},"address":58799,"endpoint":1,"linkquality":255,"groupID":null,"wasBroadcast":false,"destinationEndpoint":1}'
e[34mZigbee2MQTT:debuge[39m 2022-04-04 23:05:01: Received Zigbee message from '0x5c0272fffeefe8eb', type 'attributeReport', cluster 'genBasic', data '{"65506":22,"appVersion":64}' from endpoint 1 with groupID null
2022-04-04T21:05:01.421Z zigbee-herdsman:deconz:driver networkstate: 2 apsDataConfirm: 0 apsDataIndication: 1 configChanged: 0 apsRequestFreeSlots: 1
2022-04-04T21:05:01.433Z zigbee-herdsman:deconz:driver query aps data indication
2022-04-04T21:05:01.434Z zigbee-herdsman:deconz:frameParser read firmware version response - version: 0,7,114,38
e[32mZigbee2MQTT:info e[39m 2022-04-04 23:05:01: Coordinator firmware version: '{"meta":{"maintrel":0,"majorrel":38,"minorrel":114,"product":0,"revision":"0x26720700","transportrev":0},"type":"ConBee2/RaspBee2"}'
2022-04-04T21:05:01.438Z zigbee-herdsman:deconz:driver DATA_INDICATION - sending read data request - SeqNr. 5
2022-04-04T21:05:01.438Z zigbee-herdsman:deconz:driver send read parameter request from queue. seqNr: 6 paramId: 5
2022-04-04T21:05:01.440Z zigbee-herdsman:deconz:frameParser DATA_INDICATION RESPONSE - seqNr. 5 srcAddr: 0xaf5 destAddr: 0x0 profile id: 0x104 cluster id: 0xef00 lqi: 255
2022-04-04T21:05:01.440Z zigbee-herdsman:deconz:frameParser response payload: 9,98,1,95,205,2,2,0,4,0,0,0,170
2022-04-04T21:05:01.444Z zigbee-herdsman:controller:log Received 'zcl' data '{"frame":{"Header":{"frameControl":{"frameType":1,"manufacturerSpecific":false,"direction":1,"disableDefaultResponse":false,"reservedBits":0},"transactionSequenceNumber":98,"manufacturerCode":null,"commandIdentifier":1},"Payload":{"seq":52575,"dpValues":[{"dp":2,"datatype":2,"data":{"type":"Buffer","data":[0,0,0,170]}}]},"Command":{"ID":1,"parameters":[{"name":"seq","type":33},{"name":"dpValues","type":1011}],"name":"dataResponse"}},"address":2805,"endpoint":1,"linkquality":255,"groupID":null,"wasBroadcast":false,"destinationEndpoint":1}'
e[34mZigbee2MQTT:debuge[39m 2022-04-04 23:05:01: Received Zigbee message from '0x5c0272fffe7f7c16', type 'commandDataResponse', cluster 'manuSpecificTuya', data '{"dpValues":[{"data":{"data":[0,0,0,170],"type":"Buffer"},"datatype":2,"dp":2}],"seq":52575}' from endpoint 1 with groupID null
2022-04-04T21:05:01.448Z zigbee-herdsman:controller:endpoint DefaultResponse 0x5c0272fffe7f7c16/1 61184(1, {"sendWhen":"immediate","timeout":10000,"disableResponse":false,"disableRecovery":false,"disableDefaultResponse":true,"direction":1,"srcEndpoint":null,"reservedBits":0,"manufacturerCode":null,"transactionSequenceNumber":null,"writeUndiv":false})
2022-04-04T21:05:01.450Z zigbee-herdsman:deconz:adapter no response expected
2022-04-04T21:05:01.451Z zigbee-herdsman:deconz:driver networkstate: 2 apsDataConfirm: 0 apsDataIndication: 1 configChanged: 0 apsRequestFreeSlots: 1
2022-04-04T21:05:01.452Z zigbee-herdsman:deconz:driver DATA_REQUEST - destAddr: 0xaf5 EP:1 SeqNr. 7 request id: 1
2022-04-04T21:05:01.453Z zigbee-herdsman:deconz:driver query aps data indication
2022-04-04T21:05:01.453Z zigbee-herdsman:deconz:frameParser PANID: 1a62
2022-04-04T21:05:01.458Z zigbee-herdsman:deconz:driver DATA_INDICATION - sending read data request - SeqNr. 8
2022-04-04T21:05:01.459Z zigbee-herdsman:deconz:driver send read parameter request from queue. seqNr: 9 paramId: 11
2022-04-04T21:05:01.471Z zigbee-herdsman:deconz:frameParser DATA_REQUEST RESPONSE - request id: 1 status: 0
2022-04-04T21:05:01.471Z zigbee-herdsman:deconz:driver networkstate: 2 apsDataConfirm: 0 apsDataIndication: 1 configChanged: 0 apsRequestFreeSlots: 1
2022-04-04T21:05:01.471Z zigbee-herdsman:deconz:frameParser DEVICE_STATE changed: 10101110
2022-04-04T21:05:01.471Z zigbee-herdsman:deconz:driver networkstate: 2 apsDataConfirm: 1 apsDataIndication: 1 configChanged: 0 apsRequestFreeSlots: 1
2022-04-04T21:05:01.474Z zigbee-herdsman:deconz:driver query aps data confirm
2022-04-04T21:05:01.479Z zigbee-herdsman:deconz:driver DATA_CONFIRM - sending data state request - SeqNr. 10
2022-04-04T21:05:01.480Z zigbee-herdsman:deconz:driver query aps data indication
2022-04-04T21:05:01.481Z zigbee-herdsman:deconz:frameParser DATA_INDICATION RESPONSE - seqNr. 8 srcAddr: 0xaf5 destAddr: 0x0 profile id: 0x104 cluster id: 0xef00 lqi: 255
2022-04-04T21:05:01.481Z zigbee-herdsman:deconz:frameParser response payload: 9,99,1,95,206,4,4,0,1,2
2022-04-04T21:05:01.484Z zigbee-herdsman:controller:log Received 'zcl' data '{"frame":{"Header":{"frameControl":{"frameType":1,"manufacturerSpecific":false,"direction":1,"disableDefaultResponse":false,"reservedBits":0},"transactionSequenceNumber":99,"manufacturerCode":null,"commandIdentifier":1},"Payload":{"seq":52831,"dpValues":[{"dp":4,"datatype":4,"data":{"type":"Buffer","data":[2]}}]},"Command":{"ID":1,"parameters":[{"name":"seq","type":33},{"name":"dpValues","type":1011}],"name":"dataResponse"}},"address":2805,"endpoint":1,"linkquality":255,"groupID":null,"wasBroadcast":false,"destinationEndpoint":1}'
e[34mZigbee2MQTT:debuge[39m 2022-04-04 23:05:01: Received Zigbee message from '0x5c0272fffe7f7c16', type 'commandDataResponse', cluster 'manuSpecificTuya', data '{"dpValues":[{"data":{"data":[2],"type":"Buffer"},"datatype":4,"dp":4}],"seq":52831}' from endpoint 1 with groupID null
2022-04-04T21:05:01.486Z zigbee-herdsman:controller:endpoint DefaultResponse 0x5c0272fffe7f7c16/1 61184(1, {"sendWhen":"immediate","timeout":10000,"disableResponse":false,"disableRecovery":false,"disableDefaultResponse":true,"direction":1,"srcEndpoint":null,"reservedBits":0,"manufacturerCode":null,"transactionSequenceNumber":null,"writeUndiv":false})
2022-04-04T21:05:01.486Z zigbee-herdsman:deconz:adapter no response expected
2022-04-04T21:05:01.487Z zigbee-herdsman:deconz:driver networkstate: 2 apsDataConfirm: 1 apsDataIndication: 0 configChanged: 0 apsRequestFreeSlots: 1
2022-04-04T21:05:01.487Z zigbee-herdsman:deconz:frameParser APS_EXT_PANID: 0xdddddddddddddddd
2022-04-04T21:05:01.487Z zigbee-herdsman:deconz:driver send read parameter request from queue. seqNr: 13 paramId: 28
2022-04-04T21:05:01.488Z zigbee-herdsman:deconz:driver DATA_REQUEST - destAddr: 0xaf5 EP:1 SeqNr. 12 request id: 2
2022-04-04T21:05:01.489Z zigbee-herdsman:deconz:driver DATA_INDICATION - sending read data request - SeqNr. 11
2022-04-04T21:05:01.489Z zigbee-herdsman:deconz:driver query aps data confirm
2022-04-04T21:05:01.491Z zigbee-herdsman:deconz:frameParser DATA_CONFIRM RESPONSE - destAddr: 0xaf5 request id: 1 confirm status: 0
2022-04-04T21:05:01.491Z zigbee-herdsman:deconz:driver networkstate: 2 apsDataConfirm: 0 apsDataIndication: 0 configChanged: 0 apsRequestFreeSlots: 1
2022-04-04T21:05:01.491Z zigbee-herdsman:deconz:adapter sendZclFrameToEndpoint - message send with transSeq Nr.: 98
2022-04-04T21:05:01.491Z zigbee-herdsman:deconz:adapter false, true, false
2022-04-04T21:05:01.491Z zigbee-herdsman:deconz:adapter resolve request
2022-04-04T21:05:01.493Z zigbee-herdsman:deconz:frameParser CHANNEL: 11
2022-04-04T21:05:01.493Z zigbee-herdsman:deconz:driver send read parameter request from queue. seqNr: 15 paramId: 24
2022-04-04T21:05:01.495Z zigbee-herdsman:deconz:driver DATA_CONFIRM - sending data state request - SeqNr. 14
2022-04-04T21:05:01.518Z zigbee-herdsman:deconz:frameParser DATA_REQUEST RESPONSE - request id: 2 status: 0
2022-04-04T21:05:01.518Z zigbee-herdsman:deconz:driver networkstate: 2 apsDataConfirm: 0 apsDataIndication: 0 configChanged: 0 apsRequestFreeSlots: 1
2022-04-04T21:05:01.518Z zigbee-herdsman:deconz:frameParser DEVICE_STATE changed: 10100110
2022-04-04T21:05:01.518Z zigbee-herdsman:deconz:driver networkstate: 2 apsDataConfirm: 1 apsDataIndication: 0 configChanged: 0 apsRequestFreeSlots: 1
2022-04-04T21:05:01.518Z zigbee-herdsman:deconz:frameParser NETWORK_KEY: hidden
2022-04-04T21:05:01.518Z zigbee-herdsman:deconz:frameParser DATA_CONFIRM RESPONSE - destAddr: 0xaf5 request id: 2 confirm status: 0
2022-04-04T21:05:01.519Z zigbee-herdsman:deconz:driver networkstate: 2 apsDataConfirm: 0 apsDataIndication: 0 configChanged: 0 apsRequestFreeSlots: 1
2022-04-04T21:05:01.519Z zigbee-herdsman:deconz:adapter sendZclFrameToEndpoint - message send with transSeq Nr.: 99
2022-04-04T21:05:01.519Z zigbee-herdsman:deconz:adapter false, true, false
2022-04-04T21:05:01.519Z zigbee-herdsman:deconz:adapter resolve request
e[34mZigbee2MQTT:debuge[39m 2022-04-04 23:05:01: Zigbee network parameters: {"channel":11,"extendedPanID":"0xdddddddddddddddd","panID":6754}
e[31mZigbee2MQTT:errore[39m 2022-04-04 23:05:01: Failed to start zigbee
e[31mZigbee2MQTT:errore[39m 2022-04-04 23:05:01: Check https://www.zigbee2mqtt.io/guide/installation/20_zigbee2mqtt-fails-to-start.html for possible solutions
e[31mZigbee2MQTT:errore[39m 2022-04-04 23:05:01: Exiting...
e[31mZigbee2MQTT:errore[39m 2022-04-04 23:05:01: TypeError [ERR_INVALID_ARG_TYPE]: The "path" argument must be of type string. Received undefined
at new NodeError (internal/errors.js:322:7)
at validateString (internal/validators.js:124:11)
at Object.join (path.js:1148:7)
at Object.joinPath (/opt/zigbee2mqtt/lib/util/data.ts:17:17)
at writeDevicesOrGroups (/opt/zigbee2mqtt/lib/util/settings.ts:227:38)
at write (/opt/zigbee2mqtt/lib/util/settings.ts:233:5)
at Object.addDevice (/opt/zigbee2mqtt/lib/util/settings.ts:529:5)
at Device.ensureInSettings (/opt/zigbee2mqtt/lib/model/device.ts:41:22)
at Zigbee.resolveDevice (/opt/zigbee2mqtt/lib/zigbee.ts:230:20)
at /opt/zigbee2mqtt/lib/zigbee.ts:272:30
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! zigbee2mqtt@1.24.0 start: `node index.js`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the zigbee2mqtt@1.24.0 start script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
npm ERR! A complete log of this run can be found in:
npm ERR!     /root/.npm/_logs/2022-04-04T21_05_01_780Z-debug.log

Les logs au moment de l’appairage :

2022-04-04T21:26:08.580Z zigbee-herdsman:deconz:frameParser DEVICE_STATE changed: 10101010
2022-04-04T21:26:08.580Z zigbee-herdsman:deconz:driver networkstate: 2 apsDataConfirm: 0 apsDataIndication: 1 configChanged: 0 apsRequestFreeSlots: 1
2022-04-04T21:26:08.585Z zigbee-herdsman:deconz:driver query aps data indication
2022-04-04T21:26:08.590Z zigbee-herdsman:deconz:driver DATA_INDICATION - sending read data request - SeqNr. 180
2022-04-04T21:26:08.598Z zigbee-herdsman:deconz:frameParser DATA_INDICATION RESPONSE - seqNr. 180 srcAddr: 0x308 destAddr: 0xfffd profile id: 0x0 cluster id: 0x13 lqi: 248
2022-04-04T21:26:08.598Z zigbee-herdsman:deconz:frameParser response payload: 0,8,3,24,33,10,10,170,62,176,124,142
2022-04-04T21:26:08.600Z zigbee-herdsman:controller:log Device '0x7cb03eaa0a0a2118' joined
2022-04-04T21:26:08.600Z zigbee-herdsman:deconz:driver networkstate: 2 apsDataConfirm: 0 apsDataIndication: 0 configChanged: 0 apsRequestFreeSlots: 1
2022-04-04T21:26:08.601Z zigbee-herdsman:controller:log Device '0x7cb03eaa0a0a2118' accepted by handler
2022-04-04T21:26:08.601Z zigbee-herdsman:controller:log New device '0x7cb03eaa0a0a2118' joined
2022-04-04T21:26:08.601Z zigbee-herdsman:controller:log Creating device '0x7cb03eaa0a0a2118'
TypeError [ERR_INVALID_ARG_TYPE]: The "path" argument must be of type string. Received undefined
at new NodeError (internal/errors.js:322:7)
at validateString (internal/validators.js:124:11)
at Object.join (path.js:1148:7)
at Object.joinPath (/opt/zigbee2mqtt/lib/util/data.ts:17:17)
at writeDevicesOrGroups (/opt/zigbee2mqtt/lib/util/settings.ts:227:38)
at write (/opt/zigbee2mqtt/lib/util/settings.ts:233:5)
at Object.addDevice (/opt/zigbee2mqtt/lib/util/settings.ts:529:5)
at Device.ensureInSettings (/opt/zigbee2mqtt/lib/model/device.ts:41:22)
at Zigbee.resolveDevice (/opt/zigbee2mqtt/lib/zigbee.ts:230:20)
at Controller.<anonymous> (/opt/zigbee2mqtt/lib/zigbee.ts:89:33)
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! zigbee2mqtt@1.24.0 start: `node index.js`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the zigbee2mqtt@1.24.0 start script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
npm ERR! A complete log of this run can be found in:
npm ERR!     /root/.npm/_logs/2022-04-04T21_26_08_863Z-debug.log

Bref, je ne sais plus trop ou chercher
Une restauration permet de repartir correctement (plus de plantage de Z2M, mais le plantage se reproduit à la premiere inclusion

si quelqu’un à une idée

Norbert

2

Hello

ta version de node ?
Quel cle zigbee ? et son firmware ?

3 
##### Install or update NodeJs
NodeJs 14 already installed : Nothing to do !
###################################################

clé CONBEE2 sur le dernier Firmware stable (Aout 21)
Jeedom en 4.2.14
zigbee2mqtt en 1.25.0, mais meme pb en 1.24.0

4

Je sais plus quand mais sur le forum je suis tombé sur un topic sur lequel le membre avais le même souci que toi , et que cela venait du firmware, il a flasher avec un autre firmware est cela à résolu son souci.

Je vais essayé de retrouvé le post

5

je viens de voir que @cddu33 a eu exactement le meme pb :

Sans solution sur le post.
@cddu33 si tu passes par là, si tu peux me donner quelques news sur ton pb ?

ce post aussi, mais sans solution apportée non plus (mais pas tout à fait les meme logs d’erreur :

6

Bonsoir, je me souviens plus exactement ce que j’avais fait mais le problème ven
ait du fichier de configuration de zigbee2mqtt il y avait des virgules et des espaces à la fin du fichier qui coinçait il faisait le bugger le logiciel.
Une fois nettoyer ce fichier plus de soucis depuis

je n’ai jamais réussi à reproduire le problème

7

Bonjour,

j’ai exactement le même problème et je suis avec jeedom 4.2.14, zigbeelinker et une cle zigbee sonoff dongle plus 3.0. Tout fonctionne bien sauf quand je passe en mode inclusion et un capteur veut s’inclure.

8

Quels sont les droits sur tes fichiers dans plugin\zigbee2mqtt\data\zigbee2mqtt (de mémoire car je ne suis pas sur mon ordinateur !).
Mon pb (non résolu) est que les fichiers databzse et configuration ont des droits root, et le plugin n’arrive pas à écrire dedans pour l’inclusion.
Ça génère une discordance des équipements entre les 2 fichiers, ce qui fait planter le plugin

9

image
image775×184 7.19 KB

Et essaie de regarder ce post(Soucis démarrage service Zigbee2MQTT),une personne a resolu le probleme. Pour ma part, j’ai resolu le probleme en supprimant le plugin zigbeelinker et en le reinstallant. En esperant que ça t’aide

10

Bonjour tout le monde, Je ne sais pas si vous avez reussi a resoudre le problème, mai j’ai eu le meme problème hier avec Z2M dans le plug in officiel jeezigbee, plus moyen de demarrer Z2M, j’ai du supprimer et remettre le plug in du coup j’ai perdu mes modules en test… et je croise les doigts pour que ca ne recommence plus car si je perds les module a chaque fois c’est un peu galere…
J’avais ce message d’erreur
TypeError: The "path" argument must be of type string. Received undefined
et entre temps j’ai vu ceci sur le github

Si ca peut aider…

11

Merci.

Dans mon cas, ca a été reglé via cet autre post :

Norbert

12

Ha oui je n’ai pas trouvé où était ces mots à effacer

13

image

14

Tu peux aussi y aller via la config du plugin zigbeelinker :

image
image990×327 20.5 KB

15

Du coup en supprimant le plug in pour le réinstaller je peux retrouver mes équipements si je vais chercher le fichier configuration dans une sauvegarde jeedom ?
J’utilise z2m mais dans jeezigbee, je suppose que le fonctionnement est à peu près pareil

16

C’ets un pb dans z2m, donc supprimer leplugin et le restaurer ne devrait rien changer. le pb est dans le fichier dasn lequel tu as tes equipements. donc concretement :

  • Soit le fichier est supprimé (et donc le pb aussi), mais tous tes equipements sont supppirmés
  • Soit le fichier est conservé et donc tes équipements aussi, mais tu aura toujours le pb …

Donc pas de solution que d’aller modifier à la main

Norbert

17

Chez moi après avoir supprimé et réinstallé j’ai perdu tous les modules.
Je pensais pouvoir retrouvé le fichier dans une sauvegarde jeedom et remettre les équipements mais bon je pense que je vais les reinclure a la main. Je n’avais pas beaucoup de modules.
J’espère que ça n’arrivera plus lorsque j’aurai migré tous les modules….

18

Tu dois pouvoir récupérer tes modules dans une save via les 2 fichiers data base et configuration dans plugins\zigbee2mqtt\data\zigbee2mqtt

Pas sur du chemin exact, je suis sur mon téléphone

Norbert

19

yes je les ai dans une sauvegarde.

---
permit_join: false
mqtt:
  server: mqtt://127.0.0.1:1883
  user: ueuyey
  password: dthdrt
  base_topic: zigbee2mqtt
  include_device_information: true
serial:
  port: /dev/ttyACM0
  adapter: ezsp
frontend:
  port: 8080
  host: 0.0.0.0
  auth_token: rt6GPMat4HpmvgKRe4pvAjkL45Uq1uxE
advanced:
  last_seen: ISO_8601
  log_level: debug
external_converters:
- /var/www/html/plugins/z2m/core/class/../config/converters/Danfoss/icon.js
devices:
  "0x00158d000223a56d":
    friendly_name: Sonde Cave
  "0x2c1165fffe2224e2":
    friendly_name: Prise Karotz
  "0x00158d0004505d97":
    friendly_name: Bouton Karotz
  "0x842e14fffe074ed8":
    friendly_name: Bandeau Led Salon MQTT
  "0xa4c13867da4ac8a8":
    friendly_name: PRISE TV MQTT
  "0xbc33acfffea517aa":
    friendly_name: Bouton TV MQTT
groups: []

groups: []

c’est ca qu’il faut supprimer ?

Je ne l’avais pas trouvé car javais un autre fichier configuration mais pas dans DATA…
du coup je remets ces 2 fichiers directement ? ou je colle une partie du fichier configuration ?

20

Yes … C’est bien ça
Tu remets les 2 fichiers au même endroit et tu supprimes groupe.
Et tu relances Z2m
Nécessité peut-être de refaire une synchronisation

Norbert