I have a template that looks for a Radiator TRV to be in boost mode to then display that on the dashboard.
Today it is showing as ON but it shoudlnt be.
This is what shows:
The template is as follows:
# Boost Sensor for Radiators
- name: "Boosted Radiators"
icon: mdi:car-turbocharger
state: >
{% if states | selectattr('entity_id', 'in',
['climate.radiator_lounge', 'climate.radiator_office',
'climate.radiator_bedroom', 'climate.radiator_chloe',
'climate.radiator_charlie', 'climate.radiator_play_room',
'climate.radiator_cinema_room'])
| selectattr('attributes.is_boosted', 'eq', true) | list | count > 0 %}
ON
{% else %}
OFF
{% endif %}
Can’t quite figure that one out? No radiator should be in a boost state, I can see that a command to set the temperature in one room was issued, to set to 17 'c (cooler than current actually). That has set the TRV to the correct temperature.
Though the mini climate card shows as Boost with the time remaining, suggesting 1 hour boost
In Dev tools it also confirms boost. Maybe a Drayton Wiser integration issue rather than my templates/code? The code is seeing boosted even though it isn’t really. So my template sensor is working correctly? Though why its saying it was triggered by a completely independent and non related sensor is a mystery? If it said turned on because radiator.charlie is in boost it would make some sense at least?
1 post - 1 participant