do you consider this an issue in z2m? shouldn’t the update intervals not be configurable in the powerstrips themselves?
Yeah, that Github solution you linked to is easily configurable in the UI if you’re using Z2M if you want to override the values.
Don’t understand why this should be a Z2M issue either.
Unfortunately I don’t have the stats before acFrequency and apparentPower reporting interval configurations. But these power strips are still the most talkative devices in my network.
I’m not sure if the
linkquality can be configured the same way though. I was not able to find it in any of the endpoints…
After buying and installing mine , I also got zigbee network stability problems , and unexpected power off of the shelly power strips.
It made me discover something in my wifi network, one my router was on a channel that covered the zigbee one , I changed it and stability problems went mostly away.
Powering off still happened.
I had a third power strip that I connected thru wifi to check the firmware version and logs. No updates.
I decided to switch one of my other power strip to wifi and discovered that they can be connected to wifi and zigbee at the same time.
So far no more unexpected power off.
I
I didn't want to wait for firmware fixes any longer, so I disassembled the device following the guide at Shelly Power Strip 4 Gen4 Teardown - iFixit and switched to ESPHome at Shelly Power Strip 4 Gen4 - ESPHome Devices. Among other things, this allowed me to set colors based on current power consumption.
I have similar issues. Today package with two power strips arrived. I was very sure that it will works nice as other shelly device I already have. And it's true on wifi (not even try using matter, just paired via shelly app and shelly integration in ha). However on zigbee this device is pice of shit. By some miracle one (white) power strip connected to my zigbee network after many attempts and restarts. After pairing it was very laggy as well as all other zigbee devices in my network. I've switched to eco mode and disabled ac frequency entity and it works OK since then. But my black power strip still has problem with pairing to zigbee. At some point I want back to wifi and after enabling wifi using buttons it was pairing with shelly app for 2h. Now it's paired with app, has zigbee enabled but not paired. Once ha paired strip but strip itself thinks different and do not respond. I've tried stable and beta firmware - same story.
My ha setup: zha via conbee 3 on hp terminal (maybe t620, I don't remember exactly but it have enough resources). I have 55 zigbee devices already paired, more than half of them are currently online.
If you manually reduce the reporting frequency (for the standard reportings and two you have to set up manually), it does not make the network unusable (but still reports link quality a bit too often). Supposedly 2.0.0-beta2 will be a better experience out of the box, but then again, it was promised for two weeks ago or so and hasn't arrived yet.
I don't use Shelly, but are you sure it wasn't released in 2.0.0 beta1? Their release notes for it seem to say that's where it was released
According to Shelly support personnel, it is not: https://community.shelly.cloud/topic/11528-zigbee-network-instability-flooding-with-two shelly-power-strip-4-gen4 zigbee2mqtt-cc2652p7/page/2/#findComment-58197
Was thinking about getting this power strip on my Zigbee (ZHA) network, until I came across this thread… Can anyone confirm the issue is actually fixed in v2.0.0? The release notes do mention “Fix excessive power measurements reporting”.
Since installing 2.0.0 (there’s even a 2.0.1 now) no more shutdown or any other problemon my 2 units.
(But Zigbee Mode is still kind of broken. About half of the settings cannot be read from the Zigbee side and setting them also does not work correctly a lot of times. Direct WiFi integration works much better unfortunately.)