Scope automation switch to setpoints only, not the whole poll cycle

Master switch should behave like each zone's own auto_mode — NewBook
polling, room-state tracking, and activity logging keep running as
normal; only the actual device setpoint commands are held back.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
This commit is contained in:
jtricerolph 2026-07-27 15:48:13 +00:00
parent c6e3c73ead
commit ab14d4dfe1
2 changed files with 9 additions and 9 deletions

View file

@ -95,7 +95,7 @@ export default function Settings() {
try {
await updateConfig('automation_enabled', next)
setAutomationEnabled(next)
setMsg(next ? 'Automation resumed' : 'Automation paused — no setpoints will be sent to any device until resumed')
setMsg(next ? 'Automation resumed' : 'Automation paused — device setpoints will no longer change until resumed')
setTimeout(() => setMsg(''), 4000)
} catch (e) {
setError(e instanceof Error ? e.message : 'Failed to update automation state')
@ -155,8 +155,9 @@ export default function Settings() {
{automationEnabled ? 'Automation is ON' : 'Automation is PAUSED'}
</div>
<div className="muted" style={{ fontSize: 13, marginTop: 2 }}>
Master switch for every zone overrides each zone's own auto mode. While paused, the scheduler
skips its poll entirely: no NewBook fetch, no state tracking, no setpoints sent to any device.
Master switch for every zone overrides each zone's own auto mode. While paused, NewBook polling,
room-state tracking and activity logging all keep running as normal only setpoint changes to
TRVs/aircon devices are skipped.
</div>
</div>
<button