Learn everything you need to know about the Manage sensor page.

Manage sensors

The manage sensors page enabled users to manage their own sensors. This page is meant to configure sensors, not to see actual sensor readings, alarms and data.

This page is also meant to manage asset types and link them to sensors. This enables organizations to be scalable (there is no need to create alarmprofiles per sensor or organizational unit). This page consists out of three tabs:

1. Sensors
2. Custom alarms - Please find article here
3. Asset alarms - Please find article here 

Sensors

In the sensor tab, an overview of all sensors is shown. The following details are shown:

• Alarm set
  An indication whether one or more alarms are set, or no alarms are set.
  
  
• Sensor alias
  The name of a sensor
  
  
• Asset type
  The asset type linked to a sensor. Linked alarm profiles can also link alarm profiles automatically.
  
  
• Organizational unit
  The organizational unit the sensor is linked to.
  
  
• % of alarmprofiles active
  The percentage of alarm profiles that is active. So if there are two alarmprofiles linked, but only one is active, it is indicated as 50%.
  
  
• Recipients
  Indicates whether recipients are linked to all alarm profile, linked to some profiles (partially linked) or not linked.
  
  
• Actions
  An action button with the possiblity to:
  • Edit sensor
    The following two options can be edited: Sensor alias and asset type. Changing the asset type does impact the linked alarm profiles / recipients.
    
    
  • Manage alarm profiles
    Enable/Disable alarm profiles based on the asset type or delete alarm profiles that are custom. Custom alarms can be added here as well. The recipients per alarm profile can be linked as well.
    
    
  • Unlink
    Unlink the sensor from the organizational unit. It will become available in the sensor pool to link again or to deregister.

Cascade

For the recipients, cascade can be added as well. Cascade will send the alarm message to recipient 1 first. The first recipient should acknowledge the alarm within 15 minutes. If not, the alarm will be sent to recipient 2. Again, if not acknowledged within 15 minutes, it goes to recipient 3, and so forth. When the cascade reaches the highest number without acknowledgement, depending in the settings two different things will happen:

• Mode is set to 'once': The cascade stops after all recipients received a message
• Mode is set to 'always': The cascade continues to cycle until:
  • Somebody acknowledges the alarm
  • The maximum number of messages is reached