Dashboard not showing the correct status

Aqara Products
,
1

I control many of the lights in my house through automations and scenes. That part works beautifully. What doesn’t work so well is the status shown on my dashboards in the iPhone app — and on the iPad that’s mounted on the wall. The light is on, but the dashboard happily insists it’s off. I have to tap the tile first to force a status refresh, and only then can I switch the light or group off through the app.

Is anyone else seeing this behavior? Or better yet… does anyone already have a fix?

Check this out: Topics to remember – Bookmark and keep coming back!

Always remember: “If your car is smarter than your home… you’re driving into the future while living in the past” :red_car::house:

3 Likes
2

Yes this happens a lot to me especially with device/light groups

3

Same thing here. Group and single device. It happen at ramdom time.

4

Yep! That’s why I never use the iPad app and wish we could simply use a web browser that would sync with everything. It’s frustrating

5

Yes, same thing here. My android tablet dashboard displays maybe 2 hrs old data, very annoying. Auto refresh e.g. once a minute should not be that hard…

6

Now I think of it - if it’s a background/async process, it may work, but then it may be killed or just die because of an internal error.

To rule out killing the background job - do you use power saving/low power mode?

And iOS users: did you disable background refresh of the Aqara app?

1 Like
7

Background refresh on IOS? Can you show me where to find that feature?

1 Like
8

Settings > General. Scroll a bit, it should be under “Keyboard”

2 Likes
9

Got it … but it was enabled …. So my dashboard showing also more often a wrong status. And it’s also when I open it - then it refresh the current status

1 Like
10

I’m currently experimenting with the Aqara Open Platform API, and I believe the issue is not related to iOS or the app, as I am also receiving incorrect status information from Matter devices via the API.

traits: [
                {
                  parameter: {
                    readable: true,
                    type: 'Bool',
                    subscribable: true,
                    writable: true
                  },
                  traitId: 32920,
                  time: 1769953185433,
                  value: true,
                  traitCode: 'OnOff'
                }
              ],

The OnOff value is true, but the device is still turned off. After switching back and forth a few times, the value is then correctly displayed as false.

3 Likes
11

I’ve also noticed some discrepancies of statuses with Matter. I have programmed a custom ESP32 dimmer, connected it to the M3 as a Matter device and the app sometimes shows incorrect on/off state of my custom dimmer, especially when the device loses wifi connection or the M3 fails to change the state.

I’ve also added the dimmer to HomeKit via the Matter pairing code from the Aqara app and HomeKit usually is correct (unless I reboot the dimmer, but it’s probably a bug of mine).

1 Like
12

Cool, programming my own Matter device, I have to do that :grin:

From what I can see, this issue specifically affects the Aqara Home App (both iOS and Android) and the Aqara Open Platform API. Interestingly, my integrations with Apple Home and Home Assistant remain unaffected and continue to work as expected.

If I’m interpreting the diagram from the official API documentation correctly, it seems the app relies heavily on fetching and pushing device statuses through the cloud:

image
image810×380 29.1 KB

The diagram illustrates how the AIOT Cloud acts as the central hub for the official app. If there is a bottleneck or a sync error at the cloud level, it explains why the native app is struggling while local integrations (like HA) might still be snappy.

I can definitively confirm that this occurs with my Matter over WiFi devices. I haven’t noticed it as much with my Matter over Thread devices yet, though I can’t rule it out completely since I primarily control those via Home Assistant.

If we can gather specific details, such as the device models and connection types involved in the failures, we can provide Aqara with a concrete, actionable bug report. A well-defined technical issue is something a developer can solve, whereas a vague symptom usually just sits in a queue.

@RudyK @david @Marc3k @srl77411 @asibjarna @DEChrisE
I would be grateful if you could provide the details of your specific setup.

1 Like
13

I currently have no third-party Wi-Fi or Matter devices.

I use multiple hubs throughout my home, generally grouping hubs by room to reduce single points of failure and improve redundancy.

In total, I have 20 hubs (E1, M2, M200, M3, M100, G5 Pro) managing 248 devices, distributed across those hubs. I also have several P2 Matter motion sensors.

All hubs are shared with Home Assistant via Matter (Matter bridging).

Over the years, I’ve noticed a change in behaviour: there is now a slight delay in light state confirmation in Home Assistant when using Matter. Previously, state updates were effectively instant. Now, while the light itself turns on immediately, it takes around one second for the state to update in Home Assistant.

I’m wondering whether this delay is due to:

  • the increased number of devices, or
  • some form of cloud-based confirmation occurring before the state update is reported.

This delay seems to affect lights specifically. Door and window sensors still update their state immediately in Home Assistant, despite also being exposed via Matter bridging.

2 Likes