You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit 431bd77
Browse filesBrowse the repository at this point in the historyBrowse files
fix(gateway): never enable discharge/export after a failed window write
For a direct Hub battery, adjust_force_export wrote the discharge start
and end as two separate set_discharge_slot commands, then enabled the
scheduled discharge and switched to export mode regardless of whether
the endpoint writes were applied. schedule_write_ok only withheld the
later commit record. When the end write was refused after the start was
accepted, the Hub was left enabled with a stale wrapping window
(e.g. 02:55-00:01) and actively exporting.
Send both endpoints in one full-serial set_discharge_slot for direct Hub
batteries and verify both endpoint read-backs before continuing. Any
refusal, staged or partial ACK, timeout, publication error or swallowed
async-bridge exception returns before the enable write, export mode and
commit, leaving the commit pending for the next cycle to retry. Both
endpoints are tracked in the control ledger and share one backoff key.
Read-only, entity ownership and serial checks refuse before publishing.
Coordinators keep their staged separate-endpoint sequence; other
providers, disable and midnight windows are unchanged.
Mirrors the charge-window fix in #5531.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_018BaJjLpuMEtQYfvmTRcFJf
0 commit comments