My understanding has been that certified Zigbee 3.0 compatibility means that the 'incompatible parent' issue should go away for these devices, but I had to refresh my memory as I wasn't sure if a certified 3.0 hub needed to be part of the mix (good news, it does not). I found a good summary on TI's support forum, excerpted below. So these should join seamlessly with HA 1.2 compatible routers.
"Here is a full backwards and forwards compatibility list between Zigbee profiles:
A ZigBee Light Link device can join a distributed ZigBee 3.0 network using either classical or touch link commissioning (if supported by the network)
A ZigBee Light Link device can join a centralized ZigBee 3.0 network which does not require key exchange or install codes
A ZigBee Home Automation device can join a ZigBee 3.0 centralized network which does not require key exchange
A ZigBee 3.0 device can join either a ZigBee Light Link or a ZigBee Home Automation network using classical commissioning
A ZigBee 3.0 device can join a ZigBee Light Link network using touch link commissioning
A ZigBee 3.0 device can join a ZigBee 3.0 network with any trust center policy
A ZigBee 3.0 device can not join a ZigBee Home Automation network using touch link commissioning
A ZigBee Home Automation device can not join a ZigBee 3.0 distributed network"
Yes it should, and it's especially important to note that these new Aqara-branded devices are officially ZigBee 3.0 certified while all previously released devices only came with an unofficial claim of ZigBee HA 1.2 compatibility.
Nevertheless, I am only cautiously optimistic, because Lumi's past track record shows a real propensity towards using non-standard implementations, which, as I understand it, could still pass certification with "manufacturer-specific" data formats for messages.
I am also only cautiously optimistic because with ZigBee certification and HomeKit compatibility, these new products may land up being sold through normal North American / European / etc. retail supply channels and as a result, be priced accordingly (significantly higher).
Nice find. I wouldn't personally consider the smoke detector. The Nest Protect is just too good, but the VOC sensor is intriguing, although not something I personally have a use for.
They sure have some serious air quality issues to deal with over there. They're paying the price for the massive amount of industry polluting their air in manufacturing the products we are buying.
It will be interesting to see how the VOC works out.
I've been working with the Bosch BME680 (which includes a VOC element). The VOC sensor is apparently not a stable device. The Bosch sensor uses a proprietary "self calibration" algorithm. With this there is still plenty of drift.
I've become disillusioned with VOC sensors (I've tried the AMS sensor with similar results). So for now I'm going to rely on my nose (which doesn't need a special display).
I also bought nest protect and nest cameras before HE and trying to keep things local and off the cloud.
Initially they worked well until that last nest cloud outage which wiped out my nest account and I had to create a new account with a modified email and nest support was useless. Then I could not join one of nest protect smoke detectors again nest support was useless told to go buy a new one since it was 2 months past my warranty. It still functions without connecting just does not report in the app.
Googled online appears to have happened to others as well.
Then I go out of town on vacation and they update again now my nest cameras go offline.
I can remote to my home computer and see my wifi is fine. Luckly the nest cameras are only for a secondary interior security.
I will never buy nest again.
Hopefully these new Aqara smoke detectors are CSA approved for insurance reasons.
Or maybe ikea will carry a certified version of them.
I will likely grab 2 to test in my basement bedrooms
True. There's a lot of mystery surrounding the plans for their hub. But they've introduced a beta of local control, so depending on how open their API is will tell what's possible. I have Ecobee (You should be buying Canadian eh? ), and Wyze for the cameras. Really all I want from a smoke and CO detector is for it to work and not give false alarms.
The fact that it can notify me and turn on my lights, and light my way at night, and not over react to steam, and not make me change the batteries every year, can turn off your nest thermostats without wifi working, and sends me reports, and tests itself !!!
These things alone are incredible. But then it also gives you a little green wink before you go to bed . Interconnects without wires (very important for me in house built in 1926), and it's excellent industrial design, comes with amazing screws, nice packaging, and they cost $150 CAD before tax. My only complaint.
I have an Aqara natural gas detector on order, That post of the house exploding was a call to action for me. The Aqara Hub HomeKit edition I bought is ETL Intertek certified, even though it came with a Chinese plug and an adapter. So I'm sure the Gas, and the smoke/CO detectors are as well. Have you read anything about false alarm rates being an issue with the smoke/CO? I could use a few extra and don't need that many nests at such a high price. Do the Aqara smoke/CO detectors interconnect with themselves? Haven't researched them at all.
Actually I did upgrade my thermastst from a nest to the ecobee4. I wanted the alexa feature and was having issues with balancing heat/cooling but still have those issues with my ecobee so something I am doing wrong. I just havent made it a priority. It may have to do with the rapid tempetature changes we get here.
No I haven't found anything on if they network or false alarm. Going to try 2 to start and see how they go.
The nests are working fine will wait until they expire to replace them.
If we can get the smoke detectors to pair to HE hub then they can network that way.
Good idea will have to add 1-2 Aqara natural gas detector to my list.
I put the offline nest in my garage.
The currently available models do not, unfortunately. They are independent, and the "smart" aspect is basically just remote notification through the gateway hub. There's no way that I've read of to send commands to force the sounding of the alarm of either the smoke / gas detector.
We don't have a good device handler for the Heiman.
Perhaps, @mike.maxwell will consent to writing a native one in Hubitat. (always the preferred approach)
I believe that there is enough of a demand for that particular device.
Same. Hold the pair button (press on the top of the sensor) for six seconds until it flashes three times. Pause for 2-3 seconds and short-press the top of the sensors. Repeat ever three seconds and at some point it should appear in the Zigbee paring the window showing “Initializing”. Keep short-pressing the sensor top every 2-3 seconds until you see the option to save the device pairing in the Zigbee discovery window. Then stop clicking and save the device.
), and Wyze for the cameras. Really all I want from a smoke and CO detector is for it to work and not give false alarms. 
. Interconnects without wires (very important for me in house built in 1926), and it's excellent industrial design, comes with amazing screws, nice packaging, and they cost $150 CAD before tax. My only complaint.
