You might want to have a look at the thermostat component:
Also please do not create 2 post for the same subject:
ok.
but chrono function is not implemented ?
Why do you mean by chrono function?
timer function…so I can switching ON/OFF heating in specified hours of the day (ex. 7:00-9:00 ON, 12:00-15:00, 18:00-21:00 ON, other is OFF)
Set up some input date time components. Use an automation to enable your thermostat during those times.
E.g. (looks a bit squashed because I’m on my iPad)
- id: lounge_aircon_auto_am_on
alias: 'Lounge Room Aircon Scheduled AM On'
trigger:
platform: template
value_template: "{{ states('sensor.time') == (states.input_datetime.lounge_ac_am_on_time.state[0:5]) }}"
condition:
condition: and
conditions:
- condition: state
entity_id: input_boolean.lounge_ac_am_automation # If automation is required and ...
state: 'on'
- condition: or
conditions:
- condition: state
entity_id: input_boolean.lounge_ac_workday # If workday is not tested or is a workday
state: 'off'
- condition: state
entity_id: binary_sensor.workday_sensor
state: 'on'
action:
- service: input_select.select_option
data_template:
entity_id: input_select.lounge_ac_mode
option: >
{% if states.sensor.roomt.state < states.input_number.lounge_ac_heat_temp_set.state %}
Normal Heat
{% elif states.sensor.roomt.state > states.input_number.lounge_ac_cool_temp_set.state %}
Normal Cool
{% else %}
'Off'
{% endif %}
1 Like
ok. thanks.
This is a good idea.
But there aren’t a specific component ? I think that this is a fundamental problem for heating system…
Nobody have proposed a add-on for chrono-termostat component ?
Where I Can to do this request ?
1 Like
Are you thinking of something like
Yes, Heaty is designed for exactly this purpose and can power very flexible schedules.
Here’s the documentation:
http://hass-apps.readthedocs.io/en/stable/apps/heaty/index.html
Best regards
Robert
I think you are thinking of hass in the wrong way. Hass has a number of tools which you have to fit together. Rather than a ready to play with toy, it is a box of lego parts.
It is really up to you to fit all the little parts together to make automations to do what you want.
Heaty is an example of fitting parts together to do something really useful. The beauty of the community is that in most cases other (cleverer than me) people have already invented the wheel.
1 Like
ok.
there is a GUI to manage thermostat ?
HA hass a web interface for controlling individual entities as you know… Apart from that, Heaty has no GUI.
ok. Thanks.
Is there a possibility to save a thermostat parameter in a file ?
I would to modify the file and automatically modify parameters linked all thermostat…
With Heaty is it possible ?
The whole configuration of Heaty is YAML-based.
You still don’t seem to have read the documentation. As long as I have this feeling, I won’t go on trying to answer any of your imprecise questions. Sorry.
Best regards
Robert
I really like your approach, but as I’m a newbie, might you show the full .yaml documentation e.g. for the Lounge Room Aircon Automation card…?
Br
Stefano
entities:
- entities:
- entity: input_select.lounge_ac_mode
style: |
ha-card {
box-shadow: none;
--ha-card-background: 'rgba(0, 0, 0, 0)';
}
type: 'custom:hui-entities-card'
- columns: 3
entities:
- entity: sensor.lounge_room_temperature
- entity: sensor.lounge_room_humidity
- entity: sensor.lounge_room_condensation_chance
show_name: false
style: |
ha-card {
box-shadow: none;
--ha-card-background: 'rgba(0, 0, 0, 0)';
}
type: 'custom:hui-glance-card'
- entities:
- entities:
- entity: automation.lounge_aircon_am_schedule
name: Enable AM Schedule
state_color: true
- entity: automation.lounge_aircon_pm_schedule
name: Enable PM Schedule
state_color: true
- entity: input_boolean.lounge_ac_workday
state_color: true
- entity: input_datetime.lounge_ac_am_on_time
- entity: input_datetime.lounge_ac_am_off_time
- entity: input_datetime.lounge_ac_pm_on_time
- entity: input_datetime.lounge_ac_pm_off_time
- entity: input_number.lounge_ac_heat_temp_set
- entity: input_number.lounge_ac_cool_temp_set
- entity: input_number.lounge_ac_temp_set_heat
name: AC Heat Set Temp
- entity: input_number.lounge_ac_temp_set_cool
name: AC Cool Set Temp
- entity: binary_sensor.lounge_ac_am_automation_time_active
state_color: true
- entity: binary_sensor.lounge_ac_pm_automation_time_active
state_color: true
- entity: binary_sensor.lounge_ac_heat_required
state_color: true
- entity: binary_sensor.lounge_ac_cool_required
state_color: true
- entity: automation.heating_seasonal_adjustment_am
state_color: true
- entity: automation.heating_seasonal_adjustment_pm
state_color: true
head:
label: Automation
type: section
padding: 0
type: 'custom:fold-entity-row'
style: |
ha-card {
box-shadow: none;
--ha-card-background: 'rgba(0, 0, 0, 0)';
}
type: 'custom:hui-entities-card'
show_header_toggle: false
style: |
ha-card {
border: solid 2px var(--primary-color);
}
title: Lounge Aircon Control
type: entities
Super, thank you.
One question more, which is the meaning of …[0:5] in square bracket as per your template?
Br
/Stefano
It selects only the first 5 characters (stripping off the seconds) to match the sensor.time format (it has no seconds).
Use the template editor to experiment with it:
Once more, thank you for your fast reply and clearness, is a good suggestion to use the Template tool too.
I will capitalize this hint.
Br
Stefano
Hi There. This looks amazing. Please could you supply more info on how to achieve this.
I am after a thermostat with timer function. This this will do it for me
The full automation and Lovelace config is there, welse to you want to know?