Skip to content

docs: clarify read-only mode still performs one reset write on enable - #4388

Merged
springfall2008 merged 1 commit into
springfall2008:mainfrom
chalfontchubby:docs/read-only-reset-write-clarification
Jul 30, 2026
Merged

docs: clarify read-only mode still performs one reset write on enable#4388
springfall2008 merged 1 commit into
springfall2008:mainfrom
chalfontchubby:docs/read-only-reset-write-clarification

Conversation

@chalfontchubby

Copy link
Copy Markdown
Collaborator

Summary

Test plan

  • ./run_pre_commit (via coverage/run_pre_commit) - all hooks pass
  • Docs-only change, no code touched

Closes #4298

…rite

switch.predbat_set_read_only is flagged as a reset_inverter_force trigger,
so toggling it on deliberately fires one release write (max charge rate,
clear windows/reserve/export) to hand control back to the inverter's own
native scheduling - it isn't a violation of read-only mode, but it wasn't
documented, so it silently overwrote a manually-set inverter value for one
reporter (springfall2008#4298). Behaviour is unchanged and intentional (dates to springfall2008#519);
this just makes it visible.
@springfall2008
springfall2008 merged commit 2625a71 into springfall2008:main Jul 30, 2026
2 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

switch.predbat_set_read_only does not prevent Predbat writing timed_charge_current

2 participants