Rule condition shows TRUE in UI but Rule never transitions to SET — survives full restart

[christian_fabre]

Summer Time : fonction interval
Version reactor 22028.
We changed the time this weekend: summer time.
The interval function doesn't seem to take this change into account

[christian_fabre]

[gwp1]

@christian_fabre If I'm understanding this correctly, your expectation is that the triggers would update with the time change?

You don't state what version of MSR you're using currently - version 22080 has a new DST (Daylight Saving Time) toggle in it. From the release notes:

SystemController: A dst (boolean) attribute has been added to the reactor_system>sun (Sun Information) entity; it will be true when Daylight Saving Time is in effect, false otherwise.

[toggledbits]

@christian_fabre The intent of the Interval condition is to fire on a regular, periodic basis. Adjusting the period for DST changes so it fires at particular times of day is not consistent with its intended regularity/periodicity. From the perspective of actual time in computing terms, DST is only a change to the representation of time. The passage of seconds (or any fraction thereof) is a continuous function within the system, unaffected by DST, and that extends into Reactor. That, too, is why the condition refers to its base as "relative to" and not "at time".

Doing something every 7th day is more often handled with Weekday conditions (January 1, 2021 being a Friday for reference), coupled (by AND) with a Date/Time condition (after operator) to trigger at (or as soon as possible after, if the system is rebooting at that moment, for example) a particular time (8pm in your case).

[christian_fabre]

Thank you for your answers.
I modified as you suggest and it seems more coherent to me.
On the other hand, I also have 2 recurrences every 2 weeks, in turn:
Wednesday 1--> Action1,
Wednesday 2--> Action2,
Wednesday 3--> Action1,
Wednesday 4--> Action2,
etc...
I don't see how to do...

[toggledbits]

For that you could still use an Interval, in an AND group with a Date/Time condition using the after operator at your desired time of day. On the Interval condition, set the relative time to midnight and the delay reset option to stretch the pulse out for the full day, 86400 seconds. So the Interval, when triggered (at midnight), will stay true all day, and the AND'd Date/Time condition will take care of triggering at the right time.

That method could be applied to any interval of n>1 days universally, including that weekly in your original post. I gave you a special-case solution for weekly intervals above, but this would be the more general solution.

[christian_fabre]

tthank you.
I had thought about it but I didn't want to use the interval function anymore.
Could we also have a choice of week number?

[toggledbits]

Tell me how you would use week number.

[christian_fabre]

the previous example: for a recurrence of 2 weeks:
even week number and Date/Time condition --> Action 1
odd week number and Date/Time condition --> Action 2

[toggledbits]

Keep going. Tell me what your trip through the UI would look like in configuring such a thing.