I had Nest Thermostats on Hass working fine but just installed Nest Protects in my house. Updated the developer profile and have tried removing and re-installing Nest in HASS but each protect just shows as a binary_sensor.none, binary_sensor.none1, and so on. Anybody seen this and how do I get HASS to pick them up correctly or is this a bug? I installed the Nest Protects after upgrading to 0.74
I have my HA instance on ubuntu 18.04 server and i’m seing the same thing since i upgraded to 0.74. I removed my Nest twice already.
Dumb error on my part. I had shut off Nest notifications on my iPhone. When I went into the Messages on the Nest app there was a request to allow access. Clicked allow and voila, everything works…
In recent version, nest component has changed to use config flow, so even you remove nest from configuration.yaml, the config still exists in config_entries ([your_config_folder]/.storage/core.config_entries). If you want to reauthroize your nest client, you can either goto configuration -> integration -> configured to remove nest entry, or delete nest config entry from config_entries file. No need touch configuration.yaml unless you changed client_id/secret