Hello Aqara support.
I’ve purchased 10 of these devices and I can pair with Home Assistant & Google Home but these will not pair with Aqara.
I’m using Android to try to pair the device.
I’ve added to Home Assistant and tried to share from there and it still will not connect to Aqara Home.
I am at a loss as to what else I could try, other threads mention that this is an android issue and that iPhone hoes not have this issue. I do not have an iPhone to test.
Have you already tried removing the button from HA, factory resetting it, and pairing it directly to Aqara first? Android commissioning can sometimes be picky about the direction. If it works in Aqara, you can then share it to HA.
Alternative: If the buttons are stable in HA, you can actually expose them to Aqara using the “Matter Bridge” add-on for Home Assistant (instead of standard multi-admin sharing). Here is a guide: From Zigbee to Matter (part 2) (Don’t let the “Zigbee” title fool you; as the guide explains, you can use the HASS connector to bridge any entity, even scripts or virtual switches, to Aqara).
Hello John,
I’ve purchased 10 of these units and I’m going to try some more but the same thing happens.
I can pair to Google and I can pair to home assistant but it fails every time with aqara home.
The odd thing is when when pairing with Google home, it clearly uses the Aqara threat network because it mentions it when pairing.
My gut feeling is this is an issue with a Aqara.
Ah, I misunderstood! I initially thought the failure only happened when using the Multi-Admin code from HA, not during a direct attempt.
Your observation makes it pretty clear (more than just a gut feeling): If Google Home and HA can use the Aqara Hub as a Border Router without issues, the network itself is fine.
I would recommend opening a ticket with support to flag this.
In the meantime, as a temporary solution, you can use the Matter Bridge approach to expose the buttons from HA to Aqara.
Hello again John,
Well I’ve managed to commission my first button, I had to wait for the system to time out it then offered me another option to try to bind with the matter controller ( or words to that effect ) , this was successful.
I’m going to try another to see if this does the same.
I have two paired … but both were not smooth binding it. Which Aqara hub?
Hello I’ve M3’s, M200, M100, M2, E1 etc… you name it I’ve probably got one :o)
My primary matter controller is one of the M3’s
Ok, My solution for a quicker setup is as follows:-
I hope this help with others.
I can only confirm the “add via matter controller” with M3, I’m not sure about M100 or M200 devices.
Kind regards
Dave
That’s just a guess. But it sounds as if the commissioning process in your app isn’t working, so you’re using the operating system’s own commissioning process instead.
It might be a good idea to get someone from the support team to take a look at it.
it won’t work with android app. You can pair them by using ios app, I contacted support but they saying that it’s working
but it’s not working at all 
How long it takes to time out? what a weird workaround hah
I will try now to time it out and will update if I can pair it with m100 hub with android app.
Edit: I can’t make it with m100 hub
I think only the M3 can do this, or perhaps the M200 too but not sure.
I tried to do this without batteries, but it doesn’t work as well with the m100 hub. So I can confirm that both methods wont work for m100 hub.
I would open up a support case with Aqara.
I did, they agreed today that it’s not pairing with android, but I had to unpair buttons, then try to pair them again to create new logs, their log system is really bad for troubleshooting. They always can’t recreate a problem because they ask for authorisation after opening a ticket and they have only access to newer logs, eh.
Hello David，
Compatibility with the Matter setup process may vary across different Android versions and manufacturer-customized systems (such as MIUI, One UI, etc.). In addition, network optimization and battery optimization policies may interrupt or affect the pairing process.
To help us better identify the issue, could you please share a screenshot of the pairing failure screen in the Aqara Home app (including any error messages or the step where the process gets stuck)? If convenient, please also provide your phone model and Android system version. This information will help us further analyze the cause.
Hello xu_zhang
My phone is a Pixel 8 Pro
Android Version is 16
It generally get stuck here even after 10 minutes
If I pull the battery and setup again it eventually times out to the next screen
I then select add via Matter Controller
Add the batteries and go through the process again.
I hope this helps?
I have a sneaking suspicion that this might actually be down to app permissions. It is possible that an Android update has reset the Aqara app’s permissions.
The fact that it works via the “Matter Controller” (which runs via Google Play Services with system-level privileges) but fails directly in the app is very suspicious. It strongly suggests that the Aqara app is effectively hitting a wall because it lacks a specific permission like Bluetooth, Nearby Devices or Local Network access that the system process has by default. Whereby local network access should work.
Alternatively it could be as xu_zhang-a1163 suggested where network optimization and battery optimization policies may interrupt or affect the pairing process.
I have turned off battery optimisation, and all permissions are granted for aqara app.
Yeah, I can pair Ikea devices with google home app and with aqara thread network.
