Smart Automations 2.0: am I wrong or not?

Developer Hub
,
1

Please keep in mind that English is not my native language, Dutch is.

Lets start simple with just two devices; an Aqara hub and a door and window sensor and create two automations.

Automation A:
When:
Trigger = door and window sensor - option = Open
IF: …
THEN:
Acion = Send a message

Automation B:
WHEN:
Trigger = door and window sensor - option = Is open
IF: …
THEN:
Action = Send message

Now, switch off automation B

Open the door or window with the sensor and a message will be sent.
Close the door or window with the sensor and no message will be sent.
Automation A is working correctly.

Now, switch of automation A and turn on automation B

Open the door or window with the sensor and a message will be sent.

THIS IS WRONG.
In automation B I’m asking for the status of the sensor (is it open or closed) but I am not telling it when to run.
Automation B should not run at all.

Both automatons are giving the same result after opening the door or window and that is confusing.

Am I wrong here?

In your reply please focus on the WHEN section and how it works or should work in your opinion, otherwise it could get complicated very soon.
Workarounds are not the point here.

2 Likes
2

Hello, please make a screenshot of the automations. In addition to your question. Thank you.

1 Like
3

image
image1170×1273 72 KB

Hi. He wants to know why both “Open” (type: event) and “is open” (type: status) are triggers in the WHEN block. Neither makes sense. Personally, I would say that only the event trigger in the WHEN block and the status trigger in the IF block make sense.

2 Likes
4

@JohnD That’s my point indeed.
In addition:
Automation B should not run because “is open” is a status and not an event.

1 Like
5

Hello, to explain, I will use two sensor conditions. (°) - instantaneous, one-time, an event occurred in time. (°°) - permanent, this is a state that is not instantaneous but includes the moment of triggering (°). In mathematics, you can write it like this, (°)=[(°)] and (°°)=[(°);(°°)]. Based on my description, your automation A and B are working normally (B=A).
I agree, in automation 2.0 there is a problem with the initialization (triggering) of (°) and (°°), this condition currently works as an instantaneous WHEN for the “Run anything” selection (°), and in the “Run sequence” selection as (°°).

1 Like
6

I always use the status (°°) (for example in 1.0) in conjunction with another condition, another sensor or relay state. You know, when you give 1.0 two conditions (°) it says “Fix automation”, then you change (°)->(°°), this status (°°) is just for such conditions (example for the opening sensor).

1 Like
7

image
image1170×2060 144 KB

Thanks for the explanation, now I understand that both types make sense in “Trigger in sequence”. My automation doesn’t make sense, but it works.

2 Likes
10

It makes sense, paired with a motion sensor we get a good automation that can control the state of the process open/closed/open/motion THEN.

2 Likes
11

I think your example is also a problem of imprecise or bad english translations. Open vs Is open, is closed, etc. The English translations have always been average.

2 Likes
12

@nzjrs Yes I agree.
Don’t get me started about the translation to Dutch.
They translated “Save” to “Redden” which means in English “to rescue”. It should have been “Opslaan” which in English is “to store”.
There are much worse translations to Dutch in the app so I have gone back to English after a good laugh.

2 Likes
13

Thank you for your feedback

14

@Jericho-Yao Well, that feedback in my post above wasn’t very helpful at all, was it?

I seriously want to help you to make the translation to Dutch better.
There are probably more who want to help.

Just tell us how.

2 Likes