[MSR] Native fan capabilty

[toggledbits]

Set hours to zero first.

[gwp1]

@toggledbits Ok, that opened it up - thank you.

Maybe I'm using this incorrectly, however. I want to create a ruleset that is only in effect from October thru March annually between certain hours each day during that period.

2200 - 0600 ET daily, 10/01 - 03/31 annually.

[toggledbits]

@gwp1 said in every X days field uneditable:

I want to create a ruleset that is only in effect from October thru March annually

Actually, you want to create a Rule. A RuleSet is a collection of Rules.

Now, I have to read between the lines of your problem description a bit here, but I'm thinking you mean that you want a rule to trigger once per day from October to March? If that's the case, an Interval is not the way to go, IMO. I would use two Date/Time conditions in an AND group. The first condition would constrain the dates (i.e. "between 1 October and 1 April", assuming you want it to trigger throughout March"), and the second "after 00:00" (assuming you keep the default Follow output mode on the condition and its parent group). The second condition will only trigger once per day, whenever it can (i.e. if the system is down at midnight, it will trigger as soon as it comes back up).

If you want the trigger to happen at some other time of day, say 10am, just put that in the Date/Time after condition instead of midnight.

[gwp1]

@toggledbits I incorrectly correctly used ruleset as there will be a couple/three rules

So if I want it on between two specific times I would update what you show to

[toggledbits]

Yes, this should work. Just be aware that since your second condition spans midnight, the rule will set at midnight on 10/1 and reset at midnight on 4/1.

[gwp1]

@toggledbits what would be a better approach to ensuring it starts at 2200 EDT on 10/01 and runs thru 0600 03/31?

[tunnus]

@gwp1 just using one date/time condition and adding start & stop times to the first condition?

[gwp1]

@tunnus would that not create the condition of starting at 2200 on 10/01 and staying on until 0600 04/01?

That's not what I'm after. I'm after a daily window of hours for those months.

[tunnus]

@gwp1 you wrote "ensuring it starts at 2200 EDT on 10/01 and runs thru 0600 03/31?" so I got an impression you really wanted continuous operation. But if that's not the case, then why wouldn't those two conditions you showed in a screenshot (post #5) work? Have you tested that rule?

[gwp1]

@tunnus yes, the rule is working and @toggledbits indicated as such (that it would work) but he raised a potential issue regarding the crossing of midnight that I was asking about there being a better approach.