The switch on/off event, I think if you enable Smart Bulb mode for the relay and disable the status events it should make it stop reporting the switch on/off and also bonus the LED wont go on and off when you press the button.
The button 2 / doubleTapped events, those you will get both, reason is that I added the doubleTapped event to be more compatible with the Button Controller app grid layout. It makes it easier to see what is going on if you use the DT vs the button 2. So you can use either event. The extra event is not hurting anything.
Thanks again for your quick replies.
I know this is not directly related to your drivers, but as I am building this out, I found within the virtual devices, a "virtual fan controller" with up to five "levels" to select from. I thought this would make more sense than using 3 individual virtual buttons, and might allow the Alexa command to be "Alexa, living room fan [ low-medium-high]" rather than "turn living room fan medium on" (klunky) . Problem is, I create a new "virtual button" device, name it "living room fan", use the type "virtual fan controller" and it seems to create and save OK, but then when I go to basic rules -> when a button device -> (select device), pulldown does not include my newly created virtual fan controller. Same thing in RM. Open to suggestions if you have any!
The virtual fan controller does not have "button" capabilities, so it would not show up as an option for button devices. Not sure what you are trying to do exactly? Might be better to make a new topic for that though.
Silly question. I just noticed that most - maybe all - of the little blue leds on my zen26 and zen27 seem to be off instead of “on when switch is off”
My zen7x do not seem to be affected. I checked a couple switches driver setting and I can’t see anything changed. I have had a few blue LEDs die on some older switches but I think this is too many to go all at once.
I don’t think I missed a post about this but just thought I would check with you.
Edit. Not most - about half. Weird. Possible from the same batch.
That's what I was thinking, neither Zooz or I have changed anything with the LED settings in a while. That's a shame the LED burned when the rest of it still works. If they are within 5yrs, they might replace them for you.
Thank you for your suggestion. Yes they are under 5 years but probably close. These ones were probably purchased in 2019/2020.
But I am in Canada and these were purchased directly from the smartesthouse site, shipped to our Long Island company address and then I hand carried to Canada on a business trip. So they were not purchased through the Canadian reseller. Any RMA would be a nightmare.
About six months ago I did do a tear down - you really have to tear it down completely to get to it - and did a replacement on one switch. So it is doable, just not fun. I had two more switch’s on my todo list. I guess I have a half dozen more now
Hi everyone, Im a new hubitat user so I have been trying to wrap my head around all of this! I installed the new driver and most changes to parameters are operating as expected.
I am attempting to set my double tap to a custom brightness of 70%. For some reason, it goes to 100%. I ran a report to see what the parameters were set to using the basic zwave tool and it seems the parameters are set to correctly. single tap works as well and turns on to 25%.
Would need to know what device model and firmware, and also what settings you have.
I think maybe you are using custom brightness for single tap and maximum for double tap? If you have the brightness correction on it may be going to 70% but will show as 100%, and also some models have that correction built into the switch firmware.
You may need to disable the double tap setting on the switch itself, and then program a button event to set the brightness how you want for the double tap.
Hello. Very new here. Just installed 2X ZEN30's (on completely different circuits). Both using this driver. The first works fine and behaves as it should. The second exhibits strange behavior. Physically the buttons behave correct. Logically (virtually), when I turn on the paddle switch, it also turns on the relay. The paddle switch light comes on but the relay's fan does not, but both indicate on. Same behavior for turning off the paddle switch virtually; both go off. The light goes off, and the relay goes off, but the fan on the relay was never on to begin with. I can't seem to initiate a virtual "turn on" of the relay by itself. Using the "on" function in hubitat does nothing.
I've excluded it, included it, reinitialized it, multiple times. What can I provide the community so I can get advice as to what's happening?
Make sure you are set to my custom driver from this post, current version.
Then run "Configure" on my driver to properly detect the endpoints (this changed with the 800LR model). The configure is critical for it to function correctly when switching from the system driver over to my driver.
If still having issues please enable the Trace logging option, and then do an on/off sequence where you have the issue. Post a screenshot of the resulting logs.
I didn't see this noted in this thread, so, just in case it helps someone else...
TL;DR if you want to use "3x DOWN" on the Zooz ZEN72 (and likely other Zooz switches/dimmers), disable the "Programming from the Paddle" setting.
On my new ZEN72 800 LR switches, I enabled scene control and set up a Rule Machine rule to do something upon 3x press of the down paddle ("Button 6 Pushed"). This caused some odd and inconsistent behavior (sometimes the rule would work as expected, sometimes it wouldn't work at all, and sometimes it would partially work). Eventually I realized that, with the Programming from the Paddle option enabled (Parameter #26, Selected: 0), a 3x push of the down paddle is the on-device command to confirm a device exclusion (if initiated from the hub). I noticed that this button press took ~30 seconds to even show up in the Hubitat logs. That must be the timeout the switch uses in case there was NOT an exclusion command initiated in the hub. After the timeout was reached, the "Button 6 Pressed" log entry showed up in Hubitat, followed by this debug entry:
All other multi-tap combinations reported to Hubitat nearly immediately. The solution was to set "Programming from the Paddle" to Disabled. Then, 3x-down presses registered immediately in HE and my RM Rule started working as expected.
EDIT: just to be clear, this isn't an issue with the driver--it's due to functionality built directly into the switch
