RM 4.0 Rule Questions and Optimizations

[bravenel]

You could simplify it even more:

IF (Time between 8:29 AM and 4:01 PM) On: Elliptical
IF (Time between 9:29 PM and 9:31 PM) Off: Elliptical

[jabecker]

@jabecker

Why not just something like...

Can't as the turn ON time is different on M-F vs S-S.

True. But the shutoff time is the same on all days. If it’s not 9:30 pm, the only other choices are times you want it turned on. It will only be triggered at the three times you specified in the trigger events.

[JasonJoel]

Ok, this is it for today. I have other toys I need to play with.

[erethington]

Did you ever figure this out? I am having the same problem getting a simple repeat to work correctly. I've tried it 3 different ways and still nope...

[Ryan780]

If you post a copy of your rule, we could help you get it working.

[erethington]

Thanks! I got my answer here actually (in case anyone else is searching too), wasn't triggering the rule correctly. Rule Machine - This is Frustrating the Heck Out of Me

[AdamV]

@bravenel s it possible to set a bulb colour based on a variable or based on another devices attribute?

[bravenel]

Yes. Hue, Saturation and Level of a color bulb can all be set from a variable. A variable can be set from any device attribute you want, and hence so could colour be using a variable as intermediary.

[AdamV]

Sorry I mean the opposite - I have a number in a variable, and I want to use it to set the hue of a colour bulb

[bravenel]

Yes, that works.

[AdamV]

I must be being stupid - I can't find where to do it. If I go to set colour there is no from variable option

[bravenel]

Just put %variable-name% into the field where it asks for the Hue value. This will work for most numeric value input fields in RM.

[AdamV]

Perfect

[AdamV]

when I try to do that this happens:

[AdamV]

actually - ignore that - I got it working!

[bravenel]

I bet you discovered that it is range checking the value. So if the variable contains an out-of-range value when you set it up, you get ** bad value **

[AdamV]

exactly

[matt.thaxton]

No, still haven't figured it out. I am having an issue with canceling a delayed action too, but I think it might have a similar solution. Look up canceling here, and I think a similar thing for repeats will work.

[Released] Rule 4.0

Rule 4.0 -- The new Rule Machine Rule 4.0 is the culmination of a journey in the transformation of Rule Machine. At once it simplifies and adds power, resulting in a fully generalized automation engine. The prior top-level organization of RM is thrown out, replaced by a simpler interface. The changes are described below, and how what was done in prior versions is now accomplished. Gone are Rules, Triggers, Triggered Rules, Actions and Schedules. Instead, you define what causes a rule to run…

[mcolson1590]

Having trouble with a rule. I'd like turn a lamp off at 10:05 if I'm away, otherwise turn it off after sunrise. We leave it on at night for one of the kiddos. It seems to always turn off at 10:05.

app:1332019-08-19 03:13:55.094 pm infobasementLampOff: Resumed

app:1332019-08-19 03:13:52.651 pm infobasementLampOff: Paused

app:1332019-08-19 06:50:00.960 am infoAction: IF (( Time is 10:05 PM CDT(F) AND Mode is Away(F) ) OR Time is Sunrise+30 minutes(T) [TRUE]) THEN

app:1332019-08-19 06:50:00.647 am infoAction: Off: basementLamp

app:1332019-08-19 06:50:00.578 am infobasementLampOff Triggered

app:1332019-08-19 06:50:00.542 am infobasementLampOff: Triggered at Certain Time

app:1332019-08-18 10:05:00.631 pm infoAction: IF (( Time is 10:05 PM CDT(T) AND Mode is Away(F) ) OR Time is Sunrise+30 minutes(F) [FALSE]) THEN (skipping)

app:1332019-08-18 10:05:00.409 pm infoAction: Off: basementLamp

app:1332019-08-18 10:05:00.352 pm infobasementLampOff Triggered

app:1332019-08-18 10:05:00.322 pm infobasementLampOff: Triggered at Certain Time

[BorrisTheCat]

@mcolson1590

It seems to always turn off at 10:05.

That's correct or at sunrise +30mins. Because that's what you have told to do. You condition does nothing because it's after the off.