-
-
Save klaasnicolaas/ccfd1cd3da62a13b3199ff378480bdbb to your computer and use it in GitHub Desktop.
- type: custom:apexcharts-card | |
graph_span: 1d | |
header: | |
show: true | |
title: Electriciteitsprijzen Vandaag (€/kwh) | |
span: | |
start: day | |
now: | |
show: true | |
label: Now | |
yaxis: | |
- id: price | |
decimals: 2 | |
apex_config: | |
tickAmount: 5 | |
series: | |
- entity: sensor.energy_prices_today | |
name: Price this hour | |
yaxis_id: price | |
data_generator: | | |
return entity.attributes.prices.map((entry) => { | |
return [new Date(entry.timestamp).getTime(), entry.price]; | |
}); | |
type: column | |
show: | |
extremas: true | |
opacity: 0.8 | |
float_precision: 2 |
--- | |
# Today - Hourly energy prices | |
template: | |
- trigger: | |
- platform: homeassistant | |
event: start | |
- platform: time_pattern | |
hours: "*" | |
action: | |
- service: energyzero.get_energy_prices | |
response_variable: response | |
data: | |
config_entry: PUT_HERE_YOURS | |
incl_vat: True | |
sensor: | |
- name: Energy prices - Today | |
device_class: timestamp | |
state: "{{ now() }}" | |
attributes: | |
prices: '{{ response.prices }}' | |
# Tomorrow - Hourly energy prices | |
- trigger: | |
- platform: homeassistant | |
event: start | |
- platform: template | |
value_template: "{{ now() > today_at('14:00') and now().minute == 0 }}" | |
action: | |
- service: energyzero.get_energy_prices | |
response_variable: response | |
data: | |
config_entry: PUT_HERE_YOURS | |
start: "{{ now() + timedelta(days=1) }}" | |
end: "{{ now() + timedelta(days=1) }}" | |
incl_vat: True | |
sensor: | |
- name: Energy prices - Tomorrow | |
device_class: timestamp | |
state: "{{ now() + timedelta(days=1) }}" | |
attributes: | |
prices: '{{ response.prices }}' |
Hey Klaas, I noticed the precision of the template sensor to grab today's and tomorrow's dynamic prices has a precision of 2 digits. All other providers, I've found, use 3 digit precision. Leading to some rounding issues. Is there any way to raise the precision for the template sensor? I've given it a unique_id and fiddled with the template and checked the python code, but I'm lost :)
Here's an example of how this looks, all other providers are on the same line :
The problem is that if you request the energy data including VAT, you get prices with 2 decimal places, if you request the prices excluding VAT, you get them with 5 decimal places.
./Klaas
That's perfect, thanks!
Thx for this awesom chart...
But how do set this chart up if I want to include costs and taxes per kWh?
I have allready setup 2 extra sensors, one for additional costs and one for taxes.
Please advise...
You can add the costs and taxes in the data_generator:
data_generator: >
return entity.attributes.prices.map((entry) => [new
Date(entry.timestamp), ((entry.price*1.21) + 0.15674)]);
My taxes are 21% and the added costs (€0.15674) already have the tax included, otherwise you'd configure it like this : (entry.price+costs)*taxes.
Thx man! My taxes ar also 21% but I pay a little less at ANWB Energy!
But this worked for me...
@BeekeeperNL The 'Toon all-in prijs' toggle is about taxes being included. In HA only VAT is optionally taken into account, not the energy tax.