Zigbee2MQTT 502: Bad Gateway (several different errors)

[Shwanapacka]

I spent a total of about 8 hours of setup my new Sonoff Zigbee stick…

My issue very similar on this: WTH does Zigbee2MQTT refuse to load?

Lately I have made so many changes that I can hardly list all the actions accurately, but the general procedure was as follows:

• Installed MQTT broker
• Plugged in controller (Sonoff Zigbee Dongle-P)
• Installed Zigbee2MQTT add-on through the additional repository in the store
• Added mqtt user
• Updated Z2M config:
  
  
• Got error 502
• Flashed the adapter according to the instructions Z-Stack-firmware/coordinator/Z-Stack_3.x.0/bin at master · Koenkk/Z-Stack-firmware · GitHub (CC2652P)
• Tried different USB-ports (with cable and without)
• Changed various settings in Z2M config (after each change restarted the addon)
• Periodically restarted the whole system
• Studied the page: Zigbee2MQTT fails to start (command result test -w /dev/ttyUSB0 && echo success || echo failure gives success

As a result, I get several different errors:

1. SRSP - SYS - ping after 6000ms (when I change the port to /dev/ttyUSB0)
2. SRSP - SYS - getExtAddr after 6000ms
3. TypeError: Cannot read properties of null (reading ‘length’) (actual for now)

There was also a "Failed to call 'Frontend' 'stop' (TypeError: Cannot read property 'clients' of null..." error, but I don’t remember what parameters were used at the time of display…

Configuration:
ProxMox Virtual Environment 7.2-11
Home Assistant 2022.12.8
Supervisor 2022.11.2
Operating System 9.4
Frontend 20221213.1 - latest
Mosquitto broker: 6.1.3
Z2MQTT: 1.28.4-1

I don’t have a ZHA. Zigbee2MQTT - first integration of this type.
Could it be a problem with the adapter itself?

[moz133]

It could have been used. But it became unavailable after I updated to OS 9.4. Display 502 BAD gateway。
It is available in OS 9.3. I am also looking for the problem

[moz133]

Is your zigbee 2mqtt ready for use? Mine hasn’t been found. What’s the problem

[Shwanapacka]

Found. Determined by the system. Port indicated both simply usb
/dev/ttyUSB0
and address with an by-id.
There was an Add-on Zigbee2MQTT update recently, I updated, now version is 1.29.0-1.
But it still doesn’t work. I’ll try to write to the developer on github.

[brianuab (Brian)]

Where you have ‘core-mosquitto’ try the dedicated IP of the machine your coordinator is connected too mqtt://ip_address:1883

[moz133]

After I change the mqtt address from 172.17.0.1 to the actual haos address, I can use it

[Shwanapacka]

thanks for the tip
but
still unavailable…

[Shwanapacka]

log

[Shwanapacka]

It turned out that there are adapters that are not supported by the plugin due to the architecture.
This is strange.

My issue on zigbee2mqtt github

Several different errors about "502 Bad Gateway" · Issue #16047 · Koenkk/zigbee2mqtt · GitHub

I solved the problem by purchasing another adapter. Dongle-E instead of Dongle-P.
And replace “ezsp” instead of “zstack” in “adapter” config respectively.
Everything worked

Thanks to those who responded to the issue.