I haven’t been able to find enough time to mess with this yet. I’ll try to get to it this week.
Well, apparently there is a limit of 19 buttons for the automation. I’m not keen on trying to do some dynamic configuration, which is possible I think. So that means the best bet is to drop 3 buttons (one each for upper paddle, lower paddle, and relay switch) to get down to an “even” 18.
So…here are the candidates:
- The “Release after hold” action (retaining hold, which occurs
- The “Hold” action (retaining release, so it wouldn’t do anything until you release the button)
- The five-press action
So which parameter enables instant On/Off with the switch for the paddle (no dimming at all)? Maybe I’m understanding incorrectly, and if I am I apologize, but when looking at the ZEN30 manual, it states the following:
Ramp Rate Control for Dimmer
Parameter 13: Adjust the ramp rate for the dimmer (fade-in / fade-out effect for on/off operation). Values correspond to the number of seconds it takes for the dimmer to reach full brightness or turn off when operated manually.Values: 0 – instant on/off; 1 – 99 (seconds).
Default: 1.Size: 1 byte dec.
Then this is also in the manual which states value 0 = the setting in parameter 13 above:
Z-Wave Ramp Rate for Dimmer
Parameter 22: Choose if you would like to match the Z-Wave on/off ramp rate with the manual ramp rate or set it separately in your hub.Values: 0 – Z-Wave on/off ramp rate matches the manual ramp rate set in Parameter 13. 1 – Z-Wave on/off ramp rate is set separately through its command class in the hub. Default: 0.
Size: 1 byte dec.
Sorry for all the questions. I definitely appreciate all your work!
Parameter 13 (“Ramp Rate”) controls the speed the light turns on when you physically hit the paddle.
Parameter 22 (“Zwave Ramp Rate Control”) is related to controlling the ramp rate when using Zwave (ie through the app/platform). You can either have it just match whatever you set in Ramp Rate (parm 13) or you can control it via software through other preferences.
The other preferences are “Zwave Ramp Type” and “Zwave Ramp Speed”. If you set the Zwave Ramp Type to seconds or minutes, then the value in Zwave Ramp Speed is used. If you set it to instant, then when you turn it on via smartthings, the light will go instantly to the last brightness and not fade in. The zwave ramp stuff is strictly via zwave command classes and isn’t an actual parameter on the switch itself.
So if you set Zwave Ramp Rate Control to “Controlled by Ramp Type and Ramp Rate parameters” and then set Zwave Ramp Type to “Instant”, when you turn the light on via zwave (through the app, automation, etc) it will be instant on.
To mirror that for when you physically hit the switch, set “Ramp Rate” to 0.
Hope that makes it all clear…
Yes that’s clear. So I have all those parameters set properly however I notice that when I turn the paddle on or off I have wait for the LED “animation” to go from bottom to top or top to bottom before it finally registers to turn on/off the light and relay even though there’s no dimming or ramping done at all. It’s about 2 seconds or so for that to happen.
Here are my settings:
Have you considered using a custom dth for the relay that handles the seven buttons for the relay and reduce the buttons on the parent switch to just the 14 for the paddles?
Got some other information I was not aware of - plan on redoing it, so there will be no sacrifice of buttons. Stay tuned…
Just got an email from Zooz about this device and associated DTH’s. Here’s a link to their documentation:
Says that 2 DTH’s are needed, but that’s not the case with your latest release. The child DTH they’re having people install never gets called from your DTH. You might want to let them know unless what you have in the works changes that too?
Thanks for pointing this out, the article was based on the first version of the handler, we’ll be changing that shortly.
Thanks, installed the switch today and DTH and working great.
Is there any updates or ETA on this?
Trying to work it in with a lot of different irons in the fire. Working out the particulars of making to work right. No eta though, sorry.
Is there any need for the Zooz Zen30 Child Switch DTH? I noticed that the instructions to create that DTH are now absent from their website.
So for a previously configured Zen30 relay, what is the correct DTH to be used in conjunction with the DTH for the Zen30 dimmer?
It uses the stock child device.
@doncaruana Does this work like the old KOF device handler that adds a bunch of children cluttering up the new smartthings app? I stopped using kof device with smarttings just for that reason. Perhaps any screenshots of the zooz in the smartthings app?
@yourunclefats You are correct in that it creates a child device for the relay. I have 3 of them and they are great.
Don, wasn’t sure if here or GitHub is where to communicate a bug. I attempted to utilize the button push feature of the Zen30 using your handler but found an error in the SmartThings Classic app asking me to contact the developer.
Steps to produce:
Zen30 with 2020-02-21 release of “Zooz Zen30 Dimmer” device handler installed and operational.
Add a SmartApp using SmartThings Classic
Choose Smart Lights
Choose to control a working device
Choose to Turn On
Choose to Trigger the Action When we detect: Button Pressed
Choose Which Button: Zooz Zen30 Dimmer, Click Done
Lighting Automation screen simply says “Automate Lights, Scenes & Switches” with <Back and Next buttons at top but nothing else
Choosing Next provides red badge error reading “Error Saving unnamed page. Please contact SmartApp developer.”
I verified the device handler is providing alternative button events to ST by looking at the Events List on the API page where it logs Device Physical - button - pushed - Zooz Zen30 Dimmer Tap-Up-2 (button 3) pressed
I just can’t figure out how to use these alternative button pushes to trigger either scenes or other devices successfully. I suspect this was what you meant by:
BTW, I was able to access the Zen30 additional buttons (in particular the double tap ones 3 and 4) using the Core interface to accomplish what I needed. However, in general I prefer to use the native apps wherever possible for various reasons.
How much of this will work once a user migrates fully to the new app? Seems everyone is getting the nag message now, including myself. And I’d hate to lose functionality since this device relies so heavily on a custom device handler.
The Double Switch is fully functional in the new app with your existing custom device handler.