Lutz Finsterle f45d23df97 Fix Shelly unreachable: roll back engine state on failed actions ...

Without this, a failed Execute() left engine state diverged from hardware.
SyncHardwareState would then misread the mismatch as a manual override and
apply a 1-hour lockout — causing either a stuck-on or stuck-off loop.

Now Execute() returns per-action []error. The control loop calls
Engine.RollbackAction() for each failed action, keeping engine state in
sync with hardware so the next cycle simply retries.

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>

2026-04-08 20:44:08 +02:00

..

actuator_test.go

Fix Shelly unreachable: roll back engine state on failed actions

2026-04-08 20:44:08 +02:00

actuator.go

Fix Shelly unreachable: roll back engine state on failed actions

2026-04-08 20:44:08 +02:00