Zigbee herdsman adapter failed to validate path error spawn udevadm enoent

[Bug]: Error: spawn udevadm ENOENT #420

Description of the issue

I dont know if is my bad config or something else.

Addon version

Platform

Home Assistant 2022.11.4
Supervisor 2022.11.2
Operating System 9.3
Frontend 20221108.0 — latest

Logs of the issue (if applicable)

The text was updated successfully, but these errors were encountered:

I’ve gotting the same error.

Setup:

• Raspberry Pi 3
• Sonoff Zigbee 3.0 USB Dongle Plus

Home Assistant:
Home Assistant 2022.11.4
Supervisor 2022.11.2
Operating System 9.3
Frontend 20221108.0 — latest

dmesg:

Complete error with debug:

Solved

Excuse me.
The integration ‘Sonoff Zigbee 3.0 USB Dongle Plus’ was causing the problem.
What I had read everywhere is to remove the ‘Zigbee Home Automation’ integration. I did’t realize it was het integration from the Sonoff stick. After removing the integration, Z2M started perfectly fine.

I’ve got the same problem.

Also with the Sonoff Zigbee 3.0 USB Dongle Plus.
Generic x86/64

Home Assistant
Home Assistant 2022.11.5
Supervisor 2022.11.2
Operating System 9.3
Frontend 20221108.0 — latest

Config
Exact same error will apear if I use ‘/dev/ttyUSB0’ as serial: port:

Complete error with debug

This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 7 days

Hello everybody,
i’ve got the same problem.
I’m running HomeAssistant in a VirtualBox VM and zigbee2MQTT doesn’t start.
Error: spawn udevadm ENOENT

The Sonoff USB Stick ist installed correctly under the devices Adress port: /dev/ttyUSB0
ZHA is not running.

Home Assistant 2022.12.9
Supervisor 2022-12.1
OS 9.4
Frontend 20221213.1-latest

Zigbee2MQTT version 1.29.0-1

i’ve got the same problem. I’m running HomeAssistant in a VirtualBox VM and zigbee2MQTT doesn’t start. Error: spawn udevadm ENOENT

The Sonoff USB Stick ist installed correctly under the devices Adress port: /dev/ttyUSB0 ZHA is not running.

I have the same issue. The log shows following:

Источник

Error while starting zigbee-herdsman #2928

Every raspberry startup zigbe2mqtt process don’t startup, zigbe2mqtt process need three attempts fort startup, in the third attemp starts correctly. after raspberry reboot again the same problem appears I paste the info from logs:

zigbe2mqtt log:

Log from .npm, folder

Log from opt—>zigbe—>data

i«`
nfo 2020-02-10 14:54:31: Logging to console and directory: ‘/opt/zigbee2mqtt/data/log/2020-02-10.14-54-31’ filename: log.txt
info 2020-02-10 14:54:31: Starting zigbee2mqtt version 1.10.0-dev (commit #13b996e)
info 2020-02-10 14:54:31: Starting zigbee-herdsman.
error 2020-02-10 14:55:21: Error while starting zigbee-herdsman

The text was updated successfully, but these errors were encountered:

Got the same issue, only mine doesn’t start at all. Happend after upgrading to 1.10.0

Same here, also running zigbee2mqtt version: version 1.10.0 and happens at random times when it is running, need to stop zigbee2mqtt and unplug the usb and plug in it and start zigbee2mqtt to get it to work again.

Already tried the stuff in the FAQ?

I apologize for reopening a repeated issue, I was looking before opening it but I didn’t find it. You were right, with the tests I was doing I put the zigbe2mqtt dongle in another usb port. Thank you very much for all the support you are giving to everyone with problems that are coming out, it is very kind. Best regards

For anyone coming here with this issue when running the IOTstack zigbee2mqtt docker image, change the docker-compose.yml to use a different port. By default the port mapping is — /dev/ttyAMA0:/dev/ttyACM0 but changing it to — /dev/ttyACM0:/dev/ttyACM0 solved this issue for me.

as described here

Sorry to react on a repeated issue, but I tried everything discussed before.
Keep getting error with starting zigbee-herdsman.

Started with a CC2531 USB stick and initially all ok. After updating zigbee2mqtt the issue started with the zigbee-herdman not starting up.

Since I also had an issue with the limited number of devices and the range of the CC2531 USB stick, I bought a Texas Instruments CC26X2R1. Also in the hope this would solve the issue with the zigbee-herdsman.

At first connection the new adapter worked, but after trying to connect the third device (xiaomi plug) it stopped working.

Trying to restart the zigbee2mqtt gave again the error with the zigbee-herdsman.

This is what I get when trying to start:

pi@DOMOTICZ:/opt/zigbee2mqtt $ DEBUG=zigbee-herdsman* npm start

zigbee2mqtt@1.12.0 start /opt/zigbee2mqtt
node index.js

zigbee2mqtt:info 2020-04-08 00:49:32: Logging to console and directory: ‘/opt/zigbee2mqtt/data/log/2020-04-08.00-49-32’ filename: log.txt
zigbee2mqtt:debug 2020-04-08 00:49:32: Loaded state from file /opt/zigbee2mqtt/data/state.json
zigbee2mqtt:info 2020-04-08 00:49:32: Starting zigbee2mqtt version 1.12.0 (commit #840b9d9)
zigbee2mqtt:info 2020-04-08 00:49:32: Starting zigbee-herdsman.
zigbee2mqtt:debug 2020-04-08 00:49:32: Using zigbee-herdsman with settings: ‘<«network»:<«panID»:6754,»extendedPanID»:[221,221,221,221,221,221,221,221],»channelList»:[11],»networkKey»:»HIDDEN»>,»databasePath»:»/opt/zigbee2mqtt/data/database.db»,»databaseBackupPath»:»/opt/zigbee2mqtt/data/database.db.backup»,»backupPath»:»/opt/zigbee2mqtt/data/coordinator_backup.json»,»serialPort»:<«baudRate»:115200,»rtscts»:true,»path»:»/dev/ttyACM0″>>’
zigbee-herdsman:adapter Path ‘/dev/ttyACM0’ is valid for ‘ZStackAdapter’ +0ms
zigbee-herdsman:controller:log Starting with options ‘<«network»:<«networkKeyDistribute»:false,»networkKey»:[1,3,5,7,9,11,13,15,0,2,4,6,8,10,12,13],»panID»:6754,»extendedPanID»:[221,221,221,221,221,221,221,221],»channelList»:[11]>,»serialPort»:<«baudRate»:115200,»rtscts»:true,»path»:»/dev/ttyACM0″>,»databasePath»:»/opt/zigbee2mqtt/data/database.db»,»databaseBackupPath»:»/opt/zigbee2mqtt/data/database.db.backup»,»backupPath»:»/opt/zigbee2mqtt/data/coordinator_backup.json»>’ +0ms
zigbee-herdsman:adapter:zStack:znp:log Opening SerialPort with /dev/ttyACM0 and <«baudRate»:115200,»rtscts»:true,»autoOpen»:false>+0ms
zigbee2mqtt:error 2020-04-08 00:49:32: Error while starting zigbee-herdsman
zigbee2mqtt:error 2020-04-08 00:49:32: Failed to start zigbee
zigbee2mqtt:error 2020-04-08 00:49:32: Exiting.
zigbee2mqtt:error 2020-04-08 00:49:32: 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:113:32)
at Generator.next ()
at /opt/zigbee2mqtt/node_modules/zigbee-herdsman/dist/adapter/z-stack/znp/znp.js:8:71
at new Promise ()
at __awaiter (/opt/zigbee2mqtt/node_modules/zigbee-herdsman/dist/adapter/z-stack/znp/znp.js:4:12)
at SerialPort. (/opt/zigbee2mqtt/node_modules/zigbee-herdsman/dist/adapter/z-stack/znp/znp.js:111: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! zigbee2mqtt@1.12.0 start: node index.js
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the zigbee2mqtt@1.12.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/pi/.npm/_logs/2020-04-07T22_49_32_661Z-debug.log

Really hope that this makes sense and there is support.

Источник

Sonoff Zigbee Dongle Plus CC2652P : zigbee-herdsman:adapter Failed to validate path: ‘Error: spawn udevadm ENOENT’ #15564

What happened?

I’m running Home Assistant OS on a RaspberryPi 3.

Zigbee2MQTT is not starting properly.
According to the log, it stucks at Starting zigbee-herdsman (0.14.76)

My goal is to use my Bosch thermostat 2 via the dongle and Zigbee2MQTT. For this I bought one from Amazon (unfortunately the Dongle-E and not the -P version). This one was not able to finish the interview with the thermostat.

After figuring out that the dongle is not recommended and experimental, I bought the Dongle-P.

I adjusted the config and tried to start the Add-On. It always gets stuck at Starting zigbee-herdsman (0.14.76) .

I also tried the Edge-Version of Zigbee2MQTT (without success).
I also uninstalled Zigbee2MQTT, restarted the Home Assistant instance and reinstalled the Add-On.
I also tried to first install the Add-On and then plug the dongle in to the Raspberry Pi.
I did not install ZHA or use the dongle in any other context than Zigbee2MQTT.

I have no further idea and I’m looking for help 😿

You can find the full log below.

I’d appreciate any help 😄
Thank you very much :

What did you expect to happen?

The Add-On should start normally and work.

How to reproduce it (minimal and precise)

Install the Add-On (Zigbee2MQTT) via HACS (imported repo) and configure it as follows:

Use a SONOFF Zigbee 3.0 USB Dongle Plus, TI CC2652P + CP2102(N) as adapter.
Try to start the Add-On.

Zigbee2MQTT version

Adapter firmware version

cannot find out due to not working Add-On

Adapter

SONOFF Zigbee 3.0 USB Dongle Plus, TI CC2652P + CP2102(N)

Debug log

The text was updated successfully, but these errors were encountered:

Источник

Error while starting zigbee-herdsman, since new slaesh stick #4785

I installed my new slaesh adapter last week, and it worked for three days, after that it needed restarting zigbee2mqtt for two days to get it online and since then it stopped working. Plugin was uninstalled, installed again, restarted home assistant couple times, tried a powered usb hub my I am running out of options. Hopefully somebody sees some obvious things in the logging below.

The text was updated successfully, but these errors were encountered:

Restarting the whole thing a couple times solved the issue again.

@jbeumer sorry to jump onto your thread but I have a similar problem. I purchased the exact same zigbee stick you have and am struggling. I also see this error in my zigbee2mqtt home assistent addon:

2020-10-26T18:57:08.429Z zigbee-herdsman:adapter Failed to validate path: ‘Error: spawn udevadm ENOENT’

after that, everything in the logs seem good except I can’T pair a single one of my xiaomi devices. I know they are a bit difficult sometimes so I tried many times.

I am just unsure if above error line means my stick is or is not working? I am about to get an extra non-xiaomi zigbee sensor just to confirm my zigbee stick is actually working.

Please let me know if you have any pointers whatsoever. What does the log look like after thigsn started working on your end, is this line gone?

2020-10-26T18:57:08.429Z zigbee-herdsman:adapter Failed to validate path: ‘Error: spawn udevadm ENOENT’

have to reopen this issue, same error as @ovizii is coming up now. Stick is most off the time not working and have to restart zigbee2mqtt every two hours.

Please provide the herdsman debug logging of this.

Hi , i am using a zzh! CC2652R Stick but might have the same problem:

Same problem with:
2020-11-01T11:28:13.149Z zigbee-herdsman:adapter Failed to validate path: ‘Error: spawn udevadm ENOENT’

And the problem is back:

Zigbee2MQTT:debug 2020-11-03 20:39:16: Removing old log directory ‘/share/zigbee2mqtt/log/2020-11-03.20-34-30’ Zigbee2MQTT:info 2020-11-03 20:39:16: Starting Zigbee2MQTT version 1.16.0 (commit #1.16.0) Zigbee2MQTT:info 2020-11-03 20:39:16: Starting zigbee-herdsman. Zigbee2MQTT:debug 2020-11-03 20:39:16: Using zigbee-herdsman with settings: ‘<«adapter»:<«concurrent»:null>,»backupPath»:»/share/zigbee2mqtt/coordinator_backup.json»,»databaseBackupPath»:»/share/zigbee2mqtt/database.db.backup»,»databasePath»:»/share/zigbee2mqtt/database.db»,»network»:<«channelList»:[15],»extendedPanID»:[221,221,221,221,221,221,221,221],»networkKey»:»HIDDEN»,»panID»:6755>,»serialPort»:<«path»:»/dev/serial/by-id/usb-Silicon_Labs_slae.sh_cc2652rb_stick_-_slaesh_s_iot_stuff_00_12_4B_00_21_CC_02_79-if00-port0″>>’ 2020-11-03T20:39:17.238Z zigbee-herdsman:adapter Failed to validate path: ‘Error: spawn udevadm ENOENT’ 2020-11-03T20:39:17.243Z zigbee-herdsman:controller:log Starting with options ‘<«network»:<«networkKeyDistribute»:false,»networkKey»:[1,3,5,7,9,11,13,15,0,2,4,6,8,10,12,13],»panID»:6755,»extendedPanID»:[221,221,221,221,221,221,221,221],»channelList»:[15]>,»serialPort»:<«path»:»/dev/serial/by-id/usb-Silicon_Labs_slae.sh_cc2652rb_stick_-_slaesh_s_iot_stuff_00_12_4B_00_21_CC_02_79-if00-port0″>,»databasePath»:»/share/zigbee2mqtt/database.db»,»databaseBackupPath»:»/share/zigbee2mqtt/database.db.backup»,»backupPath»:»/share/zigbee2mqtt/coordinator_backup.json»,»adapter»:<«concurrent»:null>>’ 2020-11-03T20:39:17.254Z zigbee-herdsman:adapter:zStack:znp:log Opening SerialPort with /dev/serial/by-id/usb-Silicon_Labs_slae.sh_cc2652rb_stick_-_slaesh_s_iot_stuff_00_12_4B_00_21_CC_02_79-if00-port0 and <«baudRate»:115200,»rtscts»:false,»autoOpen»:false>2020-11-03T20:39:17.273Z zigbee-herdsman:adapter:zStack:znp:log Serialport opened 2020-11-03T20:39:17.752Z zigbee-herdsman:adapter:zStack:znp:log Writing skip bootloader payload 2020-11-03T20:39:17.754Z zigbee-herdsman:adapter:zStack:unpi:writer —> buffer [239] 2020-11-03T20:39:18.770Z zigbee-herdsman:adapter:zStack:znp:SREQ —> SYS — ping — <«capabilities»:1>2020-11-03T20:39:18.783Z zigbee-herdsman:adapter:zStack:unpi:writer —> frame [254,0,33,1,32] 2020-11-03T20:39:24.794Z zigbee-herdsman:adapter:zStack:znp:SREQ —> SYS — ping — <«capabilities»:1>2020-11-03T20:39:24.796Z zigbee-herdsman:adapter:zStack:unpi:writer —> frame [254,0,33,1,32] 2020-11-03T20:39:30.804Z zigbee-herdsman:adapter:zStack:znp:SREQ —> SYS — ping — <«capabilities»:1>2020-11-03T20:39:30.807Z zigbee-herdsman:adapter:zStack:unpi:writer —> frame [254,0,33,1,32] Zigbee2MQTT:error 2020-11-03 20:39:36: Error while starting zigbee-herdsman Zigbee2MQTT:error 2020-11-03 20:39:36: Failed to start zigbee Zigbee2MQTT:error 2020-11-03 20:39:36: Exiting. Zigbee2MQTT:error 2020-11-03 20:39:36: Error: Failed to connect to the adapter (Error: SRSP — SYS — ping after 6000ms) at ZStackAdapter. (/zigbee2mqtt-1.16.0/node_modules/zigbee-herdsman/dist/adapter/z-stack/adapter/zStackAdapter.js:94:31) at Generator.throw () at rejected (/zigbee2mqtt-1.16.0/node_modules/zigbee-herdsman/dist/adapter/z-stack/adapter/zStackAdapter.js:25:65) npm ERR! code ELIFECYCLE npm ERR! errno 1 npm ERR! zigbee2mqtt@1.16.0 start: node index.js`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the zigbee2mqtt@1.16.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/2020-11-03T20_39_36_893Z-debug.log
2020-11-03T20:39:37: PM2 log: App [npm:0] exited with code [1] via signal [SIGINT]
2020-11-03T20:39:37: PM2 log: App [npm:0] starting in -fork mode-
2020-11-03T20:39:38: PM2 log: App [npm:0] online

It crashes every day:

I guess the error is related to the new stick, I did have some issues with my cc2531 stick but the struggle got worse when I started using the new slaesh stick.

I moved my zigbee2mqtt docker from Home Assistant directly to unRaid and now it works. Probably a problem with USB and Home Assistant.

I moved my zigbee2mqtt docker from Home Assistant directly to unRaid and now it works.

I have no idea how to fix that in home assistant, could you describe on how to do that?

@Koenkk After I had a fail like in #4398 I had this error message like the OP for me it recovered somehow by itself after a few failed attempt, here is the log:
network_fail-after-restart.zip

Im running zigbee2mqtt with HomeAssistant in docker on a RPi4 with a CC2531 Stick. Today i paired some now ikea bulbs, then suddenly my switches stopped working and after a reboot of the host this error appears when i try to start zigbee2mqtt plugin. I tried all the steps in the readme regarding usb ports etc. but no luck.

This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 7 days

@eberlemartin could you find a solution? That’s exactly what happened to me. 2 new Ikea lamps and bang «Error: SRSP — SYS — Ping after 6000ms» error.

After a long search i ended up actually buying the stick from slaesh. Apparently pairing multiple devices at once can overwhelm the cc2531 and cause the programming to break, then you have to flash it again. Make sure you exhausted all other tipps first like using the by-id address for your usb port etc.

