How to Configure Status Thresholds
Set up automated status changes that alert your team when sensor values exceed acceptable limits.
Quick Summary
Open an IoT device, go to Profile → Status Thresholds → Edit. Define conditions for Critical (red) and Warning (yellow) status levels.
Before You Begin
- The asset must be an IoT device with an integration service
- The asset type must have properties defined that receive sensor data
- You must have edit permission for assets
What Are Status Thresholds?
Status thresholds are rules that automatically change an asset's status based on sensor data:
| Status | Color | When Triggered |
|---|---|---|
| Critical | Red | Conditions in Level 1 are met |
| Warning | Yellow | Conditions in Level 2 are met |
| Normal | Blue | No threshold conditions are met |
Step-by-Step Guide
Step 1: Open the IoT Device
- From the sidebar, click Asset
- Find and click on an IoT device
- Make sure you're viewing an asset with an integration service
Step 2: Access Status Thresholds
- Click the Profile tab
- Scroll to Status Thresholds section
- Click Edit Thresholds
Step 3: Add Critical Conditions (Level 1)
Define when the asset should show Critical status:
- Click Add Data Field
- Select the property to monitor (e.g., temperature)
- Choose the operator (e.g., greater than)
- Enter the threshold value (e.g., 30)
Step 4: Add Warning Conditions (Level 2)
Define when the asset should show Warning status:
- Scroll to the Warning section
- Click Add Data Field
- Configure conditions the same way as Critical
Step 5: Configure Multiple Conditions (Optional)
For complex rules:
- Add additional conditions using Add Data Field
- Choose logic operator between conditions:
- AND — All conditions must be true
- OR — Any condition can be true
Step 6: Save
Click Update to activate the thresholds.
Operators Reference
| Operator | Symbol | Use For |
|---|---|---|
| Equal To | = | Exact value match |
| Not Equal To | != | Excluding a value |
| Greater Than | > | Above a limit |
| Greater Than or Equal | >= | At or above a limit |
| Less Than | < | Below a limit |
| Less Than or Equal | <= | At or below a limit |
Logic Operators
When you have multiple conditions:
| Logic | Behavior | Example |
|---|---|---|
| AND | All must be true | temp > 30 AND humidity > 80 |
| OR | Any can be true | temp > 30 OR temp < 0 |
You can have up to 5 conditions per threshold level.
Data Types
Match the operator and value to the property type:
| Property Type | Value Input | Example |
|---|---|---|
| Float/Integer | Number input | 25.5, 100 |
| String | Text input | "OK", "Error" |
| Boolean | Checkbox | true/false |
Real-World Examples
Example 1: Temperature Monitoring for Cold Storage
Situation: Cold storage must stay between -2°C and 4°C.
Threshold Configuration:
Critical Conditions (Immediate action required):
temperature > 8ORtemperature < -5
Warning Conditions (Monitor closely):
temperature > 4ORtemperature < -2
Result:
- Normal: -2°C to 4°C (blue status)
- Warning: 4°C to 8°C or -5°C to -2°C (yellow status)
- Critical: Above 8°C or below -5°C (red status)
Example 2: Server Room Environment
Situation: Server room requires temp 18-24°C and humidity 40-60%.
Critical Conditions:
temperature > 28ORtemperature < 15- OR
humidity > 70ORhumidity < 30
Warning Conditions:
temperature > 24ORtemperature < 18- OR
humidity > 60ORhumidity < 40
Result: Alerts trigger before conditions damage equipment.
Example 3: Battery Monitoring
Situation: Alert maintenance team before sensor batteries die.
Critical Conditions:
battery < 10
Warning Conditions:
battery < 30
Result: Team can proactively replace batteries.
Example 4: Door/Window Sensor
Situation: Security door should normally be closed.
Critical Conditions:
doorOpen = true
No Warning Level Needed (door is either open or closed).
Result: Critical status when door opens unexpectedly.
Example 5: Combining Multiple Sensors
Situation: Greenhouse needs both temperature AND humidity in range.
Critical Conditions (AND logic):
temperature > 35ANDhumidity < 30
Warning Conditions:
temperature > 30ORhumidity < 40
Result: Critical only when it's both hot AND dry. Warning for either condition alone.
Troubleshooting
Status Not Changing
| Issue | Solution |
|---|---|
| Threshold not triggering | Verify the property name matches exactly |
| Wrong data type | Ensure value type matches property (number vs string) |
| Device not reporting | Check connection status and integration |
Threshold Tips
- Start with Warning first — Set conservative warning levels, then tighten critical
- Test with current data — Check if current values should trigger status
- Consider normal variation — Don't set thresholds too close to normal values
Clearing Thresholds
To remove all threshold rules:
- Open the asset
- Go to Profile → Status Thresholds → Edit
- Remove all conditions using the delete button
- Click Update
The asset will return to Normal status.
Related Articles
Need help? Contact Infodeck Support