Incorrect Sensor Alert

An alert can look incorrect for two common reasons: the configured rule does not match the condition you intended to monitor, or the Sensor reported an abnormal reading that caused a valid rule to trigger.

1. Check what triggered the alert

1. Open Message > Alarm Logs and select the alert.
2. Note the Sensor, alert type, trigger time, and reading shown in the event.
3. Open that Sensor's history and compare the reading at the same time.

If the event belongs to a different Sensor, open that Sensor's settings and review its rule. A Hub may sound for any supported Sensor assigned to the same Asset/Home.

2. Review the alert rule

Open Home > Device card > Settings > Alarm Rules, then check:

• The correct Sensor, component, or probe is selected.
• The acceptable range and unit are correct.
• Active Hours, Delay Before Alert, and Anti-False Alarm match the monitoring requirement.
• The rule is not so close to normal temperature or humidity changes that routine cycling triggers it.

Adjust the rule only when the new settings still meet the site's monitoring requirements. See Configure Alerts and Notifications.

3. Check whether the reading is abnormal

If the alert rule is correct but the history shows an unexpected spike or an implausible reading, follow Inaccurate Sensor Readings. Check placement, normal appliance cycles, probe connection, and a side-by-side comparison before applying calibration.

If the reading remains abnormal after those checks, contact support with the Sensor SN, alert screenshot, alert time, history screenshot, rule settings, and a photo of the Sensor or probe placement. This may indicate a Sensor or probe fault.