[1.4.0b1] - 2026-08-17
Changed
- Maximum contracted power increased to 20,000 W: the
max_contracted_powersetting in the initial setup and options flow now accepts values from 1,000 to 20,000 W (previously capped at 15,000 W). - 28-day quarter-hour household consumption profile: the integration now learns 96 local intervals from adjusted home demand across the previous 28 days, with trapezoidal integration, coverage thresholds, DST-aware binning, weighted weekday/day-type/global fallbacks and background Recorder backfill. Predictive charging, Solar Charge Delay and Dynamic Pricing use the profile only when it is mature and otherwise report the legacy daily fallback. The isolated Store, diagnostics sensors, dashboard card and source/coverage metadata make both the learning state and the live current-day capture visible without changing the legacy history contract.
- Temporary daily fallback curve: before the 15-minute profile is mature, legacy daily consumption is distributed with a normalized household shape that keeps overnight demand low, includes breakfast and daytime activity, and makes dinner the main peak. Dynamic Pricing remaining-day forecasts adapt gradually to today's measured consumption with a bounded correction, while DST-aware normalization keeps the daily kWh total unchanged.
- Remaining-today solar forecasts are now supported without breaking existing setups: a new recommended sensor field accepts the provider's production still expected today and replaces/removes the legacy whole-day forecast when saved. Intraday predictive charging, Solar Charge Delay and Smart Pre-discharge use matching remaining-energy horizons without subtracting measured production or applying the solar curve twice; untouched legacy
todaysensors continue through the existing approximation during the transition. A Home Assistant Repair guides legacy-only entries and clears automatically after migration. Forecast values are now normalized from Wh to kWh and their active source is exposed in diagnostics. - Predictive-charging diagnostics were simplified: seven redundant attributes were removed from
binary_sensor.omnibattery_predictive_charging_active. Usehousehold_consumption_full_day_kwh,daily_consumption_history,usable_energy_kwh,consumption_accumulator_source,solar_forecast_source,sensor.omnibattery_daily_solar_energyandplanned_grid_charge_kwhas their canonical replacements.
Fixed
- Hoymiles MS-A2 MQTT onboarding could fail with older firmware payloads: numeric telemetry and power-envelope fields are now accepted both as JSON numbers and as numeric strings, keeping firmware such as
01.05.06compatible without changing the handling of newer firmware such as01.06.03; invalid and non-finite values remain rejected. - Dashboard charts could use the browser timezone instead of Home Assistant's timezone (#266): history queries, day boundaries, hover clocks, weekday labels and the current profile hour now follow the user's Home Assistant timezone preference. Calendar-day calculations also account for daylight-saving days instead of assuming every day has exactly 24 hours.
- Hoymiles keepalive could delay Home Assistant startup (#283): the MQTT command watchdog now runs as a named background task, so its long-lived refresh loop is excluded from the bootstrap wait while still being cancelled cleanly when the integration unloads.
- Predictive charging notifications could mix daily and remaining forecast labels: Predictive Charging, Dynamic Pricing and pre-slot confirmations now identify whether solar and household consumption cover today or only the period until midnight, recognize learned-profile and temporary-curve scopes, and show the forecast basis on a separate line instead of presenting remaining consumption as a seven-day average.
- Predictive charging windows could truncate daily household consumption: the legacy daily history, same-day accumulator, Recorder backfill and quarter-hour forecast consumers now keep the full 24-hour household demand, including weekends and predictive grid-charging windows. Battery charging itself is still excluded naturally because negative battery AC power cancels the matching grid import. Existing windowed totals are rebuilt from Recorder instead of mixing partial-day and full-day data.
- Grid at Min SOC could remain at zero with a disabled manual timeslot: merely retaining a disabled or charge-only timeslot in configuration no longer suppresses the accumulator. Only enabled slots that allow discharge restrict it to their active window; with no such slot, unmet grid demand is counted all day.
- Predictive charging could report a missing solar forecast during a transient midnight update: when the configured remaining-today sensor was temporarily unavailable, the one-shot slot evaluation now waits and retries instead of consuming the evaluation with a misleading safe-mode notification.
- Dynamic Pricing could ignore a configured remaining-today sensor: horizon selection now resolves the persisted forecast configuration before choosing the daily fallback, so a valid remaining sensor is used by the 00:05 evaluation even if the controller's runtime cache is stale.
- Dynamic Pricing remaining-consumption forecast could count today's home energy twice: Manual recalculations now subtract the full-day home energy already accumulated since midnight and plan only the consumption remaining until midnight. Notifications use the explicit remaining value, with a safe adjusted full-day fallback during startup and diagnostics identifying the source used.
- Home Consumption could briefly fall to 0 W during battery charging: the derived sensor now holds its last valid positive estimate for up to 15 seconds when independently polled grid, solar and battery telemetry produces a transient negative balance, exposes the raw balance and estimate quality for diagnostics, and becomes unknown rather than publishing a false zero when the invalid balance persists.
- The live household-consumption profile could record an implausibly small positive balance during battery charging: the profile and legacy daily accumulator now share the same transient-balance guard, registerless battery power follows the aggregate sensor's sign convention, and raw profile days captured before the guard are rebuilt from Recorder after the upgrade.
- The live profile capture could briefly fall to 0 kWh during a Home Assistant restart or Recorder backfill: empty profile days and baseline-only samples now report no state until covered intervals exist, so charts no longer interpret an uninitialized capture as zero energy.
- The slow grid-sensor warning stayed after the sensor recovered (PR#280): a transient stall of three intervals raised the Repairs warning, and nothing could clear it until the integration or Home Assistant restarted, so the warning kept describing a fast meter as slow. Twenty consecutive fast intervals now clear it during the same run, and a sensor that slows down again raises it once more. Clearing deliberately needs a longer streak than raising, so a sensor hovering around the ten-second threshold does not churn the repair. A warning left over from an earlier run now also needs that longer streak, so it disappears about twenty publications into the new run instead of three. Thanks to @syphernl
- PD control quality no longer reports
sluggishwhile the controller is not allowed to act (PR#286): the per-cycle restriction check keyed on the commanded power, which a previously blocked cycle had already zeroed, so a blocked charge demand was evaluated as a discharge question, passed, and fed the full grid error into the quality metric. With charge delay active and a solar surplus the sensor readsluggishon the most aggressive profile while the batteries sat idle. The demand direction now comes from the grid-error sign, andblockedis reported only when the command has no headroom left in the direction it is already running (reducing discharge while charging is blocked remains a fair tuning verdict). Blocked cycles are skipped by the metric and the sensor reports a newblockedstate. A verdict whose metric has not advanced for over 5 minutes is reported ascollecting_datainstead of as a live verdict;metric_age_swas added to the attributes. Theblockedandbattery_limitedflags are stamped when set and expire after a minute, so a cycle that never reaches the PD tail (weekly full charge or predictive charging owning the cycle, max SOC handling, manual mode) neither erases a verdict that is still true nor latches a stale one for the whole session. Thanks to @syphernl - Force Mode and the charge/discharge setpoints silently did nothing under automatic control: on register-backed drivers (Marstek, ESPHome) these entities write the device registers directly, but the control loop re-asserts them every cycle, so the write was reverted before it took effect and the battery appeared unresponsive. Writing them while the controller owns the battery now raises an error naming Manual Mode instead of accepting the change. Battery configuration registers (SOC cutoffs, power caps) stay writable, and both Manual Mode switches (system-wide and per battery) release the guard. Thanks to @syphernl