问题描述如图
koenkk-zigbee2mqtt
date | stream | content |
---|---|---|
2020-09-17 02:34:15 | stdout | e[0m |
2020-09-17 02:34:15 | stdout | e[0me[37;40mnpme[0m e[0me[31;40mERR!e[0me[35me[0m /root/.npm/_logs/2020-09-17T02_34_14_407Z-debug.log |
2020-09-17 02:34:15 | stdout | e[37;40mnpme[0m e[0me[31;40mERR!e[0me[35me[0m A complete log of this run can be found in: |
2020-09-17 02:34:15 | stdout | e[0m |
2020-09-17 02:34:14 | stdout | e[0me[37;40mnpme[0m e[0me[31;40mERR!e[0me[35me[0m This is probably not a problem with npm. There is likely additional logging output above. |
2020-09-17 02:34:14 | stdout | e[0me[37;40mnpme[0m e[0me[31;40mERR!e[0me[35me[0m Failed at the zigbee2mqtt@1.14.4 start script. |
2020-09-17 02:34:14 | stdout | e[0me[37;40mnpme[0m e[0me[31;40mERR!e[0me[35me[0m |
2020-09-17 02:34:14 | stdout | e[0me[37;40mnpme[0m e[0me[31;40mERR!e[0me[35me[0m Exit status 1 |
2020-09-17 02:34:14 | stdout | e[0me[37;40mnpme[0m e[0me[31;40mERR!e[0me[35me[0m zigbee2mqtt@1.14.4 start: `node index.js` |
2020-09-17 02:34:14 | stdout | e[0me[37;40mnpme[0m e[0me[31;40mERR!e[0m e[0me[35merrnoe[0m 1 |
2020-09-17 02:34:14 | stdout | e[37;40mnpme[0m e[0me[31;40mERR!e[0m e[0me[35mcodee[0m ELIFECYCLE |
2020-09-17 02:34:14 | stdout | |
2020-09-17 02:34:14 | stdout | |
2020-09-17 02:34:14 | stdout | !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! |
2020-09-17 02:34:14 | stdout | |
2020-09-17 02:34:14 | stdout | If you don't know how to solve this, read https://www.zigbee2mqtt.io/information/configuration.html |
2020-09-17 02:34:14 | stdout | |
2020-09-17 02:34:14 | stdout | - Your YAML file: '/app/data/configuration.yaml' is invalid (use https://jsonformatter.org/yaml-validator to find and fix the issue) |
2020-09-17 02:34:14 | stdout | Refusing to start because configuration is not valid, found the following errors: |
2020-09-17 02:34:14 | stdout | |
2020-09-17 02:34:14 | stdout | READ THIS CAREFULLY |
2020-09-17 02:34:14 | stdout | !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! |
2020-09-17 02:34:14 | stdout | |
2020-09-17 02:34:14 | stdout | |
2020-09-17 02:34:14 | stdout | |
2020-09-17 02:34:14 | stdout | > node index.js |
2020-09-17 02:34:14 | stdout | > zigbee2mqtt@1.14.4 start /app |
2020-09-17 02:34:14 | stdout | |
2020-09-17 02:34:12 | stdout | Using '/app/data' as data directory |
2020-09-16 02:03:34 | stdout | e[0m |
2020-09-16 02:03:34 | stdout | e[0me[37;40mnpme[0m e[0me[31;40mERR!e[0me[35me[0m /root/.npm/_logs/2020-09-16T02_03_34_071Z-debug.log |
2020-09-16 02:03:34 | stdout | e[37;40mnpme[0m e[0me[31;40mERR!e[0me[35me[0m A complete log of this run can be found in: |
2020-09-16 02:03:34 | stdout | e[0m |
2020-09-16 02:03:34 | stdout | e[0me[37;40mnpme[0m e[0me[31;40mERR!e[0me[35me[0m This is probably not a problem with npm. There is likely additional logging output above. |
2020-09-16 02:03:34 | stdout | e[0me[37;40mnpme[0m e[0me[31;40mERR!e[0me[35me[0m Failed at the zigbee2mqtt@1.14.4 start script. |
2020-09-16 02:03:34 | stdout | e[0me[37;40mnpme[0m e[0me[31;40mERR!e[0me[35me[0m |
2020-09-16 02:03:34 | stdout | e[0me[37;40mnpme[0m e[0me[31;40mERR!e[0me[35me[0m Exit status 1 |
2020-09-16 02:03:34 | stdout | e[0me[37;40mnpme[0m e[0me[31;40mERR!e[0me[35me[0m zigbee2mqtt@1.14.4 start: `node index.js` |
2020-09-16 02:03:34 | stdout | e[0me[37;40mnpme[0m e[0me[31;40mERR!e[0m e[0me[35merrnoe[0m 1 |
2020-09-16 02:03:34 | stdout | e[37;40mnpme[0m e[0me[31;40mERR!e[0m e[0me[35mcodee[0m ELIFECYCLE |
2020-09-16 02:03:34 | stdout | |
2020-09-16 02:03:34 | stdout | |
2020-09-16 02:03:34 | stdout | !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! |
2020-09-16 02:03:34 | stdout | |
2020-09-16 02:03:34 | stdout | If you don't know how to solve this, read https://www.zigbee2mqtt.io/information/configuration.html |
2020-09-16 02:03:34 | stdout | |
2020-09-16 02:03:34 | stdout | - Your YAML file: '/app/data/configuration.yaml' is invalid (use https://jsonformatter.org/yaml-validator to find and fix the issue) |
2020-09-16 02:03:34 | stdout | Refusing to start because configuration is not valid, found the following errors: |
2020-09-16 02:03:34 | stdout | |
2020-09-16 02:03:34 | stdout | READ THIS CAREFULLY |
2020-09-16 02:03:34 | stdout | !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! |
2020-09-16 02:03:34 | stdout | |
2020-09-16 02:03:34 | stdout | |
2020-09-16 02:03:33 | stdout | |
2020-09-16 02:03:33 | stdout | > node index.js |
2020-09-16 02:03:33 | stdout | > zigbee2mqtt@1.14.4 start /app |
2020-09-16 02:03:33 | stdout | |
2020-09-16 02:03:32 | stdout | Using '/app/data' as data directory |
2020-09-16 01:50:17 | stdout | e[0m |
2020-09-16 01:50:17 | stdout | e[0me[37;40mnpme[0m e[0me[31;40mERR!e[0me[35me[0m /root/.npm/_logs/2020-09-16T01_50_17_136Z-debug.log |
2020-09-16 01:50:17 | stdout | e[37;40mnpme[0m e[0me[31;40mERR!e[0me[35me[0m A complete log of this run can be found in: |
2020-09-16 01:50:17 | stdout | e[0m |
2020-09-16 01:50:17 | stdout | e[0me[37;40mnpme[0m e[0me[31;40mERR!e[0me[35me[0m This is probably not a problem with npm. There is likely additional logging output above. |
2020-09-16 01:50:17 | stdout | e[0me[37;40mnpme[0m e[0me[31;40mERR!e[0me[35me[0m Failed at the zigbee2mqtt@1.14.4 start script. |
2020-09-16 01:50:17 | stdout | e[0me[37;40mnpme[0m e[0me[31;40mERR!e[0me[35me[0m |
2020-09-16 01:50:17 | stdout | e[0me[37;40mnpme[0m e[0me[31;40mERR!e[0me[35me[0m Exit status 1 |
2020-09-16 01:50:17 | stdout | e[0me[37;40mnpme[0m e[0me[31;40mERR!e[0me[35me[0m zigbee2mqtt@1.14.4 start: `node index.js` |
2020-09-16 01:50:17 | stdout | e[0me[37;40mnpme[0m e[0me[31;40mERR!e[0m e[0me[35merrnoe[0m 1 |
2020-09-16 01:50:17 | stdout | e[37;40mnpme[0m e[0me[31;40mERR!e[0m e[0me[35mcodee[0m ELIFECYCLE |
2020-09-16 01:50:17 | stdout | |
2020-09-16 01:50:17 | stdout | |
2020-09-16 01:50:17 | stdout | !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! |
2020-09-16 01:50:17 | stdout | |
2020-09-16 01:50:17 | stdout | If you don't know how to solve this, read https://www.zigbee2mqtt.io/information/configuration.html |
2020-09-16 01:50:17 | stdout | |
2020-09-16 01:50:17 | stdout | - Your YAML file: '/app/data/configuration.yaml' is invalid (use https://jsonformatter.org/yaml-validator to find and fix the issue) |
2020-09-16 01:50:17 | stdout | Refusing to start because configuration is not valid, found the following errors: |
2020-09-16 01:50:17 | stdout | |
2020-09-16 01:50:17 | stdout | READ THIS CAREFULLY |
2020-09-16 01:50:17 | stdout | !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! |
2020-09-16 01:50:17 | stdout | |
2020-09-16 01:50:17 | stdout | |
2020-09-16 01:50:17 | stdout | |
2020-09-16 01:50:17 | stdout | > node index.js |
2020-09-16 01:50:17 | stdout | > zigbee2mqtt@1.14.4 start /app |
2020-09-16 01:50:17 | stdout | |
2020-09-16 01:50:16 | stdout | Using '/app/data' as data directory |
2020-09-16 01:43:30 | stdout | e[0m |
2020-09-16 01:43:30 | stdout | e[0me[37;40mnpme[0m e[0me[31;40mERR!e[0me[35me[0m /root/.npm/_logs/2020-09-16T01_43_30_337Z-debug.log |
2020-09-16 01:43:30 | stdout | e[37;40mnpme[0m e[0me[31;40mERR!e[0me[35me[0m A complete log of this run can be found in: |
2020-09-16 01:43:30 | stdout | e[0m |
2020-09-16 01:43:30 | stdout | e[0me[37;40mnpme[0m e[0me[31;40mERR!e[0me[35me[0m This is probably not a problem with npm. There is likely additional logging output above. |
2020-09-16 01:43:30 | stdout | e[0me[37;40mnpme[0m e[0me[31;40mERR!e[0me[35me[0m Failed at the zigbee2mqtt@1.14.4 start script. |
2020-09-16 01:43:30 | stdout | e[0me[37;40mnpme[0m e[0me[31;40mERR!e[0me[35me[0m |
2020-09-16 01:43:30 | stdout | e[0me[37;40mnpme[0m e[0me[31;40mERR!e[0me[35me[0m Exit status 1 |
2020-09-16 01:43:30 | stdout | e[0me[37;40mnpme[0m e[0me[31;40mERR!e[0me[35me[0m zigbee2mqtt@1.14.4 start: `node index.js` |
2020-09-16 01:43:30 | stdout | e[0me[37;40mnpme[0m e[0me[31;40mERR!e[0m e[0me[35merrnoe[0m 1 |
2020-09-16 01:43:30 | stdout | e[37;40mnpme[0m e[0me[31;40mERR!e[0m e[0me[35mcodee[0m ELIFECYCLE |
2020-09-16 01:43:30 | stdout | at /app/node_modules/zigbee-herdsman/node_modules/@serialport/stream/lib/index.js:242:12 |
2020-09-16 01:43:30 | stdout | at SerialPort._error (/app/node_modules/zigbee-herdsman/node_modules/@serialport/stream/lib/index.js:198:14) |
2020-09-16 01:43:30 | stdout | at SerialPort.<anonymous> (/app/node_modules/zigbee-herdsman/dist/adapter/z-stack/znp/znp.js:134:49) |
2020-09-16 01:43:30 | stdout | at __awaiter (/app/node_modules/zigbee-herdsman/dist/adapter/z-stack/znp/znp.js:23:12) |
2020-09-16 01:43:30 | stdout | at new Promise (<anonymous>) |
2020-09-16 01:43:30 | stdout | at /app/node_modules/zigbee-herdsman/dist/adapter/z-stack/znp/znp.js:27:71 |
2020-09-16 01:43:30 | stdout | at Generator.next (<anonymous>) |
2020-09-16 01:43:30 | stdout | at Znp.<anonymous> (/app/node_modules/zigbee-herdsman/dist/adapter/z-stack/znp/znp.js:136:32) |
2020-09-16 01:43:30 | stdout | e[31mZigbee2MQTT:errore[39m 2020-09-16 09:43:30: Error: Error while opening serialport 'Error: Error: No such file or directory, cannot open /dev/ttyACM0' |
2020-09-16 01:43:30 | stdout | e[31mZigbee2MQTT:errore[39m 2020-09-16 09:43:30: Exiting... |
2020-09-16 01:43:30 | stdout | e[31mZigbee2MQTT:errore[39m 2020-09-16 09:43:30: Failed to start zigbee |
2020-09-16 01:43:30 | stdout | e[31mZigbee2MQTT:errore[39m 2020-09-16 09:43:30: Error while starting zigbee-herdsman |
2020-09-16 01:43:29 | stdout | e[32mZigbee2MQTT:info e[39m 2020-09-16 09:43:29: Starting zigbee-herdsman... |
2020-09-16 01:43:29 | stdout | e[32mZigbee2MQTT:info e[39m 2020-09-16 09:43:29: Starting Zigbee2MQTT version 1.14.4 (commit #654817a) |
2020-09-16 01:43:28 | stdout | e[32mZigbee2MQTT:info e[39m 2020-09-16 09:43:28: Logging to console and directory: '/app/data/log/2020-09-16.09-43-28' filename: log.txt |
2020-09-16 01:43:27 | stdout | |
2020-09-16 01:43:27 | stdout | > node index.js |
2020-09-16 01:43:27 | stdout | > zigbee2mqtt@1.14.4 start /app |
2020-09-16 01:43:27 | stdout | |
2020-09-16 01:43:22 | stdout | Using '/app/data' as data directory |