Revert "Run the Pot simulation from server startup, not just once a Sud loads"

This reverts commit 63fa093a8a.
This commit is contained in:
2026-06-24 16:09:49 +02:00
parent 17e8386002
commit 0be8ffcbe0
2 changed files with 10 additions and 19 deletions
+2 -11
View File
@@ -59,17 +59,8 @@ def _build_step(number, defaults, raw_step):
EMPTY_SUD = {
'Name': '',
'Description': '',
# pot_mass/pot_material are the physical kettle's own properties, not
# really per-recipe (every sude/*.json so far uses this exact pot) -
# defaulting to 0/None here used to make derive_plant_params() come out
# with a zero-mass plant (a ZeroDivisionError in Pot.process() waiting
# to happen) for as long as no Sud had ever been loaded yet. Matching
# the real kettle here instead lets server/brewpi.py seed the Pot with
# a physically sane default at startup, so its simulation actually
# runs - and a real Sud's own doc still overrides these the moment one
# is loaded (see SudTask.apply_plant_params()).
'pot_mass': 5.96,
'pot_material': "Edelstahl 18/10",
'pot_mass': 0,
'pot_material': None,
# Pot energy loss coefficient [W/(kg*K)] and transport propagation
# delay [s] - see derive_plant_params(). Defaults match the generic
# values brewpi.py used to hardcode for every brew alike.