502 Bad Gateway

[elminster13]

I am having some serious trouble getting Z2M running. I have historically had it working on a QNAP server with a USB ConbeeII and have recently purchased the TubesZB POE device. I have brought up a new VM on a new server in Proxmox and installed HAOS on there and added the MQTT and Z2M addons.

When I start Z2M I get an error message 502: Bad Gateway and in my logs I get:

[12:11:33] INFO: Preparing to start... [12:11:33] INFO: Socat not enabled [12:11:33] INFO: Starting Zigbee2MQTT... Zigbee2MQTT:info 2022-11-23 12:11:35: Logging to console and directory: '/config/zigbee2mqtt/log/2022-11-23.12-11-35' filename: log.txt Zigbee2MQTT:info 2022-11-23 12:11:35: Starting Zigbee2MQTT version 1.28.2 (commit #unknown) Zigbee2MQTT:info 2022-11-23 12:11:35: Starting zigbee-herdsman (0.14.68) Zigbee2MQTT:error 2022-11-23 12:12:44: Error while starting zigbee-herdsman Zigbee2MQTT:error 2022-11-23 12:12:44: Failed to start zigbee Zigbee2MQTT:error 2022-11-23 12:12:44: Check https://www.zigbee2mqtt.io/guide/installation/20_zigbee2mqtt-fails-to-start.html for possible solutions Zigbee2MQTT:error 2022-11-23 12:12:44: Exiting... Zigbee2MQTT:error 2022-11-23 12:12:44: Error: network commissioning timed out - most likely network with the same panId or extendedPanId already exists nearby at ZnpAdapterManager.beginCommissioning (/app/node_modules/zigbee-herdsman/src/adapter/z-stack/adapter/manager.ts:347:23) at ZnpAdapterManager.start (/app/node_modules/zigbee-herdsman/src/adapter/z-stack/adapter/manager.ts:92:17) at Controller.start (/app/node_modules/zigbee-herdsman/src/controller/controller.ts:132:29) at Zigbee.start (/app/lib/zigbee.ts:58:27) at Controller.start (/app/lib/controller.ts:101:27) at start (/app/index.js:109:5)

Now I have done a fair bit of reading and initially I thought that maybe my old setup was interfering with the new device so I added the following to my Z2M configuration:

mqtt: server: mqtt://core-mosquitto:1883 user: mqtt password: password serial: port: tcp://ipofPOE:6638 advanced: log_level: debug pan_id: GENERATE ext_pan_id: - 105 - 114 - 113 - 53 - 46 - 105 - 111 - 32 channel: 24 network_key: GENERATE

this didnt work so I thought well ill shutdown the QNAP server to prevent power to the conbee, uninstall Z2M in HAOS, reboot the TubesZB and then try again but alas tna.

I'm lost as to what I could do next!

[elminster13]

I had a go at changing my pan_id to 'pan_id: 6755' last night but continue to get the same error.

I can see in the device log that Z2M is connecting to the TubeZB so the connection details are good to that at least.

I have also connected to my MQTT broker with MQTT-Explorer and that is working although I cant determine whether Z2M is connecting to it as I can't see anything in the logs. Any help or ideas would be great!

I should add that I have flashed the TubesZB stick with the firmware recommended in the Z2M instructions.