top of page

iMonnit Missed a Second Sensor Alert? Check Joint Snooze

6 days ago
4 min read

One humidity sensor produces an iMonnit notification, then another sensor crosses its rule threshold without a second alert arriving. Before changing the sensors or reducing their reporting intervals, check how the rule shares its snooze period. A rule assigned to several devices needs an explicit decision about whether those devices may alert separately.


The immediate question is whether the rule is configured to snooze triggers Jointly or Independently. Check that setting alongside the received readings and notification evidence. It can explain the pattern, but it cannot establish that every missing message has the same cause.


Decide whether the first event should silence the group


Monnit documents Independently as allowing multiple sensors to alert one after another. Jointly applies the snooze after the first sensor triggers a notification. For a shared rule, that distinction matters when another device meets its trigger condition during the snooze period.



Write the operational requirement in plain language. If each monitored room needs its own initial warning, the acceptance test must include two different rooms triggering close together. If several sensors represent one common incident and the team wants to suppress closely spaced group notifications, document that intention and the information the operator will still need. A quieter phone is not sufficient evidence that the chosen policy is appropriate.


The Monnit battery-powered wireless humidity sensor pictured below is a practical example of a device used at an individual monitoring point. The issue discussed here is the iMonnit rule configuration; it is not a claim that a particular enclosure, radio variant or firmware determines the snooze policy.


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.


Use a two-device timeline


Hypothetical test: sensors A and B are assigned to the same rule, with a deliberately selected 30-minute snooze. A qualifying reading from A reaches the platform at 10:00; B supplies its own qualifying reading at 10:05. These times and the duration illustrate a test plan, not a manufacturer default or a reported customer result.


With Jointly selected, investigate whether A has started a shared snooze that explains the absent B notification. With Independently selected, test the requirement that B can produce its separate alert. Keep the rule conditions, recipients and other settings constant when comparing the two arrangements. Do not infer behaviour from an isolated test of A alone.


Repeat the comparison with B first and A second, after returning the test arrangement to a documented starting state. Reversing the order helps expose an unnoticed difference in device assignment or trigger configuration. If only one order works, retain that discrepancy for investigation instead of assuming the snooze toggle has solved the problem.


Check the setting without losing the starting configuration


In iMonnit, open Rules, select the relevant rule and use its Edit tab. Monnit identifies the Snooze each trigger section as the place to choose the configuration and save it. Confirm the interface and available options in the account being commissioned; this guide does not transfer that menu path to another Monnit software product.


Before an authorised change, record the rule name, assigned device IDs, trigger conditions, snooze duration, selected mode, schedules and recipients. Preserve a screenshot or configuration record that allows the previous arrangement to be restored. Keep passwords, security codes and account tokens out of support material.


Use spare devices, an isolated test rule or an approved test window. Agree the notification recipients and expected test traffic in advance. Do not create a real humidity excursion in valuable stock merely to exercise an alarm, or alter a production rule while relying on it for operational monitoring.


Separate a qualifying reading from a delivered message


For each test event, retain three pieces of evidence: the device identity and reading visible in the platform, the rule configuration applicable at that time, and the notification outcome. Record timestamps with a timezone. A sensor graph alone does not prove that a message reached the intended recipient.


Also distinguish the second device’s first alert from repeat notifications about the first device. Monnit’s rules documentation treats snooze, notification delay, acknowledgement, schedules and recipient configuration as separate topics. If the snooze selection matches the requirement, check those other parts systematically rather than repeatedly shortening the snooze period.



Common mistakes are testing only one sensor, changing several rule settings at once, confusing fewer messages with fewer abnormal readings, and accepting a screenshot without verifying the receiving channel. Changing sensor Heartbeats does not by itself demonstrate that a shared notification policy now meets the requirement.


Leave a reproducible handover record


Record both trigger orders, the observed results, any untested conditions and the final approved configuration. Restore temporary settings and confirm routine monitoring before closing the test. This exercise verifies a monitoring requirement; it does not establish a certified protective function or guaranteed message delivery.


For help, provide ProSense with the exact sensor models, the iMonnit product in use, a sanitised rule screenshot and the A/B event timeline. State whether the team requires one group notification or separate warnings for each location. That gives the support team a concrete behaviour to verify.


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