So Homey misidentifies an Aqara device as being from IKEA, and that’s Aqara’s fault? 
It sounds more like a fundamental issue with how Homey deals with IKEA and/or Aqara devices. I know that for Aqara, they had to implement certain changes deep in the Zigbee driver, and it wouldn’t surprise me of those changes are somehow causing a lot of these issues.
Well, I would have attributed the error more to the fact that Aqara does not disclose its data, forcing other developers to reverse-engineer it to find out how the parts actually work. This almost inevitably leads to errors, which could probably have been avoided with proper documentation.
If Aqara hadn’t been so idiosyncratic, the bug would probably never have occurred.
Whoever is responsible for it, the bug is absolutely unacceptable in a smart home (especially if it has existed for so long).
If this inevitably leads to errors, Homey shouldn’t have offered an app for it 
Besides that, @Peter_Kawa has experience with these devices both with Homey and with better other Zigbee implementations, and came to the conclusion that this issue seems to be affecting Homey’s much more, which suggests it’s a Homey issue.
It’s a big red flag that you got that particular error with trying to re-pair an Aqara device, and one that Athom should take a closer look at.
As mentioned earlier, this issue is on our radar. Aqara, IKEA, and we at Athom are all aware of it and are looking into what is causing this issue.
Is there any positive news on this front yet?
It has now been six months since this thread was started. It would therefore be really appropriate to inform Homey customers about the progress of this bug fix! This matter is really extremely unpleasant, and I am slowly starting to think about selling all this Homey/IKEA/Aqara stuff.
Please be so kind as to let us know what the current status is!
Thank you!
There are no major updates since my last message. It remains a known issue related to the Zigbee/Thread chip we use, specifically when combined with IKEA and Aqara devices. We’re not the only platform affected by this, but unfortunately, a solution has yet to be found.
@Doekse OK, thank you very much! Even if the message isn’t particularly helpful for many customers in this situation, at least it’s a clear status message (which is extremely important!).
Are there currently any concrete indications as to where the error might lie or which device is responsible for it?
Hope this will be fixed soon or any hint how we can make the situation better by any different set up ?
After more than four months, I thought I’d check again to see if this serious Homey bug has been fixed. Is there any news that would restore confidence in the Homey and Aqara brands, or is this just the way it is?
