I have over 8 of these and they all randomly do it. They usually don’t come back and require a forced removal and need to be paired again. Additionally, when they are ‘working’ their status indicated on Hubitat does not match the device. It will show (on) in the app but the device is still off. These are all within 20 ft of the hub.
My workaround was to schedule a metered refresh on all of them every hour.
Since then they only rarely go totally unresponsive. When that happen, I just unplug it from the wall and put it back. It is good to go after that.
1 Like
Weird, I have a few of these and have never had an issue with any of them
I have about 12 of these and I have never had a problem over years of use. They make up most of my mesh.
1 Like
what zigbee channel are you using? I'm on channel 25 and these have been pretty flawless, I have 3 or 4. You could try 25 or 15, as some devices aren't happy on other channels
I also have half a dozen of these and they are my repeaters. They have been rock solid performers. I'm still running a C5 on channel 20.
Any idea why such a popular name brand device doesn’t have a specific device type vs the generic zigbee outlet? How does one go about requesting one get made?
It was on channel 20 I just updated it to 25. Is yours set to the generic zigbee outlet for the device type?
What are you missing that's not covered by the Generic Zigbee Outlet driver?
There's no point in making/maintaining multiple drivers that are all the same outside of their name - that's why these various "generic" drivers exist.
1 Like
I'm actually using Markus's generic outlet driver with presence detection, although that's no longer necessary, since HE updates now reflect connectivity. Generally drivers have little to no effect on stability, assuming the device is properly initialized at pairing.
2 Likes
