The latest update for the Aqara FP400, firmware version 0.62 Zigbee, caused issues with my Home Assistant setup.
I had to recreate all the entities and update my automations because the occupancy entity was no longer available after the update.
I also had to manually update the “impact” entity and then update the related entities accordingly. This should not happen during a firmware update, especially when the update was released without any release notes or information about these changes.
For context, my system is configured with an Aqara Hub M3, with child devices connected via Zigbee and exposed to Home Assistant through Matter.
Aqara, @AqaraOfficial please take note of this issue. It took a considerable amount of investigation to understand what had happened and to restore the functionality in Home Assistant.
Firmware updates should not silently change or remove entities that are already being used in automations, without providing any information or migration guidance.
I hope this information can also help other users who have experienced the same issue.
The M3 Matter-bridge path is a useful detail to preserve in this report. Could you add the M3 firmware, Home Assistant Core and Matter Server versions, and clarify whether the old occupancy entity stayed listed as unavailable or disappeared while a new entry appeared? That would help distinguish a changed reference from a sensor entity no longer being exposed. I would not assume that other connection paths are affected from this report alone.
For other users checking automations after the update, compare entity IDs rather than just display names. Home Assistant’s documentation explains that changing an entity ID requires updating references in automations or scripts. Before deleting or re-pairing the bridge, I would record the old and replacement IDs and verify which zone each replacement represents. That keeps the mapping clear and avoids accidentally assigning an automation to a different zone.
Regarding the entities and the FP400 device, it was added as a new device with its corresponding new entities. The entities from the previous firmware (version 0060) remained unavailable and therefore unusable.
Using the entity filters, I removed the entities that were no longer available or usable and adapted my configuration to the new entities introduced by the current firmware.
I hope this is the information you were looking for.
One detail would help pin down the sequence: did you remove and re-pair the FP400 in Aqara Home, or re-add the M3 Matter bridge in Home Assistant, at any point during the update or recovery? In particular, did the replacement device appear before any re-pairing? That would help Aqara distinguish a change introduced by the update from a change during recommissioning.
Instead of updating all automations etc. to the new entities, you can rename the new entities to match the names of the old ones after deleting them. That way you don’t have to change anything else and also get to keep the history. It continues seamlessly that way
The point is that the device was recognized as a new device. I subsequently noticed that, with the previous firmware, the zones created in the Aqara Home app and then exposed to Home Assistant were separated and appeared as individual entities, whereas now they are recognized as part of the single FP400 device/entity.
@technotron007 Also, to get it recognized, I simply asked the Matter Server app to regenerate the device list, without removing the FP400 from the Aqara Home app.
It is true that I could have renamed the new entities, but I preferred to keep the old names. In the end, however, it is not that different from editing the automations.
After updating the FP400 Zigbee version from firmware 0060 to 0062, with the device connected to an Aqara Hub M3, I started getting these errors in the device settings:
“Installation Issue Detected
May cause the device to not work properly.
The device installation angle has changed, which may cause the device to not work properly. It is recommended to follow the guide to adjust the installation position.
To recalibrate the installation method, go to the settings page and select ‘Switch the Installation Method’.”
However, nothing has been changed regarding the installation or position of the device.
Even after confirming that everything is fine, the warning appears again in the device settings.
Yes, but not from an update. I got those error messages when I switched from Zigbee to Thread. The device was working fine with Zigbee. I didn’t change anything physically. Just wanted to switch to Thread. The only solution for my issue was to lay the device flat on a table, do the setup steps, then mount on the wall.