Funny thing is that I’m using substrings everywhere in my config but somehow I blindly copied someone’s code for comparing data without even thinking about it
This is a great Project @gt4020, I’ve borrowed a considerable portion of your code to get my own project up and running, but I’m slowly evolving it to suit my own heating system.
Hi Giovanni
thank you for your project, i implemented your thermostat on raspberry and it always worked fine. But since I upgraded HA to core-2021.2.3 it doesn't work anymore. It is no longer able to switch to the temperatures set by the interface on schedule hvac_temperature_knob always remains at the temperature set in the generic_thermostat. I double-checked the config files and they are correct. I think the problem is in the automations that don't trigger. I noticed that if I activate the work_timer automation, the temperature setting on the thermostat fine. In other cases, no. Thank you if you can help me solve this problem also because the project is very valid and I repeat, it has worked very well until now Thanks Mario
I’ve managed to migrate this config from configuration.yaml to automations.yaml but I have problems with the timers for the Heating Timer and for the Heating lock Timer. The switch is doing it’s job but the timer does not work, when turned on it should turn back off after the specified time, but it doesn’t do that.
My automation.yaml looks like this:
alias: Heating_lock_Timer
trigger:
platform: state
entity_id: input_boolean.switch_heating_lock_timer
to: ‘off’
platform: state
entity_id: input_boolean.switch_heating_lock_timer
to: ‘on’
for: ‘minutes: ‘’{{ states.input_number.heating_lock_timer.state | int }}’’’
action:
for:
minutes: '{{ states.input_number.caldaia_timer.state | int }}'
That’s the way the documentation shows how to do it in the fifth example in Holding a state.
EDIT
I overlooked to mention that the preferred way of getting an entity’s state value is by using the states() function (refer to the Warning message here).
for:
minutes: "{{ states('input_number.caldaia_timer') | int }}"
I’ve tried both examples, I receive the following error message:
Invalid config for [automation]: [minutes] is an invalid option for [automation]. Check: automation->minutes. (See /config/configuration.yaml, line 8).
Yes, you were right I’ve missplaced it, instead of placing the line into the “caldaia temporizzata off” automation, I’ve placed it into the “Heating_lock_Timer” automation. Now I’ve placed it into the right spot and it’s working perfectly. Using the synthax provided by you, I’ve managed to solve the synthax for “Heating_lock_Timer” automation. Both automation are now working.
Thank you very much for helping me.
Ciao Giovanni,
bel progetto! funziona benissimo! Cosa dovrei fare, se è possibile, per comandare 2 zone distinte? es. zona giorno e zona notte. vorrei comandare le due temperature autonomamente.
Hi Giovanni,
nice project! it works great! What should I do, if possible, to control 2 distinct zones? ex. living area and sleeping area. I would like to control the two temperatures independently.
I’ve been using this thermostat many years, but after upgrading HA to 2023.7.0 the weekely program is no longer working, I have the 2 following errors:
Error while executing automation automation.temp_lock: expected float for dictionary value @ data[‘temperature’]
temp_lock: Error executing script. Invalid data for call_service at pos 1: expected float for dictionary value @ data[‘temperature’]
The temp_lock automation looks like this:
alias: temp_lock
description: “”
trigger:
platform: state
entity_id: sensor.hvac_temperature_knob
platform: state
entity_id: input_boolean.heating_master
to: “on”
condition:
condition: state
entity_id: input_boolean.switch_caldaia_timer
state: “off”
condition: state
entity_id: input_boolean.heating_master
state: “on”
action:
