Belpex H integration?

[Frank-Leysen]

Hi, I live in Belgium and our electricity prices are based on Belpex H, so the hourly prices, not per quarter hour. I had the Nordpool integration in my Home Assistant system for a while, but I saw that there are quite some differences between Nordpool and Belpex H. So I switched to the Belpex/ENTSO-E/België integration. Could Belpex H be integrated in ChargeIQ? Thanks.

[johanzander]

If it has a home assistant integration, I am sure it could!

[Frank-Leysen]

Thanks! Yes, I'm using the "ENTSO-e Transparency Platform" Home Assistant integration.
Relevant entities/attributes on my system:

• sensor.belpex_h_current_electricity_market_price — current spot price
• sensor.belpex_h_average_electricity_price — attributes prices_today / prices_tomorrow

Example attribute structure:

"prices_today": [
  {"time": "2026-06-12T00:00:00", "price": 0.08555},
  ...
]

My supplier (Luminus dynamic) applies this on an hourly basis today, but I know other Belgian suppliers already use 15-minute intervals.

Happy to help test or provide debug logs if useful.

[bess-agent]

Hi @Frank-Leysen 👋 — ENTSO-e / Belpex support is now available to try in an experimental beta (v9.5.0b2).

To install it:

1. In Home Assistant: Settings → Add-ons → Add-on Store → ⋮ (top-right) → Repositories, and add:
   https://github.com/johanzander/bess-manager-beta
2. Install "BESS Manager (Beta)" from that beta repository. It's a separate add-on from your stable BESS Manager — you can keep both installed at the same time, but only one can run at a time (they share the same port). So stop the stable "BESS Manager" before starting "BESS Manager (Beta)", and switch back the same way when you're done.
3. In the setup wizard / pricing settings, choose "ENTSO-e / Belpex (Transparency Platform)" as the price provider — it should auto-detect your sensor.belpex_h_average_electricity_price.

What would help us most:

• Confirm the buy/sell prices look right for your Luminus dynamic tariff. ENTSO-e prices are VAT-exclusive spot prices, so set your VAT / markup / grid fees in the pricing section (and if you configured a VAT modifyer inside the ENTSO-e integration itself, set the add-on's VAT multiplier to 1.0 to avoid double-counting).
• From the Health tab, export a debug report and attach it here. That captures your exact config (inverter + sensors + the ENTSO-e entity) and lets us add your setup to our automated regression tests so it can't silently break in a future release.

⚠️ This is experimental and not yet real-world validated — your feedback is exactly what we need to graduate it to a stable release. Thanks for offering to test! 🙏

(Automated message from the project's bess-agent — a human maintainer will follow up on anything that needs a decision.)

[bess-manager-claude-bot]

This is a feature request for Belpex H / ENTSO-e pricing integration, which the team has already rolled out as an experimental beta (v9.5.0b1). The previous bot comment has testing instructions — we're currently waiting for debug logs from the test to validate the implementation. No action needed from triage; this will be escalated once you've tried the beta and reported back. 👍

[bess-agent]

🛰️ Lifecycle tracker — ENTSO-e / Belpex

(Maintained by bess-agent; updated in place as we progress. Path from experimental beta → stable release.)

• 1. Implemented & shipped experimental — live on the beta channel as v9.5.0b2, installs as a separate "BESS Manager (Beta)" add-on (runs alongside the stable install).
• 2. Your debug log ← we're here — install the beta, pick the ENTSO-e / Belpex provider, then export a debug report from the Health tab and attach it here (see the instructions in the comment above).
• 3. Lock your config into the regression suite — your real (anonymized) setup — inverter, sensors and the ENTSO-e entity — becomes a permanent automated test.
• 4. Re-ship beta, CI green — with your config in the test matrix.
• 5. You confirm it works on your hardware.
• 6. Promote to stable — remove the "experimental" label and ship in a normal release (this issue closes then).

[Frank-Leysen]

Thank you very much for your very fast response and fix, Johan. I will be very busy the next days with other stuff, but I will definitely keep you posted about the results on my HA system.

Have a nice weekend,
Frank

[Frank-Leysen]

Hi Johan,

Sorry it took so long before I installed the Beta.

ENTSO-e/Belpex beta works on my system — thanks again. Two follow-ups:
1. Currency locked to SEK in Electricity Pricing (should be EUR for Belgium).
2. Price calculation mismatch — Belgian dynamic contracts (e.g. Luminus) don't fit the Nordic (spot + markup) × VAT + costs model.
Preferred fix: let BESS read pre-calculated HA template sensors with raw_today / raw_tomorrow:

• Import: sensor.prijs_elektriciteit_all_in_per_uur (EUR/kWh, VAT-inclusive)
• Export: sensor.prijs_elektriciteit_injectie_per_uur (EUR/kWh, 0% VAT)
  Both derived from sensor.belpex_h_average_electricity_price. Treat as final prices — skip markup/VAT fields. Hourly slots (24 periods) should be supported.
  Our Luminus math (if useful):
• Import: (spot × 1.0175 + 0.1984) × 1.06
• Export: spot × 1.018 − 0.012685
  Fixed multipliers, not additive markup. Happy to share full breakdown + debug report.
  Growatt GEN4 Modbus: 23/23 sensors OK. Testing alongside Predbat (read-only).
  Frank

Please find the full remarks here:

bess-manager-belgium-pricing-feedback.md

[johanzander]

thank you! Could you also export debug logs from BESS - it helps us know config entries and unique ids and add your config to the regression suite! You find the export function in the top right corner, second button from the right!

[Frank-Leysen]

Update: Energy Monitoring fixed on my side.

Root cause was twofold:

1. Lifetime sensors were auto-mapped to Growatt Cloud names (lifetime_*)
   instead of solax_modbus GEN4 names (total_*)
2. Several correct Modbus lifetime entities were disabled in HA
   (disabled_by: integration) — enabling them fixed the 404 errors

Correct mappings for my Growatt MOD 5000TL3-XH (solax_modbus GEN4):

• Import: sensor.pv_growatt_total_grid_import
• Export: sensor.pv_growatt_total_grid_export
• Solar: sensor.pv_growatt_total_solar_energy
• Battery charged: sensor.pv_growatt_total_battery_input_energy
• Battery discharged: sensor.pv_growatt_total_battery_output_energy
• Load consumption: sensor.pv_growatt_total_load_energy

Health is now OK. Debug report attached separately.

Frank

bess-debug-2026-06-21-105722.md