Three timestamps to distinguish a stale sensor value from a bad reading

When an Aqara sensor looks wrong, I first separate accuracy from freshness. A high value and a stale value are different failures; comparing only the numbers can hide that distinction.

For one noncritical sensor, I record four things at the same time:

  • the Aqara Home value and its last-updated time;
  • the Apple Home or Home Assistant value and whether its timestamp changes;
  • another channel from the same device that is known to update;
  • a control reading from a nearby device after both sit in the same position for 20–30 minutes.

If Aqara Home changes but the bridged value freezes, I investigate the mapping or bridge path. If every channel updates except one, I focus on that channel, its sensor, or the app display. If all channels freeze together, I check power and connectivity before calibration. A constant zero in one ecosystem and a high last reading in another may be stale or unsupported data, not agreement.

Before resetting anything, I capture the firmware, hub, integration path, placement, and screenshots with visible times. Then I change one variable at a time. Which Aqara devices expose useful per-channel timestamps in Aqara Home?

2 Likes

I might add that Aqara sensors usually refresh its state and readings when you click the pairing button on them.

The single press checks/refreshes the connection (you will hear “Normal link confirmed” from your hub) and it also updates the values. If they are the same as before, then they were just stale.

1 Like