Zigbee2mqtt 502: Bad Gateway

Configuration Zigbee
1

version 2022:6 trying to set it up and I get the above error.

http://192.168.0.144:8123/45df7312_zigbee2mqtt/dashboard

My config is,

base_topic: zigbeezmqtt
user: mqtt_user
password: xxxxxx
server: mqtt://192.168.0.144:1883

serial:
port: /dev/ttyUSB0

This seems to be a very common problem :frowning:

at processTicksAndRejections (node:internal/process/task_queues:83:21)

[19:14:44] INFO: Handing over control to Zigbee2mqtt Core …

[email protected] start
node index.js
Zigbee2MQTT:info 2022-06-20 19:14:48: Logging to console and directory: ‘/config/zigbee2mqtt/log/2022-06-20.19-14-48’ filename: log.txt
Zigbee2MQTT:info 2022-06-20 19:14:48: Starting Zigbee2MQTT version 1.25.2 (commit #unknown)
Zigbee2MQTT:info 2022-06-20 19:14:48: Starting zigbee-herdsman (0.14.34)
Zigbee2MQTT:error 2022-06-20 19:14:48: Error while starting zigbee-herdsman
Zigbee2MQTT:error 2022-06-20 19:14:48: Failed to start zigbee
Zigbee2MQTT:error 2022-06-20 19:14:48: Check Zigbee2MQTT fails to start | Zigbee2MQTT for possible solutions
Zigbee2MQTT:error 2022-06-20 19:14:48: Exiting…
Zigbee2MQTT:error 2022-06-20 19:14:48: 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)
[19:14:49] INFO: Handing over control to Zigbee2mqtt Core …
[email protected] start
node index.js
Zigbee2MQTT:info 2022-06-20 19:14:53: Logging to console and directory: ‘/config/zigbee2mqtt/log/2022-06-20.19-14-53’ filename: log.txt
Zigbee2MQTT:info 2022-06-20 19:14:53: Starting Zigbee2MQTT version 1.25.2 (commit #unknown)
Zigbee2MQTT:info 2022-06-20 19:14:53: Starting zigbee-herdsman (0.14.34)
Zigbee2MQTT:error 2022-06-20 19:14:53: Error while starting zigbee-herdsman
Zigbee2MQTT:error 2022-06-20 19:14:53: Failed to start zigbee
xxx
Zigbee2MQTT:error 2022-06-20 19:14:53: Exiting…
Zigbee2MQTT:error 2022-06-20 19:14:53: 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)
[19:14:54] INFO: Handing over control to Zigbee2mqtt Core .

2

I removed this last night after 6 hours of failure and went with ZHA? (whatever the default is) and it worked first time so my hardware is OK its just “broken software” or documentation needs improving. Googling shows this as a common problem so its better troubleshooting docs or software that needs fixing.

3

This thread have same error and a super simple solution. I’m not related or anything to the link, just found it on google.
https://www.kincony.com/forum/showthread.php?tid=1829

4

OK, TY. Since ssh also refused to work I’ll reflash the emmc chip tonight back to 2022:5 and start again from scratch. After 6 hours I’d had enough, it might be the image or the upgrade from 2022:5 to :6 broke something, or just a bad install.