Alerts, Notifications & Channels
Configure alert rules, notification channels (Web Push, Mobile Push, WhatsApp, Email), per-vehicle settings, and troubleshoot notification delivery.
Last updated April 17, 2026
Alert System Overview
OpenVTS alerts monitor vehicle events in real-time and dispatch notifications through multiple channels. Alerts are configured per-vehicle with customizable thresholds and can be sent via four distinct channels simultaneously.
Notification Channels
| Channel | Description | Requirements |
|---|---|---|
| Web Push | Browser push notifications via service worker | Browser permission granted, HTTPS enabled |
| Mobile Push | Firebase FCM push to mobile apps | FCM configured in Settings, device token registered |
| WhatsApp Business API messages | WhatsApp API configured, E.164 phone number, approved template | |
| SMTP email notifications | SMTP configured and validated in Settings |
Per-Vehicle Configuration
Each vehicle can have individual alert settings. The speed limit field accepts a value in kph (kilometers per hour) to define the overspeed threshold for that specific vehicle.
- Select the vehicle from the vehicle dropdown
- Set the speed limit threshold (kph)
- Enable or disable individual channels for this vehicle
- Configure alert types: Ignition On/Off, Geofence Enter/Exit, Overspeed, Power Cut, SOS
- Save changes to apply the configuration
Test Notifications
Use the Test Notify button to send a test notification through the configured channels. This verifies that the channel configuration is correct and the recipient receives the message.
Toast Messages Reference
| Key | Message | Context |
|---|---|---|
| saved | Alert settings saved successfully | After saving alert configuration |
| loadFailed | Failed to load alert settings | When settings cannot be fetched |
| saveFailed | Failed to save alert settings | When save operation fails |
| pushRegistered | Push notifications registered | Browser push permission granted |
| pushAlreadyRegistered | Push notifications already registered | Permission was already granted |
| pushBlocked | Push notifications blocked by browser | User denied browser notification permission |
| pushDismissed | Push notification prompt dismissed | User dismissed the permission dialog |
| pushNotSupported | Push notifications not supported | Browser does not support push notifications |
| pushNotConfigured | Push notifications not configured | FCM or service worker not set up |
| pushFailed | Push notification registration failed | Technical failure during registration |
| testFailed | Test notification failed | Test notification could not be delivered |
Alert Types
| Alert Type | Trigger Condition | Severity |
|---|---|---|
| Ignition On | Vehicle ignition turns on | Info |
| Ignition Off | Vehicle ignition turns off | Info |
| Geofence Enter | Vehicle enters a geofence boundary | Warning |
| Geofence Exit | Vehicle exits a geofence boundary | Warning |
| Overspeed | Vehicle exceeds configured speed limit | Critical |
| Power Cut | External power supply disconnected | Critical |
| SOS | Panic/SOS button pressed on device | Critical |
| Idle | Vehicle idle exceeds threshold duration | Warning |
| Tow | Vehicle moves without ignition (potential towing) | Critical |
Troubleshooting Alerts
- Verify the channel is enabled for the specific vehicle
- Check that SMTP/WhatsApp/FCM credentials are configured in Settings
- Confirm the speed limit field has a valid kph value for overspeed alerts
- Ensure geofences are set to Active in Landmarks Studio
- Review the Vehicle Events log for delivery status of each notification
- Use Test Notify to isolate channel-specific delivery issues