Belgium, flanders

[MrOzzOnline]

New prices starting from 1/1/2023

The price for injection (= injectietarief) is without tax and costs. You can use the unmodified value.

{% set s = {
"bijz_accijns": 0.014416,
"energiebijdrage": 0.0020417,
"groenestroom_wkk": 0.02184,
"kwh_tarief": 0.0374193,
"VAT": 1.06,
"marge": 0.002040
} %}
{{((current_price + s.marge) * s.VAT + s.bijz_accijns + s.energiebijdrage + s.groenestroom_wkk + s.kwh_tarief) | float}}

Remarks:

• The value for "kwh_tarief" is different by region. These prices are for the region Antwerp.
• "marge" is the additional margin the supplier takes on the epex spot prices.
• These prices don't include the average peak costs.

Costs per region:

You can find these values on the cost sheets of your energy supplier (for example: https://www.engie.be/nl/energie/elektriciteit-gas/prijzen-voorwaarden/)

The distribution cost details can be found here:
https://www.vreg.be/nl/periodieke-nettarieven-elektriciteit-en-aardgas-2023

[elRadix]

Thank you!

[TsaneTips]

I think the cost voor "bijdrage groene stroom & WKK" is missing?

{% set s = {
"distributiekosten": 0.0787,
"transportkosten": 0.0115,
"bijz_accijns": 0.014416,
"energiebijdrage": 0.002042,
"groenestroom_wkk": 0.002544,
"VAT": 1.06
}
%}
{{(current_price * s.VAT + s.distributiekosten + s.transportkosten + s.bijz_accijns + s.energiebijdrage + s.groenestroom_wkk) | float}}

[Stinosko]

groenestroom_wkk should be 0.02544 or am i wrong?

[MrOzzOnline]

groenestroom_wkk should be 0.02544 or am i wrong?

Nope, you are right. I'll get it 100% right sooner or later ..

[blowk]

From 2023, the distribution cost will be calculated different.
Then it wil be changed to the capacity tariff, but for now I don't have the exact calculation for it.

[elRadix]

@MrOzzOnline you forgot to add a comma at the vat line

[MrOzzOnline]

@MrOzzOnline you forgot to add a comma at the vat line

thanks, corrected it

[elRadix]

it's a bit strange that the actual price in vtest.vreg.be is about 70c/kWh and in Entso-e around 21c/kWh... anything missing?

[Stinosko]

On the website of Engie you can consult the base price for each hour tommorow, those match with the prices on Entso:
https://www.engie.be/nl/energie/elektriciteit-gas/prijzen-voorwaarden
"Onze commerciële tarieven" => "dagprijzen" in the right kolom.

[MrOzzOnline]

it's a bit strange that the actual price in vtest.vreg.be is about 70c/kWh and in Entso-e around 21c/kWh... anything missing?

No. The vreg price takes into account the currently higher priced contracts which have a fixed price for 1 or 3 months.

[pyto00]

1. U are comparing 2 totally different pricing schema`s.
   Luminius = Variable - Changes every 1 or 3 months
   Enstoe graph = Dynamic - Changes every hour

2. c€/kWh =/= €/kWh

[Stinosko]

Does one of you know what price you actually get when you put electricity back on the net with a dynamic contract, i assume it would be something like this?

current_price - s.distributiekosten - s.transportkosten

[elRadix]

then what would be nice to have another sensor for "Injectie prijs"

[MrOzzOnline]

then what would be nice to have another sensor for "Injectie prijs"

It's already possible using templates, but if you want to use the attributes too (for a graph for example) the template could become quite complex. I'm working on one and I'll post it when I have it ready.

As an alternative quick fix you can pull a second set of data using https://github.com/custom-components/nordpool
It isn't possible to include a custom VAT in this integration, so it's a perfect fit for the injection prices.

At the moment I have this combining both integrations:

[MrOzzOnline]

Code for the graph above:

type: custom:apexcharts-card
graph_span: 48h
span:
  start: day
all_series_config:
  stroke_width: 1
  show:
    in_brush: true
now:
  show: true
  label: Nu
header:
  show: true
  title: Electriciteitsprijzen - afname (€/kwh)
experimental:
  brush: true
series:
  - entity: sensor.current_electricity_market_price
    name: Prijs nu
    stroke_width: 2
    float_precision: 4
    type: column
    opacity: 1
    color: ''
    data_generator: |
      return entity.attributes.prices_today.map((record, index) => {
        return [record.time, record.price];
      });
  - entity: sensor.current_electricity_market_price
    name: Zelfde tijd morgen
    stroke_width: 2
    float_precision: 4
    type: column
    opacity: 0.7
    color: ''
    data_generator: |
      return entity.attributes.prices_tomorrow.map((record, index) => {
        return [record.time, record.price];
      });
  - entity: sensor.nordpool_kwh_be_eur_5_10_0
    name: Injectie nu
    opacity: 1
    stroke_width: 2
    float_precision: 4
    type: column
    color: ''
    data_generator: |
      return entity.attributes.raw_today.map((start, index) => {
        return [new Date(start["start"]).getTime(), entity.attributes.raw_today[index]["value"]];
      });
  - entity: sensor.nordpool_kwh_be_eur_5_10_0
    name: Injectie morgen
    stroke_width: 2
    float_precision: 4
    type: column
    color: ''
    opacity: 0.5
    data_generator: |
      return entity.attributes.raw_tomorrow.map((start, index) => {
        return [new Date(start["start"]).getTime(), entity.attributes.raw_tomorrow[index]["value"]];
      });
apex_config:
  yaxis:
    opposite: false
    reversed: false
    logarithmic: false
    decimalsInFloat: 4
    labels:
      show: true
    tooltip:
      enabled: true
    crosshairs:
      show: true
  xaxis:
    labels:
      show: true
      rotate: -45
    logarithmic: true

[MrOzzOnline]

then what would be nice to have another sensor for "Injectie prijs"

It's already possible using templates, but if you want to use the attributes too (for a graph for example) the template could become quite complex. I'm working on one and I'll post it when I have it ready.

Template code (put it in configuration.yaml) to extract the additional costs (VAT + distribution) using both this sensor and nordpool:

template:
    - sensor:
        - name: "distributiekosten_en_btw"
          unit_of_measurement: "€/kWh"
          state: >
            {% set totaal_prijs = states('sensor.current_electricity_market_price') | float %}
            {% set netto_prijs = states('sensor.nordpool_kwh_be_eur_5_10_0') | float %}
          
            {{ totaal_prijs - netto_prijs | float }}

[JaccoR]

I am currently working on a way to add multiple instances of this integration. This way you could add two instances, one with a template for feed back prices and one with the normal prices!

[Stinosko]

I calculate the actually price at the chart.

graph_span: 24h

span:
  start: day
now:
  show: true
  label: Now
header:
  show: true
  title: Electriciteitsprijzen Vandaag (€/kwh)
series:
  - entity: sensor.current_electricity_market_price
    name: "Afname prijs"
    stroke_width: 2
    float_precision: 3
    type: column
    opacity: 1
    color: ''
    data_generator: >
      return entity.attributes.prices_today.map((record, index) => {
      const s = {"distributiekosten": 0.0942,
        "transportkosten": 0.0126,
        "bijz_accijns": 0.014416,
        "energiebijdrage": 0.002042,
        "groenestroom_wkk": 0.02544,
        "VAT": 1.06}
      return [record.time, (record.price * s.VAT + s.distributiekosten +
      s.transportkosten + s.bijz_accijns + s.energiebijdrage +
      s.groenestroom_wkk)];

      });
  - entity: sensor.current_electricity_market_price
    name: "Teruggave prijs"
    stroke_width: 2
    float_precision: 3
    type: column
    opacity: 1
    color: ''
    data_generator: >
      return entity.attributes.prices_today.map((record, index) => {
      return [record.time, record.price];
      });

yaxis:
  - min: 0
    decimals: 3
    align_to: 0.1

[JaccoR]

In the new release, VAT can be added as an config option. This means the template does not need the VAT anymore.

[elRadix]

@MrOzzOnline can you please adjust the template since the new release and maybe add one for 'Injectie prijs'

[MrOzzOnline]

@MrOzzOnline can you please adjust the template since the new release and maybe add one for 'Injectie prijs'

I noticed the calculation of VAT is not correct. See #54.

'injectie prijs' is the unmodified value and doesn't need a template.

[MrOzzOnline]

I noticed the margin the supplier takes (only Engie at the moment) isn't included in the price template. According to their conditions:

The 0,2040 is actually c€/kWh while the spot price is in €/MWh which is why they are multiplying it by 0,1 which is the result of /1000 (MWh to kWh) x 100 (€ to c€).

This integration gets the price in €/kWh so the actual margin used is 0,002040 €/kWh. This is before tax so the general formula becomes: (spot price x margin) x VAT + costs.

I changed the template in the first post.

[Stinosko]

They couldn't make any simpler 🙄

It guess it will become more difficult when they start calculating the distribution cost by the peak consumption...

[MrOzzOnline]

The way the additional costs are calculated has changed. New template in the first post.

[Stinosko]

How do you know that the VATs are added after all other cost are calculated?
The pdf of engie explaining the costs states prijzen inclusief 5% BTW so i assumed that most cost are already calculated with the 6% VATS?
So i was calculating the cost by:

(current_price + s.marge) * s.VAT + s.federale_accijns + s.energiebijdrage + s.groenestroom_wkk + s.kwh_tarief 

[BliXem1]

Correct, but it's 6% BTW and not 5%. So most prices are included with VAT but the current_price it's not.
The latest document of Engie Dynamic has been uploaded: https://www.engie.be/api/engie/be/ms_1/pricing/v1/public/pricesAndConditionsPDF?document=E_DYNAMIC_R_GREY_C_I_12_V_N&monthOffset=0&segment=R&language=N

[Stinosko]

Oooh yes 6% BTW, my mistake

[BliXem1]

Oooh yes 6% BTW, my mistake

I've still got this:

{{ ((current_price + marge) * VAT + distributiekosten + transportkosten + bijz_accijns + energiebijdrage + groenestroom_wkk) |float }}

The current_price + marge * VAT and then + everything. But dunno why @MrOzzOnline did change it in his post. I know about the changes of the peak price.

[BliXem1]

OK I changed it now too:

      {% set VAT = 1.06 %}
      {% set kwh_tarief = 0.0394475 %}
      {% set bijz_accijns = 0.0144160 %}
      {% set energiebijdrage = 0.0020417 %}
      {% set groenestroom_wkk = 0.02714 %}
      {% set marge = 0.002040 %}
      {{ ((current_price + marge) * VAT + kwh_tarief + bijz_accijns + energiebijdrage + groenestroom_wkk) |float }}

I'm using nordpool for now because I don't have access to the API yet. See screenshot, tomorrow will be a expansive day?
https://ibb.co/fqvWnG4

[MrOzzOnline]

Allright, I did some more digging:

You can find the full details of the distribution fees here:
https://www.vreg.be/nl/periodieke-nettarieven-elektriciteit-en-aardgas-2023

"Totaal kWh-tarief" mentioned at the Engie price sheet for distribution is actually:
(kWh-tarief + openbaredienstverplichtingen (normaal of nacht) + Tarieven voor de toeslagen + overige transmissienetkosten) * VAT
For Antwerp: (0,0090800 + 0,0215095 + 0,0011539 + 0,0035578) * 1.06 = 0,037419272 €/kWh or 3.74193 c€/kWh as in the sheet.

I'll update the first post.

[BliXem1]

I have nordpool and the entso api running, but there is a big difference in price, any idea why? And yes, both have the right calculation (kwh-tarief, etc etc). Which one is the right oned to check for the Belgium energy prices?

See screenshot: https://ibb.co/L09Mqzz

[MrOzzOnline]

the additional costs value is in euro while you values are in cents?

[BliXem1]

Well.. It's frustrating me now. I got the same results as Nordpool with the additional costs value, added in entso-e:

type: custom:apexcharts-card
graph_span: 24h
span:
  start: day
  offset: +1d
now:
  show: true
  label: Now
header:
  show: true
  title: Electriciteitsprijzen Morgen (€/kwh)
series:
  - entity: sensor.average_electricity_price_today
    stroke_width: 2
    float_precision: 3
    type: column
    opacity: 1
    color: ''
    data_generator: >
      return entity.attributes.prices_today.map((record, index) => { const s =
      {"kwh_tarief": 0.0394475,
        "bijz_accijns": 0.0144160,
        "energiebijdrage": 0.0020417,
        "groenestroom_wkk": 0.02714,
        "marge": 0.002040,
        "VAT": 1.06}
      return [record.time, ((record.price + s.marge) * s.VAT + s.kwh_tarief +
      s.bijz_accijns + s.energiebijdrage + s.groenestroom_wkk)];

      });
yaxis:
  - min: 0
    decimals: 3
    align_to: 0.1

See the results here: https://ibb.co/GkVsdQy
These are the results for tomorrow....... 3 Jan with nordpool 27,8 and with ento-se 28,1. Maybe you can give me some examples how you setup this and I can adjust it then?

[MrOzzOnline]

Both prices are wrong. The price for tomorrow at 23:00 is €0.177 (in Antwerp).

You need to remove all variables and check what is wrong. Do you get the correct value without the template? Something wrong with your chart config?

To me it looks like you've added the template twice. Once in the config, once in the chart, which would explain the error.

[BliXem1]

Yeah, removed the extension and added it again, without any VAT or add. costs, it's not showing a correct price within ents-o, within the nordpool it does it correct and it tells me what you did say, tomorrow 0.00 13cents. So Nordpool is correct now.
When I check ents-o it's showing 0,223 cents at 0.00 tomorrow. I really don't understand it anymore.

type: custom:apexcharts-card
graph_span: 24h
span:
  start: day
  offset: +1d
now:
  show: true
  label: Now
header:
  show: true
  title: Electriciteitsprijzen Vandaag (€/kwh)
series:
  - entity: sensor.average_electricity_price_today
    name: Afname prijs
    stroke_width: 2
    float_precision: 3
    type: column
    opacity: 1
    color: ''
    data_generator: >
      return entity.attributes.prices_today.map((record, index) => { const s =
      {"distributiekosten": 0.0,
        "transportkosten": 0.0,
        "bijz_accijns": 0.0,
        "energiebijdrage": 0.0,
        "groenestroom_wkk": 0.0,
        "VAT": 0.00}
      return [record.time, (record.price + s.distributiekosten +
      s.transportkosten + s.bijz_accijns + s.energiebijdrage +
      s.groenestroom_wkk)];

      });
yaxis:
  - min: 0
    decimals: 3
    align_to: 0.1

There is no config within price modifyer and VAT is on 0.00 within the config.

I will check it tomorrow again...

[BliXem1]

Got it right now, there is a difference of 0.002 euro. Are the prices correct at your side @MrOzzOnline ?

I added this:

{% set correctie = 0.002 %}

Which fixes everything now :)

[Piloteer1]

How do you use new 'capaciteitstarief' in this template? As far as I know, it's replacing the distribution and transport kost.

[MrOzzOnline]

How do you use new 'capaciteitstarief' in this template? As far as I know, it's replacing the distribution and transport kost.

It's not completely replacing it, just part of it. This rate is based on your monthly peak use and not on the current electricity usage. You can read the peak values using the https://www.home-assistant.io/integrations/dsmr_reader integration.
You can find the rates here: https://www.vreg.be/nl/periodieke-nettarieven-elektriciteit-en-aardgas-2023

This is not an Entso-e issue

[blowk]

How do you use new 'capaciteitstarief' in this template? As far as I know, it's replacing the distribution and transport kost.

This is difficult because this a variable price according to your own energy use.
This extension is mainly for the price of the energy component and used with a dynamic energy contract.

[blowk]

Sorry, my calculation is wrong. I thought the price was per kWh/year, but it's kW/year.
The cost will be the average of 12 months.
For example if the average capacity is 2.5, then the price is 2.5 * 43.6742.
2.5 is minimum.
In order to add the cost, you need a HA helper with the average peak value (sum of all peak values from each month divided by 12). Multiply this with the cost (43.6742) and dividing this with 8.760 (365 days * 24 hours).
0,0124640982 euro per hour. This value will be dynamic based on the average peak.

[Piloteer1]

Thanks for the reply and thinking with me. I however would like to have the minimum price in the template.
I only use HA for standard integrations and very specific integrations. All other intelligence is all done in Node-red.
Maybe below assumption and calculation can be challenged?
In the my energy app (Engie), it is mentioned the 'peak without additional cost' = 0,63 kWh (notice, no longer kW but kWh).
May I assume, 0,63 kWh has a cost of € 109,1855 (= 43,6742 €/kW/year *2,5).
109,1855 / 0,63 = 173,3103
173,3103 / 365 / 24 = 0,019784283 / kWh to add in the template.
Any idea if this can be correct?

[blowk]

I think you can't use your 0,63 peak value. The minimum will still be 2.5 (although you have lower peak value), so you don't have to divided by 0.63.

[Piloteer1]

In the app with overview of price and usage, as explanation for 'capaciteitstarief' you can find the below paragraph (screenshot in Dutch).
2,5 kW Peak is equal to 0,63 kWh.
If your peak is below, you pay the standard fee of 43,6742 €/kW/year.
At least that is my understanding.

[blowk]

0.63kWh is per 15 minutes.
Dynamic price is per hour so the price has only be divided by 8760.

[weemaba999]

Does anyone know, using the ENTSO-E integration, why I have for the tomorrow prices : N/A instead of the prices in the chart ?

Thanks in advance !

Bart

[blowk]

I use publish. Never tried to other options.

[weemaba999]

Very weird, here too

I posted a screenshot on the ENTSO-E community page on HAS community:

https://community.home-assistant.io/t/custom-component-entso-e-day-ahead-energy-prices/467127/91

[weemaba999]

What I've also noticed, that in development tools > status , my entso-e sensors give pricing for today 2023-09-29 and for tomorrow 2023-09-28 ????!!!! how is that possible :-)

[blowk]

Which version do you run?

Have you tried to remove the integration and re-add it again?

[blowk]

I'm using v0.3.0

My settings are