Skip to content

fix(api): apply a POSTed config through the same path as a file edit #761

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
frahlg merged 1 commit into from
Aug 4, 2026
Merged

fix(api): apply a POSTed config through the same path as a file edit #761

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
5 changes: 5 additions & 0 deletions .changeset/760-one-config-apply-path.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,5 @@
---
"ftw": patch
---

Saving a config through the API now applies it exactly like a file edit. Previously POST /api/config hot-applied only a hand-picked subset of control fields and swapped the shared config pointer itself, which blinded the config watcher's own diff — so a site meter set for the first time (the setup wizard's normal path) never reached the running controller: the dashboard showed Grid 0 W and an inflated Load, and dispatch had no site boundary until a process restart. Both paths now run one shared apply, so hot-reload of the site meter, slew enable, DC-link protection, inverter groups, fuse parameters and the mpc/loadmodel sync all work from the UI too.
Loading