Created
July 12, 2021 09:25
-
-
Save thorrrr/e45c6172ae9f18ee7db0598d6d4f50db to your computer and use it in GitHub Desktop.
z2m
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
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.20.0 start: `node index.js` | |
npm ERR! Exit status 1 | |
npm ERR! | |
npm ERR! Failed at the zigbee2mqtt@1.20.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/2021-07-12T09_17_34_004Z-debug.log | |
[10:17:34] INFO: Handing over control to Zigbee2mqtt Core ... | |
> zigbee2mqtt@1.20.0 start /app | |
> node index.js | |
Zigbee2MQTT:error 2021-07-12 10:17:36: Error while starting zigbee-herdsman | |
Zigbee2MQTT:error 2021-07-12 10:17:36: Failed to start zigbee | |
Zigbee2MQTT:error 2021-07-12 10:17:36: Check https://www.zigbee2mqtt.io/information/FAQ.html#help-zigbee2mqtt-fails-to-start for possible solutions | |
Zigbee2MQTT:error 2021-07-12 10:17:36: Exiting... | |
Zigbee2MQTT:error 2021-07-12 10:17:36: Error: Error while opening serialport 'Error: Error: No such file or directory, 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.20.0 start: `node index.js` | |
npm ERR! Exit status 1 | |
npm ERR! | |
npm ERR! Failed at the zigbee2mqtt@1.20.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/2021-07-12T09_17_36_132Z-debug.log | |
[10:17:36] INFO: Handing over control to Zigbee2mqtt Core ... | |
> zigbee2mqtt@1.20.0 start /app | |
> node index.js | |
Zigbee2MQTT:error 2021-07-12 10:17:38: Error while starting zigbee-herdsman | |
Zigbee2MQTT:error 2021-07-12 10:17:38: Failed to start zigbee | |
Zigbee2MQTT:error 2021-07-12 10:17:38: Check https://www.zigbee2mqtt.io/information/FAQ.html#help-zigbee2mqtt-fails-to-start for possible solutions | |
Zigbee2MQTT:error 2021-07-12 10:17:38: Exiting... | |
Zigbee2MQTT:error 2021-07-12 10:17:38: Error: Error while opening serialport 'Error: Error: No such file or directory, 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.20.0 start: `node index.js` | |
npm ERR! Exit status 1 | |
npm ERR! | |
npm ERR! Failed at the zigbee2mqtt@1.20.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/2021-07-12T09_17_38_248Z-debug.log |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment