I am running HomeAssistant in a VM on my Synology NAS.
Ive got a Conbee2 ZigbeeStick connected and mounted in the VM.
When i try to start Zigbee2MQTT i get the following Error Message:
[16:34:41] INFO: Preparing to start…
[16:34:41] INFO: Socat not enabled
[16:34:43] INFO: Starting Zigbee2MQTT…
Zigbee2MQTT:info 2023-02-16 16:34:48: Logging to console and directory: ‘/config/zigbee2mqtt/log/2023-02-16.16-34-48’ filename: log.txt
Zigbee2MQTT:info 2023-02-16 16:34:48: Starting Zigbee2MQTT version 1.30.1 (commit #unknown)
Zigbee2MQTT:info 2023-02-16 16:34:48: Starting zigbee-herdsman (0.14.89)
Zigbee2MQTT:error 2023-02-16 16:34:49: Error while starting zigbee-herdsman
Zigbee2MQTT:error 2023-02-16 16:34:49: Failed to start zigbee
Zigbee2MQTT:error 2023-02-16 16:34:49: Check Zigbee2MQTT fails to start | Zigbee2MQTT for possible solutions
Zigbee2MQTT:error 2023-02-16 16:34:49: Exiting…
Zigbee2MQTT:error 2023-02-16 16:34:49: Error: spawn udevadm ENOENT
at Process.ChildProcess._handle.onexit (node:internal/child_process:283:19)
at onErrorNT (node:internal/child_process:478:16)
at processTicksAndRejections (node:internal/process/task_queues:83:21)
As I just tried out Zigbee2MQTT for the first time two days ago, so I won’t be the best one to help, but I suggest you enable “zigbee_herdsman_debug” (on the config page if you’re using the Add-On) for the logs to see if it reveals any more information, and maybe show what your config looks like.
The spawn udevadm ENOENT error, if I had to guess, is that it can’t find your USB device.
I had the same problem yesterday.
I tried a lot of tips from various forum threads without success.
I think I might made a mistake in the config and the adapter: ezsp (for sonoff dongle E) under server part instead of under serial: row… but I’m not sure.
Anyhow, I uninstalled Zigbee2MQTT, rebooted, reinstalled, configured (obviously correct 2nd time) and then it started…
Any luck here? I also have the failed to load herdsmen error. I have the Sonoff stick and Zigbee2Mqtt worked on my former HomeBridge setup. I read so many posts indicating to upgrade the stick so I did that, same error. And I did verify the correct port as has been suggested.