What happened?
Switching over from "Zigbee Home Automation" to "Zigbee2MQTT"
Using a HamGeek Zigstar Universal Zigbee Gateway - PoE (Power over ethernet)
There is no way to add the Shelly 2PM-GEN4 in the Zigbee2MQTT => Permit Join => In the logging of the Shelly I do see a lot of " shelly_zigbee.cpp:187 Network steering was not successful (status: ESP_FAIL) "
The ESP / Zigbee chip in the gateway, has been upgraded to multiple version (from 2022 to all kind of version untill 2024/2025)
=> Running now ZIGBEE ( FW revision | 20250321 -- HW version | CC2652P2_launchpad )
=> ESP32 ( FW revision | 20240519 -- HW version | ESP32-D0WD )
Out of options for now... also created a ticket with Shelly to check this out....
What did you expect to happen?
No response
How to reproduce it (minimal and precise)
No response
Zigbee2MQTT version
2.6.3
Adapter firmware version
20250321
Adapter
HamGeej - Zigstar - PoE HMG-01
Setup
HA OS as a VM in ESX
Device database.db entry
No response
Debug log
No response
Notes
From Shelly:
shelly_zigbee.cpp:492 Start network steering
shelly_notification:164 Status change of zigbee: {"network_state":"steering"}
shelly_zigbee.cpp:187 Network steering was not successful (status: ESP_FAIL)
Frem Zigbee2MQTT:
[4-11-2025, 08:44:22] z2m: Zigbee: allowing new devices to join.
[4-11-2025, 08:44:22] z2m:mqtt: MQTT publish: topic 'zigbee2mqtt/bridge/response/permit_join', payload '{"data":{"time":254},"status":"ok","transaction":"bm756-1"}'
[4-11-2025, 08:51:57] z2m:mqtt: MQTT publish: topic 'zigbee2mqtt/bridge/health', payload '{"response_time":1762242717747,"os":{"load_average":[0.11,0.07,0.02],"memory_used_mb":1017.91,"memory_percent":51.6013},"process":{"uptime_sec":64206,"memory_used_mb":110.31,"memory_percent":5.5919},"mqtt":{"connected":true,"queued":0,"published":270,"received":310},"devices":{}}'
[4-11-2025, 09:01:57] z2m:mqtt: MQTT publish: topic 'zigbee2mqtt/bridge/health', payload '{"response_time":1762243317748,"os":{"load_average":[0.21,0.14,0.06],"memory_used_mb":1022.68,"memory_percent":51.8435},"process":{"uptime_sec":64806,"memory_used_mb":110.31,"memory_percent":5.5919},"mqtt":{"connected":true,"queued":0,"published":272,"received":310},"devices":{}}'
[4-11-2025, 09:11:57] z2m:mqtt: MQTT publish: topic 'zigbee2mqtt/bridge/health', payload '{"response_time":1762243917751,"os":{"load_average":[0.03,0.07,0.05],"memory_used_mb":1021.8,"memory_percent":51.7987},"process":{"uptime_sec":65406,"memory_used_mb":110.31,"memory_percent":5.5919},"mqtt":{"connected":true,"queued":0,"published":274,"received":310},"devices":{}}'
What happened?
Switching over from "Zigbee Home Automation" to "Zigbee2MQTT"
Using a HamGeek Zigstar Universal Zigbee Gateway - PoE (Power over ethernet)
There is no way to add the Shelly 2PM-GEN4 in the Zigbee2MQTT => Permit Join => In the logging of the Shelly I do see a lot of " shelly_zigbee.cpp:187 Network steering was not successful (status: ESP_FAIL) "
The ESP / Zigbee chip in the gateway, has been upgraded to multiple version (from 2022 to all kind of version untill 2024/2025)
=> Running now ZIGBEE ( FW revision | 20250321 -- HW version | CC2652P2_launchpad )
=> ESP32 ( FW revision | 20240519 -- HW version | ESP32-D0WD )
Out of options for now... also created a ticket with Shelly to check this out....
What did you expect to happen?
No response
How to reproduce it (minimal and precise)
No response
Zigbee2MQTT version
2.6.3
Adapter firmware version
20250321
Adapter
HamGeej - Zigstar - PoE HMG-01
Setup
HA OS as a VM in ESX
Device
database.dbentryNo response
Debug log
No response
Notes
From Shelly:
shelly_zigbee.cpp:492 Start network steering
shelly_notification:164 Status change of zigbee: {"network_state":"steering"}
shelly_zigbee.cpp:187 Network steering was not successful (status: ESP_FAIL)
Frem Zigbee2MQTT:
[4-11-2025, 08:44:22] z2m: Zigbee: allowing new devices to join.
[4-11-2025, 08:44:22] z2m:mqtt: MQTT publish: topic 'zigbee2mqtt/bridge/response/permit_join', payload '{"data":{"time":254},"status":"ok","transaction":"bm756-1"}'
[4-11-2025, 08:51:57] z2m:mqtt: MQTT publish: topic 'zigbee2mqtt/bridge/health', payload '{"response_time":1762242717747,"os":{"load_average":[0.11,0.07,0.02],"memory_used_mb":1017.91,"memory_percent":51.6013},"process":{"uptime_sec":64206,"memory_used_mb":110.31,"memory_percent":5.5919},"mqtt":{"connected":true,"queued":0,"published":270,"received":310},"devices":{}}'
[4-11-2025, 09:01:57] z2m:mqtt: MQTT publish: topic 'zigbee2mqtt/bridge/health', payload '{"response_time":1762243317748,"os":{"load_average":[0.21,0.14,0.06],"memory_used_mb":1022.68,"memory_percent":51.8435},"process":{"uptime_sec":64806,"memory_used_mb":110.31,"memory_percent":5.5919},"mqtt":{"connected":true,"queued":0,"published":272,"received":310},"devices":{}}'
[4-11-2025, 09:11:57] z2m:mqtt: MQTT publish: topic 'zigbee2mqtt/bridge/health', payload '{"response_time":1762243917751,"os":{"load_average":[0.03,0.07,0.05],"memory_used_mb":1021.8,"memory_percent":51.7987},"process":{"uptime_sec":65406,"memory_used_mb":110.31,"memory_percent":5.5919},"mqtt":{"connected":true,"queued":0,"published":274,"received":310},"devices":{}}'