@robi hello, could you elaborate a bit? I had Honeywell but i didnt like it.
All these Tado, honeywell presents themselves as super smart… fuzzy logic ie … assume the boiler is on … heating once you reach room temperature, but it teach itself for example for how long room gets cold so it somehow proactively starts heating before it fall below some level, so u don’t have to wait to get expected temperature etc…
thats why i am wondering how this system can manage such behavior etc.
appreciate.
No, that kind of logic is not (yet) supported.
I am using it for 2 years now.
hi @robi
i went thru the whole thread but there are still not clear items…
thank you!
In my newly built system I will use valves equipped with this kind of thermal actuators (normal open version, 24V):
The main relay board I will employ to control all the valve actuators in all the zones, will be a card like this one:
It communicates with ESPHome through MODBUS RTU protocol, has quality OMRON relays placed in sockets on the PCB.
I’m already testing ESPHome running on ESP32-POE-ISO:
I strongly recommend everyone to check this PID controlled thermostat instead of HA’s built-in generic_thermostat. Can be replaced plug-and-play inside the configuration, and allows much finer control of heating. It’s available in HACS:
Hi Robi,
This relay board is a good find with relays in sockets, thx for sharing!
Note that it can be noisy if you would place it near to living zone.
Im using this relay board below with Rpi3B+ 64, in a sealed box in a wc next to the bedroom (1wall)
and the switch noise is acceptable in that way. -bigger relays can be more noisy!-
Im using DS18b20 sensors as well, with shielded wires pulled in through the pipes in the wall paralell to electricity wires.
They are working well, even the longest wire is about 15m, im using 3sensors for 1GPIO on Rpi, with 2.2K pullup.
Viktor
Hi Phier,
you can drive your high current contactor drive coils from sonoff board relay outputs (not so sophisticated but working).
Or if you are more familiar with electronics, you can search for an appropriate optocoupler driver beetween your sonoff GPIO output and your contactor coil drive current needs.
It can be more reliable as not using 1more moving element.
Viktor
Hi Robi,
Just want to say that my system based on your work is running well, and thank you so much for your work and to share it with us, good job!
One thing that i reailzed on usage is, when i turn timer_switch or override_switch onoff when the system is in away mode, the automated temperature levels are not set back to away temp values., i have to manually trigger climate on frontend to away-none-away to set the correct values back.
I have tried to fix it somehow but failed…
Thx,
Viktor
I’ll have a look.
My relays will be in the basement so no problem with the relays ticking noise there.
is it possible to use a smart thermostat valve? do yo need to convert them to switches then? and how is that gonna work, is it just gonna full open and full close all the time?
At the moment it is tested to use HA’s built-in generic_thermostat or the smart_thermostat custom integration above.
But it could adapt to any other kind climate integration.
Hi Robert,
Thanks for sharing your setup, much appreciated!!
I’ve setup my heating in HA based on your automations. I have a total of 6 zones, each zone controls the corresponding TRVs and a main heating valve that controls the hot water flow for the heating in my apartment.
I’m having an issue with the temperature sliders as those automations don’t run because I get following error messages in the logs:
* Template variable error: 'str object' has no attribute 'timestamp' when rendering '{% set t = strptime((now().timestamp() | timestamp_local), "%Y-%m-%d %H:%M:%S").timestamp()-strptime(now().strftime("%Y-%m-%d 00:00:00"),"%Y-%m-%d %H:%M:%S").timestamp() %} {% set time_start = state_attr('input_datetime.heating_weekday_morning_start','timestamp') %} {% set time_end = state_attr('input_datetime.heating_weekday_day_start','timestamp') %} {{ time_start <= t < time_end and is_state('binary_sensor.workday_sensor', 'on')}}'
* Template variable error: 'str object' has no attribute 'timestamp' when rendering '{% set t = strptime((now().timestamp() | timestamp_local), "%Y-%m-%d %H:%M:%S").timestamp()-strptime(now().strftime("%Y-%m-%d 00:00:00"),"%Y-%m-%d %H:%M:%S").timestamp() %}'
The problem seems to be with the template condition in the adjusting temperature automations:
{% set t = strptime((now().timestamp() | timestamp_local), "%Y-%m-%d %H:%M:%S").timestamp()-strptime(now().strftime("%Y-%m-%d 00:00:00"),"%Y-%m-%d %H:%M:%S").timestamp() %}
{% set time_start = state_attr('input_datetime.heating_weekday_morning_start','timestamp') %}
{% set time_end = state_attr('input_datetime.heating_weekday_day_start','timestamp') %}
{{ time_start <= t < time_end and is_state('binary_sensor.workday_sensor', 'on')}}
Sorry but I am no expert these complex conditions so I am not sure how to fix it.
Maybe someone can put me in the right direction.
Thanks!!!
Update:
I found a solution that seems to work for now from an other post. Maybe it is useful for somebody else.
Instead of:
{% set t = strptime((now().timestamp() | timestamp_local), "%Y-%m-%d %H:%M:%S").timestamp()-strptime(now().strftime("%Y-%m-%d 00:00:00"),"%Y-%m-%d %H:%M:%S").timestamp() %}
{% set time_start = state_attr('input_datetime.heating_weekday_morning_start','timestamp') %}
{% set time_end = state_attr('input_datetime.heating_weekday_day_start','timestamp') %}
{{ time_start <= t < time_end and is_state('binary_sensor.workday_sensor', 'on')}}
I use now:
{{ now().fromtimestamp(state_attr('input_datetime.heating_weekday_morning_start', 'timestamp')).time() <= now().time() <= now().fromtimestamp(state_attr('input_datetime.heating_weekday_day_start', 'timestamp')).time() and is_state('binary_sensor.workday_sensor', 'on') }}
Changed all my automations accordingly and so far all working without errors.
Hi Robi,
First of all I’m impressed by your work and the fact of sharing it! As a starter with HA, but have experience with other domotica systems (domoticz) I would like to use your work and migrate my current heating system to HA. Maybe you’re willing to help migrating.
A little explanation;
I’m seeking for some clarifications whitin you’re solution and hopefully your willing to help me out?
Thanks in advance, John
Quite complex indeed, let me think about it, I’ll get back in a few days.
Hi Robi,
Already thanks!
Hi Robert,
I use your brilliant heating scheduler code in my Home Assistant installation. I’ve recently updated to 2021.12.4 and noticed errors in the log when starting up. I confess to not knowing enough about YAML to fix this myself. I was wondering if you may be able to help me please. Here is one of the errors:
> 2021-12-22 11:27:12 WARNING (MainThread) [homeassistant.helpers.template] Template warning: 'strptime' got invalid input '2021-12-22T11:27:12.027556+00:00' when rendering template '{% set t = strptime((now().timestamp() | timestamp_local), "%Y-%m-%d %H:%M:%S").timestamp()-strptime(now().strftime("%Y-%m-%d 00:00:00"),"%Y-%m-%d %H:%M:%S").timestamp() %} {% set time_start = state_attr('input_datetime.heating_weekday_morning_start','timestamp') %} {% set time_end = state_attr('input_datetime.heating_weekday_day_start','timestamp') %} {{ time_start <= t < time_end and is_state('binary_sensor.workday_sensor', 'on')}}' but no default was specified. Currently 'strptime' will return '2021-12-22T11:27:12.027556+00:00', however this template will fail to render in Home Assistant core 2022.1
> 2021-12-22 11:27:12 ERROR (MainThread) [homeassistant.helpers.template] Template variable error: 'str object' has no attribute 'timestamp' when rendering '{% set t = strptime((now().timestamp() | timestamp_local), "%Y-%m-%d %H:%M:%S").timestamp()-strptime(now().strftime("%Y-%m-%d 00:00:00"),"%Y-%m-%d %H:%M:%S").timestamp() %} {% set time_start = state_attr('input_datetime.heating_weekday_morning_start','timestamp') %} {% set time_end = state_attr('input_datetime.heating_weekday_day_start','timestamp') %} {{ time_start <= t < time_end and is_state('binary_sensor.workday_sensor', 'on')}}'
> 2021-12-22 11:27:12 WARNING (MainThread) [homeassistant.helpers.script] Error in 'choose[0]' evaluation: In 'template' condition: UndefinedError: 'str object' has no attribute 'timestamp'
I have searched the HA forums and there are examples of how to fix “Template warning: ‘strptime’ got invalid input” but none apply directly and my knowledge is not there (yet).
There is a block for each template that has this error. Once I know how to fix one block I can fix the others but need some help please.
Kind regards
Richard
Hi Robert,
I fixed this issue using time conditions:
It’s similar solution than @armins2k. Instead of:
{% set t = strptime((now().timestamp() | timestamp_local), "%Y-%m-%d %H:%M:%S").timestamp()-strptime(now().strftime("%Y-%m-%d 00:00:00"),"%Y-%m-%d %H:%M:%S").timestamp() %}
{% set time_start = state_attr('input_datetime.heating_weekday_morning_start','timestamp') %}
{% set time_end = state_attr('input_datetime.heating_weekday_day_start','timestamp') %}
{{ time_start <= t < time_end and is_state('binary_sensor.workday_sensor', 'on')}}
I use:
- conditions:
- condition: state
entity_id: binary_sensor.workday_sensor
state: 'off'
- condition: time
after: input_datetime.heating_weekend_day_start
before: input_datetime.heating_weekend_evening_start
For the nightime condition, I need to change a little bit:
- conditions:
- condition: state
entity_id: binary_sensor.workday_sensor
state: 'off'
- condition: or
conditions:
- condition: time
after: input_datetime.heating_weekend_night_start
- condition: time
before: input_datetime.heating_weekend_morning_start
My personal opinion is that this way is cleaner for a guy not used to be programmer.
Best regards,
Arkharim