Slowly Increase Climate Temp

[jlanglois]

For my cottage I set the temp down to 10c when not there, then on the day I head up I turn the heat up to 20 early in the day.
Recently put in a heat pump as main heat, with how it works if the set temp is more then 2 deg higher then the current temp then it kicks the secondary heating on.
Trying to set an automation so I can have it incrementally increase the set temp by 1 deg until it hits 20deg.
I can do the 1 deg increase I am just not sure the best way to have it repeat itself and have it stop at a set point.

Thanks.

[jchh ((not John))]

something like:
If current_temp is < (heating_target_temp -1)
then set thermostat_target_temp to current_temp +1

so, in config you need:

input_number:
  heating_target_temp:
    name: "Target temperature"
    unit_of_measurement: °C
    min: 10
    max: 23
    #initial: 17
    step: 1
    icon: mdi:thermometer

sensor:
  - name: thermostat current temp
      unique_id: heating_current_temp
      device_class: temperature
      unit_of_measurement: °C
      state: "{{ state_attr('climate.thermostat','current_temperature') }}". ### yours may vary
  - name: thermostat target temp
      unique_id: heating_target_temp
      device_class: temperature
      unit_of_measurement: °C
      state: "{{ state_attr('climate.thermostat','temperature') }}" ### yours may vary

Then your automation will be something like:

automation:
  - alias: heating_climb
    id: "heating_climb"
    description: ''
    mode: queued # ??
    variables: # might not need this
      from: "{{ trigger.from_state.state }}" # might not need this
      to:  "{{ trigger.to_state.state }}" # might not need this
    trigger:
      - platform: state
        entity_id: sensor.heating_current_temp
    condition:
      - condition: template  # might not need this
        value_template: "{{ from != to }}" # might not need this
      - condition: template
        value_template: "{{ states('sensor.thermostat_current_temp == ( states('sensor.thermostat_target_temp  }}" # temp will not increase
      - condition: template
        value_template: "{{ states('sensor.thermostat_current_temp < ( states('sensor.heating_target_temp -1 )   }}" # temp is still below target
    action :
      - service: climate.set_temperature
        data_template:
          temperature: "{{ states('sensor.thermostat_current_temp +1 )  }}"
          entity_id: climate.thermostat

You may need to use |round() or |int() in the templates.

[edit: typos]

[jlanglois]

Thanks.
I will give it a shot when I go back up in a couple weeks… Seems my remote access crashed on me last night so I can’t try it now.

[jchh ((not John))]

good luck. pop back here if there are problems.

[jlanglois]

Giving me indentation error at the Current_temperature part of “state: “{{ state_attr(‘climate.thermostat’,‘current_temperature’) }}”. ### yours may vary”

[jchh ((not John))]

@jlanglois

Giving me indentation error at the Current_temperature part of “state: “{{ state_attr(‘climate.thermostat’,‘current_temperature’) }}”. ### yours may vary”

@jchh

sensor:
  - name: thermostat current temp
      unique_id: heating_current_temp
      device_class: temperature
      unit_of_measurement: °C
      state: "{{ state_attr('climate.thermostat','current_temperature') }}". ### yours may vary
  - name: thermostat target temp
      unique_id: heating_target_temp
      device_class: temperature
      unit_of_measurement: °C
      state: "{{ state_attr('climate.thermostat','temperature') }}" ### yours may vary

yep, my bad. Try this:

sensor:
  - name: thermostat current temp
    unique_id: heating_current_temp
    device_class: temperature
    unit_of_measurement: °C
    state: "{{ state_attr('climate.thermostat','current_temperature') }}". ### yours may vary

  - name: thermostat target temp
    unique_id: heating_target_temp
    device_class: temperature
    unit_of_measurement: °C
    state: "{{ state_attr('climate.thermostat','temperature') }}" ### yours may vary

[jazzmonger (Jeff)]

@jchh Wow… you really know your automation magic! Perhaps you can help as I have a similar situation.

