Could NAS backup status show the last successful write for each camera?

A recent report describes three Aqara cameras backing up to one NAS: two stopped transferring footage while the third continued, and SD recording still worked. That makes “camera online” a poor substitute for knowing whether each backup is current.

Could the NAS storage page show each camera’s last successful transfer, the newest footage time backed up, and any pending backlog or last error? I would also want a warning only after an expected transfer window is missed, so an event-only camera with no new footage is not flagged just for being quiet.

If your setup already exposes this information, where do you check it, and how do you distinguish “nothing new to back up” from a stalled transfer? This is a status-design question; I have not reproduced the reported fault.

3 Likes

@jamesfengyuyang That’s a really thoughtful breakdown of the visibility gap between “device is online” and “backup is actually healthy.” I haven’t seen granular per-camera NAS transfer timestamps or backlog counters exposed in the Aqara Home app today—the current NAS setup flow focuses more on connection credentials and SMB version compatibility rather than ongoing sync telemetry.

Your distinction between “quiet because nothing happened” versus “stalled despite having data” is exactly the kind of nuance that would make status indicators genuinely useful rather than noisy. For now, most of us are probably inferring health indirectly: checking the NAS folder directly for recent file timestamps, or noticing when SD card playback has footage that never appeared on the NAS.

If you’re willing to nudge this toward the product team, the best path is through official support channels where feature requests get properly logged. Contact the Aqara Home App Customer Service Team (Profile > Help & Feedback > Customer Service) or scan the QR code:


This will be more efficient. If you do not have an Aqara Home account, please click here to create a ticket.

Would love to hear if anyone else has found a clever workaround—maybe NAS-side scripts monitoring folder activity, or particular router logging that catches SMB session drops?