Lagging app - not matching actual state of devices

Problems with my setup started 3 days ago after I updated the M3 hub with the following SW:

I believe this could be something either with the cloud services or with the hub firmware.

BTW, motion sensors over zigbee work without any problems - update state immediately after movement detection.

Interesting thread. Has Aqara seen it?

I have the same issue with an M100 hub and W600 thermostats connected via Thread.

The app often doesn’t pick up the current temperature or the target temperature (set via Home Assistant). The thermostats themselves show the correct values.

Is there an option to manually update/query the values in the app?

1 Like

@Solmath @grzegorz_zajac

open support ticket and explain what’s going on plus give them link to that topic, maybe they will fix their app issues with updating status devices connected by matter

So here status of that device is wrong, it’s closed at this moment:


But automation was executed successfully, so hub knows what is the status of that sensor for 100 percent:



When you „enable LAN control” in the settings and your phone is in the same LAN that the hub is, you can notice the state of the sensors is updated immediately. That means the „local” automations fire without problems because they use the locally stored state, not the incorrect cloud state.

for me even if I’m on same local wifi states won’t update correctly in the app.
Is it feature only for m3 hub?

Do you have an option in Profile->Settings-> LAN Control? I have M3 hub but that settings is not in hub options, but globally on the App (btw I use iPhone)

It must be m3 hub function

So It is different on iOS. Or maybe app recognizes that M3 hub is there and enables some additional items in the settings page.


it’s from iphone, it is exclusive M3 hub option

1 Like