Delay flow start until sufficient volume is observed

[mik3y]

Folks are getting spurious flow activations due to minor disturbances / bubbles. IIRC there's already a heuristic but it may be broken.

[jlopp]

Came here to report the same issue. I specifically have noted that sometimes when a user bumps into our kegerator, it sets off the sensor and the app believes that a pour has begun. What threshold of volume poured is required to set off a pour event? Seems like you should require at least several mL of flow before considering it a real event.

[mik3y]

@jlopp: There is a setting in the app (Settings -> Kegerator -> Minimum Volume), but it's only applied at record time (ie the UI may still spin up and make a racket).

The code needs to be modified to consider a sliding window of activity. We also need to be careful that slow pours (or worse, leaks) don't evade observation, ie, rate is considered with a cutoff.