I’m chasing a nasty problem with my pellet stove and it’s driving me absolutely nuts for the past year. The stove will randomly and for no apparent reason turn itself completely off. I’ve replaced all temp sensors, main board, and control board with the help of the vendor support to no avail. I think there is just some shoddy programming in this unit.

So… I’m brute force fixing it with HA. The stove’s Tuya based climate entity incorrectly reports the current temp as -4 degrees at all times (more shoddy tuya platform coding) so I built an esphome temp sensor that I put in the same room and that gives me current temp. I can read set temp from the tuya values, and luckily I can turn the stove back on via a Tuya command.

I’d like to create an automation that mimics a thermostat, since I can’t use the thermostat entity without a working current temp. Basically I want to turn the stove on when current temp is 5 degrees less than set temp. That means it’s failed as the stove normally has a 3 degree “back on” differential from its set temp, when it’s working correctly. Here’s what I have:

As you can see, it’s currently working ok as the temp diff is 68-65.5=2.5 degrees.

My current automation works, but only at a fixed temp. I really want to chase the set temp and turn it on when it’s 5 degrees less than set temp (my wife changes it all the time)

id: '1647433044968'
  alias: On Error, Turn wood stove on.
  description: ''
  trigger:
  - platform: numeric_state
    entity_id: sensor.house_temperature
    below: 60
  condition: []
  action:
  - service: climate.set_hvac_mode
    data:
      hvac_mode: heat
    target:
      entity_id:
      - climate.big_house_wood_pellet_stove
  - service: notify.mobile_app_jeffs_iphone_se
    data:
      message: Wood stove turned on due to Living room <60

This automation will be the basis for controlling the new Esphome firmware I finally flashed in my test bench Tuya MCU unit yesterday once I can solve several problems there. That is a saga in and of itself! There’s another guy battling the same thing I am so this will all be worth it for both of us.

If interested, that saga is here New Device Definition Request - Wood Pellet Stove with 8 dps · Issue #1104 · rospogrigio/localtuya · GitHub

[jchh ((not John))]

Thanks and of course I’ll try to help.

You might want to change your trigger to a template (so you can compare sensor.house_temperature with sensor.set_temp).

so, assuming that sensor.set_temp is the correct name, try this for the trigger:

trigger:
  - platform: template
    value_template "{{ states('sensor.house_temperature') +5 <= states('sensor.set_temp') }}"

The problem is that this could trigger every time sensor.house_temperature changes and is also 5 degrees below sensor.set_temp. We can avoid that by adding the condition that the trigger_from state must also be greater than 5 degrees less. so…

trigger:
  - platform: template
    value_template "{{ states('sensor.house_temperature') +5 <= states('sensor.set_temp') }}"
condition:
  - platform: template
    value_template: "{{ trigger.from_state.state +5 > states('sensor.set_temp') }}"

Let me know if that helps

[jchh ((not John))]

By the way, I have a Hive controller for my heating (heat and water, no cooling). I still use the Hive hub and Hive integration but am about to dump that and switch entirely to local control (via Z2M).

Even though I am using the (cloud based) Hive integration I control my heating & water 100% within HA and you’re welcome to have my package and dashboard that does it. You’d need to customise it for your situation but the logic is all there. My dash looks like this…

I also have a ‘read only’ single button version of the 4 mode buttons (in a vertical-stack in the top left hand corner to the left of the thermostat) which I use in other dashboards so I can always see what is going on. I rarely have to visit this page, but it is where I have my settings and diagnostics.

The 4 modes are:

• Off.
• On. 3 temps set based on whether the house is ‘awake’, asleep’, I am ‘away’ (for a couple of hours) and just adding when I am ‘on holiday’ (away for days). I press a button at night which puts the house ‘asleep’ (sets lights to dim if activated by motion, sets the heating, turns off day-only devices etc). ‘Awake’ is set by the first motion downstairs after 7am. ‘Away’ is set using person.james: not_home but could also be set by zone.home state: 0 (for multiple people).
• Schedule. 4 possible temp/time windows with a minimum temp for outside those windows. Temp also drops when I am away. Easily adjustable to be less or more windows.
• Boost. Can set the relative temp increase and the boost time. Not effected by my presence.

