Short answer
When FP2 zones change in the Aqara app but Home Assistant does not update, the usual fixes are to verify Aqara-side zone state, reload the local integration path, restart Home Assistant, or re-pair only after documenting existing entities and automations.
Next step
Symptoms this page covers
- New zones missing
- Old zone entities remain
- Presence events delayed
- Entity list stale
Likely causes
- Home Assistant has stale entities from the previous zone layout.
- FP2 zone changes were saved in Aqara app but not reflected in the local exposure path.
- HomeKit Controller or local discovery did not refresh after zone changes.
- Automations still reference old entity IDs.
Fix checklist
- Confirm the new zones work in the Aqara app first.
- Reload the relevant Home Assistant integration or restart Home Assistant.
- Check entity registry for stale FP2 zone entities.
- Update automations that reference old zone entity IDs.
- Only re-pair FP2 after recording current entity IDs and automations.
Avoid these mistakes
- Do not delete entities without checking which automations use them.
- Do not assume Aqara app zone names will map cleanly to Home Assistant entity IDs.
- Do not re-pair as the first step if a reload or restart can refresh the entities.
FAQ
Should I factory reset Aqara Presence Sensor FP2 first?
Usually no. First confirm the controller, hub, network, and integration path. Resetting too early can remove useful evidence about which ecosystem or Thread network currently owns the device.
What should I check before buying another hub?
Check whether you already have the required Matter Controller, Thread Border Router, vendor hub, Zigbee coordinator, and Home Assistant service. Use the linked calculator or diagnostic tool before purchasing extra hardware.
Can SmartHomeCompat guarantee this fix for Home Assistant?
No. These pages are based on official docs, product information, public compatibility data, and community issue patterns. They are designed to narrow the likely setup path and reveal missing pieces.
Should I use Aqara Hub, Matter, or a direct Home Assistant path?
Use Aqara Hub when you want vendor-managed setup and Aqara app features. Use Matter when cross-ecosystem sharing is more important. Use direct Home Assistant paths such as ZHA, Zigbee2MQTT, or HomeKit Controller when local control and entity exposure matter more.
Feedback
Help improve this compatibility data
Smart home compatibility changes quickly. Send a report, request a missing device, or flag information that needs another review.
Save the setup path, missing hubs, limitations, and next steps for later.
Tell us which device, hub, or ecosystem should be added to the compatibility library.
Flag outdated, incomplete, or unclear setup guidance so it can be reviewed.
Get a practical checklist for hubs, Thread border routers, Matter pairing, and fallback paths.