Skip to content

v1.1.2 - Internal PUN Calculation, price per KWh and automatic update

Choose a tag to compare

@Sanji78 Sanji78 released this 22 Sep 05:55
7bb71d2

1) Native PUN calculation (no external PUN sensors)

  • The integration now computes PUN (zonal/hourly averages and band averages) internally using its coordinator.
  • Configuration options for providing your own pun_sensor or pun_mp_sensor have been removed— the integration will always use its internal PUN calculation.
  • This simplifies setup (no need to create or maintain external PUN sensors) and ensures consistent, predictable PUN data for all bill calculations.

2) New sensor.bill_kwh_price

  • New sensor: sensor.bill_kwh_price
  • Purpose: exposes the effective price per kWh used in bill computations.
  • Calculation (conceptual): the sensor aggregates the per-kWh components (PUN, network losses, per-kWh fees and system charges) so you can inspect or reuse the exact €/kWh value used by the bill sensors.
  • Unit: €/kWh

3) Automatic refresh every 10 seconds

  • The integration now performs automatic refreshes of PUN / price data every 10 seconds by default.
  • This keeps hourly and band status accurate and promptly updates dependent sensors (useful if you want near-real-time feedback).
  • Performance note: a 10-second refresh interval increases polling frequency — if you run many integrations or have resource constraints, monitor Home Assistant performance and logs. If needed, reduce the interval by editing the integration code or configuration

Breaking changes

  • External PUN sensors are no longer supported. If you previously pointed the integration at external sensors (via pun_sensor / pun_mp_sensor), those settings are now ignored. The integration calculates PUN internally and will populate the following (example) sensors automatically:
  • sensor.pun_orario — hourly PUN price for the current hour (and hourly history in attributes)
  • sensor.pun_mono_orario / sensor.pun_mono_orario_mp — monthly averages
  • sensor.pun_fascia_f1, sensor.pun_fascia_f2, sensor.pun_fascia_f3 (and _mp previous-month variants)
  • sensor.pun_fascia_f23 / sensor.pun_fascia_f23_mp
  • sensor.pun_fascia_corrente and sensor.pun_prezzo_fascia_corrente
  • sensor.pun_prezzo_zonale
  • Because this is a breaking change for users relying on custom PUN sources, we recommend treating this release as a minor bump (your choice). In case you won't see sensors under the device named Bolletta, just remove the integration and add it again.