jensandClaude Sonnet 5 71b1010b27 heater/stirrer: zero the setpoint on every disconnect, not just explicit ones ...

A comm-error/timeout-triggered disconnect left power_soll/power_actor
(heater) or speed (stirrer) untouched, so a later reconnect - or the
closed-loop TC, which keeps computing y regardless of connection state -
could immediately resume driving the device at whatever it was doing
before the outage. HeaterTask.disconnect()/StirrerTask.disconnect() now
centralize disconnect + zero-setpoint and are used for the explicit
Disconnect message, the per-tick comm-error path, and the outer
unexpected-error recovery path alike.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01EU3NTwLygh8jkrnqPoHNXF

2026-07-07 19:46:22 +02:00

..

__init__.py

fix: guard connection-state callbacks against no running event loop

2026-07-03 19:47:17 +02:00

heater.py

heater/stirrer: zero the setpoint on every disconnect, not just explicit ones

2026-07-07 19:46:22 +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: stamp PlantParams with each logger's own elapsed, not Sud.elapsed

2026-07-01 20:53:50 +02:00

stirrer.py

heater/stirrer: zero the setpoint on every disconnect, not just explicit ones

2026-07-07 19:46:22 +02:00

sud_log.py

feat: always write a fixed-name copy of server/sud logs, use .json for sud logs

2026-07-01 20:23:16 +02:00

sud.py

feat: show status line earlier and count energy without a running Sud

2026-07-06 10:45:55 +02:00

task.py

fix: guard connection-state callbacks against no running event loop

2026-07-03 19:47:17 +02:00

tempctrl.py

Remove server-side Activate/Enable residues from heater and tempctrl tasks

2026-06-27 21:13:49 +02:00

tempsensor.py

fix: temp sensor read failures could crash startup or permanently kill the task

2026-07-03 21:45:21 +02:00