Alert thresholds
A threshold is a normal operating range (a start and an end value) for a single tag. When a reading goes outside that range, the device's status dot turns yellow and a THRESHOLD_VIOLATION alert is recorded. When the reading returns to range, a THRESHOLD_CLEARED alert is recorded and the dot goes back to green.
Alerts fire only on the crossing — once when the value leaves the range and once when it comes back — not on every reading, so you won't be flooded while a value sits out of range.
Setting or changing a threshold
- Open the device and find the tag.
- Edit its threshold start and threshold end.
- Save. The change is pushed to the gateway and takes effect on the next reading.
You can edit a threshold at any time without deleting and re-adding the tag. Set both values to 0 to remove the threshold.
Enter thresholds in displayed units. If the tag has a scaling factor (multiply or divide) or offset (see device parameters), type the start/end values as they appear on your dashboards — i.e. after scaling is applied, not the raw sensor number. The device and platform convert each raw reading to the displayed value before comparing it to the range, so a threshold of
45matches when the shown value crosses 45.
Plan feature. Setting a non-zero alert threshold requires a plan that includes thresholds. On plans without it, the threshold fields are disabled — upgrade to enable them. (You can always clear a threshold to
0.)
Threshold vs. rules
A threshold gives you the at-a-glance yellow dot and a recorded event. For actions when a value crosses a limit (email, webhook, in-app, MQTT), create an alert rule instead — rules add delivery and cooldown on top.