How does the BrewBit keep track of PID variables? Can it track information across sessions, and could we set up equipment profiles?
I have a system that is prone to overshooting. I have a big pot with a false bottom sitting on top of a hotplate with a cast iron heating surface. When I had the BrewBit set for my strike temperature, it overshot by 3 F on the first heating cycle, and then by about 1 F on the next heating cycle. I then lowered the temperature to my mash temp, which created a new "session." Sure enough, the BrewBit again overshot by 3 F on the first heating cycle.
It seems advantageous for the BrewBit to learn about my equipment over time, rather than starting fresh each "session." There's also a lot I could do to help the BrewBit out. For example, I could tell it whether I have it hooked up to my MLT, my keezer, or my fermentation fridge. If I know that I'm using more water than usual, or that it's a colder day than usual, I could nudge the starting parameters a little. After enough brew sessions with the same equipment, I think it could get pretty good at controlling it.
I also just have a UI issue with the idea of "sessions." If I change the set point manually, that doesn't mean I have a new batch or am doing something else. I'd like to see all the stages of a brew -- and certainly a mash -- linked together. I get why, on the database side, you'd need to link the settings to the results, but for presentation purposes, creating a new "session" should be a bigger deal for the user, and I shouldn't just accumulate 20 sessions from things I do on the touchscreen.