Glad you put your experiences in here! I followed your steps and was able (eventually) to get my Nest Protect entities via Homebridge into HA.
After HA auto discovering the HomeBridge, try as I might, I just could not get to the PIN input screen in the HA Homekit Controller integration. Turns out, since my HomeBridge is running in a container on a different server, even though I could access it’s web UI, I needed to select the interface for communications with HA - as it’s on a separate RPi, this was “eth0”. All working now.
Just need to work out which entities are which: smoke, heat, CO,… as the first have entities *_1 and *_2
I try trying to get this natively to HA is key, when it comes to things like life safety mixed with automation too many moving parts can be concerning.
HA has the support for the thermostats, how different is the protect api from the thermostats?
Unfortunately the ‘new’ SDM API doesn’t support Nest Protect (yet?). Thus in the mean-time I am working on porting the HomeBridge integration to Home Assistant, however the long-term goal is that Google adds support to the SDM API and that it will be supported by the official Nest integration in core.
Option 2: use ha-nest-protect which is currently in development and thus has limited features for now, but should eventually be the easiest way to achieve Nest Protect sensors in Home Assistant.
See Support for Nest Protect - #23 by imick
A status update for the others, I didn’t forget about it, but I just have been extremely busy. I hope to work on it (or get some help) in the coming weeks, since I would love to have my Nest Protects in Home Assistant.
Hi Mick , option 2 is a very good solution for me ( i do not want to install extras like HomeBridge)
hopefully you can keep up the good work , would be nice that it will be standard ntegrated into HA
When installing it , can it also be updated , when you are releasing a new version ?
Yes, however you would need to install it using HACS. HACS can keep track of any updates. Let me know (via GitHub issues) if you face any issues with the current integration.
Hi Mick, i have no HACS installed anymore , last year it suddenly stopped working. i think it is not supported anymore by AH.
But i see it can also be done manually ?
When you install it manually, you cannot update the integration automatically, this will need to be done manually as well. You can subscribe to new releases on GitHub to get notifications.
However these discussions are a bit out of scope for this topic.
Sorry for this. I’ve been looking on so many forums that I stopped scrolling. Already got this one installed 3 seconds ago and having a look at it. Hope to see updates of it very soon
Hey Mick! This is super exciting, I was holding out on buying these smoke detectors until it was possible to use with home assistant. I just sent you a friend request on Discord, I’m a python developer and have experience with api’s. I will take a look at your code tomorrow, but send over any resources you’ve found and I’ll give it a shot if you’re still short on time.
I first have to upgrade to google , i did that before what (when nest just changed to google) but it had crashed. ik hope it no no issue anymore to go the google
That is fantastic work - hope there is a way to add an option to support the legacy Nest API. My Nest Protects are probably around 5 years old now and still using the legacy Nest API.
It sounds like if the same functionality can exist after porting from Nest to Google, that would work too. Just not sure what to do with my setup in the meantime other than running and older Nest component as a custom component for my (3) Nest Protects.
Technically it would be a possibility, however it won’t be my focus. Eventually I think people should just migrate to the new Google Account login for the legacy Nest API. The current state of ha-nest-protect is not good enough to migrate yet, however in the coming weeks I hope that we can implement the real-time sensor updates.
