#Energy Sensor struggle on multiple tarrif that are not 'peak' / 'off-peak'
1 messages · Page 1 of 1 (latest)
The tariff thing doesn't actually care what the names are (a while ago I helped someone set up a utility meter to count people's steps on a treadmill using their names as a tariff). So in the utility meter you could just call them first rate and second rate etc.
If you want to keep it consistent with the guides you are reading, I'd call the first rate "peak" and the 2nd "off-peak" as peak is the more expensive one
ok makes sense, i guess i need to follow something like this:
Calculate tariff rates in Home Assistant for accurate energy monitoring using the Home Assistant Energy Portal. Change tariffs based on kWh usage thresholds to display cost based on usage. Create templates for sensors, utility_meter entities, and automate the changes.
YAML Code: https://pastebin.ubuntu.com/p/sqnYcDd5rQ/
Become a channel member...
but he uses templates in yaml and not in the UI will this still work?
Yeah there's nothing there that needs you to edit yaml
You can use the ui helpers to do all of that
Background: With my utility supplier in the UK (Utilita Energy), I have two tariff prices which depend on how much electricity I have used. Quote below from my supplier shows for the first 2kWh of energy used, I’ll be on the high tariff. After the 2kWh is used, It moves over to the lower Tariff All Periods - First 2 kWh each Day at 35.21p p...
if i follow this guide im stuck on the template part how to add this in ui helper
- platform: template
sensors:
utilita_electric_actual_daily_cost:
friendly_name: "Utilita Elec Daily Cost"
unit_of_measurement: '£/kWh'
icon_template: mdi:flash
value_template: >-
{% if states('sensor.daily_consumption') | float > states('input_number.utilitatariff_dailykwh') | float %}
{{ states("input_text.utilitatariffrate2") | round(3) }}
{% else %}
{{ states("input_text.utilitatariffrate1") | round(3) }}
{%- endif %}