zigbee2mqtt start error #584
Comments
|
Can you post the contents of your |
|
@Koenkk pi@raspberrypi:~ $ nano /opt/zigbee2mqtt/data/configuration.yaml Home Assistant integration (MQTT discovery)....homeassistant: false allow new devices to joinpermit_join: true MQTT settingsmqtt: MQTT base topic for zigbee2mqtt MQTT messagesbase_topic: zigbee2mqtt MQTT server URLserver: 'mqtt://192.168.2.105'MQTT server authentication, uncomment if required:user: xxxxxxxxxxx Serial settingsserial: Location of FTDI/ CC2530advanced: |
|
@Koenkk sry for the formation... |
|
@Koenkk Ich denke man braucht sich nicht mit der .yaml weiter beschäftigen, wenn dieser Fehler nicht behoben ist. Ich möchte einen cc2530 als coordinator verwenden. und nach folgender Anleitung geflashed: anschliessend habe ich die installation nochmals durchgeführt https://github.com/Koenkk/zigbee2mqtt/wiki/Running-the-bridge pi@raspberrypi:/opt/zigbee2mqtt $ sudo curl -sL https://deb.nodesource.com/setup_8.x | sudo -E bash - Installing the NodeSource Node.js 8.x LTS Carbon repo...Populating apt-get cache...
Confirming "stretch" is supported...
Adding the NodeSource signing key to your keyring...
Creating apt sources list file for the NodeSource Node.js 8.x LTS Carbon repo...
Running
|
|
These are audit reports which you can ignore. |
|
Hi @Koenkk , do think it is really a Report that i can ignore? Thanks for your help! Using username "pi". |
|
Can you perform a fresh install of zigbee2mqtt? |
|
@Koenkk you think that my Installation of zigbee2mqtt ins´t right? Using username "pi". The programs included with the Debian GNU/Linux system are free software; Debian GNU/Linux comes with ABSOLUTELY NO WARRANTY, to the extent Installing the NodeSource Node.js 8.x LTS Carbon repo...Populating apt-get cache...
Confirming "stretch" is supported...
Adding the NodeSource signing key to your keyring...
Creating apt sources list file for the NodeSource Node.js 8.x LTS Carbon repo...
Running
|
|
Your |
|
Hi @Koenkk thanks for your support! |
|
Use the following yaml: https://github.com/Koenkk/zigbee2mqtt/blob/master/data/configuration.yaml |
|
Hi @Koenkk, thanks for your link. I copy paste only your yaml, but i think i cant use it in this style... Because,
With the change of your Code i get this error... Error log Looks like... So works the Code only with CC2531 ? |
|
You have an error in your YAML format: |
|
for my Background which yaml documentation do you prefer? I´m very thankful for every help i can get! Is that a zigbee-shepherd, a usb or .... Problem? |
|
No yaml error, so that ok now. The location of your CC device is not ok (port What is the output of |
|
|
port: /dev/serial/by-id/usb-Silicon_Labs_CP2102_USB_to_UART_Bridge_Controll$
See the $ at the end? That's not the complete name/path.
|
|
@Koenkk @sehraf i don´t know why but the port is wrong... I change the yaml to the right seen in ls /dev. Error again. |
|
YAML require a very strict format. Change: To: ^ NOTE: only two whitespaces in front of user and everywhere else!
Check your indentation everywhere! |
|
Hello @pixeldoc2000 thanks for your answer and help. @Koenkk @sehraf Now with this modifications i run into the following error. |
|
zigbee-shepherd fails to communicate with the CC2530, probably something is not connected right. I would suggest starting with a CC2531 (which is easier to use). |
|
Hi @Koenkk i´m little bit busi at the moment... |
|
There are no clear instructions yet, but you can find some here: #465 |
|
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
Hi community,
can someone tell me what this error is all about?
Is this error known and resolved?
Last login: Sat Nov 10 23:56:48 2018 from 192.168.2.102
pi@raspberrypi:~ $ cd /opt/zigbee2mqtt
pi@raspberrypi:/opt/zigbee2mqtt $ npm start
/opt/zigbee2mqtt/lib/util/logger.js:10
const level = settings.get().advanced.log_level;
^
TypeError: Cannot read property 'log_level' of null
at Object. (/opt/zigbee2mqtt/lib/util/logger.js:10:38)
at Module._compile (module.js:653:30)
at Object.Module._extensions..js (module.js:664:10)
at Module.load (module.js:566:32)
at tryModuleLoad (module.js:506:12)
at Function.Module._load (module.js:498:3)
at Module.require (module.js:597:17)
at require (internal/module.js:11:18)
at Object. (/opt/zigbee2mqtt/lib/mqtt.js:2:16)
at Module._compile (module.js:653:30)
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! [email protected] start:
node index.jsnpm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the [email protected] start script.
npm ERR! This is probably not a problem with npm. There is likely additional log ging output above.
npm ERR! A complete log of this run can be found in:
npm ERR! /home/pi/.npm/_logs/2018-11-10T23_29_24_523Z-debug.log
pi@raspberrypi:/opt/zigbee2mqtt $
pi@raspberrypi:/opt/zigbee2mqtt $ nano /home/pi/.npm/_logs/2018-11-10T23_29_24_523Z-debug.log
GNU nano 2.7.4 Datei: /home/pi/.npm/_logs/2018-11-10T23_29_24_523Z-debug.log
0 info it worked if it ends with ok
1 verbose cli [ '/usr/bin/node', '/usr/bin/npm', 'start' ]
2 info using [email protected]
3 info using [email protected]
4 verbose run-script [ 'prestart', 'start', 'poststart' ]
5 info lifecycle [email protected]
prestart: [email protected]start: [email protected]6 info lifecycle [email protected]
7 verbose lifecycle [email protected]
start: unsafe-perm in lifecycle truestart: PATH: /usr/lib/node_modules/npm/node_modules/npm-lifecycle/node-gyp-bin:/opt/zigbee2mqtt/node_modules/.bin:/$8 verbose lifecycle [email protected]
9 verbose lifecycle [email protected]
start: CWD: /opt/zigbee2mqttstart: Args: [ '-c', 'node index.js' ]10 silly lifecycle [email protected]
11 silly lifecycle [email protected]
start: Returned: code: 1 signal: nullstart: Failed to exec start script12 info lifecycle [email protected]
13 verbose stack Error: [email protected] start:
node index.js13 verbose stack Exit status 1
13 verbose stack at EventEmitter. (/usr/lib/node_modules/npm/node_modules/npm-lifecycle/index.js:301:16)
13 verbose stack at emitTwo (events.js:126:13)
13 verbose stack at EventEmitter.emit (events.js:214:7)
13 verbose stack at ChildProcess. (/usr/lib/node_modules/npm/node_modules/npm-lifecycle/lib/spawn.js:55:14)
13 verbose stack at emitTwo (events.js:126:13)
13 verbose stack at ChildProcess.emit (events.js:214:7)
13 verbose stack at maybeClose (internal/child_process.js:915:16)
13 verbose stack at Process.ChildProcess._handle.onexit (internal/child_process.js:209:5)
14 verbose pkgid [email protected]
15 verbose cwd /opt/zigbee2mqtt
16 verbose Linux 4.14.71-v7+
17 verbose argv "/usr/bin/node" "/usr/bin/npm" "start"
18 verbose node v8.12.0
19 verbose npm v6.4.1
20 error code ELIFECYCLE
21 error errno 1
22 error [email protected] start:
node index.js22 error Exit status 1
The text was updated successfully, but these errors were encountered: