Check the health of the Z-Wave repeaters within your Iris Smart Plugs! This driver allows you to keep tabs on whether the Z-Wave portion of the device is working and checks it every 30 minutes. This is a port of my original SmartThings driver. It enables the Z-Wave device within the SmartPlug to communicate status with the hub. Optionally, it can check the health of the repeaters every 30 minutes to make sure they're still online and communicating with the hub.
After installing this driver and selecting it for each device, it is important to click the Configure() button to set the association group. This is essential so that the plug can communicate status to the hub.
Update 02/02/2020: The Palindrome day update.... This driver has been updated to take advantage of some additional Z-Wave reporting that's been recently made available in a platform update. This should work on platform 2.0.6 or newer, but to take advantage ot added version reporting metrics it requires hub version 2.1.8 or later.
Good news.. The association group command is taking, otherwise the plug wouldn't be able to send the reports back to the hub. My first guess is to question the version of hub code you are running? Back in December I reported that the Z-Wave stack was not properly parsing that command class.
They fixed that, but I have tested so many interim builds I don't know exactly what version fixed it.
Nope... They are two completely independent things. You can use the stock handler for the Zigbee SmartPlug portion if you wish. Within the device, they are two entirely separate radios as well.
My plug driver adds voltage & AC line frequency reporting. It also allows for time and threshold-based consumption (wattage) reporting, whereas the stock driver only exposes threshold based reporting. I also added support for in-device toggle, and device identification, which blinks the LED on the plug for 30 seconds.
Unless you want any of the extra reporting or functions, the stock SmartPlug driver works just fine. And either driver will work with this Z-Wave repeater driver too.
Turn on debugging and run another interrogation. I'd like to see the output in the live log. I'm still thinking that the hub is not parsing that particular command class.
@srwhite you nailed the instructions for pairing these devices. If you precisely follow your instructions you can almost always get both zigbee and zwave to pair. Sure wish I'd found them a year ago. Then with your zware driver you can tell exactly what's going on with them.
Now back to seeing just how far and through how many walls they will reliably repeat.
Thanks again for all of your efforts on these plugs.
Hi, Steve. Thanks for this. I have four of these paired as Z-Wave repeaters (for many months). One took your DH and responds great; the other three show offline and, probably obviously, don't respond to any poll or interrogate commands.
I thought that when HE found the Z-Wave device of this plug that I was safe in the expectation that the Z-Wave repeater was working. But, I guess not. Any ideas for a next step?
@srwhite are these 3210-Ls able to daisy chain connect via z-wave? Mine all seem to connect to the hub until moved a distance too far for connecting direct. And then even after a zwave repair they are not able to connect through another smart plug that is halfway between it and the hub.
This driver has now been updated to support the Power Level Node Test command class which was introduced with hub version 2.0.6. The Test Communication command now functions as expected!
Github has been updated. Anyone who has experienced or reported any issues is strongly encouraged to upgrade to this release.
