Legacy App Support

Smart Alert Management will not be supported in the legacy app workflow. It will only be supported through the API and the new UI. It will be disabled in the old app as the view will not be connected to the new API feature. Existing Smart Alerts will continue to behave normally. We will migrate those to the new configurations model. Any new ones created will need to follow the new model.

Product Overview

Configurations empower you to create rules that establish a one-to-many relationship. It will take away the need to manage settings at the device level. That has been seen to be monotonous and tedious. This feature provides a more efficient way to manage your different entities.

You can create one smart alert and affect multiple devices or zones as a user. Currently, the table shows what is supported through configurations. We will continue to roll out new entities as we develop this feature.

Smart Alert Workflow Change

Device Smart Alerts will be migrated to an account level control. We have created one source where you can manage your device's smart alerts. In addition, you will be able to set smart alerts up to affect all devices.

The original view will be deprecated as we shift to configurations. It was focused on editing smart alerts at the device level. The below image demonstrates what the previous workflow was like. The workflow will change from


to a flat list within Account Settings. For example:


The current smart alert table rows will show the following columns:

Column NameDescription
NameThe name of the smart alert
Alert TypeThe category of alerts that can range from custom data outside of bounds to a more specific type of device is not active.
Last ModifiedThe date that the smart alert configuration was last updated by a user.
ActionsButtons outlining the actions to delete the table row or configure the smart alert. Configuring will navigate you to a new page.

The migration of device-centric smart alerts to configurations will change the dynamic of how users manage smart alerts.


Migration Strategy

We recommend editing a smart alert in the list. Include/Exclude device(s) or zone(s) and rename the smart alert with a unique name targeting the zone or area of interest. Then you can proceed with deleting the other duplicate smart alerts.

We are making improvements to the list to better distinguish between device-specific alerts.

We choose this option to assist with training users on how smart alerts will have included/excluded groups of device(s) and zone(s).

Product Support

The list of features this will extend to is shown below. This is not in a prioritized list but more to demonstrate what Freedom has placed on its roadmap.

Smart AlertsSupported
Device Settings (Dashboards, Expected Available)Planning
Zone ShiftsPlanning