Repository navigation
Conversation
This branch has not been deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Explicitly enrolled engines now claim a server-issued battery-control epoch before constructing components. Refused or malformed attachment stops startup, lease expiry and drain closure permanently fence admission, and a dedicated worker reports exact local pending/uncertain transport evidence to the engine-battery-control service.
Supports the existing gated direct GivEnergy and Hub MQTT sinks. Component startup rejects uncovered battery transports and external Home Assistant service paths; ordinary installations stay unchanged. Same-object reinitialization preserves the sealed gate and tracked work.
Validation: 29 control/service cases, component registry tests, Gateway suite and 138 GivEnergy tests pass; pre-commit passes. GitNexus staged scope: six expected files, 70 mapped symbols, five restart/poll flows (MEDIUM). Tests exercise real startup, component selection, worker, shutdown and transport call sites with synthetic HTTP/provider boundaries.
Based on #5513, including merged #5514. Requires the separately reviewed SaaS service PR Predictive-Cloud-Ltd/predbat-saas#2144. Default off, no production enrollment or provider changes. This is source process evidence only: loaded configuration revision/exact inverter identity attestation, joined backend proof, physical Hub fencing, target readiness and provider commit/release remain required before activation. Provider selector, onboarding grid and automatic backup remain outstanding.