You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
One of my automations failed a few days ago, and I ended up using way more power at the cheapest hour than intended.
My target was 2 kWh, but I ended up using 2.6, and 1.9 the next day. Now I have to stay under 1.5 kWh the next 25 days...
I've set target_energy: 1.5 and it calculates sensor.available_power_this_hour correctly, but it still says 2 kWh as target level in the sensor attributes.
New attribute specifying target_energy. Editing the YAML doesn't change the target until next reboot
Take sensor.average_peak_hour_energy into account when calculating sensor.available_power_this_hour.
The text was updated successfully, but these errors were encountered:
JanPetterMG
changed the title
Make target_energy a decimal
Dynamically calculate target_energyJan 6, 2024
Thanks for this great addon.
One of my automations failed a few days ago, and I ended up using way more power at the cheapest hour than intended.
My target was 2 kWh, but I ended up using 2.6, and 1.9 the next day. Now I have to stay under 1.5 kWh the next 25 days...
I've set
target_energy: 1.5
and it calculatessensor.available_power_this_hour
correctly, but it still says 2 kWh as target level in the sensor attributes.target_energy
. Editing the YAML doesn't change the target until next rebootsensor.average_peak_hour_energy
into account when calculatingsensor.available_power_this_hour
.The text was updated successfully, but these errors were encountered: