Close

Chiller with the wifi switch

A project log for Energy saving for brewery glycol chillers

Thermal storage means brewery or cidery tank refrigeration systems don’t need to run all the time.

tim-bishopTim Bishop 04/28/2022 at 20:210 Comments

Below we can see the chiller control turning off the chiller during the late morning and afternoon of the 2nd day 11:00 - 16:30, with only a small rise in tank temperature (Tanks 2 and 3) during that period. The tanks do not change temperature very fast - this is energy storage in action, and what allows us to turn off the chiller for this time. (Tank 1 is empty and is not being chilled)

Controlling the chiller via the wifi switch has allowed us to save 30% of our chiller electricity use, which is 5-10% of our total electricity use.

We added tank temperature monitor / controllers so we could monitor the tank temperatures from off-site, to verify that our tanks did not change temperature too much when the chiller is turned off. We used the Sonoff TH16 ($27).

Tracking tank temperatures has helped us get some numbers about the rate of tank temperature change at the cidery. Our 1500 gallon tanks can be cooled at a rate of 1.5F/hour. They self heat, during fermentation, at a rate of 0.25 - 0.5F/hour in our ambient temperatures.

By watching the tank temperatures, we can turn the chiller off when we want to, and then back on when the tanks start getting too warm. This is a manual process but we are learning how long the chiller can be left off without materially affecting the ferment process.

Sometimes the wifi temperature controllers get stuck reporting the same (incorrect) temperature. For example the purple Tank 2 temperature reported below at day 1 hour 17:30 - 23:30 is shown as a flat line when we know the temperature was actually going down following the trend. This may be a problem with the eWeLink cloud, our HA installation, or a poor wifi signal.

As we develop this system it needs to degrade gracefully in the absence of local wifi, or the internet, or the dependence on the third-party cloud.

Discussions