Haha, same here. Strange, I’ll have to dig deeper…
Do you have:
camera:
- platform: badnest
???
Just set this up. First, thank you!
This is my config
badnest:
issue_token: !secret badnest_token
cookie: !secret badnest_cookie
region: us
climate:
- platform: badnest
scan_interval: 10
sensor:
- platform: badnest
camera:
- platform: badnest
My thermostat and sensors are working perfectly. I have a Nest Hello though which is not, Im not seeing the camera. Also not seeing any errors under Logs. Any ideas?
I have a google account with 2fa in case that matters
Try the access_token without quotes
Hello all,
it’s work for me but my Nest 3th Generation is configured to 20° c but in the interface I have 19.7°
I have always 0.3 difference IRL and on the Nest how I can correct this ?
Thx
I already removed the quotes when I read the instruction again. And still the same error 
I don’t see a user_id entry in your badnest block
Other than that, this appears to be a parsing error with your yaml. Can you go to Configuration -> Server Controls -> Check Configuration and see if it reports more detail as to the problem?
Hmm. Now my integration is in the same state. Doesn’t appear to be a YAML parsing issue. Looks like the update API call is getting a 200 response but no payload.
I have same error after updating raspberry with sudo apt full-upgrade.
found the fix: you need to update your access-token in config.yaml file.
I have another question: what is different between using access token and cookie method ? can i see the history of how long my hvac ran like i can see in nest app ?
This is what his github says, The target temperature reported by the integration sometimes seems to be slightly off by a few tens of a degree. This is caused by the fact that the Nest mobile app actually actually allows users to set the temperature in small increments, but the displayed temperature is rounded to the nearest 0.5 degree. In other words, the temperature displayed by the integration is correct, just more exact than what is shown in the app.
Are you using Google Auth or Nests?
Firstly thank you for creating this, it’s working great with my thermostat and my protects are showing in HA.
I have a question though, I’m not sure if anyone else has tested or experienced this. The CO and Smoke are both “OK” however when I tested the smoke alarm (with smoke and it sounded) the status within HA did not change… is it like the thermostat where you can set a “scan_interval”?
Ideally I would like to set a few automations if smoke is detected, but I’m not sure what other states are available and it’s slightly concerning that it did not update from OK.
Can anyone offer any advice? Thanks in advance!
Have you checked logs? I don’t know what about others but i have timeouts quite often in the log for badnest.
I think it also depends on for how long the alarm was triggered. Is the alarm logged in history tab of the Nest app?
And the last what came to my mind, it used a different “state code” - i think at this moment badnest utilizes only “0”, “1”, “2” and “3” but in the app code is also state “4” (somebody already mentioned that he saw state “4” related to battery state). I’m not sure if it’s used also for CO and smoke (i canceled my investigation because of other things)
EDIT: Well now i realized if the Protect used other code, it would popped-up as the state in history in HA. (at least the “4” did)
I can’t see anything in the logs relating to the nest protects, on the “history” page it just continually shows the status for CO and Smoke as “Ok”, no numbers?
The events are showing in the Nest app as an emergency and smoke clearing.
I just wonder if Bad Nest is checking the status of the protects periodically, maybe the smoke needs to be detected for a few minutes before it updates in HA?
On a side note, when I update the thermostat temperature it is lightning fast, much quicker than the native app.
Can anyone help me find the OACK cookie I have followed the guide but cannot find ocak my cookie began with SID
I just set it up today for the first time too and the string didn’t start with OACK, mine started with “SID=”. Basically, I just copied all the text within the cookie header and it worked great.
Same as @SgtHobNob for me. Just follow the whole instructions down to “last iframe call” and you will see long string which starts by “SID=…”, that’s your desired 
. 
1 Like
Is it me or do these just show up as entities? They aren’t devices for me, which isn’t horrible, I just can’t add them to an area. Aside from that, awesome work! I’m surprised no one has updated the official nest plugin to use google auth.
Latest HACS update has gone a bit funny for me but managed to install badnest and can see my gen3 thermostat. as with others my cookis started with SID= but copied from there to the end and seems to work fine!
I really hope this can be updated to allow me to boost my hot water as its the one thing I cant currently control through hassio / google home! if anyone knows any solution for this please reply
Has anyone tested the smoke alarm if it works or not? I have it added and it says “Ok” but I have no idea if it’ll actually change on alarms.