When an Aqara accessory disappears from Apple Home but still works in Aqara Home, I try not to reset or re-pair it immediately. A three-layer check is usually faster:
- Device layer: confirm the accessory is online and responsive in Aqara Home.
- Hub/bridge layer: confirm the Aqara hub or Matter bridge is still visible and identify whether other accessories exposed through the same bridge are also affected.
- Controller layer: check whether the problem is limited to one Apple device or appears across the whole Home.
If only Apple Home is affected, I restart the controller or hub before touching device pairing. If Aqara Home is also affected, I look at power, Zigbee/Thread connectivity, or the accessory itself. In a larger setup, recording which bridge exposed each accessory makes shared failures much easier to spot.
What is the quickest signal you use to decide whether a missing accessory problem is at the device, hub/bridge, or Apple Home layer?
1 Like
Hi there.i do not know how an device disappear from apple home app other that the user made an mistake and erase it but some zigbee devices are there but not showing on the main page like Aqara Magic Cube pro in my case I had to turn on “add to home view” but it was in the room I place it but not on the home page.
if an device goes offline on apple home app check :
-internet connection
-apple controller (if there are multiple apple devices set one as controller)
Now if an devices goes offline on Aqara app you need to see why and check again :
-internet connection so the hub doesn’t loose his connectivity and the signal should be strong or at least excellent if is low then devices could go offline many times per day.
-hub power supply as if an hub have poor power supply also makes child devices to go offline.
-make sure everything is up to date.
There is not an easy way to troubleshoot this.
1 Like
I have a health check automation set up in Home assistant that is triggered based on 3 trigger types. While this doesn’t answer your question directly, it is handy for me to get these SMS alerts and gives me a heads up something is unavailable or not working. I had Claude generate the below summary based on my process documentation.
2. HA Health Check
Automation: automation.atm_ha_health_check_on_update_install (name is a bit dated — it does more than update installs now)
It has three trigger types:
- Weekly — NAS cron, Sunday 05:00.
- Post-update — Core/OS/Supervisor/Matter Server update entity flips
on→off.
- On every HA reboot —
homeassistant: event: start trigger. It fires the moment HA finishes starting, then an 8-minute delay, then runs the check. (Added 2026-07-11 because a plain state-trigger on the update entities structurally can’t catch a transition that happens during the restart it also causes.
Once triggered, a NAS-hosted Python tool SSHes over (restricted key, forced command) and runs six checks:
- Duplicate entities
- Unavailable/unknown entities
- Watchman report (script validation)
- Config validation
- Unused automations
It writes a dated report, updates a dashboard sensor/card, and pushes one iOS notification ([Weekly check] or [Post-update check] — silent when clean on weekly runs, always notifies on the others).
2 Likes
@coccolino_26, the distinction between an accessory being hidden from Home View and actually being offline is important; checking the assigned room and “Add to Home View” can prevent an unnecessary reset. @Outburstin, your health-check approach adds a useful fourth layer: monitoring. Separating weekly checks, post-update checks, and delayed checks after Home Assistant restarts makes sense because each catches a different failure pattern.