Skip to content

Preserve configured export limits when composing gateway mappings - #5527

Draft
mgazza wants to merge 1 commit into
feat/physical-inverter-gatewaysfrom
fix/physical-gateway-config-defaults
Draft

mgazza wants to merge 1 commit into
feat/physical-inverter-gatewaysfrom
fix/physical-gateway-config-defaults

Conversation

@mgazza

@mgazza mgazza commented Oct 12, 2026

Copy link
Copy Markdown
Collaborator

Physical gateway composition wrote [None] for every omitted optional mapping. When Cloud discovery deliberately preserved a customer's configured 1,500 W export limit, composition erased it and inverter refresh fell back to 99,999 W.

Preserve omitted configured values and consumer defaults, while retaining explicit None as removal of an unsupported mapping. Compose mixed-provider values per physical slot and keep rediscovery bindings immutable.

Validation: eight new regressions all fail against #5526 and pass with this correction, using actual Cloud automatic configuration, UserInterface argument resolution and Inverter.refresh_config. The full suite passes 486 tests plus 19 subtests; one pre-existing custom-runner fixture case is excluded. Pre-commit passed; GitNexus detects only three expected files/seven symbols (LOW, dynamic decorator callers remain manually traced).

Draft stacked on #5526. No production feature enrollment or deployment; server-issued authority and exclusive selection handoff remain unfinished.

This branch has not been deployed

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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant