Aqara Hub M3 Matter bridge keeps getting discovered on HomeKit after any hub reboot

[Anto79-ops]

The problem

hello!

I'm using the Aqara Hub M3 solely as a Matter bridge to HA for Aqara devices. Its working well, except, everytime the hub reboots for updates (or other reasons), the hub shows up as a newly discovered device in HomeKit. I've always ignored the the notification and goes away, but a NEW notification comes everytime the hub reboots. For example, see these duplicate ignores for the same device:

thanks

please let me know if other information is required

What version of Home Assistant Core has the issue?

2024.10.1

What was the last working version of Home Assistant Core?

not sure

What type of installation are you running?

Home Assistant OS

Integration causing the issue

Homekit Bridge

Link to integration documentation on our website

https://www.home-assistant.io/integrations/homekit/

Diagnostics information

No response

Example YAML snippet

No response

Anything in the logs that might be useful for us?

No response

Additional information

No response

[home-assistant[bot]]

Hey there @bdraco, mind taking a look at this issue as it has been labeled with an integration (homekit) you are listed as a code owner for? Thanks!

Code owner commands

Code owners of `homekit` can trigger bot actions by commenting: - `@home-assistant close` Closes the issue. - `@home-assistant rename Awesome new title` Renames the issue. - `@home-assistant reopen` Reopen the issue. - `@home-assistant unassign homekit` Removes the current integration label and assignees on the issue, add the integration domain after the command. - `@home-assistant add-label needs-more-information` Add a label (needs-more-information, problem in dependency, problem in custom component) to the issue. - `@home-assistant remove-label needs-more-information` Remove a label (needs-more-information, problem in dependency, problem in custom component) on the issue.

_{^{(message by CodeOwnersMention)}}

---

homekit documentation homekit source _{^{(message by IssueLinks)}}

[home-assistant[bot]]

Hey there @jc2k, mind taking a look at this issue as it has been labeled with an integration (homekit_controller) you are listed as a code owner for? Thanks!

Code owner commands

Code owners of `homekit_controller` can trigger bot actions by commenting: - `@home-assistant close` Closes the issue. - `@home-assistant rename Awesome new title` Renames the issue. - `@home-assistant reopen` Reopen the issue. - `@home-assistant unassign homekit_controller` Removes the current integration label and assignees on the issue, add the integration domain after the command. - `@home-assistant add-label needs-more-information` Add a label (needs-more-information, problem in dependency, problem in custom component) to the issue. - `@home-assistant remove-label needs-more-information` Remove a label (needs-more-information, problem in dependency, problem in custom component) on the issue.

_{^{(message by CodeOwnersMention)}}

---

homekit_controller documentation homekit_controller source _{^{(message by IssueLinks)}}

[Jc2k]

This is probably a bug in the aqara hub. We have seen it before where a device changes its unique id every time it reboots, and only saves it to its flash memory when you pair it. When you ignore it, you are ignoring that id, and because it's temporary there's nothing we can do.

The easiest fix in that case is to pair the aqara to something, even if you don't plan to use it over the HomeKit protocol. That could even be HA (either a throwaway vm or I guess pair it to your main HA, turn the hub off, remove it from HA, restart HA for good measure/delete any stale metadata, turn the hub back on).

[Anto79-ops]

thanks for your comment!

I could try that. So, just to confirm. Next time it appears in HA, I will:

1. Adopt it via HomeKit and let it fully get integrated
2. Unplug it
3. Delete from the HomeKit integration
4. Restart HA
5. Plug the power back on

thanks