Zigbee2mqtt conbee2

Type installation : NAS / autres
Version HA : docker 20.10.1
Ver. Supervisor : 2020.12.7
Bonjour,

j’ai ma clef conbee2 qui fonctionne tres biek lais je veux la passer sur zigbee2mqtt mais j’ai un message d’erreur.
merci pour votre aide

npm ERR! A complete log of this run can be found in:
npm ERR!     /root/.npm/_logs/2020-12-27T16_39_21_506Z-debug.log
2020-12-27T17:39:23: PM2 log: App [npm:0] exited with code [1] via signal [SIGINT]
2020-12-27T17:39:23: PM2 log: App [npm:0] starting in -fork mode-
2020-12-27T17:39:23: PM2 log: App [npm:0] online
> zigbee2mqtt@1.16.2-dev start /app
> node index.js
Zigbee2MQTT:info  2020-12-27 17:39:26: Logging to console and directory: '/share/zigbee2mqtt/log/2020-12-27.17-39-25' filename: log.txt
Zigbee2MQTT:info  2020-12-27 17:39:26: Starting Zigbee2MQTT version 1.16.2-dev (commit #99c77d2)
Zigbee2MQTT:info  2020-12-27 17:39:26: Starting zigbee-herdsman (0.13.41)
Zigbee2MQTT:error 2020-12-27 17:39:26: Error while starting zigbee-herdsman
Zigbee2MQTT:error 2020-12-27 17:39:26: Failed to start zigbee
Zigbee2MQTT:error 2020-12-27 17:39:26: Exiting...
Zigbee2MQTT:error 2020-12-27 17:39:26: Error: Error while opening serialport 'Error: Error: Resource busy, cannot open /dev/ttyACM0'
    at Znp.<anonymous> (/app/node_modules/zigbee-herdsman/dist/adapter/z-stack/znp/znp.js:136:32)
    at Generator.next (<anonymous>)
    at /app/node_modules/zigbee-herdsman/dist/adapter/z-stack/znp/znp.js:27:71
    at new Promise (<anonymous>)
    at __awaiter (/app/node_modules/zigbee-herdsman/dist/adapter/z-stack/znp/znp.js:23:12)
    at SerialPort.<anonymous> (/app/node_modules/zigbee-herdsman/dist/adapter/z-stack/znp/znp.js:134:49)
    at SerialPort._error (/app/node_modules/zigbee-herdsman/node_modules/@serialport/stream/lib/index.js:198:14)
    at /app/node_modules/zigbee-herdsman/node_modules/@serialport/stream/lib/index.js:242:12
npm
 ERR! code ELIFECYCLE
npm ERR! errno 1
npm 
ERR! zigbee2mqtt@1.16.2-dev start: `node index.js`
npm ERR! Exit status 1
npm ERR! 
npm ERR! Failed at the zigbee2mqtt@1.16.2-dev 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/2020-12-27T16_39_26_615Z-debug.log
2020-12-27T17:39:27: PM2 log: App [npm:0] exited with code [1] via signal [SIGINT]
2020-12-27T17:39:27: PM2 log: App [npm:0] starting in -fork mode-
2020-12-27T17:39:27: PM2 log: App [npm:0] online
> zigbee2mqtt@1.16.2-dev start /app
> node index.js
Zigbee2MQTT:info  2020-12-27 17:39:29: Logging to console and directory: '/share/zigbee2mqtt/log/2020-12-27.17-39-28' filename: log.txt
Zigbee2MQTT:info  2020-12-27 17:39:29: Starting Zigbee2MQTT version 1.16.2-dev (commit #99c77d2)
Zigbee2MQTT:info  2020-12-27 17:39:29: Starting zigbee-herdsman (0.13.41)
Zigbee2MQTT:error 2020-12-27 17:39:29: Error while starting zigbee-herdsman
Zigbee2MQTT:error 2020-12-27 17:39:29: Failed to start zigbee
Zigbee2MQTT:error 2020-12-27 17:39:29: Exiting...
Zigbee2MQTT:error 2020-12-27 17:39:29: Error: Error while opening serialport 'Error: Error: Resource busy, cannot open /dev/ttyACM0'
    at Znp.<anonymous> (/app/node_modules/zigbee-herdsman/dist/adapter/z-stack/znp/znp.js:136:32)
    at Generator.next (<anonymous>)
    at /app/node_modules/zigbee-herdsman/dist/adapter/z-stack/znp/znp.js:27:71
    at new Promise (<anonymous>)
    at __awaiter (/app/node_modules/zigbee-herdsman/dist/adapter/z-stack/znp/znp.js:23:12)
    at SerialPort.<anonymous> (/app/node_modules/zigbee-herdsman/dist/adapter/z-stack/znp/znp.js:134:49)
    at SerialPort._error (/app/node_modules/zigbee-herdsman/node_modules/@serialport/stream/lib/index.js:198:14)
    at /app/node_modules/zigbee-herdsman/node_modules/@serialport/stream/lib/index.js:242:12
npm
 ERR! code ELIFECYCLE
npm ERR! errno 1
npm 
ERR! zigbee2mqtt@1.16.2-dev start: `node index.js`
npm ERR! Exit status 1
npm ERR! 
npm ERR! Failed at the zigbee2mqtt@1.16.2-dev 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/2020-12-27T16_39_29_850Z-debug.log
2020-12-27T17:39:30: PM2 log: App [npm:0] exited with code [1] via signal [SIGINT]
2020-12-27T17:39:30: PM2 log: App [npm:0] starting in -fork mode-
2020-12-27T17:39:30: PM2 log: App [npm:0] online
> zigbee2mqtt@1.16.2-dev start /app
> node index.js
Zigbee2MQTT:info  2020-12-27 17:39:32: Logging to console and directory: '/share/zigbee2mqtt/log/2020-12-27.17-39-31' filename: log.txt
Zigbee2MQTT:info  2020-12-27 17:39:32: Starting Zigbee2MQTT version 1.16.2-dev (commit #99c77d2)
Zigbee2MQTT:info  2020-12-27 17:39:32: Starting zigbee-herdsman (0.13.41)
Zigbee2MQTT:error 2020-12-27 17:39:33: Error while starting zigbee-herdsman
Zigbee2MQTT:error 2020-12-27 17:39:33: Failed to start zigbee
Zigbee2MQTT:error 2020-12-27 17:39:33: Exiting...
Zigbee2MQTT:error 2020-12-27 17:39:33: Error: Error while opening serialport 'Error: Error: Resource busy, cannot open /dev/ttyACM0'
    at Znp.<anonymous> (/app/node_modules/zigbee-herdsman/dist/adapter/z-stack/znp/znp.js:136:32)
    at Generator.next (<anonymous>)
    at /app/node_modules/zigbee-herdsman/dist/adapter/z-stack/znp/znp.js:27:71
    at new Promise (<anonymous>)
    at __awaiter (/app/node_modules/zigbee-herdsman/dist/adapter/z-stack/znp/znp.js:23:12)
    at SerialPort.<anonymous> (/app/node_modules/zigbee-herdsman/dist/adapter/z-stack/znp/znp.js:134:49)
    at SerialPort._error (/app/node_modules/zigbee-herdsman/node_modules/@serialport/stream/lib/index.js:198:14)
    at /app/node_modules/zigbee-herdsman/node_modules/@serialport/stream/lib/index.js:242:12
npm
 ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR!
 zigbee2mqtt@1.16.2-dev start: `node index.js`
npm ERR! Exit status 1
npm ERR! 
npm ERR! Failed at the zigbee2mqtt@1.16.2-dev 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/2020-12-27T16_39_33_126Z-debug.log
2020-12-27T17:39:33: PM2 log: App [npm:0] exited with code [1] via signal [SIGINT]
2020-12-27T17:39:33: PM2 log: App [npm:0] starting in -fork mode-
2020-12-27T17:39:33: PM2 log: App [npm:0] online

Apparemment la ressource est utilisée essayé de redémarrer ou débrancher et rebrancher ta clef… elle est pas toujours active sur deconz par hasard ?

si tu as raison elle est active sur deconz je suis sur le tel je pensais qu’a distance ca basculait dessus direct.

nope il faut couper un pour utiliser l´autre

je vais tester pour comparer et vous que me conseillez vous rester deconz ou mqtt
avantage de mqtt ?

si deconz fonctionne bien pourquoi changer?

juste pour tester :slight_smile: d’ailleurs je rebooter et j’ai le meme message en ayant desactive deconz donc pas de test for me :sob: la deco z marche tres bien que me conseiller vous pour atteindre un abri de jardin qui est a 25m