Page 1 of 1
Zigbee2mqtt failed to start
Posted: Saturday 15 December 2018 14:35
by fusionsound
Hello,
I've bought a pre installed sniffer C2531 USB for my Domoticz. I tried to install node( and NPM) but the node can't start. It says this:
Zigbee2mqtt requires node version >=8.11 10, you are running v8. 14.0!
I've searched the internet for this problem but can't find anything. Also tried to downgrade the node but no other versions are found.
Hope someone can help me out.
Kind regards,
Laurens
Re: Zigbee2mqtt failed to start
Posted: Saturday 15 December 2018 16:28
by EddyG
Re: Zigbee2mqtt failed to start
Posted: Sunday 16 December 2018 13:55
by elRedeo
This is the standardmessage and could be ignored.
Please paste full log....
Re: Zigbee2mqtt failed to start
Posted: Monday 17 December 2018 17:19
by fusionsound
I did a fresh install bacause I got a lot of errors. But now I got this problem. Somebody has an idea?
>
[email protected] start /opt/zigbee2mqtt
> node index.js
zigbee2mqtt:info 2018-12-17 16:15:08 Logging to directory: '/opt/zigbee2mqtt/data/log/2018-12-17.16-15-08'
zigbee2mqtt:info 2018-12-17 16:15:09 Starting zigbee2mqtt version 1.0.0 (commit #91bbb0d)
zigbee2mqtt:info 2018-12-17 16:15:09 Starting zigbee-shepherd
zigbee2mqtt:info 2018-12-17 16:15:09 Error while starting zigbee-shepherd, attemping to fix... (takes 60 seconds)
zigbee2mqtt:info 2018-12-17 16:16:09 Starting zigbee-shepherd
zigbee2mqtt:error 2018-12-17 16:16:09 Error while starting zigbee-shepherd!
zigbee2mqtt:error 2018-12-17 16:16:09 Press the reset button on the stick (the one closest to the USB) and start again
zigbee2mqtt:error 2018-12-17 16:16:09 Failed to start
{"message":"Error Resource temporarily unavailable Cannot lock port","stack":"Error: Error Resource temporarily unavailable Cannot lock port"}
^Z
[3]+ Stopped
Re: Zigbee2mqtt failed to start
Posted: Monday 17 December 2018 19:50
by elRedeo
As you see in the log, the software has the problem to open the port where the sniffer is connected.
Did you manage the right port in the configuration file ?
Has your user right to access this port?
You should read again :
https://koenkk.github.io/zigbee2mqtt/ge ... 2mqtt.html
Re: Zigbee2mqtt failed to start
Posted: Monday 17 December 2018 20:17
by fusionsound
I tried it both ways: by id and the "normal" way. I'm logged in as pi user.( Also tried is as root )
Re: Zigbee2mqtt failed to start
Posted: Wednesday 19 December 2018 18:30
by elRedeo
show us your configuratin.yaml
Re: Zigbee2mqtt failed to start
Posted: Monday 24 December 2018 19:08
by fusionsound
# Home Assistant integration (MQTT discovery)
homeassistant: false
# allow new devices to join
permit_join: true
# MQTT settings
mqtt:
# MQTT base topic for zigbee2mqtt MQTT messages
base_topic: zigbee2mqtt
# MQTT server URL
server: 'mqtt://192.168.2.11:8080'
# MQTT server authentication, uncomment if required:
# user: my_user
# password: my_password
# Serial settings
serial:
# Location of CC2531 USB sniffer
port: /dev/ttyACM0
Re: Zigbee2mqtt failed to start
Posted: Monday 24 December 2018 19:19
by fusionsound
Now I'm getting some completely new errors when I try to start NPM
/usr/lib/node_modules/npm/bin/npm-cli.js:2
;(function ()(; // wrapper in casE we'se in module_context mode
^
SyntaxError: Unexpected token (
at createScript (vm.js:80:10)
at Object.runInThisContext (vm.js:139:10)
at Module._compile (module.js:617:28)
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 Function.Module.runMain (module.js:694:10)
at startup (bootstrap_node.js:204:16)
at bootstrap_node.js:625:3
Re: Zigbee2mqtt failed to start
Posted: Monday 21 January 2019 22:44
by unclekoen
fusionsound wrote: ↑Monday 24 December 2018 19:08
# Serial settings
serial:
# Location of CC2531 USB sniffer
port: /dev/ttyACM0
Had this problem also. Do you know for sure if your sniffer is on port ttyACM0???
Run:
I also have a RFLink running on USB, which was using ttyACM0 and the CC2531 on ttyACM1.
Re: Zigbee2mqtt failed to start
Posted: Saturday 17 October 2020 15:28
by JuanUil
Hi There,
I have the same problem
Code: Select all
Zigbee2MQTT:info 2020-10-16 15:57:44: Logging to console and directory: ‘/opt/zigbee2mqtt/data/log/2020-10-16.15-57-44’ filename: log.txt
Zigbee2MQTT:info 2020-10-16 15:57:45: Starting Zigbee2MQTT version 1.15.0 (commit #1bccc5d)
Zigbee2MQTT:info 2020-10-16 15:57:45: Starting zigbee-herdsman…
Zigbee2MQTT:error 2020-10-16 15:57:45: Error while starting zigbee-herdsman
Zigbee2MQTT:error 2020-10-16 15:57:45: Failed to start zigbee
Zigbee2MQTT:error 2020-10-16 15:57:45: Exiting…
Zigbee2MQTT:error 2020-10-16 15:57:45: Error: Error while opening serialport ‘Error: Error Resource temporarily unavailable Cannot lock port’
at Znp. (/opt/zigbee2mqtt/node_modules/zigbee-herdsman/dist/adapter/z-stack/znp/znp.js:136:32)
at Generator.next ()
at /opt/zigbee2mqtt/node_modules/zigbee-herdsman/dist/adapter/z-stack/znp/znp.js:27:71
at new Promise ()
at __awaiter (/opt/zigbee2mqtt/node_modules/zigbee-herdsman/dist/adapter/z-stack/znp/znp.js:23:12)
at SerialPort. (/opt/zigbee2mqtt/node_modules/zigbee-herdsman/dist/adapter/z-stack/znp/znp.js:134:49)
at SerialPort._error (/opt/zigbee2mqtt/node_modules/zigbee-herdsman/node_modules/@serialport/stream/lib/index.js:198:14)
at /opt/zigbee2mqtt/node_modules/zigbee-herdsman/node_modules/@serialport/stream/lib/index.js:242:12
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! [email protected] start: node index.js
npm 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 logging output above.
npm ERR! A complete log of this run can be found in:
npm ERR! /home/pi/.npm/_logs/2020-10-16T13_57_45_835Z-debug.log
so it seems the usb is not recognized.
my configuration yaml:
Code: Select all
homeassistant: false
permit_join: true
mqtt:
base_topic: zigbee2mqtt
server: 'mqtt://192.168.2.16:8080'
serial:
port: /dev/ttyACM0
advanced:
network_key:
- 45
- 102
- 120
- 132
- 7
- 230
- 82
- 195
- 243
- 187
- 18
- 202
- 56
- 6
- 237
- 183
and this is in the complete logfile:
Code: Select all
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]
6 info lifecycle [email protected]~start: [email protected]
7 verbose lifecycle [email protected]~start: unsafe-perm in lifecycle true
8 verbose lifecycle [email protected]~start: PATH: /usr/lib/node_modules/npm/node_modules/npm-lifecycle/node-gyp-bin:/opt/zigbee2mqtt/node_modules/.bin:/u$
9 verbose lifecycle [email protected]~start: CWD: /opt/zigbee2mqtt
10 silly lifecycle [email protected]~start: Args: [ '-c', 'node index.js' ]
11 silly lifecycle [email protected]~start: Returned: code: 1 signal: null
12 info lifecycle [email protected]~start: Failed to exec start script
13 verbose stack Error: [email protected] start: `node index.js`
13 verbose stack Exit status 1
13 verbose stack at EventEmitter.<anonymous> (/usr/lib/node_modules/npm/node_modules/npm-lifecycle/index.js:332:16)
13 verbose stack at EventEmitter.emit (events.js:314:20)
13 verbose stack at ChildProcess.<anonymous> (/usr/lib/node_modules/npm/node_modules/npm-lifecycle/lib/spawn.js:55:14)
13 verbose stack at ChildProcess.emit (events.js:314:20)
13 verbose stack at maybeClose (internal/child_process.js:1021:16)
13 verbose stack at Process.ChildProcess._handle.onexit (internal/child_process.js:286:5)
14 verbose pkgid [email protected]
15 verbose cwd /opt/zigbee2mqtt
16 verbose Linux 5.4.51-v7l+
17 verbose argv "/usr/bin/node" "/usr/bin/npm" "start"
18 verbose node v12.19.0
19 verbose npm v6.14.8
20 error code ELIFECYCLE
21 error errno 1
22 error [email protected] start: `node index.js`
22 error Exit status 1
23 error Failed at the [email protected] start script.
23 error This is probably not a problem with npm. There is likely additional logging output above.
24 verbose exit [ 1, true ]
any help is greatly welcome
Jan
Re: Zigbee2mqtt failed to start
Posted: Sunday 18 October 2020 17:19
by JuanUil
nobody?
Re: Zigbee2mqtt failed to start
Posted: Wednesday 21 October 2020 19:45
by JuanUil
there was not so much support but what I want you to know is that after a fresh install of Buster evrything is working allright.
Hope I have helped somebody with the same problems.
Also hope that more people give help on this forum to make Domoticz even better as it is!!!
One thing to reach this goal is to give help when asked
Re: Zigbee2mqtt failed to start
Posted: Thursday 29 October 2020 13:36
by PeterFleur
For future reference. I think unclekoen had the right answer.
The USB port is probably something else then acm0
Peter