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

I’m pretty certain that thermostats are broken due to ongoing API upgrades. See my debugging/diagnosis in the Github issue: https://github.com/USA-RedDragon/badnest/issues/65#issuecomment-596129580

1 Like

No, it does work, set it up just now…

@zaneclaes - thanks for your efforts!

Nope, still the same overhere. Did you or somebody else found a solution for this ?

Hi, I’m noob to HA, installed it couple days ago:
Raspbian OS => Docker => Hassio

I’ve installed Badnest using detailed instructions:
HACS => Badnest (RedDragon fork)
Both appears in HA log

2020-03-14 12:28:18 WARNING (MainThread) [homeassistant.loader] You are using a custom integration for hacs which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you do experience issues with Home Assistant.
2020-03-14 12:28:18 WARNING (MainThread) [homeassistant.loader] You are using a custom integration for badnest which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you do experience issues with Home Assistant.

I’ve inserted code from instruction to configuration.yaml and tried 10+ different tokens&cookies (with 2FA, without 2FA, etc.). I see no errors and at the same time no signs of the Badnest integration anywhere. I’m still learning all terminology, but I thought that my Nest thermostat should appear in “Entities”? What am I missing?
Thank you in advance!

Just as a heads up to anyone else that runs into this issue, my badnest integration stopped working. After a restart of HASS, it notified me that the issue was my access token.

I went back through the setup of this integration and noticed I couldn’t find my cookie starting with “OCAK=…”.

I did however find my access cookie starting with “HSID=…”. This new cookie was much longer and had more fields and values included in it. Updating my cookie to this new value worked flawlessly for me and I have access to my thermostat again.

Don’t know if google updated their authentication today, or if it’s just an issue with me. Hope this helps someone else.

3 Likes

Ran into the same issue, and this helped, thank you. Back up and running now.

So I have migrated my Nest account to Google (I do not have 2FA enabled) - is that ok? Or do I need to enable 2FA.
I have followed the steps and added the issue token and cookie (My cookie ends in a “.” - is that ok?)

I bought the cameras from the US but I am in Australia - should I use AU or US?

I have tried all the combos I can think of - there are no errors in the logs if I leave the “.” at the end of the cookie and if I remove the “.” then I get “access_token” issue.

Either way after restarting, I am going to Config -> Entities I do not see any of my cameras.

Please help - I have tried all day and no luck.

wow what a super helpful thread! I was able to use the forked edition today and have my 3 nest cams updating via Picture Glance card. Whew! Before using the forked edition I saw no error in my log, but there was nothing discovered … now I see the 3 cameras.

what’s missing though are my door sensors, alarm (protect) and front door (Yale+ Nest). Any chance anyone has figured those out? So pumped to have Nest in HA!

1 Like

Hi! Could you please share what you call ‘forked’?

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

I did the Oauth config and was error free … uninstalled and then reinstalled this other version (config settings stayed in place) and then my sensors showed.

woke up and it’s busted. Images are not loading. :frowning:

To be honest I just made my urls public, and then used the url in a picture card. But then I’m not using badnest currently since my old integration via Works With Nest into Smartthings is working and seems to reliably feed through to HA.

and it’s back. guess I’ll just live with it for now.

