A saved settings file could not be loaded, or a save was refused because it failed validation.
| At a glance | |
|---|---|
| Code | 530 |
| Shown as | Config Error |
| Severity | Severe |
| Category | 5xx — System / lifecycle |
| Clears | Stays until the controller restarts. Acknowledge it once you have reviewed it. |
| Keyed by | The settings file, shown as Config: file under the title (upcoming firmware) |
When a settings file is damaged or unreadable, the controller falls back to defaults for that file — so control modes, WiFi settings, or the profile may have reverted. When a save fails validation, it is refused rather than overwriting the good file.
Control modes are handled one at a time (upcoming firmware). If one saved mode cannot be read, the controller sets it aside and loads all the others, instead of starting with no modes at all. The alarm names the control-modes file; the set-aside mode is missing from Settings → Control Modes. The original file is kept on the controller for support to recover it. The next save writes the file without the set-aside mode.
Runs on the defaults for the affected settings.