Includes everything tagged as 1.0.22-beta.10 and 1.0.22-beta.11; neither was published because CI failed on them.
Changed
- The interpolated SoC can now run up to 0.494 % above the reported value, up from 0.44 %. Between the inverter's whole-percent SoC readings, the cards estimate SoC from battery power, held within
[tick − 0.5, tick + 0.494]of the latest reading. The wider top end lets the estimate climb almost to the next whole percent during a charge before it stops, and the rounded value still matches the SoC entity.
Fixed
- Turning the Mode Scheduler master switch on or off now works (issues #16, #17, #30). The integration sent it to
/op/v0/device/scheduler/set, which the FoxESS Cloud does not serve on any model: KH, H1 and H3 inverters all answered HTTP 404. Sofoxess_control.disable_schedulerand Release the inverter when idle could never turn the switch off, and the switch was never explicitly turned on before a schedule write (the "Could not turn the Mode Scheduler master switch on" warning). It now uses/op/v1/device/scheduler/set/flag, the counterpart of the/op/v1/device/scheduler/get/flagread the integration already uses. - The Work Mode sensor no longer crashes with foxess_modbus (issue #24). foxess_modbus reports the work mode as
Self Use,Force Chargeand so on, while the sensor only acceptsSelfUse,ForceChargeand the other mode values. So the sensor never got a state and every refresh logged aValueError. The labels are now translated, and a mode with no equivalent here, such asPeak Shaving, shows as unknown. Thanks to @jesmon84 (PR #25) and @yourrival for the diagnosis. - Setup no longer fails on inverters whose device detail has no capacity (issues #13, #33). The M1-800-E and the MQ2200-M-H (NextEnergy Orbit-M) omit the
capacityfield, so setup stopped at "Could not determine inverter capacity from device detail" and retried forever. The integration now uses the maximum charge/discharge power the inverter declares for its schedules, and only fails if the inverter declares that too. - The options can be saved again with foxess_modbus installed and entity fields left empty (issue #33). Every empty entity field on the foxess_modbus step was rejected with "Entity is neither a valid entity ID nor a valid UUID", which blocked saving options for any cloud entry on a system with foxess_modbus installed. Empty fields are now accepted, and detected or current entities are still pre-filled.