Yeah I was not to sure how the whole command class versions thing worked, but I guess that makes sense to use the lowest version you need for the features you are using. As long as the device can accept that version which is another thing I am never sure of exactly.
As for the parameter, I was just trying to make it not have too many parameters so I combined those 3 into one comma list, but it could be done either way.
I am still trying to get Zooz to have it use the current color which is why I never posted this but I figured might as well get it out there for now.
Hi, I am relatively new and trying to figure out how to add this to my Zen 32. I have the code listed in drivers code area but cannot figure out how to add it to the switch driver.
The code above is the driver. To use this driver on a device, navigate to Devices (from the left-side menu of the hub interface), then open the page for your ZEN32 device. Scroll down to Type under Device Information, then choose this driver from the list. It will be under "User Drivers" and happens to be named "Zooz Scene Controller (ZEN32)," as you'll see in the Drivers Code screen.
Thanks, I will give it a try. I am assuming you are pretty knowledgeable about this switch. I have three 8' LED strip lights in my garage. I installed Zooz Zen51 relays in each light. The light switches are 3 way. I wired per Zooz. What I am trying to do is setup the Zen32 1-4 buttons to control individual lights with the top button to control all three and set up so when the garage door is opened one light comes on instead of all three. Everything is kind of working except I have about a 5 second delay when turning on the lights. With smart switches shouldn't there be voltage through the neutral at all times? I do not have voltage at the relays when the lights are off. So, it will not work to turn on the lights when the door is opened. Wondering if this switch isn't going to work for this application since there is still a mechanical switch in the circuit? I was told by Zooz it would work.
I've never used this with a relay (or the ZEN51 at all), but if it's not actually cutting power to the load/relays, it seems like that should work. If it is cutting power, I could see that being an issue, but I'm guessing yours isn't and is just connected ti the "switch" input on the relays, in which case I assume this should work similarly to a dumb switch and cause the relay to toggle (without much of a delay, though there is still a slight delay from the ZEN32 since it has to wait to see if you're doing a multi-tap or not--but I think under a second and not noticeable to me).
You might want to start another thread on this issue so it doesn't get buried in discussion of the driver.
Version 2.0 of the driver has been released. Changes:
Added support for "Indicator" command class, including the ability to turn the LEDs on or off (without changing a parameter and causing the green blink) or create a blink/flash effect
Recommend at least firmware 10.10 for ZEN32 (or setIndicator() will not work; everything else should back to original firmware)
I finally got around to testing the Indicator command class support that @jtp10181 also implemented above (thanks!), though in a slightly different format (if you use his branch now, you'll need minor modifications to use my setIndicator() command instead).
There are now two ways, it appears, to just turn the LED on or off--the parameter method in setLED() or the Indicator method in setIndicator(). I'd prefer the latter myself because it avoids the oddity that the big button's LED flashes green three times any time a parameter gets changed--but it does require recent device firmware. The "flash"/blink functionality is new with Indicator, so that's the only way if you want that. Again, anything with setIndicator() requires at least firmware 10.x, likely 10.10, which is what I tested on.
I just sunset my ST (SmartThings) Hub and brought everything over to HE (Habitat C7). I had the ZEN32 (FW10.10) LED's working in ST and have been having trouble in HE. Looks like my timing is good for doing this.
I've been struggling with the 'Zooz Scene Controller (ZEN32)' and have not figured out the right combinations of pull downs to get the LED's to work within RuleMachine. They work fine from the Device's main page
I see that v2.0 of the driver is released and I'm hoping it addresses my issues.
I'm new here and I don't see a link to it.
Where can I get a copy of the driver?
There is a link in the first post in thus thread (the little green pop-up scrollbar that will appear is usually an easier way to get there than the one in your browser in this forum software, Discourse, but either way should work).
That being said, regardless of driver, it's important to get the parameter order, types, and values correct in Rule Machine. Feel free to ask more about that if you still have troubles!
But, I'm not wrapping my head around how to set up the code.
Since I'm new here, I'm not able to attach a screen shot.
In screen --> Select Actions to Run
Select capability of action device -> Button
Select Button devices to act on -> Hall Controller
Select custom command -> setLED
parameter type -> string
string value -> 3, 'red', 100
Here is what it shows for the resulting command -> setLED('3, 'red', 100') on Hall Controller
First off, thank you for your work in making this driver and sharing it with everyone!
I loaded your driver and tried to populate a button controller, but I only got 5 button options. Did I do something wrong?
Also, just out of curiosity, is there a reason there aren’t child devices for the LED’s? I have those with my Inovelli Red switches and they are really easy to program. I’m having an issue with the LEDs working the way I want, but in fairness I’ve only spent about 30 minutes messing with the driver and setting rules.
I'm getting an odd behavior when using 'Set Indicator' from either the device page or in code.
HT: C-7
Zooz 32: FW 10.10
Regardless what options I choose for 'Set Indicator' or what color the LED is, it sets the led color (for that button) back to white. It leaves the brightness alone.
Does anyone happen to have the link for the C5 hub update? I contacted Zooz and they sent me the C7 file, which their instructions specifically say do not work for the C5. The link they provide for a C5 hub told me to contact them for the firmware file. I don’t understand why they don’t just have those links available on their support page. Anyway, I was hoping to get this done tonight so I thought I’d see if anyone else has it since their office is now closed. Thanks!
Send a 'setIndicator' flash sequence eg(3,'flash',10,20,5)
BEFORE it finishes the sequence, send 'setIndicator' ON (3,on). I was doing this to interrupt the flash sequence.
The LED will be stuck on White. It will change brightness but not color with 'setLED'. It stays this way indefinitely.
To unstick the color send another 'setIndicator' flash sequence even a very short one. (3,'flash',1,1,1).
This will also interrupt a flash sequence and let the setLED work normally.
The firmware update file is the same. What you need is a way to perform the update, as Hubitat's Device Firmware Updater app does not work on the C-5 or earlier. There is a "community" firmware update driver that should work for this. You need the "binary" version for this update (I think--assuming the update is a .GBL or similar format), which can be found in this post: [RELEASE] Z-Wave Firmware Updater - #860 by bcopeland
I didn't do extensive testing with combinations of commands, just verified that each alone with various parameters I tried appeared to work as expected. I assume you mean a bug in the device firmware? I can't imagine anything the driver could be doing that would cause that. Again, you may want to reach out to Zooz to report this. (I don't have easy access to a real device except on weekends, so I'm unable to test this myself now...)
That link was VERY helpful - I wish Zooz had provided it. Their email was extremely unclear. The one thing I can’t figure out is what firmware target to use with the binary updater. Any suggestions? I am so appreciative of your help.
) behavior, I'd suggest contacting them with this feature request.
