brewpi

Files

T

jensandClaude Sonnet 4.6 031b13ca2c Fill the post-confirm forecast gap with the real setpoint, not a mid-ramp snapshot

_continue_forecast_after_confirm()'s bridge was repeating forecast_theta[-1]
to cover the real-world wait, but that's whatever value the simulation
happened to log the instant WAIT_USER tripped - often still mid-ramp, not the
step's actual hold target. The real controller stays enabled and actively
holding throughout WAIT_USER, so capture its setpoint (tc.get_theta_soll_set())
in recv() before calling Sud.confirm() - confirming synchronously pushes the
next step's own target onto it - and use that to fill the gap instead.

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

2026-06-22 17:24:02 +02:00

__init__.py

Add mash-schedule (Sud) automation: temp/rate sequencing + stirrer switching

2026-06-19 17:54:42 +02:00

heater.py

Add a real-time Plot tab to brewpi_gui, mirroring demo_sud figure 1

2026-06-20 22:31:07 +02:00

pot.py

Add a "Pot reset to ambient temperature" button, sim-only

2026-06-21 12:15:35 +02:00

stirrer.py

- removed recognising of activate