<aside> 🌡️
The Govee H5179 sensors in our refrigerators and freezers report to Govee's cloud. A Google Apps Script checks every sensor every 10 minutes, keeps the live status below current, writes one reading per sensor per hour to the Temperature Log, and emails Erica, Sonni and that hospital's supervisors when a unit goes out of range or a sensor stops reporting.
</aside>
| Event | When it fires | Email subject starts with |
|---|---|---|
| Out of range | 3 checks in a row outside the range (about 30 min) — a quick door opening won't trigger it | TOO WARM / TOO COLD |
| Still out of range | Every 2 hours until it recovers | STILL TOO WARM / STILL TOO COLD |
| Recovered | First in-range check after an alert | BACK IN RANGE |
| Sensor not reporting | No data for 30 min, or the exact same reading for 3+ hours | SENSOR OFFLINE (then BACK ONLINE) |
Default ranges (used when Min °F / Max °F are left blank on a sensor): Refrigerator 36–46°F (2–8°C) · Freezer −58 to 5°F (−50 to −15°C). Type a different Min/Max on any sensor row to override it.
Who gets emailed: @Sonni, Erica and that hospital's supervisors. Each alert goes only to the addresses in that sensor's Alert Emails column. The plan is one Google Group per hospital (members: Erica, Sonni and that hospital's supervisors), so each sensor lists just its group address and every alert is a single email. If a sensor's Alert Emails cell is blank, the alert goes to Erica and Sonni directly.
Time out of range: every Alert, Reminder and Back in range row shows Out of Range Since (the first out-of-range reading) and Time Out of Range. The original Alert row keeps a running total and ends with the final total for that event once the unit recovers, so you can read the whole event from one row. Timing is accurate to about 10 minutes (one check).
setup or syncDevices runs — or add a row yourself and type the Govee app name in Govee Name.