Probably more of a "release" version. I'm using it with about 100 devices without any problems (switches, dimmers, multi-endpoint devices, Ring G2 motion sensors, etc.). Definitely works with the WD100 and WS200 (I have multiples of those).
Just be sure to reboot after this is assigned to any device or click the "initialize" control for the device. If the "initialize" routine hasn't run, you'll just get errors until it does run. Let me know if it works for the Zen17.
Note that for your HomeSeer devices (and all devices with Central Scene), there is a "new" custom attribute "multiTapButton" which lets you work with more than 2 taps.
The multiTapButton attribute will report a decimal number in a X.Y form like 3.1, 1.2. The X part is the button number, the Y part is the number of taps. So a value of 3.1 would mean button #3, 1 tap. You can use this in a rule (triggered by a custom Attribute) and then check the value to trigger off of 1, 2, 3, 4, or 5 taps (traditional "pushed" and "doubleTap" are also supported). I plan to explain this further on the wiki, but haven't posted about that there yet.
The only reason I'm not calling it a "release" yet is I am still doing some code cleanup and plan to add "wake" support for battery operated sensor devices. May also add lock support.
My driver requires a specific naming format for child device network IDs and it will rewrite the child devices if the format it finds is incorrect. The format of child names must be in the format of "-ep" followed by a endpoint number. Like "-ep1" or "-ep001"
I believe your Zen17 device will already have child devices and the driver will delete old child devices and create new ones if the format is wrong. This will break the old rules. So, to make the transition process easier, set up several virtual devices to correspond to existing Zen17 child devices. Update your rules to point to those as a temporary "holding" spot. Then install my driver.
They'll be preserved. So this should be a "no risk" kind of thing - try the driver, if it doesn't work for you, just switch it back.
I’ll be travelling again soon, (finally!), so I’m probably best to wait for a general roll-out, but I’ll give it a go on one or two HS-WD/WS devices that my wife doesn’t use (my office).
Have you had a chance to test your driver against the just-released 2.2.9 platform? Do any of the S2 fixes/enhancements affect your new or old drivers?
@jvm33, I tried the driver out on my Zen17 by installing the bundle and ran into an issue.
The Z17 can be wired to 2 sensors and can act as a relay to 2 devices.
When I install the stock driver, I have access to 4 child devices, per screenshot # 1, below.
When I use your driver, I get 3 child devices:
EP0 is a master that can trigger both relays. The stock driver does not provide access to this functionality.
EP1 enables me to control relay 1 when configured as a switch.
EP2 enables me to control relay 2 when configured as a switch.
Unfortunately, I cannot find any way to see the status of sensor 1 or sensor 2. I tried to create an additional child device for endpoint 2, but that did not help. You can see the device info in screenshot # 2, below.
When I short the the appropriate terminals for sensor 2 together, I get the error shown in screenshot # 3 below.
The link above is for the "Full" driver - i.e., it includes all the necessary libraries from the bundle file pulled together. Just install it as you would any other driver.
I will eventually update the individual bundle library, but not until the weekend.
I did both. First I tried initialize. When the errors happened, I rebooted the hub.
Update: I tried again. Hit initialize and it produced the error shown below. I then hit initialize again, just in case, and encountered the same error. That is why you see the error twice.
