core: Nest Thermostat Automations not working

The problem

Logger: homeassistant.components.automation.lower_heat_at_10_pm_main Source: helpers/script.py:1783 Integration: Automation (documentation, issues) First occurred: November 11, 2023 at 10:00:10 PM (1 occurrences) Last logged: November 11, 2023 at 10:00:10 PM

Lower Heat at 10 pm Main: Error executing script. Error for call_service at pos 3: Error setting climate.thermostat_2 temperature to {‘temperature’: 16.666666666666668, ‘entity_id’: [‘climate.thermostat_2’]}: Error from API: 400: INVALID_ARGUMENT: coolCelsius contains an invalid value.: Bad Request

What version of Home Assistant Core has the issue?

2023.11.2

What was the last working version of Home Assistant Core?

No response

What type of installation are you running?

Home Assistant Container

Integration causing the issue

Google Nest

Link to integration documentation on our website

https://www.home-assistant.io/integrations/nest/

Diagnostics information

No response

Example YAML snippet

No response

Anything in the logs that might be useful for us?

Lower Heat at 10 pm Second: Error executing script. Error for call_service at pos 3: Error setting climate.thermostat temperature to {'temperature': 16.666666666666668, 'entity_id': ['climate.thermostat']}: Error from API: 400: INVALID_ARGUMENT: coolCelsius contains an invalid value.: Bad Request

Additional information

No response

About this issue

Original URL
State: closed
Created 8 months ago
Comments: 63 (25 by maintainers)

Most upvoted comments

The issues that get resolved are often ones where:

you include details like the thermostat and model number
you have clear concise steps like I asked for above (e.g. forgot all the talk about automations, just focus on the service calls and the events published. Basically show it’s not a home assistant since messages published are invalid)
you have a private Google doc with the data that you offer to share with them
the doc includes timestamps and timezones as well as the Google account address affected

Then if multiple people do that it usually gets resolved. Otherwise it’s hard for them to reproduce or diagnose.

I encourage everyone seeing this issue to do the same.

allenporter on Dec 1, 2023

@pdobrien3 OK, understanding the “off” issue is the most interesting for now. Let’s reset here a bit here, the most helpful information is:

developer tools showing the state attributes (screenshot is ok, this will show something lower level than the frontend UI)
diagnostics (attached as a file, not copy/pasted)
debug logs containing events, hopefully capturing an “OFF” event. redacting these of ids is fine (attached as a file is easiest)

(Having these separately, or partially, isn’t super helpful. Let’s ignore anything about automations for now)

allenporter on Nov 23, 2023