You can set up an alert to inform you about the following device health conditions:


  • An LMU (location messaging unit) is not reporting to CTC. The alert is triggered if it hasn't reported for the last seven days.
     
  • An LMU is reporting an ESN (electronic serial number) of 0 (zero).
     
  • An LMU-55xx device has booted in failsafe mode and therefore has reverted to old firmware.
     
  • A VBUS has been turned off due to a CAN (controller area network) error.


To add a Device Health notification, follow these steps:


  1. Make sure that you are logged in to the account or parent of the subaccounts to which you want to add the Device Health alert. (See Switching Accounts if you need to change the parent account.)
    Note: Only devices in this account (and its child accounts, if you leave Process for Subaccounts selected) will trigger the alert.
  2. Click  on the left sidebar menu.
     
  3. Click Notifications on the flyout menu that appears.
     
    The Admin - Notifications screen will appear and list the alerts of the account you are logged in to.
      
  4. Click Add New at the top right.
     
    The Add Notification dialog box will be displayed.
        
  5. Type the name to use for the alert in the Notification Name field, such as "Device Health - LMU Not Reporting."
     
  6. Click the Notification Type drop-down arrow and select the Device Health alert type you want to use, as follows:
    Note: To find the alerts more quickly, you can type "Health" in the Notification Type field. Only matching results will remain in the drop-down list.
    • Select DeviceHealthEventAlertType to have CTC Admin send you an alert if an LMU is not reporting to the system (this will be triggered if the LMU hasn't reported for seven days); if a device is reporting an ESN of 0 instead of its actual ESN; or if an LMU-55xx device has booted in failsafe mode and thus has reverted to old firmware.
      Note: Do not be confused if the drop-down list item reads "DeviceHealthEventAlertType 12571"; it's the notification type you want, but may still have a label left over from the background code.
    • Choose DeviceHealthEventAlertType_VBUS to trigger a notice when a VBUS has been turned off due to a CAN error.
       
  7. Type an explanation of what the notification is designed to inform the user about in the Description field, such as "An LMU isn't reporting to CTC."
     
  8. Click the Severity drop-down arrow and select the priority level of the alert: Low, Medium, High, or Critical.
     
  9. Leave the Notification Status field at its default value of Enabled.
    Note: Disabled and Suspended will halt triggering the notification, but that's not likely what you'll want when you are adding a new one.
  10. Optionally, in the Snooze Duration field, type a snooze value (in seconds) for how long you would like the system to wait before sending another notification triggered from this alert.
     
  11. If you want the alert to be triggered by devices in subaccounts of the account you are logged in to, leave Process for Subaccounts selected.
     
  12. In the Triggers section of the dialog box, leave the triggers at their default values.
     
    These will be as follows, depending on the type of Device Health notification you selected:
     
    DeviceHealthEventAlertType
      
    		FAILSAFE_ACTION_NEEDED: Informs CTC if an LMU-55xx has booted in failsafe mode.
     
    ESN_0_DETECTED: Sends an alert if a device's ESN is reported as 0.
     
    GENERATE_FURL: Triggers an alert if an LMU hasn't reported to CTC for seven days.
    DeviceHealthEventAlertType_VBUS
      
    		VBUS_STATE_CHANGE: Sends a notification if a VBUS has been turned off.
     
    The Notification Actions section determines how the notification will be delivered — by text (SMS), email, URL POST, and/or push notification.
     
    The Device Health alert types automatically select the Email toggle and apply the default email template for the specific type.
      
  13. You can keep the default selections, or you can change which methods you want to use by clicking the sliders.
     
    To change the template of the message being sent, click the Template drop-down arrow and choose the new one.
     
  14. For Email, enter the email address(es) and subject to use.
     
    For SMS, enter the recipient's mobile number.
     
    For URL POST, provide the URL, username, and password.
     
    For Mobile PUSH, specify the app name, platform, and device IDs.
     
  15. Click Done.
     
    A success message will appear at the bottom of the screen, and your new alert will appear in the Admin - Notifications list.
      
  16. Click OK to dismiss it. (Or you can wait a few seconds, and it will automatically close.)