Monnit vs Fridge Display: Match Measurement Times Before Applying an Offset
A fridge display reads 4.0°C while the latest iMonnit history row says 5.2°C. Entering a −1.2°C offset may make the numbers agree today and introduce an error tomorrow. First establish whether the two numbers describe the same measurement time, location and sensing arrangement. A useful comparison is a set of matched observations, rather than one photograph of two screens.
This guide focuses on investigating disagreement. Keep the normal storage response procedure active throughout: a comparison exercise does not determine whether stored goods remain suitable for use.
Start with the timestamp attached to the value
Monnit identifies comparing a previous Heartbeat reading with an instantaneous appliance display as a cause of apparent disagreement. Record the measurement timestamp beside each wireless value. Record when the display was observed separately. A dashboard viewed at 10:15 does not establish that its latest value was measured at 10:15.
Make a simple comparison log with columns for sensor ID, measurement time, wireless value, display observation time, displayed value and equipment activity. Keep the time zone explicit. If you cannot obtain a display value corresponding to the wireless measurement, label the pair as unmatched and retain it as context; do not use its difference as an adjustment value.

The ProSense catalogue temperature sensor is an ALTA device offered with different lead configurations. Establish whether your unit measures at the enclosure or through an external lead. The location of the radio enclosure alone may not identify the measurement point.
Make the physical comparison meaningful
The built-in refrigeration sensor may occupy another part of the cabinet, and its display may average readings. Monnit’s current accuracy guidance explains that fast responses to door openings or airflow changes can therefore differ from the appliance display. Obtain the appliance manual or ask its manufacturer what the display represents before treating it as a reference.
Document the monitored point with a location description and photograph. Identify whether either probe is buffered, touching a surface or exposed to a different airflow. Do not relocate the operational monitoring point merely to obtain agreement. If temporary relocation is authorised, record the start and end times and provide appropriate monitoring coverage while it is moved.
Use a controlled sensor-to-sensor check
Monnit’s comparison procedure uses two operating sensors with probes close together, matching Heartbeat and Aware State Heartbeat intervals, and coordinated power-up. Its guidance recommends allowing about 90 minutes for stabilisation. Follow the instructions for the exact sensor and service plan, and check that settings have actually reached both devices.
Before changing calibration or restarting devices, save the existing configuration and relevant history, agree the test with the person responsible for monitoring, and manage the temporary interruption. Monnit’s procedure includes returning supported sensors to default calibration. Treat that as a documented configuration change, rather than an automatic first action on a live installation.
The published comparison guidance gives ±1°C for the Standard Temperature Sensor and consequently allows up to 2°C separation between two such sensors. It explicitly requires using the applicable datasheet accuracy for other sensor types. Agreement between two devices is a useful consistency check; it does not establish traceability or satisfy a tighter application tolerance by itself.
Worked example: why one offset can be misleading
Hypothetical observations: a wireless sensor measured 5.2°C at 10:00. At 10:15 a technician sees 4.0°C on the fridge display. The arithmetic difference is 1.2°C, but the observation times are 15 minutes apart. That pair cannot establish a 1.2°C instrument error.
The team then logs the display alongside subsequent wireless measurement times and performs an authorised comparison with a second sensor at the same point. If the wireless sensors track together while the cabinet display behaves differently, investigate what the display represents. If a repeatable difference remains between comparable sensors after stabilisation, escalate with the test evidence. Neither outcome justifies inventing a correction from the first unmatched pair.
Check repeating equipment events and close the investigation
For repeating peaks or missing reports, compare the recorded event times with the refrigeration manufacturer’s defrost schedule. Monnit documents that proximity to a defrost unit can influence both temperature history and radio communications. Record signal and reporting information alongside temperature instead of assuming every gap is a thermal event.
Avoid changing probe position, reporting interval, calibration and alarm delay together: the resulting record will not show which change affected the disagreement. Investigate one documented change at a time under the site procedure. Never relax storage limits simply to make an alert disappear.
If calibration is warranted, use a suitable trusted reference and the model-specific procedure. Monnit states that a calibration saved in iMonnit is applied on a subsequent sensor communication and that the probe must remain at a stable temperature until application is complete. Finish by verifying later readings and restoring any temporary reporting settings.
Send ProSense the exact sensor model, current configuration, matched timestamp log, probe-location photographs, relevant history and appliance display description. That evidence supports a practical decision about placement, reference testing or sensor service without discarding the original measurements.
Technical references
Need help with your application?
ProSense Instruments - discuss temperature instruments and monitoring hardware: sales@prosenseinstruments.com.au or 1800 560 854.
ProSense Solutions - discuss system integration: sales@prosense.com.au. ProSight Software - discuss software requirements: info@prosightsoftware.com. Device integration must be confirmed for your application.




Comments