Zigbee network instability / flooding with two Shelly Power Strip 4 Gen4 (Zigbee2MQTT + CC2652P7)

Setup

  • Home Assistant + Zigbee2MQTT
  • Coordinator: CC2652P7 (cod.m, LAN)
  • Network size: 63 Zigbee devices
  • Problematic devices: 2× Shelly Power Strip 4 Gen4
  • Firmware (both strips): 20250819-150402/ga0def2d

Issue (recurring crashes)
I’m seeing repeated Zigbee network crashes after bringing the two Shelly Power Strip 4 Gen4 online. When it happens, the coordinator becomes overwhelmed, the mesh becomes unresponsive, and all Zigbee devices go offline until I restart Zigbee2MQTT / power-cycle the coordinator.

What I observe

  • High message rates from each strip when idle: ~0.5–1.5 msg/s (measured via Zigbee2MQTT logs/health).
  • Repeated publishes of attributes like ac_frequency , current, energy, power, and voltage (even while I totally deleted all reportings)
  • Other devices on the same network (e.g., Frient SPLZB-141) behave normally and do not cause instability.

What I tried (no improvement)

  • Set very conservative reporting intervals and thresholds for the Shelly attributes.
  • Cleared bindings and reset/deleted reporting on clusters; re-interviewed the devices.

Any Help what I can do, to get the Shelly Power Strip 4 Gen4 to work in a Zigbee Network?

3 Likes

What do you have plugged into the power strips?

So far nothing.

I opened a ticket with Shelly Support 20 days ago regarding the above issue and unfortunately have not received a response to date, except for a request for the log files.

Is there anyone here in the community who has a solution?
Or am I the only one whose Shelly Power Strip 4 Gen4 does not work in Zigbee mode, or is it perhaps due to my set-up?

I think I have similar issue: did some changes to my network few days back and one of the changes was including S4PL-00416EU. After that, my network froze couple of times a day - I had to unplug the adapter or reboot the z2m machine to get it working. At first I thought my SLZB-02 was faulty so I replaced it with SLZB-06P7 but today got another freeze. I’ve unplugged the Shelly few hours ago and see what happens… Unfortunately I have no idea at the moment how to pinpoint if the powerstrip is the main culprit but before adding it, my network was rock solid. I also noticed that is is very chatty device (~10x more messages than single plug), so maybe it and MTG275-ZB-RL (also very chatty device) together managed to overload the coordinator :-/

Zigbee network behaves as before after the exclusion of the powerstrip. Connected it using WI-FI as a workaround

Same here.

The powerstrip was lagging my whole ZigBee network.

I started over because I bought a couple of SLZB-MR3’s. With the powerstrip in ZigBee mode I couldn’t pair my IKEA Stybar’s remotes. The interviews failed everytime.

I put it to WiFi mode and everything is fine now. I saw in the Zigbee2MQTT that the powerstrip send almost 1700 messages in 10 hours time. It’s crazy.

1 Like

I still haven’t received a reply how to handle the big issue from Shelly Support regarding my Shelly Power Strip 4 Gen 4. Besides asking for some debug files. I have no idea whether they are trying to solve the Zigbee issue or have simply given up.

Hello all,

As it happens i only read this thread after ordering 3 of the power-strips. Curious to see if the issues have been resolved.
When using Wifi, is it still possible to talk mqtt to the device, or does it work through the Shelly integration?

@Toni1, did you receive any updates on the case from Shelly?

1 Like

I was able to enable MQTT via WiFi.
But I also have an issue with adding it to my Zigbee network.

Just received them, they work well over wifi and matter.

@Toni1 Have you by any chance tested to put the strips into ‘eco mode’ and see if that makes a difference? http://IP//
#/settings/eco-mode

Same issues here,
unfortunate that we need to resort to switching to wifi.
I will also report back to Shelly since I believe it has to do with the very high frequency of messages being sent, for each socket so it’s 4x the “normal” and then also at higher frequency than I have seen any device in my network.

Same problem here. It’s flooding my Zigbee network. I suspect the linkquality is changing a lot and generating those messages. Even with all plugs off it still sending average 2 messages per second.

Same issue here. Since I installed one Power Strip 4 Gen 4, I have instability (after a while, zigbee2mqtt need to be restarted because no data is received or sent to devices). I tried to throttle to 5 seconds, I see less messages from the strip, but the instability remains.

It seems that I am experiencing similar issue. Had a very stable Zigbee network running on SLZB-06 coordinator and a bunch of plugs acting as routers scattered around the house. I’ve decided to replace the majority of those plugs with 2 Shelly power strips. The idea is, that I will still use Shelly integration (and WiFi connectivity) to control the power strips (this is more for consistency rather than anything else, because I have a bunch of other Shelly devices in this integration, and I want to have everything related to this vendor in one place), and Zigbee will be used purely for routing purposes and improve / simplify overall network.

I’ve also noticed crazy amount of activity originating from them, so I tweaked the reporting frequency for apparentPower and acFrequency attributes as documented here: hass/docs/tests/shelly-power-strip-4-gen4.md at 219c24fb9a08c805a5cdf3ba420c1632096fa50c · maxim-mityutko/hass · GitHub

However at random times (could be once per day, could be couple of days) the network becomes unresponsive. Z2M reports routers as offline, and if I try to reboot Z2M, I’m getting the " SRSP - SYS - ping after 6000ms" error. I’ve tried to follow the instructions here, but my configuration is already as expected. The only way to restore network to the operational state is to reboot the coordinator.

For now I’m dealing with this problem in a very nasty way. I’ve added the automation that checks when one of the routers goes to the unavailable state for more than 5 minutes, and then it restarts the PoE on the port that powers the coordinator via TP-Link Omada integration. Very nasty!

I have a spare SLZB-06M and I’m thinking about replacing SLZB-06 to see if it resolves the problem. But that’s the project for another day.

I’ve also noticed, that despite the fact these power strips are supposed to act as Zigbee routers, none of the other devices in the network are connected through them. I’ve tried to pair Aqara Door Sensor and Thirdreality moisture sensors directly to them, but it did not work.

same problem for me with the Shelly Power Strip 4 Gen4 with Zigbee 2MQTT , coordinator is a SLZB-06 on LAN. The Zigbee coordinator crashed 3 times in 2 days of use when I included the Shelly Power Strip.
Turn OFF , Turn ON the coordinator , then the zigbee network is back to normal.

I had no issues before with my zigbee network.

I unplugged the Shelly, and had no issue since. It seems the Shelly Power Strip is the problem.

I guess we should all report it to the support, the more cases that have, the more likely it will be investigated

2 Likes

A few stats from the last 7 days on coordinator reboots…

Bought four of these and experienced the same thing on Zigbee. Crazy amount of linkquality and AC- frequency messages (even when WiFi is set to off).

Did anybody find a workaround? I’d like to keep them on Zigbee only to function as routers/repeaters.

1 Like