Aqara automation 2.0 feedback

[Thorioum]

I got into the Aqara ecosystem after searching for a built-in solution for my smart home setup, instead of just relying on additional switches and smart bulbs with IKEA. After having added 40 devices to my Aqara M3 hub (switches, camera, plugs, thermostats), here are a couple of suggestions how the automation module could be improved via software updates:

• Add an action to trigger an automation from another automation (not just turn them on/off). As scenes currently can’t have conditions, this could make complex use cases easier.
• Add an action to create and adjust variables. True/false, number, text, etc. Then another condition to check for the value of a variable, to benefit more complex automations. An ugly workaround is technically possible by treating useless automations as true/false (on/off) variables.
• Extend Outdoor Weather > Sunrise/Sunset triggers to be able to define minutes before/after this event.

I’m happy to share other feedback if this was useful, as there are quite some inconsistencies in the app with user interface and the navigation tree of certain device settings.

[gafich10]

@Thorioum

Extend Outdoor Weather > Sunrise/Sunset triggers to be able to define minutes before/after this event.

Hello, this function is described in this lesson. Fig. 6,7,9.

Automation 2.0. Lesson2. Advanced settings "..." (Execution time, delay of conditions, reversal of conditions) is

Lesson 1 (continued) Automation 2.0, lesson 1 (continued), description of the algorithm for transitioning automation 1.0 to 2.0 Good afternoon. Some users do not pay attention to this symbol next to the automation conditions “…”, these are very important updated components of automation 2.0. Let’s consider the conditions that are hidden under the “…” icon. Fig1 [IMG_20250919_091201] CONDITIONS “…” WHEN. The first condition, the time interval for executing the conditions. In this setting,…

[Thorioum]

@gafich10 I believe that’s not the same?

My understanding is that “acting time” only defines the time in between the automation should run if the trigger condition is met. But I’m not looking to limit the automation to only run from sunrise to sunset, but to trigger at sunrise, or 15 mins before sunrise – and the latter is not possible.

I hope this clarifies!

[gafich10]

Hello. I completely agree with you, the WHEN section does not have a trigger that can be triggered before or after sunset/sunrise. To trigger this condition after sunset, sunrise, in the THEN section I add a time delay. I also support you with the proposal to add virtual switches in automation 2.0.

[gafich10]

This may sound absurd. But I use the W100 temperature sensor as a permanent trigger in the WHEN section. I set the data transfer period to 10 minutes (you can use less if necessary). The sensor conditions are always met (e.g. above -20°C)

[moe313]

Really solid feedback, especially the idea of triggering automations from other automations and adding variables—that would make complex setups way more flexible. The sunrise/sunset offset is also something that feels like it should already exist. Hopefully Aqara picks some of these up, because the hardware is great but the automation side still has room to grow

[Caroline_Zzz]

Thanks for the advice, we’ll review it shortly.