Error while executing automation climate set_operation_mode

Installation Home Assistant OS
1

Hi,
one week ago, i updated my hassio from 0.88.2 to 0.100.1. and few days later to 0.100.2.

Now i’m getting errors with an automation:

“Error while executing automation automation.a_set_thermostat_eco_mode. Service not found for call_service at pos 1: Unable to find service climate/set_operation_mode”

the automation:

# Heizung abends aus
- alias: 'a_set_thermostat_eco_mode'
  initial_state: true
  trigger:
    - platform: time
      at: "21:00:00"
  action:
    service: climate.set_operation_mode
    data:
      entity_id:
        - climate.buro
        - climate.heizung_esszimmer
        - climate.werkstatt
      operation_mode: "eco"

In the documentation of the climate component “set_oparation_mode” is no more listed, seems to be dropped?! .
Maybe I missed some “breaking changes” informations.
Does anybody know, what i should use instead?

btw.: It’s a AVM Fritz 301 Thermostat, working fine so far.
Connection itself is ok, reading of values (temperatur, battery level) is working.

2

They did a complete clean up in 0.96 see below.

Everything works now with the new climate integration

1 Like
3

Many thanks, @Infineghost! I didn’t see that!
I’ll replace “set_operation_mode” with “set_hvac_mode”, hoping it works and I’ll give feedback…

4

I suspect it won’t be exactly what you need as I see operation_mode: "eco" - you’ll probably need to use set_preset_mode instead.

1 Like
5

@AhmadK You are right!
I tried

- alias: 'a_set_thermostat_eco_mode'
  initial_state: true
  trigger:
    - platform: time
      at: "12:55:00"
  action:
    service: climate.set_hvac_mode
    data:
      entity_id:
        - climate.buro
        - climate.heizung_esszimmer
        - climate.werkstatt
      hvac_mode: "eco"

But, hvac_mode doesn’t know/accept the value “eco”.

After a look into the sources i think I understand the background of the changes.
Next try is:

- alias: 'a_set_thermostat_eco_mode'
  initial_state: true
  trigger:
    - platform: time
      at: "21:00:00"
  action:
    service: climate.set_preset_mode
    data:
      entity_id:
        - climate.buro
        - climate.heizung_esszimmer
        - climate.werkstatt
      preset_mode: "eco"

that’s what you suggested…i think it will work now, Thank You, Ahmad!

6

you’re welcome!
I hope it will work.

For the future, every generic_thermostat has preset_modes attribute so you can find out in Dev tools - > States what’s valid (but yeah, it’s not one of hvac_mode, they are separated now).

Don’t forget to change your climate.buro, climate.heizung_esszimmer and climate.werkstatt configs, namely:

initial_hvac_mode: 'heat' # I hope it's a heater ;)

And one more thing… nowadays there is no need in this bit, just remove it as it’s true by default and stays true unless you change it (kind of devs guarantee it):

initial_state: true
1 Like
7

Thx Ahmad, i removed “initial_state: true”,

Concerning initial hvac mode: the hvac_mode seems to be “heat” by default.
At the moment all my thermostats are AVM Fritz Devices, the attributes seem to be “learned”
from FritzBox automatically, there was no need to configure a generic thermostat.
All i did, is adding follwing entry in configuration.yaml

## Fritzbox SmartHome Devices
fritzbox:
  devices:
    - host: 192.168.x.y
      username: !secret fb_user
      password: !secret fb_passwd

Under Developer Tools - States I see this:

climate.heizung_esszimmer	heat	hvac_modes: heat,off
current_temperature: 26
min_temp: 8
max_temp: 28
temperature: 9
preset_mode: eco
preset_modes: eco,comfort
battery_low: false
device_locked: false
locked: false
battery_level: 70
holiday_mode: false
summer_mode: false
window_open: false
friendly_name: Heizung Esszimmer
supported_features: 17

Should i do any further configurations?

8

I own a dumb self-upgraded boiler so no smart things here and mine supports only off/heat mode and none/away preset.
Good that your one picked up hvac_mode automatically (but not sure it’s heat by default, would rather bet on off and the source code has the answer).
Don’t think you need anything else to configure if it works as expected - the rest you can do through climate service calls.

9

I got the same. I got a Central Heating Boiler which has 2 connection. First one is modbus which is connected to my manual thermostat (its a must for the WAF).

Upon inspection i also had the terminals for a On/Off thermostat, Which i now connected to a Relay with an ESP. My boiler regulates the rest of it.