The post discusses how to customize the LEDs in general.
You'll want to be sure to set the "Relay LED Indicator Mode" option to "Control with 'Set LED' command".
Apologies.....In my quick scan, I missread that and though it was doing the opposite....the buttons were controlling different light colors (like a multi color light bulb). I feel like a fool.
1 Like
Bored here today, so I checked out Zooz's firmware update page...
For the 800LR hardware version Z32, new f/w 2.40 was just released that has new param 27 -- it can disable the LED flash/blink when you press a button.
I just loaded it up, and that new parameter works great -- button-press blinky now gone 
Added it to the driver!
Untested on my real device but can't see why this wouldn't work...
3 Likes
A post was merged into an existing topic: [RELEASE] Dimmer Button Controller (configure Pico to emulate Hue Dimmer or any button device to easily control lights)
Robert, the OP link, looks like there’s a missing comma on row 117. FWIW.
Fixed, thanks!
1 Like
So am I a dev now? 
1 Like
When I issue a setLED() command, it often takes 20-30 seconds or more for the device to respond. I checked the logs and played with device parameters, but have not been able to get to the bottom of it, other than being confident the command is getting issued right away.
Anyone else experiencing similar?
I use setLED() with both a Z32 and one of my Z71s, and both get used regularly -- with both devices, the LED-change response time is snappy.
I think I'm using Jeff's fork of Robert's driver for the Z32, but I'm pretty sure Robert's driver surfaces these 2 options too -- the one with the bolder outline is most important...
Thanks for sharing that. My driver UI is different (Jeff vs. Robert), but I can tell my two parms are set the same way. Hmm, it's a mystery.
1 Like
My two cents: I use the setLED command on five ZEN 32's and not had issues. But I have had long delays (up to 15sec) on ZWave commands to specific devices. I think that was down to corrupted RF messages, cured by moving from a PoE powered C7 to a wall powered C8.
Genuinely appreciate you sharing your experience, but I don't think I have zwave issues. My zwave mesh is solid; I measure response times every hour and they're never above 50 ms. And my hub is mains powered.
But please keep the ideas coming! I'm looking under rocks over here....
I'm using Robert's driver, but I can't figure out how to get the LED on button 1 to change based on the on/off status of the device I'm using the button to trigger the action. The LED just maintains the present color and won't turn off. I'm assuming I have some parameter set up incorrectly. Any help would be appreciated.
I would use the SetIndicator command to just turn the LED on and off if you dont need to change the color.
If you use the SetLED and SetIndicator commands right from the device page do they work?
Here is an example rule I have to turn the LED on and off any time a switch changes states. This keeps it in sync
1 Like
I am using a number of ZEN 32's where the buttons control and show the state of another light. It's been a long time since I set them up but I think I set the LED's to a default state of OFF using the Set Indicator Command. In other words set parameters 2 to 5 to a value of 2.
1 Like
Thank you! This helped big time. For my scenario, under the Set Indicator Command, parameters 1 to 4 were each set to off, then I used the rule from @jtp10181 .
I'm using this driver, but I cannot get the LED on the main button 5 to turn off. I can change the color and intensity, but when I set the intensity to 0, the command is ignored. I can tell because I still have the LEDs blink when they receive commands.
I can also turn buttons 1-4 off just fine as well....just not 5.
Well, it doesn't look like anyone is monitoring this thread. If anyone needs to know, the answer to my issue is to not follow the Zooz FAQ and change the "Relay Indicator Mode" to "As Modified by LED commands" which is hidden at the bottom of the options list.
Glad you figured it out.
When I first saw your post, that setting was my first thought to check, but then your post made it sound like it was all working fine for every button except 5, and I didn't have any ideas for solving just that.
