Summary
On 9.9.0b23, after day-ahead prices became available, BESS kept showing tomorrow’s buy/sell curves as flat / ~0.00 EUR and planned tomorrow with a near-useless Net Grid Cost (+0.21 EUR). Home Assistant already had a full 24h raw_tomorrow on our price sensors (after reloading the HA price integration). A BESS addon restart immediately fixed it: real price curves, sensible schedule, tomorrow Net Grid Cost −2.54 EUR.
This looks like BESS’s own ENTSO-e fetch / horizon refresh not picking up tomorrow until process restart — not “prices not published yet”.
Environment
- BESS Manager 9.9.0b23
- Growatt MOD 5000TL3-XH via solax_modbus
- Belgium / Luminus Dynamic (Belpex H) — BESS price source: ENTSO-e (
entsoe_source)
- Timezone Europe/Brussels
- Reporter: @Frank-Leysen
Observed
Before restart (~15:26–15:27 CEST, 23 Jul 2026)
- Dashboard Energy Flow: tomorrow sell ≈ 0.00 flat, buy ≈ flat low value
- Cost card: Today −1.08 EUR, Tomorrow +0.21 EUR
- Schedule for tomorrow looked populated but economically wrong given flat zeros
- Addon log during health check only showed today’s fetch, e.g.:
Fetched 24 ENTSO-e prices for 2026-07-23 (expanded to 96 quarterly periods): range 0.0054 - 0.1900 EUR/kWh
2026-07-24 line observed at that time)
Parallel: HA price sensors were already OK
After reloading our HA electricity-price integration, both:
sensor.prijs_elektriciteit_injectie_per_uursensor.prijs_elektriciteit_all_in_per_uur
had full 24-hour raw_tomorrow (realistic evening peak ~0.19 EUR/kWh injection). So the day-ahead data existed; BESS UI/optimizer still behaved as if tomorrow were empty/zero.
After BESS addon restart (~15:44–15:47)
- Tomorrow buy/sell curves normal (evening peak present)
- Tomorrow Net Grid Cost −2.54 EUR, 2-day total −3.34 EUR
- Schedule for tomorrow looks coherent again (Solar Storage → evening Selling to Grid)
Desired
When ENTSO-e day-ahead for tomorrow becomes available (or shortly after), BESS should:
- Fetch and apply tomorrow’s prices without requiring an addon restart
- Log clearly when tomorrow is fetched (
2026-07-24 / next calendar day)
- Not treat missing tomorrow hours as 0.00 in a way that drives a misleading optimization / Net Grid Cost
Debug bundles
Happy to capture another occurrence if this reproduces on a later day without restart.
Summary
On 9.9.0b23, after day-ahead prices became available, BESS kept showing tomorrow’s buy/sell curves as flat / ~0.00 EUR and planned tomorrow with a near-useless Net Grid Cost (+0.21 EUR). Home Assistant already had a full 24h
raw_tomorrowon our price sensors (after reloading the HA price integration). A BESS addon restart immediately fixed it: real price curves, sensible schedule, tomorrow Net Grid Cost −2.54 EUR.This looks like BESS’s own ENTSO-e fetch / horizon refresh not picking up tomorrow until process restart — not “prices not published yet”.
Environment
entsoe_source)Observed
Before restart (~15:26–15:27 CEST, 23 Jul 2026)
2026-07-24line observed at that time)Parallel: HA price sensors were already OK
After reloading our HA electricity-price integration, both:
sensor.prijs_elektriciteit_injectie_per_uursensor.prijs_elektriciteit_all_in_per_uurhad full 24-hour
raw_tomorrow(realistic evening peak ~0.19 EUR/kWh injection). So the day-ahead data existed; BESS UI/optimizer still behaved as if tomorrow were empty/zero.After BESS addon restart (~15:44–15:47)
Desired
When ENTSO-e day-ahead for tomorrow becomes available (or shortly after), BESS should:
2026-07-24/ next calendar day)Debug bundles
Happy to capture another occurrence if this reproduces on a later day without restart.