Repository navigation
Conversation
Co-authored-by: Copilot Autofix powered by AI <175728472+Copilot@users.noreply.github.com>
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
2 participants
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.
An optional display with no initial MQTT telemetry currently consumes the shared 120-second startup budget and leaves
api_startedfalse. This makes component health, the web ping endpoint and final optimiser status fail despite a healthy selected Cloud provider.Initialise display mode as soon as its background listener is scheduled. Keep actual display availability in the existing freshness-aware online sensor, and retain both connection and auto-configuration waits for control mode. Stacked on #5500.
Validation: reproduced the startup health failure before the fix; all 16 display tests pass, including real component health, ping, final-run status and a control-startup counterexample. Local SaaS-to-engine TLS integration passes GivEnergy/Fox display payloads, token refresh and both role transitions; captured payloads pass two real firmware receiver tests without releasing standby. Transport/provider fixtures are local, no production changes or device messages.
GitNexus: exact run-method upstream impact LOW, no indexed callers; dynamic component lifecycle manually checked. Change detection reports HIGH downstream scope over nine run-method flows (discovery, auth, freshness and dashboard), reviewed through existing source and tests. Full pre-commit could not run because the local interpreter lacks pre_commit; CI remains required.