Ask for help: condition

[sprnza]

Hi there! Thanks for the project! I try to create my first automation with a condition. I've read a lot of related discussions but I'm not able to wrap my head around how conditions works in Easer. What I try to do is to check if there is no call going and to switch airplane mode at 23:00. I've created a profile "Switch Airplane mode on", a condition "Call" with no ticks near "Idle", "Ringing", "Ongoing" (I've tried varios combinations of those to no avail), an Event "23:00" with time set to 23:00 and a two scripts "Night mode starts" wich has no profile selected but has the Event "23:00". And a profile "Check if no call" with the profile "Switch Airplane mode on" selected, "Night mode starts" selected as Predecessor and the condition "Call" selected as condition.

What I get on the Pivot view is the scripts and the profile are lined up as expected but when the event is firing only the "Night mode starts" script gets the green dot but the "Check if no call" script gets the red one. What do I miss here?

Without the condition the script works as expected and airplane mode is being switched on correctly.

Also as FR: as soon as condition is like a "state" (is it?) it would be great to always have red/green dot appeared on the pivot view event the predecessor script is not run yet.

[renyuneyun]

Hi. Apologise for the delayed reply. It looks like you are generally doing alright. I may need to look into the logic inside Call Condition to see if there is any issue with it. What if you select everything for Call Condition, and then tick "reverse" in the relevant Script? This should mean the same as "not anything".

Also, you might want to use Time Condition for checking time.

As a hint for everyone: if there is a Condition and an Event for the same thing, always use Condition. This gives you more freedom afterwards if you decide to chain Scripts. Read this wiki page to learn more about this behaviour.