badnest

A bad Nest integration that uses the web api to work after Works with Nest was shut down (bad Google, go sit in your corner and think about what you did)

This repo is based off of the original from RedDragon with fixes provided by the community since that repo has gone stale.

Why is it bad

This isn't an advertised or public API, it's still better than web scraping, but will never be as reliable as the original API

Features

• Doesn't use the now defunct Works with Nest API
• Works with migrated/new accounts via Google auth
• Nest Protect support
• Nest Thermostat support
• Nest Thermostat Sensor support
• Nest Camera support

Drawbacks

• Tested with a single thermostat, I have no other devices to test with
• Nest could change their webapp api at any time, making this defunct (this has happened before, see https://github.com/USA-RedDragon/badnest/issues/67)

Configuration

Example configuration.yaml - When you are using the Google Auth Login

badnest:
  issue_token: "https://accounts.google.com/o/oauth2/iframerpc....."
  cookie: "......"

climate:
  - platform: badnest
    scan_interval: 10

camera:
  - platform: badnest

sensor:
  - platform: badnest

Google Login support added with many thanks to: chrisjshull from https://github.com/chrisjshull/homebridge-nest/

The values of "issue_token" and "cookie" are specific to your Google Account. To get them, follow these steps (only needs to be done once, as long as you stay logged into your Google Account).

1. Open a Chrome browser tab in Incognito Mode (or clear your cache).
2. Open Developer Tools (View/Developer/Developer Tools).
3. Click on 'Network' tab. Make sure 'Preserve Log' is checked.
4. In the 'Filter' box, enter issueToken
5. Go to home.nest.com, and click 'Sign in with Google'. Log into your account.
6. One network call (beginning with iframerpc) will appear in the Dev Tools window. Click on it.
7. In the Headers tab, under General, copy the entire Request URL (beginning with https://accounts.google.com, ending with nest.com). This is your "issue_token" in configuration.yaml.
8. In the 'Filter' box, enter oauth2/iframe
9. Several network calls will appear in the Dev Tools window. Click on the last iframe call.
10. In the Headers tab, under Request Headers, copy the entire cookie ( include the whole string which is several lines long and has many field/value pairs - do not include the cookie: name). This is your "cookie" in configuration.yaml.

Example configuration.yaml - When you are using the Nest Login

badnest:
  user_id: 1234567
  access_token: "....."

climate:
  - platform: badnest
    scan_interval: 10

camera:
  - platform: badnest

sensor:
  - platform: badnest

The values of "user_id" and "access_token" are specific to your Nest account. To get them, follow these steps:

1. Open https://home.nest.com in Chrome.
2. Open Developer Tools (View/Developer/Developer Tools).
3. Click on 'Network' tab. Make sure 'Preserve Log' is checked.
4. In the 'Filter' box, enter session
5. Log into your account using your Nest login
6. One network call (beginning with session?_=) will appear in the Dev Tools window. Click on it.
7. In the Response tab, find your access_token and userid from the JSON response. The userid value should be used for the "user_id" configuration value.

Notes

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.