I have been using the Hive integration for a while and tend to use the boost function more than the schedule and wanted the ability to be able to configure the boost on the dashboard in the same way as the Hive app.
I have also tried to replicate the Hive usage graphs by using history helpers. I would like to do some analysis or comparisons in the future but haven’t got round to that yet!
Description:
Heating - shows whether the heating is currently on or off (i.e. if the current temp is below the target temp)
Boost off: Turns the current boost off
Minutes: Number of minutes remaining of the current boost
Target temp: The current target temp of the thermostat
Current temp: The current temp of the thermostat
Boost 30 mins: Boosts for 30 mins to 21 °C
Boost 1 hour: Boosts for 1 hour to 21 °C
Boost - Hours: Number of hours to boost for
Boost - Temp: Temperature to boost to
Boost: Whether the boost is active or not
Requirements:
Hive HACS integration - this provides additional sensors compared to the core component. You can also use the core component but the information for the remaining boost time is not available.
Mushroom cards (HACS)
Creation of a number helper named “thermostat boost hours”, set the step size to 0.5 (or less if you’d like)
Creation of a number helper named “thermostat boost temperature”, set the step size to 0.5 (or less if you’d like)
Creation of a script named “heating boost with inputs” with the following code:
alias: Boost heating with inputs
sequence:
- action: hive.boost_heating_on
metadata: {}
data:
entity_id: climate.thermostat
time_period: |
{% set m = (states('input_number.thermostat_boost_hours')|float * 60)%}
{{'%02i:%02i:%02i'%(m/60,m%60,(60*m)%60) }}
temperature: |
{{ float(states('input_number.thermostat_boost_temperature')) }}
A script was required as using a button to call an action didn’t seem to accept variables for time and temperature.
Creation of a template sensor to track if the heating is on or not. The device class is set to measurement to persist the data as the standard hive entity histories are wiped according to the recorder settings
Yaml for templates/config.yaml
Creation of history stats helpers to track the period you’d like to graph. I have created daily, weekly and monthly helpers. Set the entity to ‘heating_on’ and the state to ‘1’. This sensor will only start tracking from when it is created and is not backdated.
Thanks for this, the history stats helpers were really interesting, I’d not used them before and will give me some nice graphs in the days/weeks/months to come!
You can also double check the attribute exists in your installation, if you go to developer tools and click states, you can search for the entity to see if the attribute is there:
Ah glad you’ve got it working! Sorry I had forgotten that I was using the HACS Hive integration too, it must provide additional sensors that I wanted.
Do you mean the 30 mins and 1 hour buttons plus the modifiable temp/hours buttons? I have been using the 30 mins/1hour buttons for the past 18 months and have only recently added the custom boost section. I am keeping the quick 30 mins/1 hour buttons for now because sometimes I want to quickly turn the heating on briefly.
Hi Millie!
I am new to Hive and to HA… While I had a little problems with your code/screens (mainly because my thermostat was renamed to thermostat_2) and I was also missing Hive Custom Component, I finally got it working (ok ChatGPT helped too)…
Good job man, you created really nice screens… At the moment I plan to use Hive in “Cloud” mode, so that I can also use their original app, so your screens are real help…