Google Nest integration stopped detecting 'eco' preset triggered by 'Away'

janus · April 4, 2023, 12:21pm

Hi I also experienced the same issue and behaviour since few days. It was working fine before. I also removed the Nest integration and re-added it but it never got resolved. I can confirm that setting the target temperature works as expected as well as turning it off. Preset mode is broken at the moment. Hope someone can fix this asap. It stopped working per 1st April after checking my Nest energy usage history. Thanks!

vinzouilleus · April 4, 2023, 3:26pm

Same here.
I have seen the issue reported on Github as well. Seems like it depends on the Thermostat model.

github.com/home-assistant/core

Nest Thermostat No Longer Responds to preset_mode: none or preset_mode: eco

opened 10:21PM - 31 Mar 23 UTC

Blu53E

integration: nest

### The problem To begin with, my apologies if this is already documented as …an issue, a similar issue is already created, etc. This is my first time using GitHub and although I tried searching for similar issues, I'm not used to the interface. I just created my account within the last few hours. Have an automation that sets my Nest Thermostats to either none or eco based on presence, etc. I have an automation the controls two Nest Thermostats. As of yesterday, the 1st Floor Nest Thermostat no longer responds to eco or none presets. The 2nd Floor Nest Thermostat works fine via the automation. The automation has been working flawlessly for a few months till yesterday. Through exhaustive testing and troubleshooting the 1st Floor Nest Thermostat via Developer Tools: Services and directly interacting with the device via Settings: Devices & Services: Integrations, I cannot change the preset_mode. I am able to change everything else; ie: the temperature, the mode (cool, heat, heat / cool, turn on / off the fan) but when I try to set the preset, it doesn't change to the mode I want. Again, just for 1 of 2 Thermostat. The 1st Floor Thermostat reponds to all requests except for the preset_mode. The 1st Floor Thermostat is a 1st Generation Nest Thermostat. The 2nd Floor is either a 2nd or 3rd Generation. Both worked fine till yesterday. I did however, upgrade HA Operating System and HA Core and I believe that's when it no longer worked. I tried restoring from a previous backup using my prior version of HA Core but without luck. Looks as though I can't restore the Operating System. I don't know if updating my HA caused this issue or if it was coincidence. Here's an example of where I try to toggle the Preset via the interface. When changed, it flips back in about 2 seconds. Again, I can change the Operation, Fan Mode, Temp (up / down) and those all work fine. ![image](https://user-images.githubusercontent.com/129550186/229240979-0c170ff0-6c26-4bc2-a3b9-32d359d3422d.png) Here's example YAML via Developer Tools. When I click "Call Service", I get a green check mark and nothing happens. ![image](https://user-images.githubusercontent.com/129550186/229241150-6a406ec1-9e85-4829-b3e3-33e2753ff8a2.png) If I use the native Nest web app or the app on Android, I can set the preset mode. I did set the following lines in configuration.yaml but not sure where the output is being logged. I did look in home-assistant.log but don't see much there but it may be due to my lack of understanding of what I'm trying to read. And under the Integrations Tab for Google Nest, I did turn on Enable debug logging and after a few attempts, I'm not really understanding the log output but nothing really sticks out. logger: default: info logs: homeassistant.components.nest: debug google_nest_sdm.event: debug This WYSIWYG isn't indenting the above correctly, screenshot: ![image](https://user-images.githubusercontent.com/129550186/229243533-9a5ef28d-2a39-446e-8ecf-e7229f3f4bb8.png) ### What version of Home Assistant Core has the issue? core-2023.3.6 ### What was the last working version of Home Assistant Core? core-2022.12.8 ### What type of installation are you running? Home Assistant OS ### Integration causing the issue nest ### Link to integration documentation on our website https://www.home-assistant.io/integrations/nest ### Diagnostics information [config_entry-nest-20ee2783cd1f0b0c97fdf79072210691.json.txt](https://github.com/home-assistant/core/files/11127358/config_entry-nest-20ee2783cd1f0b0c97fdf79072210691.json.txt) ### Example YAML snippet ```yaml service: climate.set_preset_mode data: preset_mode: none target: entity_id: - climate.1st_floor Also - service: climate.set_preset_mode data: preset_mode: none target: entity_id: - climate.1st_floor - climate.2nd_floor In above example, 2nd floor works. 1st floor doesn't in either example. I've toggle the value from none to eco, back and forth, etc. 2nd floor always responded, 1st floor not. Partial example of a longer automation: then: - device_id: [redacted] domain: climate entity_id: climate.1st_floor type: set_preset_mode preset_mode: eco - service: notify.mobile_app_pixel_6_pro data: title: Home Presence message: [redacted] & [redacted] not home. Turned on Eco Mode for 1st Floor. The above snippet for 2nd floor Nest Thermostat works as expected. ``` ### Anything in the logs that might be useful for us? ```txt No. I think I got everything noted above. Actually, yes: if I set the mode (or any other options), via the web app, the android app or the physical device itself, Home Assistant shows the correct state of anything I change, including preset_mode. However, I can't set preset_mode via Home Assistant. ``` ### Additional information Appreciate the assistance. Again, apologies if this is duplicative. New to GitHub and hope to master it soon.

