I have flashed 3 different SONOFF Zigbee 3.0 USB Dongle Plus Gateway ( * Base on TI CC2652P + CP2102N) cannot get any of them in to booloader mode. But I think i successfully flashed them through python script.
I’m running home assistant OS on Synology VMM the dongle shows up. I fixed the port in the Z2M configuration. But no matter what I do I get the same message:
[15:42:33] INFO: Preparing to start…
[15:42:34] INFO: Socat not enabled
[15:42:34] INFO: Starting Zigbee2MQTT…
Zigbee2MQTT:info 2024-01-04 15:42:36: Logging to console and directory: ‘/config/zigbee2mqtt/log/2024-01-04.15-42-36’ filename: log.txt
Zigbee2MQTT:info 2024-01-04 15:42:36: Starting Zigbee2MQTT version 1.35.0 (commit #unknown)
Zigbee2MQTT:info 2024-01-04 15:42:36: Starting zigbee-herdsman (0.30.0)
Zigbee2MQTT:error 2024-01-04 15:42:36: Error while starting zigbee-herdsman
Zigbee2MQTT:error 2024-01-04 15:42:36: Failed to start zigbee
Zigbee2MQTT:error 2024-01-04 15:42:36: Check Zigbee2MQTT fails to start | Zigbee2MQTT for possible solutions
Zigbee2MQTT:error 2024-01-04 15:42:36: Exiting…
Zigbee2MQTT:error 2024-01-04 15:42:36: Error: spawn udevadm ENOENT
at Process.ChildProcess._handle.onexit (node:internal/child_process:284:19)
at onErrorNT (node:internal/child_process:477:16)
at processTicksAndRejections (node:internal/process/task_queues:82:21)
quick google search of this message yields a number of threads referencing this message. This one might be a start, have a close look at your configuration.yaml. Modifying this file, either or both via command line and GUI can cause some issues. Check changes after each edit and save.