Aqara wireless switch stops working and changes to unk_manufacturer/unk_model after each restart

[p-mitana]

The problem

I have one Aqara wireless switch (H1 EU) linked and a few automations using it.

Every time I restart Home Assistant Core, the switch stops working. It is changed to unk_manufacturer and unk_model. Also all automations that use it are reported as broken.

In order to fix the issue, I need to remove the switch from Home Assistant, then factory reset it, then pair it again and then update each automation by deleting and readding the trigger related to the switch. I currently have only one switch and it's already cumbersome and I already have a few more of them to install soon.

I think the problem started a few months ago, but I can't recall if it was after updating the particular version. Still, it wasn't there from the beginning when I bought the switch.

I use ZHA. I have another ZigBee device – a fingerbot – and this one does not have this problem.

There is a thread on the forum where two other users report the same issue: https://community.home-assistant.io/t/zha-aqara-switch-unk-model/760411/3

What version of Home Assistant Core has the issue?

core-2024.10.1

What was the last working version of Home Assistant Core?

No response

What type of installation are you running?

Home Assistant OS

Integration causing the issue

ZHA

Link to integration documentation on our website

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

Diagnostics information

home-assistant_zha_2024-10-07T18-51-27.704Z.log

During the log recording I installed the update to core-2024.10.1 and the system restarted.

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 @dmulcahey, @adminiuga, @puddly, @thejulianjes, mind taking a look at this issue as it has been labeled with an integration (zha) you are listed as a code owner for? Thanks!

Code owner commands

Code owners of zha 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 zha 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)}}

---

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

[p-mitana]

I noticed that the issue did not show up recently when I restarted and during the lasted core update. Possibly some change in 2024.10.3 fixed it.

[Fabeuss]

I have exactly the same issue, this morning with the 2024.11.0 core update...Need to delete device, automation and repair H1...Don't understand, really frustrating

We're not alone : https://community.home-assistant.io/t/zha-aqara-switch-unk-model/760411/4

[p-mitana]

I also saw the problem back after updating to 2024.11.0. It definitely worked before when I restarted/updated a few times and now the issue returned. :(

[Fabeuss]

After removing switch from HA, waiting a few minutes to make sure the device is removed from the database, restart and re-pair the switch, I finally added a custom quirk for testing and it seems to work for the moment...Maybe you can try this. https://gist.github.com/xuxiaoqiao/6ed8dcb950f26337218d0507733970a0

[jeverley]

@Fabeuss, @p-mitana do you two encounter this issue when using the updated v2 quirk in https://github.com/zigpy/zha-device-handlers/pull/3564?

[p-mitana]

I haven't replaced any quirks or done any manual actions, but the latest one or two updates seemed to work OK for me.

[issue-triage-workflows[bot]]

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍 This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.

[jeverley]

I encountered this again last week when adding two new switches.

Fixed by removing and re-pairing, but it looks like the the underlying problem is still there.

[DanielBCoffaro]

Hello. I am also experiencing this issue. The switches worked for a short period of time and then switched to to unk_manufacturer and unk_model. I would really appreciate any help for knowledge you could provide.

[Thorn-hill]

Hi, also having the same issue, is there any progress? Having to remove, factory reset and add again every day is.. not fun.

[DanielBCoffaro]

I ended up switching to ZigBee2mqtt and buying a SMLIGHT SLZB. Nothing else I tried worked. It's been stable now for about a month.

[p-mitana]

Since I think a few versions I haven't encountered this problem again, but I can't tell which exactly resolved it. Let's see if it strikes back again at some point.

[issue-triage-workflows[bot]]

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍 This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.

[pergpau]

I have the exact same issue, and my H1 button turns into unk_model by unk_manufacturer on each restart, so removing and repairing isn't really an option. It started happening very recently, and was working fine until then.

[jwoodard80]

I seem to be having this same issue... however, it only seems to be the 6 button that I have.

Would love to know what is causing this and how to resolve it.

[Kinggrass]

Same issue here with the h1.

Home Assistant Core 2025.6.3 Home Assistant Operating System 15.2