Cold crashing to achieve pitching temps has always been a struggle for me.
Using constant beer temp mode takes longer than expected and constant fridge mode needs baby sitting (and causes overshoot by a few degrees after switching to beer temp mode).
You have no fridge setting active, why? I don’t see a beer setpoint here.
Do you still use the indirect control mode? Our current default setup is to not use a dynamic fridge setpoint, but instead change the PID settings when switching between beer and fridge control. I think this would work better for you.
You could try to re-run the fridge wizard with our new defaults and see how that works for you.
If you only have this process set up, I would erase all blocks and re-run the wizard. You can export blocks first to be able to restore them if you don’t like it.
At the very begin of the graphic I started a “mini crash” (from 30C to 20C) to achieve the fermentation temperature (constant beer mode set to 20C).
I was expecting a “cold crash behavior”: deep lowering of the fridge temp to achieve the 20C as fast as possible.
As this behavior was not happening I decided to start the constant fridge temp mode (4C setting).
After the beer achieved the desired 20C I returned the mode to beer temp but this caused a little overshoot (beer cooled down to ~18C).
This is maybe due to the absence of a heater too, but I think if there was a crash option in the constant beer mode maybe this type of overshoot wouldn’t happen.
I’ll start to cold crash the beer I had fermenting previously.
Took the time to delete all the blocks and create everything from scratch (with the Wizard help of course).
Everything went OK. I just miss an option to create a fermentation fridge without the heating part (I don’t use a heater).
The other thing I noticed (and I think this is a bug) is that whenever I try to edit a Brewery Builder block it opens and old Brewery Builder block that doesn’t exist anymore (from a previously deleted Dashboard).
We need to make that dropdown a lot more prominent it appears.
The editor initially showing the wrong layout indeed is a bug. The fix is already applied, and will be part of the next release.
Builder layouts are not stored on the controller (and technically not blocks). Would you say that requires more explanation/attention in the UI?
They actually used to be, until we decided to give the editor its own page. We also had had feature requests for builder widgets on dashboards being able to toggle between layouts, so we separated the concepts.
It’s very much like how dashboard widgets only use blocks on the controller, and not own them. (If you remove a dashboard, blocks still exist on the controller).
In software engineering these “reference” relations are extremely common, but we’re still working on how to make the concept intuitive in the UI.
