Nick SzaunigandClaude Sonnet 5
792806b967
VarroaMeasurement.calculatedValue was already used as "Milben/Tag" by the VARROA_THRESHOLD automation (thresholdMitesPerDay) and the annual PDF report, but no client ever actually computed it - the frontend form only collects raw miteCount and durationMinutes. That meant the threshold check was comparing a raw, un-normalized mite count against a per-day threshold: e.g. 12 mites counted over 5 days (2.4/day, healthy) would incorrectly trigger the same alert as 12 mites counted over 1 day (a real problem). VarroaService now derives calculatedValue = miteCount / duration in days for NATURAL_MITE_FALL measurements, on create and (only when no value exists yet) on update, without ever overwriting an explicitly provided or already-stored value. Other methods (Puderzucker, Waschmethode, Drohnenbrutkontrolle) use a different, non-time-based metric and are left for manual entry rather than guessing an unverified formula. Co-Authored-By: Claude Sonnet 5 <[email protected]>