Been working on some rules to manipulate led color based on certain states and conditions. Using the setLED command in RM.
It works well enough but a couple questions:
the brightness parameter 0-100 doesn’t seem very linear. 0 is off. 100 is max brightness, but 1 (1%) while dim, is still fairly bright. Wanted to dim LEDs in a bedroom at night but 1% just seems too bright. Is this others experience?
when changing brightness for 5 different LEDs I have done five separate actions one for each LED. Is there a way to adjust brightness or color for all five LEDs in one line?
the top LED turns green briefly while updating the switch settings. Much like when you hit the config command. Is there a way to suppress this?
1.) The Z32 has 3 brightness settings - 30, 60, 100. If you try to set anything else, it'll just actually round to the closest of those 3 values.
2.) Doubt it, but I don't know for certain - it's not a use case I've ever needed or looked into myself. AFAIK, the setLED command is just a nice way of packaging up several parameter settings, and I think those various parameters can only apply to one LED at a time.
3.) Ensure Value = 1 is set for Parameters 23 and 27
ahhh, got fooled by the % sign, should have read the datasheet.
Update: I have this working fine now. I would have enjoyed a lower led dim setting ( lower than 30%) but I understand this now. I have a rule that shuts off the LEDs at 11PM on ZEN 32, 76, and 77 units beside the bed. They turn back on at 8AM.
I did find the setLED commands aren’t rock solid so I run the actions twice in the morning to ensure they light up.
I do the actions as separate setLED actions for each LED. Should I just do one setLED and cascade all the parameters into a single line (for the ZEN32)?
I've never used the setLED custom action in @jtp10181 's driver.
I have used the setParameter command though, to change several switches leds to red if the driveway gate is open. Those switches can act as buttons to open and close the gate with triple taps.
I also use parameters to light up on default when a motion override switch was thrown, or the well pump is off.
There for a while I was using a rule to light up a switch's led for a short time as a guide after the bathroom door was opened in case I wanted to go downstairs and everything was black. No longer necessary because the Ecobee thermostat now provides illumination (on low), lol.
My point being the parameter method is reliable for me.
Also, I did a mod on my Zooz toggles, and even dim is quite bright, which is good for the daytime.
wait a minute.
I think you may have it wrong.
Looking here at the zen32 advanced settings, I don't think you have to write 'blue', no?
Then again, I never used setLED, only setParameter, and don't have a zen32.
edit: I probably shouldn't gotten involved, not knowing how setLED works. Carry on.
setLED is a custom command, it is not directly related to the parameter settings.
When you use custom actions in rule machine you send the parameters EXACTLY as shown on the device page, in the same order. This works the same for any command available on the device page.
For Enum you send the exact text option you want from the dropdown.
I group multiple lights into a room lighting group and then just apply the settings to all of them by using the activator device that it creates. My rule is controlling the color temperature of lights in groups. But, it should work for dimming and set level as well. (Mine is a little more complicated than sending a single command.... but you should be able to get the idea)
Create a room light group from the individual devices. Make sure the activator device is named (creates a virtual device of the group you just made), and then reference the activator device when you want to control them all together.
This approach is nice but won't work for custom commands, only the "standard" ones that are part of the activator device ("setLED()" is a command specific to the ZEN32 that changes the LED indicators on the device according to a few parameters this Z-Wave device offers, not the light/dimmer output itself).
Yes it turns out this isn't much of an issue. If you are setting LEDs identically to more than one (of the same device i.e. ZEN32) then this is pretty easy. Here is a rule just to set two of the button keys the same across four different locations:
I did wonder if I could change multiple LEDs (on the same device) with one action command in a rule by concatenating the parameters. For instance (change LEDs 1-5 all to blue @ 60%):
But this didn't work presumably because setLED is just a command for a single instance at a time. So I had to do it as shown below. The editing of the setLED commands is a little clunky which is why I was hoping for shortcut but it's not like you do it that often. So I am fine with the result below
