all,
just wanted your opinion/experience on RL. it's new to me.
this is a RL to turn on light on the first floor.
activated by 2 zen32 buttons.
no turn off option.
that simple 
what's your take on "other activation option" ?
like when I have a dimmer at 20% and the RL calls 99%, it stays at 20%. but if I set "force" then it goes to 99%. but I dont like to generate useless zwave traffic to turn on a light already on...
so what's your take on "other activation option" ?
anyone?
is this expected that without the "force" a light dimmed at 20% wont go to 99% as instructed by the RL?
What do the logs show for the RL app and the devices that's not changing?
I tested a similar setup with one of mine, turned one light off and set the other to 100%, the RL is set for 20%. The light which was on, but incorrect level, had nothing logged from the app, it just skipped over it because it was already on is what it seems.
@bravenel you are the only one who would know, is this intended behavior?
Here is my similar RL for reference.
thanks for the reply.
I turned the RL off, then dimmed a light at 20% then activate the RL.
logs skip the light dimmed. like if it consider it ON already. like partly on.. good enough lol
if the same light is off. then it goes on to the set level in the RL.
and to ensure it was not a communication issue. I tested with a light 4 feet away from the hub.
I would believe "Activate even if already partially activated" would take care of it
BTW, I love that new RL thing. I feel it's more flexible and quicker to configure. love it. good work guys!
I tagged the dev who created the app up above, I think he is the only one who will know if this is intentional behavior or not. There could be a setup where you would not want it to change the level so he has it this way on purpose, in which case the Force option does what you want. So just have to wait for him to respond at this point I think.
Also, using the Force will not be too bad here, since I am guessing you are not pressing that button repeatedly. A quick flurry of 7 level commands (and one on command) should not cause any problems.
thanks.
issue appear to be only on the ON command. Off command works even if dimmer is at 99 or 20.
so I did this. and it works. (this a the "movie" RL where I turn off most of the lights on the main floor and dim a few) only need to force those that are set to be ON.
@jtp10181 just curious, before when I was creating a scene, I had to use metering otherwise some lights were not going on or went to the wrong level.
now that option is gone which worried me until I realized that I dont have the issues I had before.
so what has been done? I love it! (just curious again, sorry, off topic)
Might be helpful for you to look through below on RL:
General info:
Groups and Scenes in RL:
On metering specifically, from the second link:
Yeah, that's the way it works at the moment, and I agree that is incorrect. It should be more nuanced, and set the level when it is not set correctly. Next release... Please test it when that comes out.
Fix seems to work, ran the same test and the light that was set to 100% adjusted down to 20% while the one which was off, turned on at 20% as expected.
Would this apply across all RL apps or just if you are using it with the Scene Indicator?
It is independent of scene indicator.
Before it was only looking at switch state. Now it looks at all relevant attributes.
Ok this will be interesting to see what happens in my master bath, I have a fade up over time in a separate rule for when it gets turned on in the AM. Re-activation via the motion sensor might make it reset back to the initial level. I do not have "Activate even if partially activated" enabled on that one. I will wait and see what happens.
I cannot think of any other situations this might cause a conflict right now, will see how it works.
wow, that was a quick fix! love it!
tested and it works!
if I may, I would have a little feature request. (or if it's there, I dont know how to use it)
would be nice if a RL activator could have 3 states: on/off/someOn (I see logs showing them) but I can't seems to do RM on "someOn"
reason is, we install zen32 keypad for our customers. some buttons are "basement on" and "basement off" which triggers their respective RL. then, based on the RL status, we have RM that triggers on the status of the RL to turn on or off the leds of the zen32 buttons. if the RL could have the 3 status, I could only use one RL called "basement" instead of 2 RL ("basement on" and "basement off")
thanks
Its in the Current States of the activator device that can be created for the RL instance.
You could use that as a custom attribute in RM.
Here is my RM I use on one of my ZEN32 buttons to turn the LED on and off with a RL activator. I just use the on/off state of the activator. I have never used the groupState for anytihng.
Here is the RL:
And here is the button controller which toggles the activator:
glad im doing it the same way as you! I feel smart now!
that's what I do most of the time except for managing the second floor lights
on zen32:
button 1: 2nd floor on.
button 2: 2nd floor off.
like you, I want the zen32 leds to reflect the status. if 2nd floor is on, I want led of button 1 to be on and button 2 to be on if all light are off. the challange is when they are either all on or all off (SomeOn)
so Im doing it that way:
which require 2 RL.
but if a RL could be on/off/SomeOn, then one RL would be enough.
Download the Hubitat app
