Im having the exact same issue. First with RedDragon’s version and now with vinsomishra’s version as well.
Like you said, my thermostat does work, but my log gets hundreds of these entrys per day.
Just starting using this and it’s perfect for getting my nest protect status into homeassistant
Camera’s though I assumed would be a live feed but seems they take snapshots every 30 seconds, is it possible to get live feeds instead?
1 Like
Does someone now how to set the min_temp and max_temp for the thermostat correctly?
The default HA setting is 7-35 degrees Celcius, but my Nest only allows changes between 9-32 degrees Celcius
I wonder if anybody of you experienced the same issue here.
I installed badnest via HACS, configured everything for my thermostat and all went well until the update to 0.11x (something…I couldn’t recall it anymore). I thought I wouldn’t need this anymore so I tried alternatives and nothing worked. Then I wanted to figure out a way and give it another try with badnest. Now, when I install the badnest repo via HACS as usual (install - restart HA) then it shows as installed but the directory is not created in the www/community folder and the lovelace dashboard entry is missing too.
Tried to add them manually but nothing works. Reinstalled but it’s the same behaviour. Does anybody have a clue how I should solve the install?
Every other integration/frontend via HACS works (run, entries, install etc.)
It’s a custom component not a Lovelace card, so you will see it installed in custom_component, not in www/community.
Oh noooo, I feel like I placed an absolute NOOB question…you’re totally right…definitely in there.
Now I need to figure out how to make it work again, since I get this notification:
The following integrations and platforms could not be set up:
- badnest
- badnest.climate
Please check your config.
Maybe I need to copy in the files from another fork, like suggested earlier.
Hello,
with the 3rd generation it’s possible to control hot water ?
THx
So Incognito Mode doesn’t work anymore for me it says cookies are blocked. Also going through View doesn’t work for me either.
- On your computer, open Chrome.
- At the top right, click More
Settings . - Under ‘Privacy and security’, click Cookies and other site data .
- Click See all cookies and site data .
- At the top right, search for Nest.
- To the right of the sites, click Remove
. - Open a New Tab.
- Press Control+Shift+C to open the Developer’s Tools (More Tools/Developer Tools)
- Click on ‘Network’ tab. Make sure ‘Preserve Log’ is checked.
- In the ‘Filter’ box, enter
issueToken - Go to
home.nest.com, and click ‘Sign in with Google’. Log into your account. - One network call (beginning with
iframerpc) will appear in the Dev Tools window. Click on it. - In the Headers tab, under General, copy the entire
Request URL(beginning withhttps://accounts.google.com, ending withnest.com). This is your"issue_token"inconfiguration.yaml. - In the ‘Filter’ box, enter
oauth2/iframe - Several network calls will appear in the Dev Tools window. Click on the last
iframecall. - In the Headers tab, under Request Headers, copy the entire
cookie(beginningOCAK=...- include the whole string which is several lines long and has many field/value pairs - do not include thecookie:name). This is your"cookie"inconfiguration.yaml.
2 Likes
Hello everyone,
is this normal? i am seeing a lots of these entries
Updating badnest climate took longer than the scheduled update interval 0:00:10
As i mentioned above i’m getting a lots of these. 
is that expected behavior ?
@Ascari depending on what you want to do, you can try adding this pull request to your set up - https://github.com/USA-RedDragon/badnest/pull/113
1 Like
This didn’t work for me. Is there a way to not remove all my cookies?
I know this is an old comment, but did you have to do anything special to get the Nest E to show up? nobody else seems to have it working
You can temporary allow all cookies and then get the token and cookie you need with the steps I posted. I can verify this still works as I just did it because my cookie expired. This eliminates having to remove any existing cookies in the browser.
In Chrome go to Settings, under ‘Privacy and Security’ click ‘Cookies and other site data’, there change to ‘Allow all cookies’. (Once you got the token and cookie you can revert this.)
Edit: This is for the original Badnest.
2 Likes
I followed these instructions, unfortunately the cookie I’m getting looks different (no OCAK=… in there), so I have no idea what to copy:
cookie: __Secure-3PAPISID=…/…; __Secure-3PSID=…
Can somebody help?
Thanks!
Seems like cookies do not always start with OCAK anymore. Under the ‘Request Header’ section, copy the whole string (several lines) after cookie: and paste that into your HA config.
3 Likes
That worked, thanks a lot!
Robert
1 Like
I thought this may be helpful information for people that seemingly can’t, for some unknown reason, get any of the badnest repo’s working
https://github.com/mattsch/badnest/issues/11#issuecomment-669494747
This issue occurs because Google/Nest is in the process of switching to a new Protobuf-based API (discussed here: chrisjshull/homebridge-nest#148). Currently it only affects some users, but I assume that eventually everyone will be forced onto the new API. There is a workaround that involves resetting the Nest thermostat (Settings → Reset → WWN Connection), but it’s likely that this is only temporary until Google moves everyone to the new Protobuf API. The only way that this library can continue working for everyone in the long term is by implementing the new Protobuf API like homebridge-nest (a similar library for Homebridge) did. Maybe it wouldn’t be too difficult to implement the new API, since the author of homebridge-nest already did most of the reverse-engineering work.
1 Like