chore(drivers): bundle easee_cloud 1.2.0 — request_active reaches Core - #1008
Merged
Conversation
Move the pin to srcfl/device-drivers@f98d5c5f (#103): easee_cloud emits request_active (false on Easee reason 50 / op_mode 4), which turns on the session-completion latch, manual-hold auto-release and interruption-noise suppression for Easee sites. Part of #1002. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01C1d4uknzs7QUv7nE9rW4fi
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. |
![cursor[bot]](https://avatars.githubusercontent.com/in/1210556?s=60&v=4){kind=small}
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.
Final piece of #1002. Moves the recovery-snapshot pin to srcfl/device-drivers@f98d5c5f (srcfl/device-drivers#103): easee_cloud 1.2.0 emits
request_active— false only on Easee reason 50 ("secondary unit not requesting current") or op_mode 4 ("completed").No Core change needed: this turns on three protections Core already has but that were dead for Easee (only ctek_hybrid emitted the field):
charging.interruptedstops firing on the car's own ~900 W renegotiation bursts.scripts/sync-bundled-drivers.shrun against the new pin (38 drivers), Lua contract suite green (go test ./internal/drivers/),make verifyclean.🤖 Generated with Claude Code
https://claude.ai/code/session_01C1d4uknzs7QUv7nE9rW4fi
Note
Medium Risk
Changes EV charging control and notifications for Easee sites via a bundled driver swap, but reuses existing Core protections rather than new logic.
Overview
Updates the recovery bundled-driver snapshot pin in
drivers/BUNDLED_SOURCE.jsonto srcfl/device-drivers@f98d5c5f, pulling in easee_cloud 1.2.0 (device-drivers#103). A patch changeset documents the user-visible effect.The bundled driver now emits
request_active, so Core can distinguish the car stopping its charge request (Easee reason 50 / completed) from the charger pausing on its own. That activates existing loadpoint logic that previously only worked for drivers likectek_hybrid: session-completion planning, auto-release of manual Start holds after sustained decline, and fewer spuriouscharging.interruptedevents during low-power renegotiation. The update also notes pcall-hardening on the driver’s HTTP transport.No Core code changes in this PR—behavior comes from syncing the bundled Lua snapshot.
Reviewed by Cursor Bugbot for commit a6b00cd. Bugbot is set up for automated code reviews on this repo. Configure here.