Nest Legacy

Share your Projects! Custom Integrations
21

I think he means on chrome > 3 dot menu > more tools > dev tools > network tab

this lets you see debug/source/etc info on the web pages

22

Yes that’s what I mean. But the latest release fixed your fan control issue so there is no need to capture the payload.

23

Sorry, I can’t believe I missed that. :man_facepalming:

24

I hoped that the update will show my thermostats, but it didn’t. Sad face :frowning:

Can I help you somehow? Do some diagnostics, maybe at home.nest.com?

25

Hello – Google announced that Gen 1/2 thermostats can no longer be remotely controlled at the end of this month. Will this legacy integration continue to work afterwards? I presume not, as it still relies on Google’s cloud services, correct?

26

Correct. I don’t see how this could continue working

27

I’m trying to get this working using Legacy Nest Account Configuration. It accepts my access token but during the initializing phase I only get this error:

Failed Setup, will retry: Failed to initialize Nest: invalid literal for int() with base 10: ‘none’

28

Can you enable debug logs and attach them in a new GitHub issue?

30

I am struggling to get the integration working, receive the following error:

Failed setup, will retry: Failed to initialize Nest: ‘serial_number’

I filed an issue on Github with the log.

31

This is exactly what I wanted as it will solve one of the biggest problems in my home, the nest thermostat. I do not want to give even more money to google than I have to. I added this integration to my HA and it was able to find my door lock. However, it did not add my gen 3 nest thermostat. I already see that this issue is already on GitHub. Great work so far!

32

Context:
Google semi-bricking Gen1 and Gen2 Nest thermostats and not providing a way of opening them up to local control. FULU bounty won (although weirdly the Fulu page not updated?).
Github for that here

There is also a Home Assistant addon!

33

Try the latest version. It should be working now.

34

@tronikos i am try to activate a change in temperature programmatically via appdaemon. is that possible at all?
i have tried setting either the temperature or target_temp_high attributes to the desired value and the hvac_action to ‘heat’ but it’s not activating the change. any clues or is this not possible?
everything else is working as expected in the UI

35

I don’t use AppDaemon. If the same works in the UI I assume it’s either a user error or an AppDaemon issue. Does it work if you call the action in developer tools > actions? If yes you should ask for help wherever AppDaemon is discussed.

36

it was a case of me calling the wrong service, or action as it’s known in the UI. it’s working now.

self.call_service('climate/set_temperature', entity_id=const.HEATING, temperature=target, hvac_mode='heat')

and the equivalent yaml was

action: climate.set_temperature
target:
  entity_id: climate.heating
data:
  temperature: 23.5
  hvac_mode: heat
37

For me it does not discover all thermostats. I have 4, 2 gen2 and 2 gen3. The legacy nest only discovers 1 of them (a gen3 one)

38

Currently, I have been using two separate HA Nest integrations for my Gen 3 Nest Thermostats and Remote sensors.

  • I use the standard Nest integration to read the value of the controlling sensor, set the temperature, and read the status of the HVAC
  • I use the Nest Protect integration to read the value of the Remote sensor

This is all fine and good when the controlling sensor is the thermostat itself as I can then read both sensors independently.
When the controlling thermostat switches to the remote sensor, then both integrations read the remote sensor and I have no way to read the actual thermostat sensor on the device from HA.

  • Will your integration allow me to read both sensors independently? (temperature/humidity on the thermostat and temperature on the remote sensor)

  • Does your integration allow one to:

  1. Switch control between thermostat and remote sensor
  2. Turn on/off Eco mode
  3. Switch Home/Away
  4. Detect presence
  5. Edit the schedule from HA

Conversely, is there anything that Nest Protect does that your integration doesn’t do or that it does better? (said another way, if I can get your integration working, is there any reason to still use Nest Protect or is your integration a superset for the purpose of thermostat and remote temperature sensor control)
I would like to avoid having 3 separate integrations for 1 stinkin’ Google thermostat :slight_smile:

Thanks!

39

Yes it should. If not, open a GitHub issue with debug logs.

  1. Currently not but shouldn’t be too hard adding support for this
  2. Yes
  3. Yes
  4. Yes
  5. No

Nest Legacy is a superset of the Nest Protect integration. There is no reason to have the Nest Protect if you install Nest Legacy.

1 Like
40

That’s amazing!
Would be great if you could support #1 (switching control between native and remote sensors) as I would like to add that to an automation.
Thanks!

41

Couple of additional questions:

  1. What does “occupancy” do and/or how do I control it? It seems to just show “clear” on all my thermostats

  2. I get entities created for “target humidity”, “filter_runtime” and “filter_replacement_needed” but I have never seen those before on either the thermostat itself or the Nest or Google Home app? Are they even relevant for a Nest Learning Thermostat (Gen3) used on a gas furnace

  3. Is there any way to turn on-off “Farsight/Wake-on-Approach” mode (used to automatically turn on/off the display) from the API?