What are Notifications?

What Is a Notification?

A notification is an alert generated by your Stat Temp system to inform you about an issue or event. Notifications are device-specific, meaning they must be assigned to a sensor or monitor to function.

You can create as many notifications as needed, but each device can only have one notification of each type at a time. For example, a single sensor can only have one active "Critical Temperature" notification assigned.

Default Notifications

When setting up your Stat Temp site, you’ll have access to a predefined list of events that notifications can be assigned to. These event types correspond to specific conditions detected by your sensors or monitors.

You can create or clone notifications for any of the following events:

Sensor Events

These events relate to environmental readings or sensor behavior.

Critical Temperature/Humidity
Warning Temperature/Humidity
Missed Check-in (3 missed network check-ins in a row. This can be adjusted up to 10 missed checks if needed).

Monitor Events

These events relate to environmental readings or monitor's behavior.

Running on Power
Running on Battery
Low Battery
No Battery
Low Drive Space
Low Signal Strength
No Sensors Attached

Notification Glossary

Here’s a breakdown of the main options you’ll encounter when configuring a notification:

Device Type: Choose "Sensor" or "Monitor." This determines which devices the notification can be assigned to. (Cannot be changed after creation.)
Notification Delay: How long the system waits before triggering the alert. This delay allows the issue to potentially resolve itself before notifying users.
Create Event: If enabled, this notification will log an event to the Events page.
Requires Acknowledgement: If checked, users must manually acknowledge the notification.
- Notification Link Type:
  - View Event: Opens the Events page where actions can be taken.
  - Auto-Acknowledge: Marks the alert acknowledged and opens the event page.
- Snooze Option: Allows users to temporarily silence the notification.
Requires Resolution: Indicates whether action must be taken to mark the event resolved.
Auto Close: Automatically closes the event once resolved.
Repeat / Repeat Forever: Determines whether and how often the alert repeats.
Notification Chain: Defines who is notified, in what order, and by what method (email, SMS, phone call).
Schedule: Enables time-based delivery (e.g., only during work hours).
Notification Message: Editable message fields for email and text with dynamic device-specific data.