🔥 Advanced Heating Control

Blueprints Exchange
, ,
3491

Hello @panhas, I’d like to revisit the request for a Timed Manual Override (reverting the temperature after X minutes). Previously, you indicated this being impossible due to a bug in Home Assistant that prevented the automation from distinguishing its own actions from manual adjustments (ui or device).

Do you think this bug has been resolved in recent HA updates? I’ve been looking into the event logs, and it seems the context object now identifies the source of a change.

See the “log snippet” where the parent_id is null, it could identify true manual overrides (physical or UI) without being triggered by its own logic.

Technical Data from Logs:

  1. From Automation (parent_id is populated):

YAML context:
parent_id: 01KNW8CCCJB5VD7XE8MN5BTW48
user_id: null`

  1. From Physical Device (parent_id and user_id are both null):

YAML context:
parent_id: null
user_id: null`

  1. From User UI (user_id is populated):

YAML context:
parent_id: null
user_id: a865cdb8…`

If you think this is now technically feasible now (bug is solved), I would love to help write this feature via a Pull Request. What are your thoughts?

3492

Hi everyone!

I try to insert in Heating Schedule Adjustments the following but time is ignored, the comfort and eco temperatures are immediately applied.

  • time: “20:00”
    comfort: “24”
    eco: “17”

I don’t understand. What I’m doing wrong?

Many thanks for your help.
Stéphane

3493

Hey, me again.

I think the “Winter mode / Automation Toggle” is not working quite right. I have an entity that is on when I want the heating automations to work, then I planned to turn it off around this time of year, and according to the helper text, the automations “go to sleep”.

Except they don’t go to sleep. They are very much still running, just to turn everything off!

E.g. I wanted to toggle a radiator on manually so we can heat the bathroom up. Thermostat turned on, but then the automation runs and turns that radiator off within 5 seconds. Not quite what I was expecting. If I have toggled the automation off, I would expect it to not run. I guess I just have to disable the automation instead? Not as helpful as I thought :joy:

3494

Hi all,
since my update from AHC V5.3 to V5.5, I see in the logger the following error:

Logger:
homeassistant.components.automation.thermostatsteuerung_wzez_neu
Quelle: components/automation/init.py:814
Integration: Automation (Dokumentation, Probleme)
Erstmals aufgetreten: 16:30:19 (4 Vorkommnisse)
Zuletzt protokolliert: 16:32:24

Error rendering variables: ValueError: Template error: float got invalid input ‘None’ when rendering template ‘{% if trigger.id == ‘temperature_change_valve_target’ %} {{ trigger.to_state.attributes.temperature | float }} {% else %} {{ none }} {% endif %}’ but no default was specified

I isolated this behaviour to the situation, when the thermostat goes to “off” triggered by an open window.
Controlling the thermostat by window open/close works fine, except this error-message.

Any help appreciated.

3496

Hi all again,

Is there anybody out there?

3497

Hello everyone,

I’ve been using the AHC Blueprint for quite some time now. I’ve always kept Home Assistant up to date, but until recently, I was still using version 4 of AHC. An update to Home Assistant has apparently caused breaking changes, resulting in AHC sporadically turning the thermostats up to full power despite them being in winter mode. For this reason, I updated to AHC V5. This resolved the aforementioned issue. However, I’ve now noticed a different problem.

I use Home Assistant Green (the current version) with a Nabu Casa Z-Wave USB antenna and older Devolo Z-Wave radiator and room thermostats. These require a few settings in the Blueprint, such as generic calibration and setting "min" instead of "off".

I use an input_helper to switch between summer and winter modes. When I activate summer mode, the thermostats are set to their minimum (AHC selects 0 °C here), after which the thermostat adjusts this to its minimum of 4 °C. Up to this point, the behaviour is identical to that of AHC V4.

However, the generic calibration in AHC V5 does not respect the switch to summer mode, instead adjusting the set value to 3.5°, 2° or 5°, and so on.

The TRV resets any value below 4°C back to 4°C, which triggers the generic calibration.

Every few minutes, the automation is activated, triggering the corresponding Z-Wave radio traffic. If I disable the generic calibration, there is radio silence.

This is also clearly visible in the thermostat’s temperature graph, showing whether the setpoint is set to 0° every five minutes and immediately corrected back to 4°, or whether it remains at 4° continuously.

Could the generic calibration be failing to turn off or on with the summer/winter mode switch?

Thank you in advance for checking whether others are experiencing this behaviour and for providing a brief response.

Best regards

3499

Hey there,
Is it possible to change Off If Nobody Home to Eco If Nobody Home?
I don’t want 5 degrees in wintertime when nobody is home.
Thanks

3500

@NebuNC2

I don't use Away Mode, but it seems possible to adjust the offset temperature. Here is a screenshot:

grafik
grafik941×618 89.7 KB