top of page

Monnit Humidity Still Aware Below the Limit? Check the Recovery Buffer

Nov 12
4 min read

A humidity reading has fallen below its high threshold, but the Monnit sensor still appears Aware. Before changing calibration or repeatedly editing the alarm limit, check the Aware State Buffer. This hysteresis setting separates the entry condition from the recovery condition, so a small movement back across the original threshold may not be enough to restore standard operation.

Illustrative humidity monitoring concept with separate high-limit and recovery boundaries.
Original conceptual illustration; not a specific installation or an exact drawing of the listed device.

Key takeaways

A reading can be below the high limit while the sensor remains aware. Confirm the recovery buffer and device settings before changing notifications or treating the reading as recovered.


1. Read both the threshold and the buffer


Monnit’s ALTA Humidity Sensor guide identifies separate humidity and temperature thresholds, with corresponding Aware State buffers. The buffer prevents repeated switching when measurements hover close to a limit. Confirm which measured variable is being investigated; a temperature setting is not a humidity setting.


Record the displayed field names, units and existing values before making a change. Include the sensor identity and the application’s rule settings in that record. A screenshot labelled only “alarm set to 70” leaves important questions unanswered: 70 of what, on which channel, with which recovery margin, and in the sensor or the receiving application?


Monnit ALTA humidity sensor in a black enclosure with mounting tabs and an antenna
Monnit ALTA battery-powered wireless humidity sensor - product photograph from the ProSense Instruments catalogue, not a customer installation.


2. Use a recovery example with clear units


Consider a hypothetical high-humidity warning set at 70% RH with a buffer of three RH percentage points. Under that assumed hysteresis arrangement, the recovery boundary is 70 minus 3, or 67% RH. A sequence of 71, 69 and 68% RH can therefore be consistent with remaining Aware after the high condition occurred. Returning below the entry threshold alone does not demonstrate recovery.


The arithmetic uses percentage points of RH, not three per cent of the threshold value. Three per cent of 70 would be 2.1, which describes a different margin. Write the intended recovery boundary explicitly in the commissioning record and verify the actual device behaviour on either side of it. Avoid relying on a test held exactly at the boundary, where display rounding makes interpretation harder.


These values illustrate the logic; they are not recommended storage conditions or a specification for measurement accuracy. The application owner must choose acceptable limits and recovery behaviour for the materials, process and response plan. A wide buffer may reduce state changes, but it also requires a larger return towards normal before recovery.


3. Separate sensor state from a notification


Monnit’s operating-state explanation distinguishes the sensor’s Aware operation, assessment timing and reporting behaviour. It also describes gateway handling of Aware messages. Sensor state, received data and a person’s notification are separate observations; diagnose the layer that differs from the requirement.


For example, a newly received humidity value does not by itself establish that a notification rule has reset. Conversely, a delayed screen update does not prove that the sensing element is stuck. Compare timestamped evidence from the sensor history with the relevant rule history before deciding whether to adjust the buffer, investigate communications or review the application rule.


Hypothetical humidity alarm example: a 70 percent RH high limit and three percentage-point buffer give a 67 percent RH recovery boundary.
Original commissioning diagram. Example values explain the buffer; they are not application recommendations.

4. Test entry and recovery as a pair


Use a spare device or an authorised noncritical test arrangement. Do not alter a production room’s humidity simply to generate a test event, and do not wet the sensing element. Agree on a safe method, stable conditions and a suitable reference instrument with the responsible technician.


  1. Save the current configuration and confirm the intended settings have reached the sensor before testing.

  2. Establish a stable normal condition and record the reference reading, sensor reading and timestamps.

  3. Move safely beyond the chosen entry boundary and record the observed state and received event.

  4. Return inside the original threshold while remaining short of the planned recovery boundary; check that the result matches the intended hysteresis.

  5. Continue beyond the recovery boundary, allow for measurement and reporting timing, and verify recovery in the actual records.

  6. Repeat the cycle, then restore and document the approved final configuration.


5. Investigate an unexpected result before widening limits


Check whether the wrong variable’s buffer was edited, whether the units were misunderstood, or whether an application rule was mistaken for a device setting. Keep one controlled change per test so its effect remains identifiable. Moving both the threshold and buffer at once can make a successful result difficult to explain.


If the reference and sensor disagree under stable conditions, investigate measurement quality separately. Hysteresis changes state transitions; it does not correct an inaccurate humidity reading. Equally, do not apply an offset just to make an unwanted Aware indication disappear. Retain the original readings and configuration so support can reproduce the question.


A useful handover record shows the entry threshold, recovery margin, expected recovery boundary and observed results from two complete cycles. Include the reporting configuration and the application’s separate response requirements. This provides a practical basis for maintenance without implying that a generic wireless alarm is a certified protective function.


For support, send ProSense the exact sensor model, current threshold and buffer fields, units, a short timestamped history and the result you expected. Confirm any proposed software integration separately before assuming the same alarm behaviour will carry into another platform.


Need help with your application?


ProSense Instruments - explore instruments, sensors, data loggers and test equipment.


ProSense Solutions - discuss complete monitoring and automation systems.


ProSight Software - explore cloud dashboards, alarms and reporting. Device integration must be confirmed for your application.



Project enquiries: sales@prosense.com.au. Software enquiries: info@prosightsoftware.com.

Comments


bottom of page