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

[RogTP (Roger Selwyn)]

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.

[atmasphere (Jonathan Greene)]

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

[_casper]

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.

[rsachoc]

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.

[desiparis]

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.

[kapytan (Catalin)]

I got it working. Thank you so much.

[WoodpeckerCZ88 (Woodpeckercz)]

@Jgaudet

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.

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

[Sym0nd0 (Sy)]

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!

[Tomiam (Tom)]

Have you tried this version.

vinodmishra/badnest

[Sym0nd0 (Sy)]

Have those changes not been merged in to @USA-RedDragon’s repo? It doesn’t look like it’s been updated since October last year (I’m rubbish with Github so could be wrong there).

I’ll give this fork a go tomorrow and see if that does the trick. Cheers.

[Tomiam (Tom)]

I cant remember exactly. I think its the fork I am using and its been fine for ages.

[Sym0nd0 (Sy)]

Awesome, thanks I’ll give it a whirl tomorrow.

[Sym0nd0 (Sy)]

Well, now I’ve merged those changes in I finally have a entity showing for my doorbell camera, woohoo!

Sadly, I can’t get an output to display for it lol.

Picture card with:

aspect_ratio: 75%
entity: camera.front_door
type: picture-entity

At least it’s a step in the right direction. I’ll remove the Badnest integration and manually install the custom component, hopefully that gets it up and running.

Thanks for the point in the right direction and thanks to @USA-RedDragon for all his work on this and @vinodmishra for the fork, hopefully the changes get merged.

[Sym0nd0 (Sy)]

CRACKED IT!

Final piece of the jigsaw was to leave the region as eu, I’d changed it to gb whilst testing and forgot to set it back. All up and running now.

Thanks again @Tomiam, @USA-RedDragon and @vinodmishra. Have a great weekend.

[Tomiam (Tom)]

Glad to see you sorted it! Love to see a success. Badnest was a great find for me after missing out on a Dev account. Love having Nest in HA

[Groto]

Has anyone figured out how to improve the camera picture quality? It looks way better in the Nest cam and pretty fuzzy in Home Assistant.

[VinistoisR]

yeah the image is total junk next to the unifi protect cams.

on the plus side, even though its just a still image, it updates pretty fast, the delay seems to only be 2-3 seconds, compared to 10-15 for protect.

[Groto]

I’m actually slowly replacing my network with Ubiquiti and plan to use the Protect cams. Are you saying the picture quality in Home Assistant looks great on those, but it is just real slow to update? Thanks

[VinistoisR]

protect:

Nest:

• In HA, in a lovelace grid view, the picture quality looks 100x better on the protect cams than the nest cam. There is a fuzzy blur on the nest cam, whereas the protect cams are sharp.

• in lovelace view my protect cams are always streaming, always displaying nice smooth video from 10-15 seconds ago.

• in lovelace view my nest cam is a still image, which seems to never update until something in the scene changes. I have mine pointed at a gate… when someone goes through the gate, I get an image of a closed gate, then an image of an open one, and an image of a closed one again. I seldom see an image of the actual person, so I think the update rate isn’t fast enough.

• the motion triggers in unifi are very fast and respond instantly, even though the camera image is delayed. Using the (excellent) protect integration, you can put the little motion dude overlaid on the cam image, and it responds really well. You get none of that with nest:

• comparing the nest app to the unifi protect app, I’d say the quality is about par.

• in HA lovelace, if I click on a protect thumbnail, the popup fills the page, nice big sharp image. But if I click on the nest thumbnail, it pops up the same size. This is the root of the issue I think with the blur, its like only a tiny thumbnail can be pulled.

[MiguelAngelLV (Miguel Ángel)]

It works perfect, thanks you.

The “oficial version” does not show my camera.

Any way to get when anyone press the button on Hello Nest?