Zigbee2MQTT Start Error: No path provided and failed to auto detect pat #14622
Labels
problem
Something isn't working
Comments
|
On my raspi, no /dev/ttyAMA0 is available. Also, no /dev/serial/by-id/* is working, as there is no "by-id". The only serial device, besides /dev/ttyS0 is /dev/ttyAMA0. So, I added /dev/ttyAMA0 as port in the yaml config file. |
|
|
so, as you can see, I did some research, update and another npm ci... Need some hint in which direction to go further to analyze the root case... |
|
OK, found solution: deConz service was still up and running. Now working fine with RaspBee II. |
|
I have also an RaspBee II and using the snoff zigbee 3.0 USB Dongle Plus and got this error, ` |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
What happened?
Raspi bullseye
RaspBee II
udev is installed
/opt/zigbee2mqtt/data/configuration.yaml
homeassistant: false
permit_join: true
mqtt:
base_topic: zigbee2mqtt
server: mqtt://192.168.178.78
user:
password:
serial:
adapter: deconz
frontend: false
advanced:
network_key:
console output:
admin@node-000:/opt/zigbee2mqtt $ npm start
Zigbee2MQTT:info 2022-10-23 23:21:16: Logging to console and directory: '/opt/zigbee2mqtt/data/log/2022-10-23.23-21-16' filename: log.txt
Zigbee2MQTT:info 2022-10-23 23:21:16: Starting Zigbee2MQTT version 1.28.0 (commit #03ba647)
Zigbee2MQTT:info 2022-10-23 23:21:16: Starting zigbee-herdsman (0.14.62)
Zigbee2MQTT:error 2022-10-23 23:21:16: Error while starting zigbee-herdsman
Zigbee2MQTT:error 2022-10-23 23:21:16: Failed to start zigbee
Zigbee2MQTT:error 2022-10-23 23:21:16: Check https://www.zigbee2mqtt.io/guide/installation/20_zigbee2mqtt-fails-to-start.html for possible solutions
Zigbee2MQTT:error 2022-10-23 23:21:16: Exiting...
Zigbee2MQTT:error 2022-10-23 23:21:17: Error: No path provided and failed to auto detect path
at Function.create (/opt/zigbee2mqtt/node_modules/zigbee-herdsman/src/adapter/adapter.ts:81:23)
at processTicksAndRejections (internal/process/task_queues.js:95:5)
at Controller.start (/opt/zigbee2mqtt/node_modules/zigbee-herdsman/src/controller/controller.ts:129:24)
at Zigbee.start (/opt/zigbee2mqtt/lib/zigbee.ts:58:27)
at Controller.start (/opt/zigbee2mqtt/lib/controller.ts:101:27)
at start (/opt/zigbee2mqtt/index.js:109:5)
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! zigbee2mqtt@1.28.0 start:
node index.jsnpm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the zigbee2mqtt@1.28.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! /home/admin/.npm/_logs/2022-10-23T21_21_17_081Z-debug.log
What did you expect to happen?
just starting ...
How to reproduce it (minimal and precise)
No response
Zigbee2MQTT version
1.28.0 (commit #03ba647)
Adapter firmware version
latest
Adapter
ConBee 2
Debug log
dmin@node-000:/opt/zigbee2mqtt $ EBUG=zigbee-herdsman* npm start
internal/modules/cjs/loader.js:905
throw err;
^
Error: Cannot find module 'semver'
Require stack:
at Function.Module._resolveFilename (internal/modules/cjs/loader.js:902:15)
at Function.Module._load (internal/modules/cjs/loader.js:746:27)
at Module.require (internal/modules/cjs/loader.js:974:19)
at require (internal/modules/cjs/helpers.js:101:18)
at Object. (/opt/zigbee2mqtt/index.js:3:16)
at Module._compile (internal/modules/cjs/loader.js:1085:14)
at Object.Module._extensions..js (internal/modules/cjs/loader.js:1114:10)
at Module.load (internal/modules/cjs/loader.js:950:32)
at Function.Module._load (internal/modules/cjs/loader.js:790:12)
at Function.executeUserEntryPoint [as runMain] (internal/modules/run_main.js:75:12) {
code: 'MODULE_NOT_FOUND',
requireStack: [ '/opt/zigbee2mqtt/index.js' ]
}
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! zigbee2mqtt@1.28.0 start:
node index.jsnpm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the zigbee2mqtt@1.28.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! /home/admin/.npm/_logs/2022-10-23T21_37_12_999Z-debug.log
The text was updated successfully, but these errors were encountered: