Good afternoon, Aqara.
There is a big (in my opinion) malfunction in automation 2.0.
I started running an individual heating system and was unable to transfer most of the automation from 1.0 to 2.0.
Automation description.
The room temperature sensor sends a signal to the relay (turn on) if the temperature in the room is lower than the set one. Additionally, it is necessary to ensure that the relay cannot be accidentally turned off (erroneously) (turn on the boiler) when the temperature is lower than the set one.
Fig. 1 (1.0)
If we transfer to automation 2.0, we get a variant in which all conditions in WHEN and IF are duplicated. To set the control temperature, you need to change the parameters in WHEN and IF, which is very inconvenient for the user (decreases efficiency, random error when replacing one parameter).
Fig. 2.
I draw your attention to the fact that the relay state in the WHEN parameters is selected in the mode ( (°°) constant control mode, Fig. 3a).
If I rework the automation in this form
Fig. 3
I get a simplified automation with a temperature variable in one sector, IF. The disadvantage of this version of automation (Fig. 3) is that it does not work in constant mode. If the relay is off and the parameters in the IF part at some point in time will satisfy the automation conditions, the automation in Fig. 3 WILL NOT WORK (will not turn on the relay).
The automation will turn on only when I make the On->Off relay manually, although in the relay parameters WHEN (°°) Fig. 3a.
My proposal for improvement 2.0.
When any change of state occurs in IF conditions, it is necessary for the automation algorithm to trigger a polling signal with the following sequence:
1- polling signal in the WHEN part for correspondence of ready triggers with (°°) (all triggers with (°) are ignored);
2- in the case of a ready trigger with (°°) in WHEN, polling continues in the IF area.
3- if all conditions are met, we start the automation.
I give another example with control of a relay group (heating control). The same automation. The boiler relay will not operate when all auxiliary relays change state to off.
Automation 1.0
Fig. 4.
Automation 2.0 is automatically translated, very large and loaded with duplicated conditions.
Fig. 5
Automation 2.0 has been redesigned, for which I propose to start it according to my algorithm.
Figure 6
I understand the current algorithm of 2.0, and therefore I propose to improve the 2.0 system. Please note that the described flaw in 2.0 is already quite often criticized by Aqara users. They say that this is a step back in some issues compared to 1.0.
I would be grateful for an answer to my question.
I also understand that the algorithm I proposed may not be used in 2.0 for technical reasons.
I am missing the “night” settings where you can set the start time to “sunset” and the end time to “selected time”. Example, start time “15 minutes before sunrise” and end time “23.00”.
Same with sunrise, start time “06.00” and end time “15 minutes after sunrise” (this is just an example).
Maybe the 2.0 developers will read this post and take our suggestion into account, @AqaraOfficial, pass on our request to the 2.0 automation developers.
A banal automation in which I want to control the absence of movement in a pair with the lamp on also does not work.
Fig 1
It will work if I set a delay of 5 seconds in WHEN and then everything is ok.
Fig 2.
You fixed this problem with relay control (On, Off) when the same states in WHEN and IF in motion sensors did not do this. I personally checked this problem.
The problem with automation, which theoretically should be cloud-based (using weather servers), in the settings it says that it is local automation. Automation 2.0. Request for explanation of weather conditions
Simple automation using time for one socket, now not local, socket is connected to gateway M2 (there is also gateway M3 in the house). Is this a bug or a new problem of 2.0?
Fig1,2.
Now I want to post some feedback and discussions from the forum.
1.
A feedback on using relay group control, such automations are logically simple in 1.0, in 2.0 it is public automation, it falls under the algorithm change that I proposed. Automation 2: Disappointing removal of feature - #7 by nzjrs
2.
This discussion shows that the simplest automation created in one automation 1.0 (motion sensor + FP presence sensor) is super difficult to implement in 2.0 (in one automation). To implement it, you need to make two automations 2.0. Believe me, I tried all possible options, none of them worked stably (I’m talking about one automation 2.0 for this case, not a group). Automation with multiple sensors - turning off funktion - #9 by migu17
