Understanding Notifications in Stat Temp
Using the Prebuilt Notifications in Your Portal
Assigning Users to Notifications
Creating or Cloning Notifications (Advanced Use)
Assigning Notifications to Sensors and Monitors
Escalation & Conditional (Scheduled) Alerting
What to do after receiving a notification
Notification Throttling (Long-Running Events)
Notifications are a core part of Stat Temp’s monitoring system. They alert you when a sensor or monitor detects a condition that may require attention—such as a temperature excursion, a missed check-in, or a hardware status change. Understanding what notifications are, how they behave, and how they interact with events will help you use your system confidently.
Every Stat Temp portal includes several prebuilt notifications designed to cover the most common environmental and device conditions. These notifications come with recommended settings already in place. To begin receiving alerts, you will simply:
- Assign users to each notification, and
- Assign the notifications to the appropriate devices
This section introduces how notifications work and the types of events they support. The next section will walk through the prebuilt notifications themselves and how to use them.
What Is a Notification?
A notification is an automated alert created by Stat Temp when a sensor or monitor detects a predefined condition. These alerts help ensure you remain aware of critical changes in your environment, allowing you to take timely action when needed.
Notifications are device-specific, meaning:
- A notification is assigned to either a sensor or a monitor
- Each device can only have one notification per event type (for example, a sensor cannot have two “Critical Temperature” notifications)
You can create as many notifications as your facility requires to support different workflows, groups, or alerting needs.
Types of Notification Events
Stat Temp supports both sensor-based and monitor-based events. Each event type corresponds to a condition the system can detect. Notifications must be configured for at least one event type in order to trigger alerts.
Sensor-Based Events
These events are triggered when a sensor detects environmental conditions outside your defined ranges or stops communicating as expected.
| Event Name | Description |
|---|---|
| Critical Temperature / Humidity | Readings fall outside allowable temperature or humidity ranges |
| Warning Temperature / Humidity | Readings are trending toward critical thresholds |
| Missed Check-In | Triggered when the sensor fails to report data for a set number of check-ins (default: 3, configurable up to 10) |
Monitor-Based Events
Monitor-based notifications alert you to hardware or system conditions happening directly on the monitor.
| Event Name | Description |
|---|---|
| Running on Power | Monitor is powered via AC |
| Running on Battery | Monitor has switched to battery power |
| Low Battery | Battery level is below the recommended threshold |
| No Battery | Battery is not detected |
| Low Drive Space | Internal storage is nearing capacity |
| Low Signal Strength | Monitor’s network connection is weak |
| No Sensors Attached | Monitor has no active or detected sensors |
Why Notifications Matter
Notifications allow you to:
- Maintain visibility into temperature- and humidity-sensitive areas
- Respond quickly to excursions or equipment issues
- Meet compliance and documentation requirements
- Ensure your workflows and teams remain informed
Whether you’re monitoring a single unit or an entire facility, notifications help keep operations running smoothly by ensuring the right information reaches the right people at the right time.
Next Steps
If you’re ready to start configuring your alerting system, continue to: