Building the mudroom automation took maybe twenty minutes of actual logic work and closer to an hour of fighting the app to find where that logic lived. Scenes, automations, and the scheduling rules for the U2 US switch all sit in slightly different menus, and I’ve lost track more than once of whether a behavior I’m seeing is coming from a scene, an automation, or a leftover schedule I forgot existed. Last month I spent fifteen minutes hunting for why the mudroom light was firing early, before I found a schedule from setup week that had nothing to do with the FP300 at all.
None of this is a hardware complaint. The FP300 reads presence exactly like it should. The cameras record cleanly. The problem is that Aqara built genuinely capable sensors and then buried the logic for combining them behind an interface that doesn’t match how people actually think about automation, which is “if this zone is active, do that,” not “go check three separate menus to find which one is currently in charge.”
I keep seeing device announcements, FP400 included, and my first thought isn’t “what will this sense,” it’s “where in the app am I going to have to go dig for it.”
Is this an app-specific complaint, or does everyone hit this once they cross a certain number of devices? Curious if six was my threshold or if it happens even earlier for people with a simpler setup.
2 Likes
Yes, it can be frustrating at times. I wish Aqara would build a desktop app or allow Browser access and fix translations issues. Don’t get me going on navigation issues. (I bite my tongue everyday…)
Some things simply make no sense so I use Apple Home or Home Assistant to complete the goals.
1 Like
Hello, I disagree with the statement about setting up the Aqara APP. The Aqara device setting algorithm is not a **personal computer ** that each user adjusts to their own standard. This is a much more complex system (device setting APP) that is fixedly recorded in the APP. The more complex the device, the more complex the configuration architecture. Please note that users in the Aqara APP are not cut off from access to the settings.
It would be possible to make 4 settings (the rest will be fixed by default by the manufacturer) instead of 20, but then the charm of the semi-professional Aqara program is lost.
Regarding error finding, this is the usual process of setting up stable, working automation, although I have been using the Aqara APP for 5 years, in a system where there are more than two or three components, there is always a risk of building a faulty automation 2.0.
By the way, no one blocked you from automation 1.0 in the APP, the algorithm and construction there are much easier than 2.0.
1 Like
Hello, your phrase shows the diversity of user approaches, it makes no sense to you, but someone else will be delighted. This is called full access to settings.
3 Likes