I’ve installed badnest through HACS, both from fork (https://github.com/vinodmishra/badnest) as orignal (https://github.com/USA-RedDragon/badnest). I don’t get any climate entities for some reason. Initially I had a Nest account but since that didn’t work I’ve migrated to a Google account but still no luck. My configuration:

badnest:
  issue_token: "https://accounts.google.com/o/oauth2/iframerpc?action=issueToken&response_type=token%20id_token&login_hint=SOME_INFO_HERE&ss_domain=https%3A%2F%2Fhome.nest.com"
  cookie: "OCAK=SOME_EXTRA_INFO"
  region: eu

climate:
  - platform: badnest
    scan_interval: 10

Any idea what I can do to get this to work? I’m not able to find any info (logs) regarding failed login or whatsoever. If that’s available somewhere, please let me know.

I and several others have had the same problem, I’ve never managed to solve it though. I went so far as to buy a cheap Z-wave thermostat as I know I can use that locally…now to get around to installing it.

Could an expert please look in this.i have same problem. Installed HACS and baddest and no error in logs, but no entities either.

Have Nest learning 3rd gen with 3.1 software version. I guess it’s the updated software that is trouble. Am using google Auth with or without 2FA, but no luck.

I got it working. Thank you so much.

Same thing happened to me a while back, and it seems to have stopped working again tonight.

Hi all,
So, I’ve spent pretty much all day trying to get this to work but with no success.

Steps taken

  • Installed repo in HACS, as integration
  • Installed the Bad nest integration in HACS
  • Amended my config, using the Google Auth login method
badnest:
  issue_token: "https://accounts.google.com/o/oauth2/iframerpc?action=issueToken&<long string>home.nest.com"
  cookie: "OCAK=<long string>"
  region: eu

climate:
  - platform: badnest
    scan_interval: 10

camera:
  - platform: badnest

sensor:
  - platform: badnest
  • Tried gb instead of eu
  • Removed the climate entry, as I only have a Nest Hello
  • Added my API key
  • Signed out of Nest and back in, updated with new cookie
  • Rebooting my RPi a lot
  • Come close to tears
  • Swearing
  • Disabling Adguard Home

All of this and still nothing showing up at all. No entities at all. Nothing in any logs, errors or confirmation of it adding new devices.

Here’s my current System log, in case anyone can spot anything I’ve missed:

[s6-init] making user provided files available at /var/run/s6/etc...exited 0.
[s6-init] ensuring user provided files have correct perms...exited 0.
[fix-attrs.d] applying ownership & permissions fixes...
[fix-attrs.d] done.
[cont-init.d] executing container initialization scripts...
[cont-init.d] udev.sh: executing... 
[13:32:05] INFO: Update udev informations
[cont-init.d] udev.sh: exited 0.
[cont-init.d] done.
[services.d] starting services
[services.d] done.
20-04-02 13:32:09 INFO (MainThread) [__main__] Initialize Supervisor setup
20-04-02 13:32:09 INFO (SyncWorker_0) [supervisor.docker.supervisor] Attach to Supervisor homeassistant/armv7-hassio-supervisor with version 214
20-04-02 13:32:09 INFO (MainThread) [__main__] Setup Supervisor
20-04-02 13:32:09 INFO (MainThread) [supervisor.utils.gdbus] Connect to dbus: org.freedesktop.systemd1 - /org/freedesktop/systemd1
20-04-02 13:32:09 INFO (MainThread) [supervisor.utils.gdbus] Connect to dbus: org.freedesktop.hostname1 - /org/freedesktop/hostname1
20-04-02 13:32:09 INFO (MainThread) [supervisor.utils.gdbus] Connect to dbus: de.pengutronix.rauc - /
20-04-02 13:32:09 INFO (MainThread) [supervisor.utils.gdbus] Connect to dbus: org.freedesktop.NetworkManager - /org/freedesktop/NetworkManager/DnsManager
20-04-02 13:32:09 INFO (MainThread) [supervisor.host.info] Update local host information
20-04-02 13:32:09 INFO (MainThread) [supervisor.utils.gdbus] Call org.freedesktop.DBus.Properties.GetAll on /org/freedesktop/hostname1
20-04-02 13:32:09 INFO (MainThread) [supervisor.host.services] Update service information
20-04-02 13:32:09 INFO (MainThread) [supervisor.utils.gdbus] Call org.freedesktop.systemd1.Manager.ListUnits on /org/freedesktop/systemd1
20-04-02 13:32:09 INFO (MainThread) [supervisor.host.network] Update local network DNS information
20-04-02 13:32:09 INFO (MainThread) [supervisor.utils.gdbus] Call org.freedesktop.DBus.Properties.GetAll on /org/freedesktop/NetworkManager/DnsManager
20-04-02 13:32:09 INFO (MainThread) [supervisor.host.sound] Update PulseAudio information
20-04-02 13:32:09 INFO (MainThread) [supervisor.host.apparmor] Load AppArmor Profiles: {'hassio-supervisor'}
20-04-02 13:32:09 INFO (MainThread) [supervisor.host.services] Reload local service hassos-apparmor.service
20-04-02 13:32:09 INFO (MainThread) [supervisor.utils.gdbus] Call org.freedesktop.systemd1.Manager.ReloadOrRestartUnit on /org/freedesktop/systemd1
20-04-02 13:32:09 INFO (SyncWorker_2) [supervisor.docker.interface] Attach to homeassistant/armv7-hassio-dns with version 3
20-04-02 13:32:09 INFO (SyncWorker_0) [supervisor.docker.interface] Attach to homeassistant/armv7-hassio-cli with version 24
20-04-02 13:32:09 INFO (SyncWorker_1) [supervisor.docker.interface] Attach to homeassistant/armv7-hassio-audio with version 9
20-04-02 13:32:09 INFO (MainThread) [supervisor.dns] Start CoreDNS plugin
20-04-02 13:32:10 INFO (SyncWorker_4) [supervisor.docker.interface] Clean hassio_dns application
20-04-02 13:32:10 INFO (MainThread) [supervisor.cli] Start cli plugin
20-04-02 13:32:10 INFO (MainThread) [supervisor.audio] Start Audio plugin
20-04-02 13:32:10 INFO (SyncWorker_2) [supervisor.docker.interface] Clean hassio_cli application
20-04-02 13:32:10 INFO (MainThread) [supervisor.misc.forwarder] Start DNS port forwarding to 172.30.32.3
20-04-02 13:32:10 INFO (SyncWorker_3) [supervisor.docker.interface] Clean hassio_audio application
20-04-02 13:32:11 INFO (SyncWorker_2) [supervisor.docker.cli] Start CLI homeassistant/armv7-hassio-cli with version 24 - 172.30.32.4
20-04-02 13:32:12 INFO (SyncWorker_4) [supervisor.docker.dns] Start DNS homeassistant/armv7-hassio-dns with version 3 - 172.30.32.3
20-04-02 13:32:12 INFO (MainThread) [supervisor.dns] Updated /etc/resolv.conf
20-04-02 13:32:12 INFO (SyncWorker_3) [supervisor.docker.audio] Start Audio homeassistant/armv7-hassio-audio with version 9 - 172.30.32.4
20-04-02 13:32:12 INFO (SyncWorker_1) [supervisor.docker.interface] Attach to homeassistant/raspberrypi4-homeassistant with version 0.107.7
20-04-02 13:32:12 INFO (MainThread) [supervisor.utils.gdbus] Call org.freedesktop.DBus.Properties.GetAll on /
20-04-02 13:32:12 INFO (MainThread) [supervisor.hassos] Detect HassOS 3.12 / BootSlot A
20-04-02 13:32:13 INFO (MainThread) [supervisor.store.git] Load add-on /data/addons/core repository
20-04-02 13:32:13 INFO (MainThread) [supervisor.store.git] Load add-on /data/addons/git/a0d7b954 repository
20-04-02 13:32:13 INFO (MainThread) [supervisor.store] Load add-ons from store: 65 all - 65 new - 0 remove
20-04-02 13:32:13 INFO (MainThread) [supervisor.addons] Found 6 installed add-ons
20-04-02 13:32:13 INFO (SyncWorker_15) [supervisor.docker.interface] Attach to homeassistant/armv7-addon-duckdns with version 1.11
20-04-02 13:32:13 INFO (SyncWorker_11) [supervisor.docker.interface] Attach to homeassistant/armv7-addon-samba with version 9.0
20-04-02 13:32:13 INFO (SyncWorker_17) [supervisor.docker.interface] Attach to hassioaddons/adguard-armv7 with version 2.3.3
20-04-02 13:32:13 INFO (SyncWorker_2) [supervisor.docker.interface] Attach to homeassistant/armv7-addon-ssh with version 8.5.3
20-04-02 13:32:13 INFO (SyncWorker_3) [supervisor.docker.interface] Attach to hassioaddons/node-red-armv7 with version 6.1.4
20-04-02 13:32:13 INFO (SyncWorker_16) [supervisor.docker.interface] Attach to homeassistant/armv7-addon-configurator with version 4.7
20-04-02 13:32:13 INFO (MainThread) [supervisor.updater] Fetch update data from https://version.home-assistant.io/stable.json
20-04-02 13:32:13 INFO (MainThread) [supervisor.snapshots] Found 1 snapshot files
20-04-02 13:32:13 INFO (MainThread) [supervisor.discovery] Load 1 messages
20-04-02 13:32:13 INFO (MainThread) [supervisor.ingress] Load 1 ingress session
20-04-02 13:32:14 INFO (MainThread) [supervisor.secrets] Load Home Assistant secrets: 5
20-04-02 13:32:14 INFO (MainThread) [__main__] Run Supervisor
20-04-02 13:32:14 INFO (MainThread) [supervisor.api] Start API on 172.30.32.2
20-04-02 13:32:14 INFO (MainThread) [supervisor.utils.gdbus] Call de.pengutronix.rauc.Installer.Mark on /
20-04-02 13:32:14 INFO (MainThread) [supervisor.hassos] Rauc: A - marked slot kernel.0 as good
20-04-02 13:32:14 INFO (MainThread) [supervisor.addons] Phase 'initialize' start 0 add-ons
20-04-02 13:32:14 INFO (MainThread) [supervisor.addons] Phase 'system' start 0 add-ons
20-04-02 13:32:14 INFO (MainThread) [supervisor.addons] Phase 'services' start 4 add-ons
20-04-02 13:32:15 INFO (SyncWorker_5) [supervisor.docker.addon] Start Docker add-on hassioaddons/adguard-armv7 with version 2.3.3
20-04-02 13:32:15 INFO (SyncWorker_1) [supervisor.docker.addon] Start Docker add-on homeassistant/armv7-addon-samba with version 9.0
20-04-02 13:32:16 INFO (SyncWorker_9) [supervisor.docker.addon] Start Docker add-on homeassistant/armv7-addon-duckdns with version 1.11
20-04-02 13:32:16 INFO (SyncWorker_6) [supervisor.docker.addon] Start Docker add-on homeassistant/armv7-addon-ssh with version 8.5.3
20-04-02 13:32:50 INFO (MainThread) [supervisor.api.security] /host/info access from a0d7b954_adguard
20-04-02 13:32:53 INFO (MainThread) [supervisor.api.security] /dns/info access from a0d7b954_adguard
20-04-02 13:32:54 INFO (SyncWorker_12) [supervisor.docker.interface] Start homeassistant/raspberrypi4-homeassistant
20-04-02 13:33:25 INFO (MainThread) [supervisor.homeassistant] Detect a running Home Assistant instance
20-04-02 13:33:25 INFO (MainThread) [supervisor.addons] Phase 'application' start 2 add-ons
20-04-02 13:33:26 INFO (SyncWorker_19) [supervisor.docker.addon] Start Docker add-on hassioaddons/node-red-armv7 with version 6.1.4
20-04-02 13:33:26 INFO (SyncWorker_15) [supervisor.docker.addon] Start Docker add-on homeassistant/armv7-addon-configurator with version 4.7
20-04-02 13:33:27 INFO (MainThread) [supervisor.api.security] /host/info access from a0d7b954_nodered
20-04-02 13:33:30 INFO (MainThread) [supervisor.api.security] /dns/info access from a0d7b954_nodered
20-04-02 13:33:31 INFO (MainThread) [supervisor.tasks] All core tasks are scheduled
20-04-02 13:33:31 INFO (MainThread) [supervisor.hwmon] Started Supervisor hardware monitor
20-04-02 13:33:31 INFO (MainThread) [supervisor.core] Supervisor is up and running
20-04-02 13:33:31 INFO (MainThread) [supervisor.host.info] Update local host information
20-04-02 13:33:31 INFO (MainThread) [supervisor.utils.gdbus] Call org.freedesktop.DBus.Properties.GetAll on /org/freedesktop/hostname1
20-04-02 13:33:31 INFO (MainThread) [supervisor.updater] Fetch update data from https://version.home-assistant.io/stable.json
20-04-02 13:33:32 INFO (MainThread) [supervisor.host.services] Update service information
20-04-02 13:33:32 INFO (MainThread) [supervisor.utils.gdbus] Call org.freedesktop.systemd1.Manager.ListUnits on /org/freedesktop/systemd1
20-04-02 13:33:32 INFO (MainThread) [supervisor.host.network] Update local network DNS information
20-04-02 13:33:32 INFO (MainThread) [supervisor.utils.gdbus] Call org.freedesktop.DBus.Properties.GetAll on /org/freedesktop/NetworkManager/DnsManager
20-04-02 13:33:32 INFO (MainThread) [supervisor.host.sound] Update PulseAudio information
20-04-02 13:33:54 INFO (MainThread) [supervisor.api.proxy] Home Assistant WebSocket API request initialize
20-04-02 13:33:54 INFO (MainThread) [supervisor.api.proxy] Home Assistant WebSocket API request initialize
20-04-02 13:33:54 INFO (MainThread) [supervisor.api.proxy] WebSocket access from a0d7b954_nodered
20-04-02 13:33:54 INFO (MainThread) [supervisor.api.proxy] WebSocket access from a0d7b954_nodered
20-04-02 13:33:54 INFO (MainThread) [supervisor.homeassistant] Updated Home Assistant API token
20-04-02 13:33:54 INFO (MainThread) [supervisor.homeassistant] Updated Home Assistant API token
20-04-02 13:33:54 INFO (MainThread) [supervisor.api.proxy] Home Assistant WebSocket API request running
20-04-02 13:33:54 INFO (MainThread) [supervisor.api.proxy] Home Assistant WebSocket API request running

And Dev tools logs shows nothing I wouldn’t expect to see:

2020-04-02 14:33:04 WARNING (MainThread) [homeassistant.loader] You are using a custom integration for hacs which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant.
2020-04-02 14:33:04 WARNING (MainThread) [homeassistant.loader] You are using a custom integration for badnest which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant.

I’m all out of ideas but happy to try anything anyone can suggest to try and get my doorbell camera to show.

Thanks!

1 Like