I just went to the site and found them just fine.....
I, too, have bought 3 of them for VFD motor controls and they work great.
I had to use the Zwave basic tool to change the switch action and dimming speed, but notice that on the Zooz parameter list, they state that the ramp rate parameter (3) is 2 bytes... it should be 1 byte using the tool.
It also works with the generic dimmer driver.
SO 1 "tap" of the switch turns it on (110 VAC relay and previous DC output level), tap and hold increases the DC output using the ramp rate.
Release and tap and hold decreases the DC output.
Tap when on ramps the DC output down then off and the internal relay turns off (110 VAC).
This is how I got to clear up some Zen77 dimmers with UNK00. I switched the driver to Device, then Save, then Get Data and Configure. I did not click Clear all States. Then back to the zooz driver (Save, Configure) but no changes were displayed. Then, back to the Device driver to repeat the steps. At this point the device shows as Zen77, so I switched back to the zooz driver, save, and it shows correctly. I did this sequence on 4 switches and was successful on all.
Try adding a short delay, like maybe 0.5 seconds, for turning on the switch load.
Also, why not just allow the switch to control the load directly at this point? You will still get the button event you can use to trigger the rule for the relay.
In this situation this is my Master Bedroom and the dimmer is the main room lights and the relay is the fan. I want to double tap up on the rocker to enable my “dim” room scene which is basically just my small nightstand light so I can get dressed without waking my wife. With load control enabled, the full room lights blast on instantly and then shut off when my scene gets invoked by the double tap. So my wife gets a big flash of light and it wakes her up. Not ideal.
Awesome. Thanks! Hey, I remember seeing a chart that listed what each of the 10 button presses corresponds to, but I can't find it anymore. Do you know where that is laid out? For example, button 3 press is actually double tap up. It gets confusing, and I'm just trying to find the best way to reference what means what when creating rules and such. Thanks!
https://www.support.getzooz.com/kb/article/314-zen27-s2-dimmer-ver-3-01-advanced-settings/ The ZEN27 docs has a table at the bottom. Should apple to the ZEN30 dimmer as well. I always find it easier to just press what you want on the switch and then check the logs! Especially when working on the ZEN32 buttons (not this driver obviously). If anyone wants to make a fancy little graphic I could add it to the main post.
If you think about it, it is just odds are up and evens are down. 1,3,5,7,9 is 1x-5x for up and 2,4,6,8,10 is 1x-5x for down.
If using Button Controller app I also found it handy to rename each instance so when I go back to make edits I know what they are:
So my ZEN30 seems borked at the moment. I did an air gap reset and even that didn't fix it. It is stuck with
syncStatus : 26 Pending Changes
I've tried to reconfigure, refresh, everything. Any ideas how to get this back up and working?
With Zigbee, I would try to re-pair the device, but I'm not real sure how to do that with Z-Wave? If I run an exclude, it's going to remove it from my Hub and also break everything that uses that switch. Is there another way to "factory restore" the switch and re-include it without having to break all the apps/etc it's utilized in?
Hmm. How would I do this with this double switch since it has a child device (relay) and both the dimmer/child are tied to multiple things throughout Hubitat.
First off, thanks for that tutorial about replacing the device. It worked like a champ!
Secondly, that double-tap function setting did fix the blaring light issue on double-tap, so thanks for that!
My final issue now is that all of my button events (in my case activating/turning off Room Lighting "scenes") is extremely slow. Like 3-4 seconds after I press the button, the Room Lighting scene activates or turns off.
Turn on logging on the Device (just info) and on the Room Lighting instance (Info and debug).
Then capture some logs and post a SCREENSHOT (including the timestamps).
This will show if the delays is in the device or in the RL App.
I have button rules setup for a few different devices, controlling lights directly or via RL, they all execute pretty quick, not a noticeable delay.
Will do! On that note, am I missing something when it comes to logging? Typically I keep on Info Logging for all devices and apps, but then, whenever I need to troubleshoot and go into the logs, it fills up instantly with stuff I don't care about. Is there an easier way to globally enable/disable info and/or debug logging? Then is there an easier way to toggle those on for specific devices/apps more easily than going into each one and manually turning them on? Seems like there is a lot of room for improvement when it comes to enabling/disabling logging in Hubitat, unless, like I said, I am missing something?
You can also look in the "Event" tab of a device to see prior events, depending on how much history you have enabled for that device. I have been turning off a lot of the info logging and then only turn on to troubleshoot or things I really want to see the info for all the time.
What gets logged it up to the driver and there are not really any standards around how or what to log. Some people make their apps/drivers very chatty and some people have no logging.
Also, there is filters at the top of the logs. So for this case you could filter it to JUST this device and the RL app we are interested in, then you wont see any extra clutter.
Oh also, if you click the device/app number it will filter to that entity only.
If you click the Info/Debug/Warn icon it will take you to that device so you can turn logging off if desired. That is how I have been slowing turning off things I dont want to see anymore.
