Thanks, but is this by time?
The rule has the condition if it's between 8:30 pm and Sunrise it sets dim level to 15. Any other time it's regular.
You can have the default level be 15 and then if the time is between sunrise and 8:30 pm and the level =15, set it to 100. Then you're not relying on the physical switch to be the trigger but the switch level being =15.
Sounds like a good work around for that dimmer. I have a couple of others that are not Leviton that I'd like to get the rule working on. Maybe @bravenel can chime in on what the issue with the rule might be.
Thanks for your help Ryan!!
It does look like that is happening. I'll look into it...
1 Like
Bruce, it's the weekend! A holiday one at that!
Thanks for looking in to this. I'm amazed at the response from the Hubitat team. Simply awesome.
And Ryan, don't think I'm not grateful for what you offered as well. Thank you for giving your insight.
I can confirm there is a bug in RM. Good catch!
4 Likes
I swear, I'm so low on knowledge on this stuff I never thought I'd create something that would find a bug. Blind luck I guess. LOL
Fixed. Will be in the next release.
Thanks Bruce!
The way I handle this is with variables, have a variable in the background that contains the value at which you would like the dimmer to turn on. (This value can of course be changed by anything in rm) then when the dimmer turns on, have it's level set to the variable instead of to any number in particular. As long as the variable is set correctly your dimmer will always turn on at the desired level.
Can you please share how you set the dimmer to the value of the variable? I am trying to do this and failing miserably due to my lack of understanding what the software wants me to select to achieve this.
Thanks,
Jon
1 Like
I was interested in this too, I found this in the RM4 docs
Global Variables Can Be Used for Level/Color
Global variables can be used in actions that set dimmer or bulb levels, color temperature, or hue/saturation values. To use a variable in this way, include it with %global-variable-name%. In each case only a "Number" global variable is allowed, and it is not range checked
I read this, too. I can't figure out how to set the dimmer I am turning on to the value of the variable. Not sure which options to choose in RM4 when making my rule for the light to set the correct level.
Thanks,
Jon
Setting the level for most dimmers will also turn on the light. Unless the light allows for Level Prestaging (Sengled native hubitat drivers) or a Default Level setting (GE Motion Dimmer or Leviton Dimmers) the load is going to be turned on when you set the level to the light. That's just the way the firmware works. There's no way to get around it with variables or anything else.
1 Like
This is true in a sense, but what I was saying is when the condition arises where you want to change the turn on value of the dimmer you don't change the dimmer level at all, instead you change the value of a variable, then when you turn on the dimmer you turn it on at the level of the variable, thus every dimmer turn on is to the desired level. Because you never set the value of the dimmer unless you want the light on (only the value of the variable) the light won't turn on inappropriately.
Here's an action in a rule I have all you have to do is put %variablename% as the level you want to set the dimmer to. You'll also need a different rule which sets the variable in the conditions at which you want the dimmer to start turning on at a different level
It doesn't work that way. When you turn on most dimmers they will immediately ramp to their last set value. Only dimmers with prestaging or default values will not do this. All setting your variable does is lower the light after its turned on. So, if your variable is 10 but the light was last on at 100, the light will come on to 100 then dim to 10. There's no avoiding that.
Sure I guess it's just a difference in interpretation of the question, I thought what he wanted was to have the level become the relevant value when he turns it on, not necessarily at the same instant, but in general
It doesn't help you to store that value in a variable vs set it directly in the rule.
