'it is after' not the same as in v0.8

---

Simple rule with it is after xx:xx would ALWAYS be true if it is AFTER the specific time in v0.8.
You could activate a rule on 22:00 while the the rule itself had it is after 10:00 and it would be true (obvious, off course).
But in v0.9 the rule is only true when system time changes to after the specific time.

Example:
When current time is 21:33 and the rule is it is after 21:34 the rule would be executed at 21:34 , but creating/activating the samen rule on 21:35 (with the same 24:34 trigger in the rule) is simply not working (anymore).
Bug or design?

edit: Simple rule with it is before 22:00 doesn’t seem to do anything as well

it’s a feature no bug
i started a feature request a while ago to trigger rules manually. imho it’s a nice mockup.
so feel free to vote. maybe @sweetpi can do this somehow if there will be some more votes …

https://forum.pimatic.org/topic/706/trigger-rule-manually

@leader21 Why is it a feature? It worked like expected in 0.8 but changed in 0.9
Th entire it is after is now the same as it is.

To be honest, I don’t understand why it shouldn’t work as it did in 0.8
The option for it is after is great to handle stuff whenever something becomes true AFTER a certain time.

But it is geeting stranger:
Rule
WHEN it is after 08:00 and lamp is off THEN turn lamp on
Now, when you create this rule and a moment LATER than 08:00 while the lamp is off, nothing happens. Even if you manually activate the rule, nothing happens. But … if you turn on the lamp and then turn it off again … the rule kicks in?!

IMHO it would me silly to create extra rules to trigger a other rule for something that worked as expected in the previous version

i will let sweetpi have a look.

Would be really great, thanks,
I have several devices with rules like WHEN it is after xx:xx and bla and bla THEN turn device on that now won’t work if something is valid after the specific time.

Any news on this bug/feature?

sorry … we discussed it internally and @mwittig told that if it is after xx:xx is not a trigger but a condition.
i am still a little confused about that …

That’s strange, because if I have this rule :

WHEN it is after xx:xx and device is off THEN turn device on the device will be turned on at the specific time. It the device is turned off the same rule will turn it back on again.
However, if you change the time (or create the rule) and it is allready after that time, the device will not be turned on. But when you turn it manually on and off again the rule will kick in and turn it on again.

Not consistent if you ask me

Hey, have the same “issue” right now. I don’t know how to get my heating rules configured failsave now.
In 0.8 it was easy to use if its after ...

Now I dont see the point of actually having expressions like that. You can simply use when its 20:00 because thats the only time the rule triggers.

What are the options? I want to have a rule that works even if the pi gets a restart or something else.

what about when it is after 22.00 and it is before 6:00 then ...
that triggers the time between 22:00 and 6:00

@leader21 said in 'it is after' not the same as in v0.8:

what about when it is after 22.00 and it is before 6:00 then ...
that triggers the time between 22:00 and 6:00

thats the point. It won’t. Only on 22:01. On v0.8 it triggered everytime in within that time span.

hm … well yes, when the pi or pimatic is restarted, the rules are not triggered anymore.
that’s new in v.0.9

what about somnething like that
when every 1 minute and it is after 22.00 and it is before 6:00 then ...
thi should check the rule every minute.

if this does not work with your then part, you might use a placeholder varible
when it is after 22.00 and it is before 6:00 then set $placeholder = "true"
when every 1 minute and $placeholder = "true" then do something ...

The biggest problem is using state of devices in such rules. It’s not working as it did in 0.8

@leader21 said in 'it is after' not the same as in v0.8:

hm … well yes, when the pi or pimatic is restarted, the rules are not triggered anymore.
that’s new in v.0.9

what about somnething like that
when every 1 minute and it is after 22.00 and it is before 6:00 then ...
thi should check the rule every minute.

if this does not work with your then part, you might use a placeholder varible
when it is after 22.00 and it is before 6:00 then set $placeholder = "true"
when every 1 minute and $placeholder = "true" then do something ...

when every sounds like a good idea. I will try that By the way, is for x minutes still working?

@leader21 every x minutes did the trick! thank you! Now everything works perfect.

nice to hear

I also had to adapt some rules but the combination

when it is after 22.00 and it is before 6:00 then set $placeholder = "true"
when every 1 minute and $placeholder = "true" then do something

also works in one rule
when $some_variable = 1 and it is after 08.00 and it is before 22:00 then do something