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

I don’t see any climate entities

Yes I have restarted HA.

So it seems that when home assistant reports a state of 0 for a nest protect sensor that means all is well. It also seems, from an earlier comment, that a state of 2 is a warning from the nest protect. Does anyone have any idea what state will be reported in home assistant for an emergency?

Thanks for the integration! It’s working with no issues for the 3rd gen thermostat.

I"m having the same issue as @krock . Followed the directions to the letter. No errors and no entities showing up.

1 Like

@AndrewG Just curious if you recently switched/upgraded your thermostat? I haven’t been able to get badenest to discover mine since I went from a V2 to a V3. It sees all my other devices like cameras and protects which haven’t changed.

It’s a V3 that I’ve only had about 2 months, was bought used. I’m also quite new to HA having had it running only a few weeks. I ended up re-imaging and starting fresh having made a mess the first time round. As far as I can tell, badnest just does not work no matter what I try.

I also tried connecting badnest with a token_id & cookie from my wife’s account (also connected to our nest v3) - but was unable to connect.

I might try reinstalling hass.io and starting over…

I did a second instance of hass that was completely clean and only had badnest installed and it still wouldn’t recognize the thermostat. I’m wondering if something in the web api has changed. I can still get it to discover my Protect and Cameras but just not the thermostat.

If anybody wonder, “smoke_status 3” means Emergency (smoke alarm). :nerd_face:

2 Likes

Maybe asking the obvious, but did you actually add the custom repository first?

The way I got it to work is:

Add USA-RedDragon/badnest in HACS > Settings > Add custom repository (Integration)
Badnest will then show as installable integration. Install, restart ha.

configuration.yaml:

badnest:
  issue_token: "long tokenstring" 
  cookie: "long cookiestring"

climate:
  - platform: badnest
    scan_interval: 10

#Sensor for Nest attributes

sensor:
  - platform: template
    sensors:
      woonkamer_temperatuur:                                                                                                       
        friendly_name: "Woonkamer Temperatuur"                                                                           
        entity_id: climate.woonkamer_thermostat                                                                            
        unit_of_measurement: '°C'                                                                                                    
        value_template: "{{ state_attr('climate.woonkamer_thermostat', 'current_temperature') }}"

Also, is it possible to change the way these states are displayed in the frontend? If state 0 always means clear and 2 always means warning, can we somehow change that to say ‘Clear’ and ‘Warning’ in Lovelace?

I think at this moment, we can create a Template sensor to rename the values. (there is probably a better way, don’t know, i’m just a HA noob :laughing: )

Like so:

sensor:
  - platform: template
    sensors:
      nest_protect1_smoke:
        friendly_name: "Smoke"
        value_template: >-
          {% if is_state('sensor.protect_smoke_status', '3') %}
            Emergency
          {% elif is_state('sensor.protect_smoke_status', '2') %}
            Heads-up
          {% else %}
            Ok
          {% endif %}

Anyone? Seems like a major part of this otherwise great integration is missing.

Aren’t we all :grin:
Thanks for the template, ill play with it tonight to see if I can get it working :slight_smile:

@axg20202; Not sure, but I don’t think that has been integrated yet. Maybe we can ask @USA-RedDragon nicely if he can add it.

This morning I noticed that my 2 cameras stopped being discovered as well along with my V3 thermostat. (Running HASS 0.103.0) Anyone else noticed devices suddenly stopped being discovered?

My camera is missing, but not caused by .103 as .103 keeps failing when I try to update.

Nedst doorbell and thermostat are missing. Was in old hass and in updated. Also reset login to no avail.

I noticed that my ‘cookie’ in chrome starts with a lot of characters prior to ‘OCAK’… should I include these in my configuration?

Per the docs, skip everything before PCAK=. Include the entire cookie, which is more than just the OCAK=…; (SMSV=, SID=, etc.) and put it in quotes in your config to make sure the entire string stays intact. Unfortunately, the component does not seem to do much logging so there is nothing to be gained by adding debug logging to your config.