[jazzmonger (Jeff)]

Awesome! Templating gives me fits. I’ll give it a try in the AM. Gotta get some sleep now!

[jchh ((not John))]

let me know!

[jazzmonger (Jeff)]

Ok, now you’re getting me excited! That looks exactly like what I need to figure out. My stove also has 4 modes and 2 eco settings. The datapoints that come out of esphome are all there and I can see them, and I’ve mapped them. I just need to figure out how to get them into a useable format so I can control them. The thread I mentioned is where that fun is unfolding.
There’s another guy who’s done amazing things with his thermostat

My Nest Thermostat card config using thermostat-dark-card

I have just now (1 year, 8 months later) fixed this! I was doing something else totally unrelated which brough me back to card-mod style options when I noticed this in the docs: type: vertical-stack cards: - type: entities entities: - type: 'custom:multiple-entity-row' entity: sun.sun entities: - entity: sun.sun name: Default - type: entities entities: - type: 'custom:multiple-entity-row' entity: sun.sun style: …

Jeff

[jchh ((not John))]

yes, I took a look at it - very interesting stuff! What time zone are you? Idaho. Got it. PST.

[jazzmonger (Jeff)]

I’m MUCH better on the hardware side if things. I’m a hack programmer at best! Yawn…

[jchh ((not John))]

I don’t want to stop you sleeping but wish I had your skills on the hardware side - it looks very impressive.

[dbrunt (Daniel)]

Me too but us hackers get better with practice…and age!

[jazzmonger (Jeff)]

I defined this sensor and checked it works in the dev tools template checker and returns a value of 68 which is correct.

 - platform: template
    sensors:
      house_set_temp:
        value_template:  "{{ state_attr('climate.big_house_wood_pellet_stove', 'temperature') }}"

{{ states(‘sensor.house_temperature’) +5 <= states(‘sensor.house_set_temp’) }}

gives this in the dev tools template checker:
TypeError: can only concatenate str (not “int”) to str

Here are the attributes of the pellet stove:

 "home_assistant": {
      "name": "Big house Wood Pellet Stove",
      "entities": [
        {
          "unit_of_measurement": null,
          "state": {
            "entity_id": "climate.big_house_wood_pellet_stove",
            "state": "off",
            "attributes": {
              "hvac_modes": [
                "off",
                "heat"
              ],
              "min_temp": 50,
              "max_temp": 122,
              "target_temp_step": 1.0,
              "current_temperature": -4,
              "temperature": 68,
              "friendly_name": "Big house Wood Pellet Stove",
              "supported_features": 1
            },

Did I mention I DESPISE TEMPLATING?

[jchh ((not John))]

yep, sorry - forgot to add the |float() to convert from a string to a real number so you can then add ‘5’ to it.

Note I have selected 0 and 99 as the default values. So the automation will go off if the sensors fail for any reason. You can change that if you want.

Try this:

{{ states(‘sensor.house_temperature’)|float(0) +5 <= states(‘sensor.house_set_temp’)|float(99) }}

[jazzmonger (Jeff)]

This works

{{ states("sensor.house_temperature")|float(0) +8 <= states("sensor.house_set_temp")|float(99) }}

Looks like 8 is the magic value that turns it TRUE.

Now the Automation

Invalid condition configuration

Unexpected value for condition: ‘[{‘platform’: ‘template’, ‘value_template’: “{{ trigger.from_state.state +5 > states(‘sensor.house_temperature’) }}”}]’. Expected and, device, not, numeric_state, or, state, sun, template, time, trigger, zone

[jchh ((not John))]

@jazzmonger

Looks like 8 is the magic value that turns it TRUE.

…so the actual temp is currently 8 below the set point?

@jazzmonger

Unexpected value for condition:

I think this may be the same problem. try:

“{{ trigger.from_state.state|float(0) +5 > states(‘sensor.house_temperature’)|float(99) }}”

…sorry for the errors - I am not doing this from my computer where I can check for typos and errors etc.

edit: Actually if +8 works, +5 should also work - you might want to check that.