I was happily using a Sonoff Zigbee-Bridge with ZHA. Rocksolid & no problems. I have to add another Zigbee-coordinator in another building some distance away, so I thought of using a Sonoff Zigbee-Bridge Pro with the Zigbee2MQTT-addon to have my current ZHA runnning together. All I am getting is 502: Bad Gateway. After spending two days trying countless steps from the zigbee2mqtt-, tasmota- and HA-forums, this is my last straw.
Hardware
- Sonoff Zigbee-Bridge Pro with Tasmota 14.3.0 (release-zbbrdgpro)
Software
- Home Assistant 2024.10.4 (as VM in Proxmox)
- Supervisor 2024.10.3
- Operating System 13.2
- Mosquitto broker 6.4.1
- Zigbee2MQTT 1.40.2-1
Before I started this process, I unplugged the Sonoff Zigbee-Bridge and deactivated the ZHA-instance & restarted HA.
Setting up the coordinator
- flashing Tasmota 14.3.0 (release-zbbrdgpro) via WebInstaller
- set to “Sonoff ZBPro TCP” under Configuration → Auto-Configuration according to https://zigbee.blakadder.com/Sonoff_ZBBridge-P.html
- set GPIO15 as relay under “Configure Template” and rule after restart in Console according to https://github.com/arendst/Tasmota/discussions/17998
- according to the logs in Tasmota: Starting TCP server on port 8888
- the coordinator is found in TasmoAdmin and given the same settings than the ZHA-coordinator, except for the group topic: I changed that from the standard “tasmotas” to “tasmotas_packshed” since the devices from the different coordinators will be completely separated.
Setting up the Zigbee2MQTT-addon
My configuration.yaml:
homeassistant: true
advanced:
network_key:
- 114
- 113
- 58
- 237
- 249
- 179
- 10
- 83
- 155
- 16
- 222
- 211
- 50
- 120
- 153
- 251
pan_id: 5631
ext_pan_id:
- 181
- 173
- 164
- 178
- 251
- 58
- 146
- 104
channel: 11
mqtt:
server: mqtt://192.168.0.178:1883
user: mqtt-user
password: mqtt-password
serial:
port: tcp://192.168.0.99:8888
adapter: zstack
frontend: true
This is the log I am getting:
[10:27:08] INFO: Preparing to start...
[10:27:08] INFO: Socat not enabled
[10:27:11] INFO: Starting Zigbee2MQTT...
Starting Zigbee2MQTT without watchdog.
[2024-10-28 10:27:22] info: z2m: Logging to console, file (filename: log.log)
[2024-10-28 10:27:22] info: z2m: Starting Zigbee2MQTT version 1.40.2 (commit #unknown)
[2024-10-28 10:27:22] info: z2m: Starting zigbee-herdsman (2.1.3)
[2024-10-28 10:27:23] info: zh:zstack:znp: Opening TCP socket with 192.168.0.99:8888
[2024-10-28 10:27:23] info: zh:zstack:znp: Socket connected
[2024-10-28 10:27:23] info: zh:zstack:znp: Socket ready
[2024-10-28 10:27:23] info: zh:zstack:znp: Writing CC2530/CC2531 skip bootloader payload
[2024-10-28 10:27:24] info: zh:zstack:znp: Skip bootloader for CC2652/CC1352
[2024-10-28 10:27:25] error: zh:zstack:znp: Error while parsing to ZpiObject 'Error: CommandID '0' from subsystem '0' not found'
[2024-10-28 10:27:31] error: z2m: Error while starting zigbee-herdsman
[2024-10-28 10:27:31] error: z2m: Failed to start zigbee
[2024-10-28 10:27:31] error: z2m: Check https://www.zigbee2mqtt.io/guide/installation/20_zigbee2mqtt-fails-to-start.html for possible solutions
[2024-10-28 10:27:31] error: z2m: Exiting...
[2024-10-28 10:27:31] error: z2m: Error: SRSP - SAPI - readConfiguration after 6000ms
at Object.start (/app/node_modules/zigbee-herdsman/src/utils/waitress.ts:59:23)
at /app/node_modules/zigbee-herdsman/src/adapter/z-stack/znp/znp.ts:285:45
at Queue.execute (/app/node_modules/zigbee-herdsman/src/utils/queue.ts:36:26)
at Znp.request (/app/node_modules/zigbee-herdsman/src/adapter/z-stack/znp/znp.ts:278:27)
at Znp.requestWithReply (/app/node_modules/zigbee-herdsman/src/adapter/z-stack/znp/znp.ts:257:34)
at ZnpAdapterManager.determineStrategy (/app/node_modules/zigbee-herdsman/src/adapter/z-stack/adapter/manager.ts:122:39)
at processTicksAndRejections (node:internal/process/task_queues:95:5)
at ZnpAdapterManager.start (/app/node_modules/zigbee-herdsman/src/adapter/z-stack/adapter/manager.ts:62:26)
at ZStackAdapter.start (/app/node_modules/zigbee-herdsman/src/adapter/z-stack/adapter/zStackAdapter.ts:158:16)
at Controller.start (/app/node_modules/zigbee-herdsman/src/controller/controller.ts:137:29)
I tried this procedure: https://community.home-assistant.io/t/zigbee2mqtt-502-bad-gateway-solved/447571?u=elmbob
- deleted the PAN ID, extended PAN ID and network key and wrote GENERATE instead. With the next restart new keys where generated, according to Running Zigbee2MQTT and ZHA together - #11 by Zwaantje
I was also thinking about the ports:
https://community.home-assistant.io/t/zigbee2mqtt-web-ui-not-opening-502-bad-gateway/270283
- frontend port is default with 8080
- mqtt port is default with 1883
Some thoughts:
- some people are not recommending the a Wifi-coordinator, since it can be unstable. That was never an issue in my network.
- can the different MQTT-group topics be a problem?
- I am not applying a
base_topic: zigbee2mqttin theconfiguration.yaml. Is that okay?
I do not know what the error [2024-10-28 10:27:25] error: zh:zstack:znp: Error while parsing to ZpiObject 'Error: CommandID '0' from subsystem '0' not found' really means.
Maybe somebody of you guys has an idea. Any idea would be greatly appreciated.