Not sure if it works on others, not sure I have tried but works everywhere I have tried.
Yes sounds correct. Just test the extract before you remov the original with a temp device.
@jtp10181 I attempted the procedure you suggested but hit a snag. I ran z-wave exclude from the settings page and then hit the down paddle 3-times rapidly. The Zen30 double switch was not excluded from the network. It's also worth noting that the switch's LEDs did not start to blink the way I typically expect them to when the device enters inclusion or exclusion mode. I tried multiple times with both the up and down paddle. I reverted the DNI to "29" and the device worked normally, so the exclusion did not happen.
Would it make sense to do a full reset on the ZEN30?
Any other suggestions?
Marc
You probably have the setting enabled which blocks the exclusion taps from working. I think it is called something about programming from the paddle.
You could factory reset it, but you will be left with a ghost node. Would be better to exclude it.
That was it -- thank you!
I've migrated 1 Zen 30 and it seems to be working.
Question: Do I need to manually migrate the parent device as well, or can I safely use "swap device" for that? If I can use swap device for the parnet, should I do that before or after I migrate the child device?
Thanks again!
Marc
And it wont matter what order you do it in.
1 Like
Any plans on adding ZEN75 to the driver?
Is there any way to set the dimmer level of a Zen77 switch in Hubitat using this driver without the light coming on? Right now anytime I set the dimmer level using the Driver Command it sets the level correctly but also turns on the light. I was hoping the level could be set without actually turning on the light so it was at the level the next time someone turns on the light.
For example, I want to create automation rules that set some switches back to 100% when MODE becomes "Day" as they were likely dimmed during the night. Rules are working fine they just unfortunately are turning on the lights.
Short answer: No.
Long answer: Nooooooooo 
I've asked here and Zooz. I have a vast majority of Zooz devices, but this is the one sticking point preventing me from using more - setting the level without turning the light on.
3 Likes
Thanks for the confirmation, I'm not missing something. I will also send ZooZ support an email asking if they can add this as a much-needed feature.
3 Likes
No but there are ways around it. The actual reason it does not work is probably due to Zwave spec, I am guessing somewhere it says that the device shall activate when you send it a level command.
I use Room Lighting to setup the levels I want per mode or time of day in the room. Then you set the default level of the device to your lowest level you would start it at. I have the RL trigger when the light is turned on, so then when the RL activates it will also set the light to the correct level based on the mode. Sometimes this will result in the light coming on dim and then quickly ramping up but its not that big of a deal for me.
The other way around it would be to set the custom brightness on the fly. If you setup the parameters so that the light turns on to the custom brightness setting, you can then set that custom brightness from a rule using the Set Parameter command. That would basically pre-set the level for the next time it is turned on.
7 Likes
I love that setParameter command!
Anyway, I tried it on my one dimmer, a ZEN74, and it works great.
If the flashing led is a distraction when settings are changed, that can be turned off.
Not being a programming guru, I wonder if using a variable to change the parameter could be of some use.
edit: Maybe affected by a lux sensor, somehow, somewhere, lol?
Again, all Z-Wave drivers should have the setParameter command!
1 Like
I hadn't thought of this before. Cool.
It also occurs to me this may be a way to set various parameters in a rule when they aren't exposed in the driver (yet) as they device vendor adds new items. You could write a rule that runs at startup to set the parameters you care about in one place on various devices. That would be tidier than manually entering parameters at a console with no record keeping of what you changed.
I never used RL after it was introduced. This workaround sounds great. For this RM rule, I would guess that I need two RLs - one with the restrictions, and one without restrictions (or probably NOT restrictions)?
You might not gain anything from that example moving it to RL. I also dont know what is triggering your rule?
What might work for your case is to have your normal conditions setup in RL, you could block the RL from running for any special cases. The special more complex cases you could then have a separate Rule in RM to handle. I do this in two bathrooms to have a slow ramp up for your eyes to adjust, but only in the morning during certain times. All the other normal cases are handled in one RL instance, but then these two special slow ramp is in RM so that I could restrict it further.
1 Like
The bathroom light turning on.
Ignore: In your driver, where do I set the minimum default level for the switch to come on, e.g. 1%. The current long-standing issue is that the light turns on at last set level, blinds the occupant in the middle of the night, and THEN dims down to RM level in a second.
Update: Found it, but it only applies to physically turning it on. Doesn't seem to apply to motion events turning the light on.
Which brings me back to the previous question of pre-setting the level without it turning on. There are other brand switches that can do it (don't remember the other recommendation thread) so are those zigbee? My Wifi wemo dimmers can't do setlevel quietly either.
This is the resonse I received from ZooZ support today:
Hi Chris,
Thank you for reaching out and for the detailed explanation of your setup and goals.
What you're seeing is expected behavior with both the ZEN77 firmware and the way Hubitat handles dimmer level commands. In Z Wave, a "set level" command is generally treated as an instruction to turn the dimmer on to that level, rather than storing a future brightness value while remaining off.
At this time, there is no supported way to change the dimmer level silently while keeping the load off using the “set level” command. One possible workaround is to avoid changing the preset level directly and instead use automation rules that adjust brightness only when the dimmer is physically turned on. For example:
- Create a Rule Machine rule triggered by:
Physical Switch → ZEN77 → turns on - Add a Required Expression:
Time between 7:00 AM and 8:00 PM - Add an Action:
Set Dimmer Level → 100%
This approach does not turn the light on itself. Instead, it waits until someone physically turns the dimmer on, then immediately adjusts the brightness to the desired level. Please note that because the dimmer initially turns on using its previous level before the automation runs, there may be a very brief transition before the new brightness is applied.
We definitely understand the usefulness of a true "preset level without turning on" feature, but unfortunately that functionality is not currently available at this time.
Sara
Zooz Support Team
1 Like
you totally don't like the SetParameter approach I outlined above?
I haven't tested the implementation yet. Light keeps turning on. Then I realized I was using the wrong command. 
Wanted to migrate over to Room Lighting.
Is there any drawback to having the setparameter approach every time the light turns on? I don't want to do something too much to screw it up. The alternative is to fire a rule on mode change and changing conditions, which would mean a handful of times a day.
You wouldn't have to set the parameter every time you turn the light on, would you. Single tap behavior parameter would be a once and done thing. You would just be changing the Physical Custom Brightness Level On parameter. It would stay that way, say, at 30%. If you wanted it brighter at the time, you could make it brighter, but the next time you turn it on it will go to 30%. Now you can change that parameter using the SetParameter command using a rule. As I said, maybe some condition like sunshine, time of day, whatever, could be a trigger to change the parameter. You could even use a variable parameter in your rule. You wouldn't be changing the parameter every time you flip the switch. It would be done in the background with rules.
Unless I'm misunderstanding what you want to do. It seems like this would fit the bill.
Good point I have not actually tested it. I was thinking that if you send an ON command instead of set level it would honor the custom brightness instead of using the "Last Level" but maybe not. Would probably need to use the Basic Set custom brightness but then also have the driver able to send a Basic Set command.
@velvetfoot is correct, you would not do this every time, you would just change the parameter for every mode you want a different default.
I believe these two complication is why I just use Room Lighting to do it.