Nest Thermostat action going 1F above what script pushes

Configuration
1

Hot days make AC usage a crazy life. So, I put a script together to increase it to 77F on hot days. However, Nest is showing the change as 78F when it happens. Very weird behavior and curious if anyone has insight?

id: da20fe56-351c-11ee-be56-0242ac120002
alias: increase HVAC temp because outside 94F or hotter during afternoon
trigger:
  - platform: numeric_state
    entity_id: sensor.temperature_34
    above: 94
    below: 150
    for:
      hours: 0
      minutes: 15
      seconds: 0
      milliseconds: 0
  - platform: time
    at: '11:35:00'
  - platform: time
    at: '12:35:15'
  - platform: time
    at: '13:01:15'
  - platform: time
    at: '13:45:15'
  - platform: time
    at: '14:35:15'
  - platform: time
    at: '15:31:15'
  - platform: time
    at: '16:05:15'
  - platform: time
    at: '16:15:15'
condition:
  condition: and
  conditions:
    - condition: time
      before: '17:35'
      after: '11:30'
    - condition: numeric_state
      entity_id: sensor.temperature_34
      above: 94
    - condition: device
      device_id: 9c2059a1a21eb91033f498f8fcb0baab
      domain: climate
      entity_id: d99887dac1440f472ba4ccdddb91f776
      type: is_preset_mode
      preset_mode: none
    - condition: or
      conditions:
        - condition: zone
          entity_id: device_tracker.pixel_7_pro_3
          zone: zone.local_area
        - condition: zone
          entity_id: device_tracker.pixel_7_pro_3
          zone: zone.home
        - condition: zone
          entity_id: device_tracker.gaby_pixel_7_pro
          zone: zone.local_area
        - condition: zone
          entity_id: device_tracker.gaby_pixel_7_pro
          zone: zone.home
action:
  - service: climate.set_temperature
    target:
      entity_id: climate.entryway
    data:
      temperature: 77

Eco mode hot temp is 90F so no way it’s hitting that number somehow.

Kind of just really confused here and beer doesn’t help.

2

The YAML I use for adjusting my Nest’s setpoint is a little different than what you’re using. Here’s the action I have in my “pre-cool on an extra hot day” automation:

service: climate.set_temperature
data_template:
  entity_id: climate.home
  temperature: "{{ state_attr('climate.home', 'temperature') - 1 }}"

Obviously can just put in the temperature you want instead of the template I have.

3

I’ll give it a try. It’s just super weird it’s going up 2 degrees. It’s almost like Nest is rounding up. I wonder, too, if decimals can be used like 77.0 or something to avoid a rounding issue if that’s it. Can’t find any docs in my searching on Nest and decimals/rounding except that Celsius temps apparently do have decimals.

4

It’s as bad with Celsius - HA doesn’t show what the Nest shows due to the conversion (apparently).

5

As a rule of thumb I always send float values to my Nest, whether I’m trying to target a fractional temperature or not, and I’ve never had it set the setpoints improperly. This was never to address an issue, it’s just my thermostat is highly automated and I generally pull values using, for example, float(states('sensor.xyz'), 0) and only convert to/pull as integers if the destination entity doesn’t like floats.

6

That is weird. I’m also using Fahrenheit and have never had that issue, but this is the only automation I have that sets the temperature and it doesn’t get ran very often. Hopefully the different format works for some reason.

7

Thanks all. I’m going to toy around with it a bit and see if anything matters. I’m just wondering if it’s rounding that crap up -or- (just thought about this) injecting those automatic leaf adjustments even though I have it disabled. Kind of a head scratcher.