brewpi

Files

T

jensandClaude Sonnet 4.6 9f221c5d19 fix: re-enable closed-loop on Sud start regardless of client

HeaterTask.shutdown() switched the heater to open-loop when a brew
ended, but nothing switched it back when a new Sud was started.  The
browser happened to send {ClosedLoop: true} as part of its UI setup,
so its connect-and-start path worked; PyQt (and any other client that
doesn't send that message) left the heater in open-loop and the TC
never drove it.

Add SudTask._on_start / set_on_start() hook, HeaterTask.start_closed_loop()
(mirror of shutdown()), and wire them in brewpi.py so the server
switches to closed-loop and broadcasts the new state to all clients the
moment any client starts a brew.

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

2026-07-01 00:43:55 +02:00

__init__.py

refactor: replace SudLogTask with ServerLogTask for all logging

2026-06-30 23:22:11 +02:00

heater.py

fix: re-enable closed-loop on Sud start regardless of client

2026-07-01 00:43:55 +02:00

pot.py

Move set_on_changed registrations from on_process() to __init__()

2026-06-25 20:39:06 +02:00

server_log.py

fix: embed dt and startup plant params in server log; open-loop replay_sim