Community Examples
This page collects real-world examples contributed by the community β templates, automations, dashboard cards, and creative solutions built with Tibber Prices.
Before you start: All examples require adaptation to your setup. At minimum, replace entity IDs like
sensor.<home_name>_...with your own. See Settings β Devices & Services β Entities to find the correct IDs.
Country-Specific Price Calculationsβ
The Tibber API provides the raw spot price (energy_price attribute) and tax/fee component (tax attribute) on every price sensor. Since the exact composition of tax varies by country, you can use these attributes to build your own country-specific calculations with Home Assistant templates.
Tax rates and energy fees change regularly (often annually). Using input_number helpers in Home Assistant keeps your calculations up-to-date with a simple UI adjustment β no integration update needed.
The tax rates and fees shown below are examples only. Verify them against your energy provider's invoices and update them when rates change (usually January 1st).
π³π± Netherlands: Solar Feed-In Compensationβ
Contributed by community member OdynBrouwer (Discussion #105)
Backgroundβ
In the Netherlands, the electricity price paid to consumers includes:
| Component | Dutch Name | Typical Value (2025) |
|---|---|---|
| Spot price | Inkoopprijs | Variable (= energy_price attribute) |
| Energy tax | Energiebelasting | ~0.0916 β¬/kWh (excl. VAT) |
| VAT | BTW | 21% |
| Purchase fee | Inkoopvergoeding | ~0.0205 β¬/kWh |
| Sales fee | Verkoopvergoeding | ~0.0205 β¬/kWh |
The values above are examples. Check Rijksoverheid.nl for current energy tax rates and your energy contract for purchase/sales fees.
Saldering (Net Metering) β Until 2027β
The Netherlands currently uses saldering (net metering): solar feed-in is offset against consumption at the full consumer price. This effectively means you earn the total price for each kWh exported. The Dutch government has confirmed this ends in 2027.
Step 1: Create Input Number Helpersβ
Create input_number helpers in Home Assistant for each fee component. This way, when rates change (usually January 1st), you only need to update the values in the UI.
Settings β Devices & Services β Helpers β Create Helper β Number
| Helper | Entity ID | Min | Max | Step | Unit | Example Value |
|---|---|---|---|---|---|---|
| Energiebelasting | input_number.energiebelasting | 0 | 1 | 0.0001 | β¬/kWh | 0.0916 |
| BTW percentage | input_number.btw_percentage | 0 | 100 | 0.01 | % | 21 |
| Inkoopvergoeding | input_number.inkoopvergoeding | 0 | 1 | 0.0001 | β¬/kWh | 0.0205 |
| Verkoopvergoeding | input_number.verkoopvergoeding | 0 | 1 | 0.0001 | β¬/kWh | 0.0205 |
Show YAML: Input Number Helpers
If you prefer YAML configuration over the UI, add these to your configuration.yaml:
input_number:
energiebelasting:
name: Energiebelasting
min: 0
max: 1
step: 0.0001
unit_of_measurement: "β¬/kWh"
icon: mdi:lightning-bolt
btw_percentage:
name: BTW Percentage
min: 0
max: 100
step: 0.01
unit_of_measurement: "%"
icon: mdi:percent
inkoopvergoeding:
name: Inkoopvergoeding
min: 0
max: 1
step: 0.0001
unit_of_measurement: "β¬/kWh"
icon: mdi:cash-minus
verkoopvergoeding:
name: Verkoopvergoeding
min: 0
max: 1
step: 0.0001
unit_of_measurement: "β¬/kWh"
icon: mdi:cash-plus
Step 2: Template Sensors for Feed-In Compensationβ
These template sensors calculate what you earn per kWh when feeding solar power back to the grid.
Show YAML: Feed-In Compensation Sensors
template:
- sensor:
# Feed-in compensation WITH saldering (current rules, until 2027)
# With saldering, you effectively earn the full consumer price
# minus the purchase fee, plus the sales fee.
- name: "Solar Feed-In Price (with Saldering)"
unique_id: solar_feed_in_saldering
unit_of_measurement: "β¬/kWh"
device_class: monetary
state: >
{% set energy = state_attr('sensor.<home_name>_current_electricity_price', 'energy_price') %}
{% set eb = states('input_number.energiebelasting') | float %}
{% set btw = states('input_number.btw_percentage') | float / 100 %}
{% set inkoop = states('input_number.inkoopvergoeding') | float %}
{% set verkoop = states('input_number.verkoopvergoeding') | float %}
{% if energy is not none %}
{{ ((energy + eb) * (1 + btw) - inkoop + verkoop) | round(4) }}
{% else %}
unavailable
{% endif %}
icon: mdi:solar-power-variant
# Feed-in compensation WITHOUT saldering (after 2027)
# Without saldering, you only earn the raw spot price
# minus the purchase fee, plus the sales fee.
- name: "Solar Feed-In Price (without Saldering)"
unique_id: solar_feed_in_no_saldering
unit_of_measurement: "β¬/kWh"
device_class: monetary
state: >
{% set energy = state_attr('sensor.<home_name>_current_electricity_price', 'energy_price') %}
{% set inkoop = states('input_number.inkoopvergoeding') | float %}
{% set verkoop = states('input_number.verkoopvergoeding') | float %}
{% if energy is not none %}
{{ (energy - inkoop + verkoop) | round(4) }}
{% else %}
unavailable
{% endif %}
icon: mdi:solar-power-variant-outline
Step 3: Use in Automationsβ
Now you can use these sensors to make smarter decisions about when to export solar power vs. charge a battery:
Show YAML: Feed-In Automation
automation:
- alias: "Solar: Smart Export Decision"
description: >
When solar production exceeds consumption, decide whether to
export power or charge the home battery based on current
feed-in compensation vs. upcoming price forecasts.
trigger:
- platform: numeric_state
entity_id: sensor.solar_production_power
above: 2000
condition:
- condition: template
value_template: >
{# Export if feed-in price is above the next 3 hours average #}
{% set feed_in = states('sensor.solar_feed_in_price_with_saldering') | float(0) %}
{% set upcoming = states('sensor.<home_name>_next_3h_average_price') | float(0) %}
{{ feed_in > upcoming }}
action:
- service: switch.turn_off
entity_id: switch.battery_charging
Preparing for the End of Salderingβ
To understand the financial impact of the saldering phase-out, you can create a dashboard comparing both scenarios side by side:
Show YAML: Preparing for the End of Saldering
type: entities
title: "Solar Feed-In Compensation Comparison"
entities:
- entity: sensor.<home_name>_current_electricity_price
name: "Consumer Price (total)"
- type: attribute
entity: sensor.<home_name>_current_electricity_price
attribute: energy_price
name: "Spot Price (energy)"
icon: mdi:transmission-tower
- entity: sensor.solar_feed_in_price_with_saldering
name: "Feed-In with Saldering"
icon: mdi:solar-power-variant
- entity: sensor.solar_feed_in_price_no_saldering
name: "Feed-In without Saldering (2027+)"
icon: mdi:solar-power-variant-outline
π©πͺ Germany: Price Compositionβ
Backgroundβ
In Germany, the electricity price includes numerous components bundled into tax:
| Component | German Name | Description |
|---|---|---|
| Spot price | BΓΆrsenstrompreis | Variable (= energy_price attribute) |
| Grid fees | Netzentgelte | Varies by grid operator |
| Electricity tax | Stromsteuer | Fixed per kWh |
| Concession fee | Konzessionsabgabe | Varies by municipality |
| Surcharges | Umlagen (Β§19, Offshore, KWKG) | Various regulatory surcharges |
| VAT | Mehrwertsteuer | 19% |
Template: Spot Price Shareβ
A simple template sensor showing what percentage of your total price is the actual energy cost:
Show YAML: Spot Price Share
template:
- sensor:
- name: "Spot Price Share"
unique_id: spot_price_share
unit_of_measurement: "%"
state: >
{% set energy = state_attr('sensor.<home_name>_current_electricity_price', 'energy_price') %}
{% set total = states('sensor.<home_name>_current_electricity_price') | float %}
{% if energy is not none and total > 0 %}
{{ ((energy / total) * 100) | round(1) }}
{% else %}
unavailable
{% endif %}
icon: mdi:chart-pie
π³π΄ Norway / πΈπͺ Sweden: Grid & Tax Componentsβ
Norway and Sweden have their own fee structures, but the same pattern applies β use input_number helpers for the fixed/semi-fixed components and energy_price for the spot price.
Contributions welcome! If you have working template examples for Norway or Sweden, please share them in a GitHub Discussion.
Contributing Your Own Examplesβ
Have a useful template, automation, or dashboard card built with Tibber Prices? We'd love to feature it here!
- Share it in a GitHub Discussion
- Describe your use case and include the YAML code
- Tested examples that work with the current version are preferred
Community examples are attributed to their original authors.