[{"data":1,"prerenderedAt":291},["ShallowReactive",2],{"doc-\u002Fgetting-started\u002Ffirst-30-days":3},{"id":4,"title":5,"body":6,"description":282,"edit":283,"extension":284,"meta":285,"navigation":31,"path":286,"seo":287,"stem":288,"vertical":283,"weight":289,"__hash__":290},"content\u002Fgetting-started\u002Ffirst-30-days.md","First 30 days",{"type":7,"value":8,"toc":269},"minimark",[9,13,18,73,77,80,83,117,120,124,131,134,161,165,191,195,222,226,229,243,251],[10,11,12],"p",{},"A week-by-week runbook for the first 30 days of a new OpenSense site.\nTargets a single café or small kitchen, three or four sensors, one\noperator. Adapt cadences for larger operations.",[14,15,17],"h2",{"id":16},"week-0-install-day","Week 0 — install day",[19,20,23,39,45,55,61,67],"ul",{"className":21},[22],"contains-task-list",[24,25,28,33,34,38],"li",{"className":26},[27],"task-list-item",[29,30],"input",{"disabled":31,"type":32},true,"checkbox"," Choose sensor placements ",[35,36,37],"em",{},"with food on the shelves",". The\nwarmest stored item is the sensor location; \"the geometric\ncentre of the fridge\" is wrong if there is hot air dumping at\nthe top.",[24,40,42,44],{"className":41},[27],[29,43],{"disabled":31,"type":32}," Pair every sensor and watch one reading land before walking\naway. Do not assume.",[24,46,48,50,51,54],{"className":47},[27],[29,49],{"disabled":31,"type":32}," Photograph each sensor location and upload to the device page.\nIn 3 months you (or a different operator) will need to know\n",[35,52,53],{},"which"," probe is \"front-fridge\".",[24,56,58,60],{"className":57},[27],[29,59],{"disabled":31,"type":32}," Connect Telegram. Send the test alert. Confirm it lands.",[24,62,64,66],{"className":63},[27],[29,65],{"disabled":31,"type":32}," Connect email recipients. Send the test alert. Confirm it\nlands.",[24,68,70,72],{"className":69},[27],[29,71],{"disabled":31,"type":32}," Set the site's timezone. Send a test report; verify the day\nboundaries.",[14,74,76],{"id":75},"week-1-observation","Week 1 — observation",[10,78,79],{},"You will get false alarms in the first week. That is normal and\ncorrect — the system is showing you that defaults do not match your\noperation.",[10,81,82],{},"Common false-alarm causes in week 1, in order of frequency:",[84,85,86,93,99,105,111],"ol",{},[24,87,88,92],{},[89,90,91],"strong",{},"Delivery door propped open."," Set a 15-minute grace period; if\ndeliveries are routine, widen to 30 minutes.",[24,94,95,98],{},[89,96,97],{},"Defrost cycle."," Configure a time-of-day window on the rule.",[24,100,101,104],{},[89,102,103],{},"Probe in the wrong place."," Move the probe; do not soften the\nalarm.",[24,106,107,110],{},[89,108,109],{},"Compressor short-cycle on an old fridge."," Add a second probe\nat the opposite end of the cabinet to confirm the swing is real.",[24,112,113,116],{},[89,114,115],{},"Captive-portal WiFi."," Move sensors to a dedicated SSID if\npossible.",[10,118,119],{},"After every false alarm, leave a note in the acknowledgement field\nexplaining what you changed. This is what the auditor wants to see in\nmonth 6.",[14,121,123],{"id":122},"week-2-refine","Week 2 — refine",[10,125,126,127,130],{},"By week 2 the false-alarm rate should be 0–1 per device per week. If\nit is higher, ",[89,128,129],{},"investigate before suppressing",". A 5-alarms-per-week\nrate is the system telling you the fridge is not holding temperature;\nsuppressing the alarms with a wider operating range masks a real\nmaintenance issue.",[10,132,133],{},"Tasks:",[19,135,137,143,149,155],{"className":136},[22],[24,138,140,142],{"className":139},[27],[29,141],{"disabled":31,"type":32}," Review every channel's last-7-day chart. Are the band edges\ntight? Loose? Adjust per channel.",[24,144,146,148],{"className":145},[27],[29,147],{"disabled":31,"type":32}," If you have a freezer that hits −18 °C ± 1 °C consistently,\ntighten the operating range to capture compressor decline early.",[24,150,152,154],{"className":151},[27],[29,153],{"disabled":31,"type":32}," Set up a monthly report subscription (auto-render on the 1st\nat 02:00 site-local, email to all recipients).",[24,156,158,160],{"className":157},[27],[29,159],{"disabled":31,"type":32}," Confirm at least one acknowledgement note is in the system\nfrom a real event. Practice the workflow.",[14,162,164],{"id":163},"week-3-backfill-and-audit-prep","Week 3 — backfill and audit-prep",[19,166,168,174,180],{"className":167},[22],[24,169,171,173],{"className":170},[27],[29,172],{"disabled":31,"type":32}," Print the first 14-day report on paper. Sign and date the\ncover page. Drop it in the same folder as the paper logs you\nare migrating from (if any).",[24,175,177,179],{"className":176},[27],[29,178],{"disabled":31,"type":32}," If you migrated from a paper logbook, file the last hand-written\npage next to the cover sheet. Inspector understanding: \"we\nmoved on this date.\"",[24,181,183,185,186,190],{"className":182},[27],[29,184],{"disabled":31,"type":32}," If you have not had a real alarm yet, force one. Set the\noperating range to room temperature for 60 seconds, save,\nrevert. The audit trail records the test as\n",[187,188,189],"code",{},"alarm_opened → alarm_cleared"," within minutes; tag it\n\"test event\" in the note. Auditors prefer to see one practice\nevent over a fully clean month-1.",[14,192,194],{"id":193},"week-4-first-monthly-report","Week 4 — first monthly report",[19,196,198,204,210,216],{"className":197},[22],[24,199,201,203],{"className":200},[27],[29,202],{"disabled":31,"type":32}," Render the month-1 PDF. Read it like an auditor would.",[24,205,207,209],{"className":206},[27],[29,208],{"disabled":31,"type":32}," Look for the \"OFFLINE — no data\" stripes. Investigate any gap\n> 1 h.",[24,211,213,215],{"className":212},[27],[29,214],{"disabled":31,"type":32}," Look at the excursion log. Each entry should have an\nacknowledgement note; if any do not, retroactively add a note\nexplaining what you understand now.",[24,217,219,221],{"className":218},[27],[29,220],{"disabled":31,"type":32}," Calibration record: enter the date of any sensor calibration\nevents you have performed (none expected in month 1; the field\nstarts populating in month 6 if you run periodic checks).",[14,223,225],{"id":224},"week-5-steady-state","Week 5+ — steady state",[10,227,228],{},"After the first month:",[19,230,231,234,237,240],{},[24,232,233],{},"The system runs itself; you read the monthly report.",[24,235,236],{},"A real alarm fires ≈ every 6–12 weeks per device for normal\ncold-chain operation. If it is more frequent, the underlying\nequipment is failing.",[24,238,239],{},"Calibrate the sensors annually: take a portable calibrated probe,\nhold it next to each installed sensor for 5 minutes, record the\ndelta. Apply offsets in the channel config if drift > 0.5 °C.",[24,241,242],{},"Rotate device tokens annually. The dashboard flags devices with\n365-day-old tokens; do not let the flag carry into month 14.",[14,244,246,247,250],{"id":245},"what-you-should-not-do","What you should ",[89,248,249],{},"not"," do",[19,252,253,259,264],{},[24,254,255,258],{},[89,256,257],{},"Do not"," soften alarms because they are annoying. They are\nsignalling a real-world problem; fix the world.",[24,260,261,263],{},[89,262,257],{}," delete a device because it has had alarms. The audit\ntrail will show the deletion; auditors are suspicious.",[24,265,266,268],{},[89,267,257],{}," share login credentials with multiple operators. Wait\nfor the Team tier or rotate the magic-link email per operator.",{"title":270,"searchDepth":271,"depth":271,"links":272},"",3,[273,275,276,277,278,279,280],{"id":16,"depth":274,"text":17},2,{"id":75,"depth":274,"text":76},{"id":122,"depth":274,"text":123},{"id":163,"depth":274,"text":164},{"id":193,"depth":274,"text":194},{"id":224,"depth":274,"text":225},{"id":245,"depth":274,"text":281},"What you should not do","Operator runbook for the first month",null,"md",{},"\u002Fgetting-started\u002Ffirst-30-days",{"title":5,"description":282},"getting-started\u002Ffirst-30-days",25,"sqQx18ar3O1TDI-NXencO5tq8Xiwd7Pa_j14IgOv5nY",1779022953358]