I’m getting the error:

[22:04:00] INFO: Zigbee Herdsman debug logging enabled
[22:04:00] INFO: Handing over control to Zigbee2mqtt Core .

Источник

Error while starting zigbee-herdsman, since new slaesh stick #4785

I installed my new slaesh adapter last week, and it worked for three days, after that it needed restarting zigbee2mqtt for two days to get it online and since then it stopped working. Plugin was uninstalled, installed again, restarted home assistant couple times, tried a powered usb hub my I am running out of options. Hopefully somebody sees some obvious things in the logging below.

The text was updated successfully, but these errors were encountered:

Restarting the whole thing a couple times solved the issue again.

@jbeumer sorry to jump onto your thread but I have a similar problem. I purchased the exact same zigbee stick you have and am struggling. I also see this error in my zigbee2mqtt home assistent addon:

2020-10-26T18:57:08.429Z zigbee-herdsman:adapter Failed to validate path: ‘Error: spawn udevadm ENOENT’

after that, everything in the logs seem good except I can’T pair a single one of my xiaomi devices. I know they are a bit difficult sometimes so I tried many times.

I am just unsure if above error line means my stick is or is not working? I am about to get an extra non-xiaomi zigbee sensor just to confirm my zigbee stick is actually working.

Please let me know if you have any pointers whatsoever. What does the log look like after thigsn started working on your end, is this line gone?

2020-10-26T18:57:08.429Z zigbee-herdsman:adapter Failed to validate path: ‘Error: spawn udevadm ENOENT’

have to reopen this issue, same error as @ovizii is coming up now. Stick is most off the time not working and have to restart zigbee2mqtt every two hours.

Please provide the herdsman debug logging of this.

Hi , i am using a zzh! CC2652R Stick but might have the same problem:

Same problem with:
2020-11-01T11:28:13.149Z zigbee-herdsman:adapter Failed to validate path: ‘Error: spawn udevadm ENOENT’

And the problem is back:

