Unfortunately, I can only access five traces, and they were from the last 10 minutes. The problem occurred again this afternoon. How can I access traces from the entire day?
Thanks for this! It looks super good! I donât know if this is the right tool for my setup can you please advise?
I have a Nest Thermostat (Connected to the Boiler) in the Living Room
In the Living Room I have 2 Smart TRVs and 1 External temp sensor.
I also have a Bedroom and Guest room with 1 smart TRV and 1 External Temp sensor.
I believe this wont be the correct solution for me because the boiler will turn off too soon to heat all the rooms.
Example:
Bedroom Temp sensor = 20C
Bedroom TRV = 22C
Nest Thermostat Temp = 21C
In the above example, this would not turn on the boiler and the bedroom would not reach the temp of the TRV
Another question I have is what happens to the boiler when one of the roomâs reaches the TRV Temp? How does it know how to turn the boiler off? (Sorry if this is dumb question, Iâve got a newborn so have baby brain haha)
Hey There! I was using my own automations, but quickly found out that Advanced Heating Control does more and better!
One thing, I would want to change is to leave thermostats that are off switched off.
I use AHC to switch between comfort and eco based on presence and use a calendar for night/day temperature. Sometimes, I switch an thermostat off and I want to keep it that way, i.e. do not switch it on again if I leave/come back the house.
Can this somehow be achieved: keep an thermostat that is off off?
In general, the control system works exactly as it should â and Iâm very happy with it. To disable heating during the summer months, I created an input boolean (switch). When this switch is set to âoffâ, all thermostats should be disabled so that no heating takes place (summer mode).
Unfortunately, this doesnât work reliably. While the thermostats initially turn off when toggling the switch, they later turn back on by themselves â even though the switch remains set to âoffâ.
This is quite frustrating and goes against the intended behavior. Does anyone know what might be causing this?
Attached is an example of the automation Iâve set up for the hallway.
I use Aqara E1 Radiators via Zigbee.
Edit:
Iâve since found out that the thermostats turn back on whenever a door/window contact in the room is active. This causes the thermostats to reactivate. Bug or feature?
thank you very much for your answer and apologies for the late reply. You can find both trace logs at the below links. I hope you can help me in some way.
I need some help configuring the blueprint. Im confused if this is only for heating or both heating and cooling? Tittle says heating control, but the description has âheating / cooling based onâ also I see " If you own an air conditioner it will support auto or cool , too.". Could you please explain how to control both(if we can)? we can start with very basic, presence sensing to start heat or cool based on the outside temperature.
@panhans Iâd like to use this blueprint, but I fail to understand if it can support the auxiliary heating?
So I have a radiator heating (with TRV), but sometimes Iâd like to use the aircon as an auxiliary heating for short period of time. Today I have an input boolean to enable the feature and when TRV is in heating mode, I turn on the AC in the heat mode with +5 degree increase to make sure its internal thermostat doesnât control it.
This is my super dummy automation that works well enough for me, with several limitations tho.
alias: HVAC heating AC - Use AC as a auxiliary mode for TRV
description: >-
When room thermostat changes its state, automation will copy the configuration
to the AC heating system (turbo mode with the help of AC)
triggers:
- trigger: state
entity_id:
- climate.living_room_thermostat
- climate.office_thermostat
- input_boolean.hvac_living_room_ac_turbo
- input_boolean.hvac_hallway_ac_turbo
conditions:
- condition: state
entity_id: input_boolean.hvac_heating_is_allowed
state: "on"
actions:
- repeat:
for_each:
- entity_trv: climate.living_room_thermostat
entity_aircon: climate.ac_living_room
entity_turbo: input_boolean.hvac_living_room_ac_turbo
- entity_trv: climate.office_thermostat
entity_aircon: climate.ac_hallway
entity_turbo: input_boolean.hvac_hallway_ac_turbo
sequence:
- if:
- condition: template
value_template: "{{ is_state(repeat.item.entity_turbo, 'on') }}"
then:
- if:
- condition: template
value_template: >-
{{ is_state_attr(repeat.item.entity_trv, 'hvac_action',
'idle') }}
then:
- action: climate.set_hvac_mode
data_template:
entity_id: "{{ repeat.item.entity_aircon }}"
hvac_mode: "off"
else:
- action: climate.set_hvac_mode
data_template:
entity_id: "{{ repeat.item.entity_aircon }}"
hvac_mode: "{{ states(repeat.item.entity_trv) }}"
- action: climate.set_temperature
data_template:
entity_id: "{{ repeat.item.entity_aircon }}"
temperature: >-
{{ (state_attr(repeat.item.entity_trv,
'temperature')|float) + 5 }}
else:
- action: climate.set_hvac_mode
data_template:
entity_id: "{{ repeat.item.entity_aircon }}"
hvac_mode: "off"
mode: single
Hello every one, I recentrly buy the TADO X system to command my heating system comprending 6 radiator and 1 boiler.
I have issue with the boiler thermostat that push the pressure of the boiler to high when after a pahase of heating the radiators valves close the system and the boiler keep heat, this cause an over pressure in my system.
So i try to control all the valves and the bolier thermostat with HA via MATTER and i saw this blue print, it can introduce a delay of closing the valve and let the boiler drop down the pressure?
Thanks everyone help me out
I really like this automation and enjoyed setting it up. Unfortunately I struggle with making it work with my tado thermostats. I have external temperature sensors and selected them for each room. I also set up a schedule for each room, set temperatures, set geofencing, ⊠Unfortunately the thermostats calibrate basically 24/7 and only stop doing so, if I set the time between calibration to e.g. 6h. They only calibrate every 6h then. What also helped is changing the calibration Delta to max (5C). But this obviously leads to a huge delta. How can I set it up in a way that only the temperature of my external sensor is used and the calibration is reduced to a minimum? Should I deactivate the tado temperature sensor?
This shouldnât be a problem since the restore state of the thermostats will be the state before the window was opened. But as I see you defined an window open temperature this can cause that issue.
So this mus be fixed. Thanks for reporting.
I think the only correct way is an template sensor based on the zone or persons or the proximity integration. I will see if I drop some options in the future to be save this works as expected. Maybe we see some kind of accessing historical data in the future.
But your confuguration right now should be fine.
The Blueprint was originally designed for heating. Cooling does work, but if so, you should configure both in 2 different automations. At least for the moment.
Since this is very special you are good to go with a custom automation. But if you like you can also add a custom action to trigger this. If you are familiar with templates you can evaluate the variables in the template sensor easily.
No this is something handled by the thermostat itself. But the high flow temperature or the over preasue should be compensated by your heating system itself. A pressure equalization vessel is normally installed in a heating circuit.
Once you can black out time windows when calibration shouldnât be processed or you can enable generic calibration. In this mode the offset will be added to the target temperature of your thermostats. Be sure you set the calibrated value to zero manually / disable the external temperature feature of your thermostat.
//Sorry again for the lack of support. I am still right busy atm. Will looking for some updates & fixes soonâŠ
As of the latest HA update Iâm getting some really strange behaviour from the blueprint - I havenât changed the config but essentially this is the summary:
Context: I have a three schedules with a schedule selector. âWinterâ schedule is currently selected. It had a scheduled on period between 11am-2pm - the script kept on turning off the climate entity.
I have presence detection (with schedule) enabled from 2pm-10:30pm. It is set to require no presence for an hour but keeps turning off the climate entity as soon as there is no presence.
Either way, the script today just turns off the AC and I am having to disable it now to use my AC at all!
Trace attached and some screen shots of the log entry for the climate entity, showing the presence scenario described above.
Not clear on the cause, all was fine until yesterday (when I installed HA updates), please help!
How does the winter mode work? I have set a helper boolean to off, so the automation should not be running. But when I manually turn the heat up (because unfortunatelly we are experiencing some cold days even though I want it to be summer ) the heater gets turned off again by AHC. Is this expected behavior?
What I would love: If the winter mode is set to be inactive, I want all scheudles etc. diabled and the thermostats to be off. If someone manually changes something: keep the change. But reset everything to off in a regular intervall (once per day maybe). This cant be achieved with AHC currently, correct?
Playing with some other TRVs I found another issue with the Physical Temperature Change/Sync.
When the Sonoff TRVZB is turned to âOffâ, the temperature setpoint changes to the frost protection setpoint set in the thermostat. When you set the temperature setpoint below the frost protection setpoint (e.g. Minimum), it sometimes sets it back to the frost protection setpoint.
This all confuses the Temperature Sync pretty much and changes the comfort temperature all the way down.
I guess there are some other combinations where this fails to work as well.
I think the easiest solution would be: Only modify/sync the temperature to the thermostat setpoint if it is within a (user set) temperature band. For example, only sync if the thermostat setpoint was changed to between 18C and 23C.
The âOff If Above/Below Room Temperatureâ setting is causing an issue.
This feature works perfectly in heating mode for my air conditioner. However, thereâs a problem:
When heating is OFF and I manually turn ON the air conditioner in cooling mode, the automation turns it OFF again.
To use cooling mode, I currently have to disable the automation entirely.
For the âWinter Mode / Automation Toggleâ function I have the following template helper:
{{ (
states(âclimate.airco_woonkamerâ) != âcoolâ
) and (
states(âsensor.seasonâ) in [âautumnâ, âwinterâ, âspringâ] or
states(âinput_boolean.heating_on_offâ) == âonâ
) }}
Is the following an option for the future:
The âOff If Above/Below Room Temperatureâ function is only applied when the selected HVAC mode in the automation is active.
Hi! I am wondering if you can help me here - I have used your blueprint before and after some trial and error (learning curve on my part), found it great! However I have a new challenge for it, and Iâm struggling.
I have built a craft room for my wife, and installed an Electriq mini split AC system that heats and cools (building is separate to the house). I am attempting to control the climate in such a way that when she is in the room, the air con is set to 21, and when the room is empty, allow a maximum temperature of 28 before cooling kicks in, and a minimum temperature of 14 before heating kicks in.
The room has a presence sensor, and a temperature sensor both of which are reporting to HA OK.
The air con unit supports heat and cool modes, auto (according to the manufacturer) is a hard coded 25 degrees with no option to change. Heat_cool I am testing, but I do have the room cooling at the moment with just cool set in the blueprint.
Am i correct in thinking that the automation will support this, Iâm just being too thick to have it work correctly at the moment?