Last year my insurance company told me I needed central smoke/CO monitoring to continue coverage with them. My Smoke/CO detectors are all Nest Protects and I didn't want to spend $100s of dollars to replace them in that they all have ~5 years of life left. So I purchased a Starling Home Hub and signed up for their $8/mo Starling Protect 24/7 Monitoring service. The Starling Home Hub imports Google Protect devices into Apple HomeKit, though I don't use HomeKit but rather purchased the Starling Home Hub exclusively for the monitoring service. I was thrilled with this setup until Starling shutdown the service last month. So I am scrambling to find a reasonably priced central monitoring service to replace this setup. I am more interested in low cost than simplicity.
Konnected.io has 24/7 monitoring integration with Hubitat for $10/mo, using the same Moonlight monitoring service Starling Protect did. So I'm working toward a Hubitat based solution using Konnected.io
So I installed the Hubitat HomeKit Controller app on my C8 Pro Hub. I pointed it to my Starling Home Hub and it imported all my Nests into Hubitat. This process was simple and hassle free. Each of my 8 nest detectors show up in Hubitat, specifically as a HomeKit Parent device with a CO detector device and a smoke detector device under it.
But....
I 'm unable to get events from these devices when I test my detectors. The CO and smoke sub-devices originally had device type "HomeKit device". I changed them to "HomeKit Carbon Monoxide Sensor" and "HomeLink Carbon Dioxide Sensor" device types but still no luck.
Anyone seeing this familiar with the Hubitat HomeKit Controller and what I might be doing wrong? Note the Hubitat HomeKit Controller is different than the Hubitat HomeKit Bridge. The former imports Homelink devices into Hubitat (which is that I want), the later exports Hubitat devices to HomeKit.
I see @assigner4 was trying to do exactly what I am (Smoke detectors), but that thread went silent. Maybe he/she was successful or maybe he/she gave up.
If your device pairs using the "HomeKit Device" driver, no matching driver was found. It is likely your device is not compatible with the integration at this time.
I have a starling hub but haven't really paid attention to what's happened since the shutdown. Never had the monitoring service, because I self-monitor through the Nest app.
I could try bringing it into HomeKit Controller myself to see, but it sounds like it's already been attempted by at least two of you and it doesn't work. For Hubitat integration, I use the Nest Protect integration on Home Assistant (available in the HACS store). To bring the sensor output from the detectors into Hubitat, I then use Home Assistant Device Bridge.
There are several options:
Use the above Nest Protect HACS on HA > Hubitat via HADB
Bring the devices into HA via the Starling hub using their HomeKit integration (which they now call HomeKit Device) and then use HADB to bring the sensor data into Hubitat.
Vibe-code the Nest Protect HACS integration into a Hubitat driver. There's a "Nest Doorbell via Starling Hub" integration for Hubitat that might provide addition help for the AI to work from. LLMs are not intelligent depite what many people think and they work best when you give example code from Human developers. It could probably create a Hubitat driver just using the two code examples.
Bring the Starling hub into HomeKit via an Apple TV or HomePod and then use virtual switches and HomeKit automations to get the sensor state synced to HomeKit.
Ask @gopher.ny to investigate why it doesn't work proplerly with HomeKit Controller (least viable IMHO since it's an unpopular product that is discontinued).
I just tried adding the Starling Hub to HomeKit Controller and it's only the smoke that doesn't currently show statue because there's no "HomeKit Smoke Detector" driver. As you can see from the screenshot below, it appears to work for the Carbon Monixide sensor. You have to change the driver, click Save, and then click Refresh on the Commands tab.
I did try the "Ecolink Smoke/CO Audio Detector" driver with the Nest Smoke Sensor device and the does show Smoke Status after I click refresh (see screenshot). If that works, then you could probably get what you need from the smoke device until @gopher.ny has a chance to investigate and create a "HomeKit Smoke Detector" driver.
I have not tested these to see if the status on Hubitat really does change when there's an event and I'm not going to. You will need to do that yourself. Occupancy works and for me that's good enough since I don't use Smoke and CO events for anything in Hubitat.
I could not find a smoke detector device to test it with. I can add device type support, the HomeKit interface is well documented. Someone will have to confirm it's working IRL, though.
I've found another (more convoluted) way to meet my overall goal of notifying my Hubitat when one of my Nest Protects Smoke/CO detectors activate (Nest Protect -> Google Home Automation Script -> Virtual Switch -> Hubitat Google Home App) but my preference would be to use the Starling and Hubitat HomeKit Controller so I don't have to go to the internet to get two devices a few feet away from each other to communicate.
So I'm willing to test it if you want. Unfortunately performing a manual test on a Nest Protect Smoke/CO sensor by design does not change the state reported by the sensor, one actually has to expose the sensor to smoke. My wife does this every month or so cooking dinner, but I can perform some scheduled testing to see both that the state is present and that it works.
As Rick mentioned above; and recommend to me, an Ecolink firefighter device worked great for me. You can look for the model Ecolink Z-Wave Plus FireFighter Wireless Audio Detector FF-ZWAVE5-ECCCO. Typically sell for around $39.50
