I made a crappy Nest Thermostat integration that will work as a stopgap until alternatives come out

It should be working. Mine did pass the state of my Protecs to HA several times.

I’ve published a prerelease with some pretty significant refactoring under the hood. It’s been running for a while here, but as I only have cameras I’d be interested to hear if it broke functionality for anyone else. It should show up in HACS shortly, direct link is here: https://github.com/mattsch/badnest/releases/tag/v0.0.2

1 Like

Sounds good, thank you!

Are you using Google Authentication or Nest old school?

Everything seems to work.
But:

ClimateDevice is deprecated, modify NestClimate to extend ClimateEntity

I am trying to install this, but i get nothing? How do i add my camera? Or is it so that nest hello isnt recognised as camera?

And also my cookie begins with “SMSV=…” Is this right or should i do anything different? Using the google login

my configuration.yaml looks like this

#nest hello
badnest:
  issue_token: https://accounts.google.com/o/oauth2/iframerpc?action=issueTo...
  cookie: SMSV=ADHTe-DTCI2bAv0SGn...
  region: eu
  
camera:
  - platform: badnest

Try putting quotes ("") around both token and cookie.

My Cookie starts with “HSID=” - works fine in 109.6.

tried that too, but getting nothing. I am totally new to this with HA.
Can i somehow check if i got any entitities from bad nest? so i later can add them to cards?

Goto Development Tools -> States. There you can find all your devices.

My issue_token & cookie look simular and for me it is working in 110.2. I’m using the badnest repository: https://github.com/mattsch/badnest

what should i look for in there? I changed to your repo now. Lets see what this gives

now i got the camera working from nest hello. But i don’t get any sensors at all. Doesnt the hello have any sensors? I have a nest protect to, and dont get any sensors from that either

More errors in v0.0.2. In v0.0.1 they were not.

Entity id already exists - ignoring: climate.thermostat. Platform badnest does not generate unique IDs
Entity id already exists - ignoring: sensor.thermostat_temperature_raw. Platform badnest does not generate unique IDs

This only uses Google authentication.

Fixed on master, will cut a new release soon-ish.

I’ll look into this, but I haven’t touched anything that should have impacted the ability to generate entity id’s. Could you generate debugging logs by setting custom_components.badnest and custom_components.badnest.climate to debug, restart HA, and post them to a new issue on GitHub? Please make sure any tokens or anything potentially sensitive gets removed.

1 Like

I’ll do it now.

Thanks Stanislav. Just switched to your repo. However; Thermostat and Smokedetectors are working fine but Camera’s are appear… any idea what this can be?

sensor:

  • platform: badnest

badnest:
issue_token: "https://accounts.google.com/o/oauth2/
region: eu

camera:

  • platform: badnest

climate:

  • platform: badnest
    scan_interval: 10

Nice, after upgrading to version 0.0.3 my camera’s are working. Thanks!

My integration stopped working.
This happened before but then I could simply grab the new login issueToken and OCAK.

This time when trying to do so, I cannot find the OCAK string, it starts with SMSV. In my prior strings SMSV always came after OCAK. Now its not there at all anymore.

Any ideas? This certainly blows my technical understanding away…

You didn’t happen to throw in a person detection binary_sensor did you?
If I could get that through this integration I’d probably drop my official Nest integration.
We’ll see when they force me to switch from Nest to Google account…

My Nest still works with HA. Is that because I registered it a long time ago?

Just joining in to say this is awesome thanks!

Also if youre thrown by not having 0CAK in the cookie, just use whatever value is there instead, worked fine for so they must have just changed the reference.

Finally got my thermostat back into HA. Thanks. I also have a Nest Hub Max. Should Badnest be able to integrate the camera in that as well?