tivoo · April 5, 2023, 6:30pm

Exactly the same issue here. Setting the preset mode has become unresponsive. Good to see it’s not just me. Running Home Assistant 2023.3.5 and Nest Learning Thermostat V3. Been running this setup for quite some time now, without any issues up until now.

Xanox · April 14, 2023, 9:38am

I too am running into this problem. climate.set_preset_mode simply seems to get ignored by my thermostat.

Nest V3
Home Assistant 2023.4.4
Supervisor 2023.04.0
Operating System 9.5
Frontend 20230309.1 - latest

I have worked around it by setting a temperature manually for now. It might screw with your schedules, but for me this was no issue.

hanszant · April 28, 2023, 8:36am

Same Issue here!!
But is this a home assistant problem or a Google problem?

Home Assistant 2023.4.6
Supervisor 2023.04.1
Operating System 10.0

flyingorthopod · April 28, 2023, 1:06pm

Same here - not wokring at all. Also not showing accurate heat history data

DOSirl · May 9, 2023, 10:57am

Hi,
I’m very much a novice when it comes to Home Assistant and integrations, but I just found a solution that works for my needs, but understand it may not work for others.

I’ve changed the action in my automation to send a text command instead of changing the preset.
My Nest Thermostat is called “Hallway”.

I know it is a workaround, but it works for me.

PHvD · May 25, 2023, 5:03pm

I know this isn’t quite the same as the OP, but I landed here as I was trying to work out how to turn eco on from an automation, rather than read its state, and the set_preset_mode isn’t working as an action either.

The workaround of using the set_hvac_mode action is working, which for me has the same effect as turning eco on/off.

theimpimp · November 30, 2023, 10:27am

Same issue here - I can set eco in the Nest app or the Google Home app and it applies, I can also set eco from Home Assistant and it applies, but if I set eco from the Nest App or Google Home app it doesn’t update Home Assistant to show Eco mode.

I have an EU Nest Thermostat 2nd Gen.

rob6 · February 8, 2024, 4:10pm

It seems like this issue has re-appeared for me, out of the blue this morning 8th Feb 2024. No mode changes being applied from the HA UI and HA not reflecting the current state when the thermostat is set outside of HA using the Nest App or SmartThings. I’m in the UK, all been working fine on the below versions.

Core2024.1.5
Supervisor2024.01.1
Operating System11.4
Frontend20240104.0

justin4480 · February 8, 2024, 5:01pm

Same here… in UK and as of today (8th Feb 2024) the current state of the Thermostat is not showing correctly in HA.

rob6 · February 8, 2024, 5:44pm

…seems to have recovered

justin4480 · February 8, 2024, 6:14pm

Glad to hear it @rob6 … did you do anything or did it just start working?

Mine is still unresolved… It’s strange as I can control the Nest thermostat from HA (change HVAC mode, change preset and set target temp), but the entity state and attributes don’t refresh until I reboot HA. I’ve even spun up a new HA container instance on my proxmox server and setup a fresh google cloud / OAuth account with same issue.

Hard to know if it’s hardware or cloud issue.

rob6 · February 9, 2024, 6:59am

Hi @justin4480, the integration just started working again, interestingly after I’d posted that things were ok again, the integration stopped sometime during the evening, but has recovered again overnight without any intervention from me.

justin4480 · February 9, 2024, 9:45am

Update from me… After spending a good amount of time on this last night I finally gave up and went to bed. However, I woke this morning to find everything magically working again; nothing I did to fix it - I’m convinced it was a google API issue.

For anyone else in the future that finds themselves facing this issue… I was able to send commands from HA to the nest thermostat, i.e.

  - domain: climate
    type: set_hvac_mode
    hvac_mode: heat
    ...
  - domain: climate
    type: set_preset_mode
    preset_mode: none
    ...
  - service: climate.set_temperature
    data:
      temperature: 22
    ...

…however, the HA state attributes (in the devices page or Developer Tools >> States) would only update after:

Waiting 15 minutes (although not always)
Rebooting HA
Reloading Nest Integration (Integrations >> Google Nest >> 3 dots >> reload)

Now things have resolved, when my nest thermostat state changes (either via direct manual control or via HA) the HA state attributes update within 5-10 seconds.

I should add, to ensure my issue wasn’t an HA issue I setup a second HA instance to run in parallel, i.e. I had my original HA OS, but also a temporary HA instance running in a proxmox container. My original instance was using my originally setup “Google Cloud” and “Google Device Access” projects, and for my sandbox HA container I setup a fresh “Google Cloud” and “Google Device Access” project.

This is speculation on my part, but I got the sense this might be to do with the Google “Cloud Pub/Sub API”. See below screenshot which was a big spike in “API calls during the period I was facing issues”.

My nest thermostat is my one remaining cloud integration, I really need to find a local alternative. I’m so done with cloud API’s, particularly Google’s