Seems like there is some confusion about gateway versions and the difference between aqara and xiaomi.
Now following the smart home lineup for quite a while this is my impression of it’s history:
Important to know is, that Xiaomi has made a platform for different manufacturers to integrate their smart devices in one big ecosystem. For example Yeelight - they build the lamps, but integrate them with the Xiaomi protocol making them compatible with the MiHome App. Same for the vacuum robot, which is build by a different company (Rockrobo or so…). I guess Mijia might be similar…
This is also the case for our smart home devices. The first generation was built by Lumi. I don’t know if they rebranded to Aqara or if it’s a different company now but the newer devices are all built by Aqara.
Actually this is not the case. My gateway identifies iteslf with the MI IO binding (see here) as lumi.gateway.v3 and it’s the round one!
This is the square one @bartsnijder is talking about. I know, very confusing!
So to clarify:
- Round “Lumi” gateway: there are two versions (v2 & v3), which look the same and are round, probably the ones most people use here - I don’t know what the difference is between them
- Round “Aqara” gateway: the new gateway (supporting HomeKit) - this is not tested with the binding, brand new, and the community would appreciate any pioneer buying that thing and giving it a go with the binding and OH
- Devices, which are able to act as a gateway, for example the Air Conditioning Companion see here
Regarding support for the acpartner devices - If anybody has this device please do following:
Enable TRACE logging, make sure the acpartner is set up in your network and developer mode is on. Then trigger a discovery in OH PaperUI and log the result. The binding should send a message with { cmnd: whois } and every gateway answer. Then open an issue and post the log here.