As far as I can tell you removed the ‘all’ logic option from automations V2.
In V2 I can trigger a ‘when’ when any condition is met, but not when all conditions are met (a sequence with 1s delays is not a replacement).
This is a significant regression and I have had to disable automations V2 until it is fixed. Please write here in this topic when this limitation is removed and feature parity with V1 is restored.
Hello @nzjrs
Please give an example of automation in 1.0 that cannot be done in 2.0. Screen
It would be a solution if the ‘When’ clause could be empty, because I only want to apply ‘All’ logic to the ‘If’, but I can not leave ‘When’ empty.
I think I have a solution to this issue, please post a screenshot of the automation you need. I faced a similar problem and solved it. I’m talking about 2.0.
I also plan to do a lesson on this issue.
I have many automations where the logic is something like
If A or B or C
turn on
elif (not A) and (not B) and (not C)
turn off
endif
Here is one such example
Now, translate at least one automation to 2.0 and take a screenshot here. I’ll finish the solution. There is a solution 
I already translated it to 2.0 and it duplicates it into the When block. Is this guarenteed to be equivalent functionality?
Are you suggesting I need to add a 1s delay in the when block?
A 5s delay seems like a regression compared to V1. I will just stay on V1 and let the bugs be fixed and evaluate this again in future.
I just don’t really have trust that software gets better over time. All these updates just seem to bring more problems which never get fixed. Between W100 lack of automations, T2 regression of automation functionality, S100 unavailability and now Automations V2 lacking features compared to V1 I have been only disappointed with Aqara this year.
I chose this brand because my day job is software engineering and I wanted a smart home system that is reliable and just works, I don’t want to waste time programming HA or mainitaining my own automation engine. Aqara used to be just good enough for me to believe this, but I am starting to doubt this now.
At least as long as they keep supporting V1 that will be OK I guess.
It’s your choice, you can always work on V1, it remains stable and familiar to experienced users. In my opinion, version 2.0 is a semi-professional version that allows for more flexible automation setup. Development and improvement of 2.0 will be supported constantly.
By the way, my first emotions when using 2.0 were very similar to yours🙂
I’m not saying V2 doesn’t have improvements, but regressions are unacceptable.
By the way, I also combine 1.0 and 2.0 in creating automations.
Interesting, thanks
This isn’t actually a flaw, but rather a consequence of the new structure. When can only trigger events, simultaneous triggering logic cannot exist. So if you need to implement your idea, configure it according to this logic: any one is turned on, and all are on, then…
This is not an Aqara limitation, it was merely an issue with the previous V4.3.7 firmware. Currently, this additional logic is no longer required.
Hello, the automation you created for the example doesn’t work. Check it out for yourself.
Thanks for telling me, they were down during testing. I’ll check and report back.
