Skip to content

PV and steam boiler bounds count UNCERTAIN components, the distributor does not #1488

Open

Description

@Marenz

Follow-up from #1477.

The PV and steam boiler pool bounds count an UNCERTAIN component as usable (pv_pool/_system_bounds_tracker.py and steam_boiler_pool/_system_bounds_tracker.py use working | uncertain), while the power distributor leaves it out (_pv_inverter_manager.py uses get_working_components()). A failed set-power makes a component UNCERTAIN. The battery pool is fine, because both sides use get_working_components().

Usually this only makes the reported range too wide: the bounds keep the component's whole range, so the target is not clamped too far. It becomes a real double cut when the component's measured power is outside its own reported bounds, for example when it still runs at an older setpoint after its bounds have shrunk (derating, temperature, SoC).

Fixing it now would start a formula on the bounds side for every failed set-power and bring the restart dip from #1486 to these two pools, so it is best done together with the per-component power streams.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Fields

    Priority

    None yet

    Projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions