github springfall2008/batpred v9.5.0
Hypervolt EV charger, GE Cloud EV-only mode and PV calibration clipping fix

2 hours ago

What's new in v9.5.0

Hypervolt EV charger component: a Hypervolt charger now works with Predbat directly, on Predbat.com and Docker as well as in Home Assistant, without the regex wiring and start/stop automation described in the devices guide. Every charger on the account is published as {prefix}_hypervolt_<id>_* entities, and car_charging_energy, car_charging_planned, car_charging_plugged, car_charging_power and car_charging_now are configured automatically. Set hypervolt_control to let Predbat start and stop each charger from its car's plan (off by default). Config keys: hypervolt_username, hypervolt_password, hypervolt_automatic and hypervolt_control.

GE Cloud: EV charger without the inverter: GE Cloud Direct now has separate monitor and control settings for the inverter and the EV charger. Until now, using a GivEnergy EV charger through GE Cloud meant setting ge_cloud_direct: true, which also brought in the inverters and reset their settings once a day. That was a problem where GivTCP or the GivEnergy app runs the inverter. Use the new ge_cloud_evc_direct: true for the charger on its own, and ge_cloud_inverter_control (default true) to monitor the inverter without controlling it. Existing configs with ge_cloud_direct: true behave exactly as before.

PV calibration no longer learns inverter clipping as forecast error: where the array can produce more than the inverter can pass, sunny-day generation is capped at the inverter limit. Calibration treated those capped readings as exact, so a clipped sunny week scaled the next sunny day's forecast down (for example an 18 kW forecast calibrated to 13.8 kW on an 11.5 kW inverter). The planner then left too little room in the battery ahead of the solar peak. Readings at the clipping limit are now treated as "at least this much", for both the P50 forecast and the PV10/PV90 band.

Intelligent Octopus with two cars: the daily cap on cheap dispatch time (octopus_slot_max) is per account, but Predbat applied it per car. With two Intelligent cars on a capped tariff, up to twice the allowance was planned as cheap and then billed at the day rate. The cap is now shared between the cars, counted in clock time. Also, a car charging on either charger now confirms an Intelligent dispatch, so a dispatch is no longer cancelled when Predbat's car numbering differs from the charger Octopus controls.

EV chargers

Octopus

Inverters

Plan and execution

Predbat gateway and MCP

  • Gateway: measured Hub display feed and independent visibility by @mgazza in #5714
  • Gateway: declare the inverters Predbat controls with set_commanded_serials by @mgazza in #5722
  • Gateway: report a silent hub as unhealthy by @springfall2008 in #5713
  • MCP: serve /mcp-scoped protected resource metadata and CORS preflight on token/register (#3807) by @springfall2008 in #5622

Documentation

New Contributors

Full Changelog: v9.4.6...v9.5.0

Don't miss a new batpred release

NewReleases is sending notifications on new releases.