Zigbee2MQTT:debug 2020-11-03 20:39:16: Removing old log directory ‘/share/zigbee2mqtt/log/2020-11-03.20-34-30’ Zigbee2MQTT:info 2020-11-03 20:39:16: Starting Zigbee2MQTT version 1.16.0 (commit #1.16.0) Zigbee2MQTT:info 2020-11-03 20:39:16: Starting zigbee-herdsman. Zigbee2MQTT:debug 2020-11-03 20:39:16: Using zigbee-herdsman with settings: ‘<«adapter»:<«concurrent»:null>,»backupPath»:»/share/zigbee2mqtt/coordinator_backup.json»,»databaseBackupPath»:»/share/zigbee2mqtt/database.db.backup»,»databasePath»:»/share/zigbee2mqtt/database.db»,»network»:<«channelList»:[15],»extendedPanID»:[221,221,221,221,221,221,221,221],»networkKey»:»HIDDEN»,»panID»:6755>,»serialPort»:<«path»:»/dev/serial/by-id/usb-Silicon_Labs_slae.sh_cc2652rb_stick_-_slaesh_s_iot_stuff_00_12_4B_00_21_CC_02_79-if00-port0″>>’ 2020-11-03T20:39:17.238Z zigbee-herdsman:adapter Failed to validate path: ‘Error: spawn udevadm ENOENT’ 2020-11-03T20:39:17.243Z zigbee-herdsman:controller:log Starting with options ‘<«network»:<«networkKeyDistribute»:false,»networkKey»:[1,3,5,7,9,11,13,15,0,2,4,6,8,10,12,13],»panID»:6755,»extendedPanID»:[221,221,221,221,221,221,221,221],»channelList»:[15]>,»serialPort»:<«path»:»/dev/serial/by-id/usb-Silicon_Labs_slae.sh_cc2652rb_stick_-_slaesh_s_iot_stuff_00_12_4B_00_21_CC_02_79-if00-port0″>,»databasePath»:»/share/zigbee2mqtt/database.db»,»databaseBackupPath»:»/share/zigbee2mqtt/database.db.backup»,»backupPath»:»/share/zigbee2mqtt/coordinator_backup.json»,»adapter»:<«concurrent»:null>>’ 2020-11-03T20:39:17.254Z zigbee-herdsman:adapter:zStack:znp:log Opening SerialPort with /dev/serial/by-id/usb-Silicon_Labs_slae.sh_cc2652rb_stick_-_slaesh_s_iot_stuff_00_12_4B_00_21_CC_02_79-if00-port0 and <«baudRate»:115200,»rtscts»:false,»autoOpen»:false>2020-11-03T20:39:17.273Z zigbee-herdsman:adapter:zStack:znp:log Serialport opened 2020-11-03T20:39:17.752Z zigbee-herdsman:adapter:zStack:znp:log Writing skip bootloader payload 2020-11-03T20:39:17.754Z zigbee-herdsman:adapter:zStack:unpi:writer —> buffer [239] 2020-11-03T20:39:18.770Z zigbee-herdsman:adapter:zStack:znp:SREQ —> SYS — ping — <«capabilities»:1>2020-11-03T20:39:18.783Z zigbee-herdsman:adapter:zStack:unpi:writer —> frame [254,0,33,1,32] 2020-11-03T20:39:24.794Z zigbee-herdsman:adapter:zStack:znp:SREQ —> SYS — ping — <«capabilities»:1>2020-11-03T20:39:24.796Z zigbee-herdsman:adapter:zStack:unpi:writer —> frame [254,0,33,1,32] 2020-11-03T20:39:30.804Z zigbee-herdsman:adapter:zStack:znp:SREQ —> SYS — ping — <«capabilities»:1>2020-11-03T20:39:30.807Z zigbee-herdsman:adapter:zStack:unpi:writer —> frame [254,0,33,1,32] Zigbee2MQTT:error 2020-11-03 20:39:36: Error while starting zigbee-herdsman Zigbee2MQTT:error 2020-11-03 20:39:36: Failed to start zigbee Zigbee2MQTT:error 2020-11-03 20:39:36: Exiting. Zigbee2MQTT:error 2020-11-03 20:39:36: Error: Failed to connect to the adapter (Error: SRSP — SYS — ping after 6000ms) at ZStackAdapter. (/zigbee2mqtt-1.16.0/node_modules/zigbee-herdsman/dist/adapter/z-stack/adapter/zStackAdapter.js:94:31) at Generator.throw () at rejected (/zigbee2mqtt-1.16.0/node_modules/zigbee-herdsman/dist/adapter/z-stack/adapter/zStackAdapter.js:25:65) npm ERR! code ELIFECYCLE npm ERR! errno 1 npm ERR! zigbee2mqtt@1.16.0 start: node index.js`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the zigbee2mqtt@1.16.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/2020-11-03T20_39_36_893Z-debug.log
2020-11-03T20:39:37: PM2 log: App [npm:0] exited with code [1] via signal [SIGINT]
2020-11-03T20:39:37: PM2 log: App [npm:0] starting in -fork mode-
2020-11-03T20:39:38: PM2 log: App [npm:0] online

It crashes every day:

I guess the error is related to the new stick, I did have some issues with my cc2531 stick but the struggle got worse when I started using the new slaesh stick.

I moved my zigbee2mqtt docker from Home Assistant directly to unRaid and now it works. Probably a problem with USB and Home Assistant.

I moved my zigbee2mqtt docker from Home Assistant directly to unRaid and now it works.

I have no idea how to fix that in home assistant, could you describe on how to do that?

@Koenkk After I had a fail like in #4398 I had this error message like the OP for me it recovered somehow by itself after a few failed attempt, here is the log:
network_fail-after-restart.zip

Im running zigbee2mqtt with HomeAssistant in docker on a RPi4 with a CC2531 Stick. Today i paired some now ikea bulbs, then suddenly my switches stopped working and after a reboot of the host this error appears when i try to start zigbee2mqtt plugin. I tried all the steps in the readme regarding usb ports etc. but no luck.

This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 7 days

@eberlemartin could you find a solution? That’s exactly what happened to me. 2 new Ikea lamps and bang «Error: SRSP — SYS — Ping after 6000ms» error.

After a long search i ended up actually buying the stick from slaesh. Apparently pairing multiple devices at once can overwhelm the cc2531 and cause the programming to break, then you have to flash it again. Make sure you exhausted all other tipps first like using the by-id address for your usb port etc.

I’m getting the error:

[22:04:00] INFO: Zigbee Herdsman debug logging enabled
[22:04:00] INFO: Handing over control to Zigbee2mqtt Core .

Источник

Upgraded from CC2531 to CC2652 — cannot add devices to zigbee network #9565

realalexandergeorgiev commented Nov 8, 2021

What happened

I did upgrade from CC2531 to CC2652. I did not change the pan_id or other values. The old config worked mostly flawless

What did you expect to happen

Adding new devices to the network should work. Adding old devices as well.

How to reproduce it (minimal and precise)

I removed a Xiaomi wireless switch and tried to add it — without success.

Debug info

Zigbee2MQTT version: 1.22.0 commit: unknown
Adapter hardware: CC26X2R1
Adapter firmware version: 20210708 coordinator zstack3x0

I had no luck pairing an IKEA E1734 as well. Both new batteries, 30cm next to adapter.

The text was updated successfully, but these errors were encountered:

Hello, I have the same hardware and it worked without problem.

It could be an problem from your Xiaomi switch.
Try this:
In this case, you should first start the pairing process of the device according to the instructions, i.e. press the reset button for 10 seconds. As soon as the Smart Switch is in pairing mode, continue to press the reset button every second with a pointed object.

As a result, the Smart Switch regularly sends a sign of life and is (re) recognized by the gateway within a short time.

realalexandergeorgiev commented Nov 9, 2021

Thank you for the quick reply.

Very strange. I have tried the IKEA switch as well and it didn’t work. I have borrowed 2 Xiaomi switches and none is able to pair.

So my issue isn’t related to the switches I guess.

check your configuration.yaml
important parameter from my one as example:
homeassistant: false permit_join: true mqtt: base_topic: zigbee2mqtt server: mqtt://mqtt serial: port: /dev/ttyUSB0 advanced: rtscts: false baudrate: 115200 log_level: debug channel: 25 network_key: — xxx — xxx — xx — xxx — xxx — xxx — xx — xxx — x — xxx — xxx — xx — xx — xx — xx — xxx devices: ‘0x00158d000448ae93’: friendly_name: PaulmannRGB2

the network key is masked. There are normaly numbers

perhaps send a debug log.

It could be important to pair the device near by the cc2652 stick (5cm distance).

realalexandergeorgiev commented Nov 9, 2021

I use mosquito, but the configuration seems similar. Rtscts is false, 115200 etc. I wouldnt be able to control my network with errors here, right?

The log doesn’t show anything for the joining devices. Only the other devices exchanging data.

That could be your problem.
To use the zigbee stick you will need a software component to communicate with the stick. This is the zigbee2mqtt software from Koenkk. This component is connecteted to the broker mosquito. And your Home automation Software is connected to mosquito.
If you only see communication from mosquito and nothing from zigbee2mqtt. You will have a problem on the zigbee2mqtt component .
Normaly if you find the configuration.yml file in your directory. In the same directory is an sub folder called «log». There you will find the debug log from zigbee2mqtt.

My installation based on docker. So I can inspect all running containers.
https://github.com/ct-Open-Source/ct-Smart-Home

If your installation based also of docker. Inspect all running containers.

realalexandergeorgiev commented Nov 9, 2021

I see the logs from my network, just nothing from the devices trying to join

I can control 60 devices, no issues. Only joining isnt working.

If you restart your zigbee component you will get a log like this:

debug 2021-11-09 14:35:58: Loaded state from file /app/data/state.json info 2021-11-09 14:35:58: Logging to console and directory: ‘/app/data/log/2021-11-09.14-35-55’ filename: log.txt debug 2021-11-09 14:35:58: Removing old log directory ‘/app/data/log/2021-11-07.12-49-14’ info 2021-11-09 14:35:58: Starting Zigbee2MQTT version 1.22.0-dev (commit #6ba743c ) info 2021-11-09 14:35:58: Starting zigbee-herdsman (0.13.166) debug 2021-11-09 14:35:58: Using zigbee-herdsman with settings: ‘<«adapter»:<«concurrent»:null,»delay»:null,»disableLED»:false>,»backupPath»:»/app/data/coordinator_backup.json»,»databaseBackupPath»:»/app/data/database.db.backup»,»databasePath»:»/app/data/database.db»,»network»:<«channelList»:[25],»extendedPanID»:[221,221,221,221,221,221,221,221],»networkKey»:»HIDDEN»,»panID»:6754>,»serialPort»:<«baudRate»:115200,»path»:»/dev/ttyUSB0″,»rtscts»:false>>’ info 2021-11-09 14:35:59: zigbee-herdsman started (resumed) info 2021-11-09 14:35:59: Coordinator firmware version: ‘<«meta»:<«maintrel»:1,»majorrel»:2,»minorrel»:7,»product»:1,»revision»:20210708,»transportrev»:2>,»type»:»zStack3x0″>’ debug 2021-11-09 14:35:59: Zigbee network parameters: <«channel»:25,»extendedPanID»:»0xdddddddddddddddd»,»panID»:6754>info 2021-11-09 14:35:59: Currently 57 devices are joined: info 2021-11-09 14:35:59: PaulmannRGB2 (0x00158d000448ae93): 371000002 — Paulmann Amaris LED panels (Router) info 2021-11-09 14:35:59: PaulmannRGB1 (0x00158d000448ab66): 371000002 — Paulmann Amaris LED panels (Router) info 2021-11-09 14:35:59: DoorSensor_2 (0x00158d0004148762): MCCGQ11LM — Xiaomi Aqara door & window contact sensor (EndDevice) info 2021-11-09 14:35:59: DoorSensor_1 (0x00158d0003e81487): MCCGQ11LM — Xiaomi Aqara door & window contact sensor (EndDevice) info 2021-11-09 14:35:59: DoorSensor_3 (0x00158d0003e787dc): MCCGQ11LM — Xiaomi Aqara door & window contact sensor (EndDevice) info 2021-11-09 14:35:59: DoorSensor_4 (0x00158d0003e8139d): MCCGQ11LM — Xiaomi Aqara door & window contact sensor (EndDevice)

realalexandergeorgiev commented Nov 9, 2021

debug 2021-11-09 15:36:49: Loaded state from file /share/zigbee2mqtt/state.json info 2021-11-09 15:36:49: Logging to console and directory: ‘/share/zigbee2mqtt/log/2021-11-09.15-36-47’ filename: log.txt debug 2021-11-09 15:36:49: Removing old log directory ‘/share/zigbee2mqtt/log/2021-10-19.16-40-23’ info 2021-11-09 15:36:49: Starting Zigbee2MQTT version 1.22.0 (commit #unknown) info 2021-11-09 15:36:49: Starting zigbee-herdsman (0.13.164) debug 2021-11-09 15:36:49: Using zigbee-herdsman with settings: ‘<«adapter»:<«concurrent»:null,»delay»:null,»disableLED»:false>,»backupPath»:»/share/zigbee2mqtt/coordinator _backup.json»,»databaseBackupPath»:»/share/zigbee2mqtt/database.db.backup»,»databasePath»:»/share/zigbee2mqtt/database.db»,»network»:<«channelList»:[11],»extendedPanID»:[22 1,221,221,221,221,221,221,221],»networkKey»:»HIDDEN»,»panID»:6754>,»serialPort»:<«path»:»/dev/ttyUSB0″>>’ info 2021-11-09 15:36:50: zigbee-herdsman started (resumed) info 2021-11-09 15:36:50: Coordinator firmware version: ‘<«meta»:<«maintrel»:1,»majorrel»:2,»minorrel»:7,»product»:1,»revision»:20210708,»transportrev»:2>,»type»:»zStack3x 0″>’ debug 2021-11-09 15:36:50: Zigbee network parameters: <«channel»:11,»extendedPanID»:»0x00124b0019369f5c»,»panID»:6754>info 2021-11-09 15:36:50: Currently 60 devices are joined: [..]

I think your configuration.yaml settings could be the problem.
Check my second post.

realalexandergeorgiev commented Nov 9, 2021

How would I be communicating with the devices if the baudrate was wrong?

However, there is a difference and my version works.
Try to eleminate the difference.

realalexandergeorgiev commented Nov 9, 2021

I appreciate your efforts in helping me, but your logic isnt right here. Its like asking me to paint my car green, because yours is and yours works

Nice analogy
I am not an expert and only try to isolate the problem by eliminating differences.
But maybe others have a better idea.

realalexandergeorgiev commented Nov 9, 2021

No worries. The RTSCTS and baud rates you use are default. If there would be any issue I would have zero communication with the zigbee adapter and therefore no control over the zigbee network (I wouldnt even be able to read messages). The communication is done via USB but emulating serial (https://en.wikipedia.org/wiki/RS-232). I am old enough to remember those cables

I assume my adapter is a) unable to parse the messages correct or b) (more likely) TX power isnt high enough and I think for joining new devices talk to the controller itself, not routers. I remember reading somewhere that TX power is lower and fixed in the firmware of the new CC chips.

Check the site https://electrolama.com/radio-docs/zigbee2mqtt/
The setting
rtscts: false
is nessesary.
But that’s enough of me
Good luck troubleshooting

@realalexandergeorgiev I just experience exactly the same thing — today upgraded from CC2531 (that I had problems with, network simply halting) to CCC2652 (slaesh), it works flawlessly, but I cannot pair any new devices, even if I am close to the coordinator (like IKEA repeater 10 cm from slaesh stick). Adding worked fine when I was on cc2531. I thought it is #8670 , but I cannot pair anything even if it’s close. I wanted to repair my IKEA blind, but simply without success (I force-removed it, but then I cannot pair it again).

Here is a full debug log when trying to pair the IKEA repeater. I don’t see anything interesting, it doesn’t really do much. This is the case when it’s 10 cm from the slaesh coordinator.

I found this in my logs, specifically here, but I don’t know how it’s relevant:

The maps generates fine:

and controlling existing devices also works fine.

I am happy to provide any more logs or sniffs if needed. Would flashing coordinator help or can I make things somehow worse? I switched from CC2531 to slaesh while being on 1.21 and then upgraded to 1.22 (probably without restarting, not entirely sure), if that’s relevant (not sure this might be related).

Источник

I need some help with my Zigbee network. Since a week I’m having problems with my zigbee2MQTT network.First my CC2531 stick started acting up with the following log:

[12:46:05] INFO: Zigbee Herdsman debug logging enabled
[12:46:05] INFO: Handing over control to Zigbee2mqtt Core ...

> zigbee2mqtt@1.18.1 start /app
> node index.js

Zigbee2MQTT:debug 2021-09-06 12:46:08: Loaded state from file /share/zigbee2mqtt/state.json
Zigbee2MQTT:info  2021-09-06 12:46:08: Logging to console and directory: '/share/zigbee2mqtt/log/2021-09-06.12-46-07' filename: log.txt
Zigbee2MQTT:debug 2021-09-06 12:46:08: Removing old log directory '/share/zigbee2mqtt/log/2021-09-06.12-45-30'
Zigbee2MQTT:info  2021-09-06 12:46:08: Starting Zigbee2MQTT version 1.18.1 (commit #1.18.1)
Zigbee2MQTT:info  2021-09-06 12:46:08: Starting zigbee-herdsman (0.13.71)
Zigbee2MQTT:debug 2021-09-06 12:46:08: Using zigbee-herdsman with settings: '{"adapter":{"concurrent":null,"delay":null},"backupPath":"/share/zigbee2mqtt/coordinator_backup.json","databaseBackupPath":"/share/zigbee2mqtt/database.db.backup","databasePath":"/share/zigbee2mqtt/database.db","network":{"channelList":[11],"extendedPanID":[221,221,221,221,221,221,221,221],"networkKey":"HIDDEN","panID":6754},"serialPort":{"path":"/dev/ttyACM1"}}'
2021-09-06T10:46:08.749Z zigbee-herdsman:adapter:zStack:znp:error Failed to determine if path is valid: 'Error: ENOENT: no such file or directory, lstat '/dev/ttyACM1''
2021-09-06T10:46:08.777Z zigbee-herdsman:adapter Failed to validate path: 'Error: spawn udevadm ENOENT'
2021-09-06T10:46:08.780Z zigbee-herdsman:controller:log Starting with options '{"network":{"networkKeyDistribute":false,"networkKey":[1,3,5,7,9,11,13,15,0,2,4,6,8,10,12,13],"panID":6754,"extendedPanID":[221,221,221,221,221,221,221,221],"channelList":[11]},"serialPort":{"path":"/dev/ttyACM1"},"databasePath":"/share/zigbee2mqtt/database.db","databaseBackupPath":"/share/zigbee2mqtt/database.db.backup","backupPath":"/share/zigbee2mqtt/coordinator_backup.json","adapter":{"concurrent":null,"delay":null}}'
2021-09-06T10:46:08.792Z zigbee-herdsman:adapter:zStack:znp:log Opening SerialPort with /dev/ttyACM1 and {"baudRate":115200,"rtscts":false,"autoOpen":false}
Zigbee2MQTT:error 2021-09-06 12:46:08: Error while starting zigbee-herdsman
Zigbee2MQTT:error 2021-09-06 12:46:08: Failed to start zigbee
Zigbee2MQTT:error 2021-09-06 12:46:08: Exiting...
Zigbee2MQTT:error 2021-09-06 12:46:08: Error: Error while opening serialport 'Error: Error: No such file or directory, cannot open /dev/ttyACM1'
    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.18.1 start: `node index.js`
npm ERR! Exit status 1
npm ERR! 
npm ERR! Failed at the zigbee2mqtt@1.18.1 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-09-06T10_46_08_858Z-debug.log

After reflashing everything worked again but only for a few days, after that the problem reappeared.So I bought a new stick and the problem immediatly happened. After reflashing it is working for 1 or 2 hours and then it goes down again.

I’ve already changed the port to the device ID, but that’s not changing anything either. See config:

data_path: /share/zigbee2mqtt
external_converters: []
devices: devices.yaml
groups: groups.yaml
homeassistant: true
permit_join: true
mqtt:
  base_topic: zigbee2mqtt
  server: mqtt://core-mosquitto:1883
  user: XXXXXXX
  password: XXXXXXX
serial:
  port: /dev/ttyACM1
advanced:
  pan_id: 6754
  channel: 11
  network_key:
    - 1
    - 3
    - 5
    - 7
    - 9
    - 11
    - 13
    - 15
    - 0
    - 2
    - 4
    - 6
    - 8
    - 10
    - 12
    - 13
  availability_blocklist: []
  availability_passlist: []
device_options: {}
blocklist: []
passlist: []
queue: {}
frontend:
  port: 8099
experimental:
  new_api: true
socat:
  enabled: false
  master: pty,raw,echo=0,link=/dev/ttyZ2M,mode=777
  slave: tcp-listen:8485,keepalive,nodelay,reuseaddr,keepidle=1,keepintvl=1,keepcnt=5
  restartdelay: 1
  initialdelay: 1
  options: '-d -d'
  log: false
ban: []
whitelist: []
zigbee_herdsman_debug: true

Also after the last error, my hue bulbs keep flickering and wall outlets turning on and off at random (with Zigbee2MQTT down). My Ikea bulbs are also not able to join and I can’t control them.

Any idea what might be the issue? I Already restored a snapshot, but that’s not solving the issue(s).

1. 
   Home

2. 
   Deutsch

3. 
   Error/Bug

4. 
   Error: spawn udevadm ENOENT Zigbee Adapter