Repository navigation
fix(chargers): surface missing saved connections - #1743
Merged
Merged
Conversation
Codex Review SummaryThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
This was referenced Oct 19, 2026
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
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.
When a charger kept the name of a removed or renamed driver, Settings showed it as a saved connection and validation gave no warning. Settings now marks the missing connection, keeps the warning after save, and clears it when the owner chooses a configured charger or removes the entry. The saved choice stays intact. An unseen OCPP identity remains unverified.
Setup validation now saves warnings even when it leaves the settings bytes unchanged, and binds those warnings to the reviewed draft revision. The diagnostic catalogue includes exact saved charger names and their binding status, plus the full-read workflow an assistant needs to check them.
Paired Cloud change: srcfl/ftw-cloud#41 (MCP guidance and diagnostic refusal handling).
Validation:
make verifypassed.easee_cloudsaves the new binding and removes the old option and warning; the narrow view has no horizontal overflow.Fredrik reviewed the rendered UI and approved both paired merges on 19 October 2026. The local preview uses no private site data. Release, Cloud deployment and box installation remain separate steps.