You may confirm that Device ManageR is running by following these steps:

1. Open the Services tool in the Windows system that Device ManageR is installed on.
   • You may find Services at the following path: Start–> Control Panel–> Administrative Tools–> Services.
2. Locate AVTECH Device ManageR in the list of programs.
3. The Status column will display Running if the service is running.
   • Otherwise, the status will be blank.
4. If the service is running, the options to the left of the screen will be Stop and Restart.
   • If the service is not running, the only available option will be Start.

You may view your Device ManageR alert configurations by viewing the software’s .XML files in your web browser or in a text editor.

1. First, locate Device ManageR’s installation directory.
   • By default, you can find it at C:\Program Files\AVTECH Device ManageR or C:\Program Files (x86)\AVTECH Device ManageR.
2. In Device ManageR’s installation directory, open the “conf” folder.
3. In the “conf” folder, you’ll see program files containing Device ManageR’s settings and alert configurations, as show below:
   
4. When you initially set up alerts in Device ManageR, you had to create these individual components:
   1. First you set up individual Contacts. (This is where a user’s email address and phone number are stored).
   2. Next you created Actions. You could create notification actions (like an email action that is associated with a particular contact) or a different type of action, such as a relay toggle or system shutdown action.
   3. Then you created Action/Notification Lists. These lists are how you associated an action or group of actions with individual alerts.
   4. Finally you created Alerts on Room Alert or TemPageR devices, Axis cameras or external pings.
5. These alert configurations are stored in separate files:
   • contacts.xml contains your Contacts
   • actions.xml contains your Actions
   • action_schedules.xml contains your Action/Notification Lists
   • alerts.xml contains your Alerts
6. To view Device ManageR’s alert configurations, open the desired .xml file through your browser or in a text editing program, such as Notepad or Notepad++.
7. The tabs below show example .xml files loaded in Notepad++:

contacts.xmlactions.xmlaction_schedules.xmlalerts.xml

Shown below is an example contacts.xml file loaded in Notepad++:

This file shows us that we currently have two contacts configured and enabled: IT Mgr and Facilities Mgr.

The following elements make up each <contact> in the XML file:

• <id>: When this contact is used to create an action, this ID number is referenced in the actions.xml as <contact_id>.
• <name>: In our example, the name of our first contact is IT Mgr.
• <description>: Description is always an optional field in Device ManageR. In our example, this field is left blank.
• <email>: The email address of our first contact is IT_Mgr@Example.com.
• <schedule_id>: In Device ManageR, you may associate schedules with your contacts, actions, alerts, etc. If you do, then the schedule’s ID number appears here. In our example, there is no schedule associated with either contact.
• <enabled>: This field reads true if the contact is enabled and false if the contact is disabled. (When a contact is disabled, Device ManageR cannot send notifications to them.) In our example, both contacts are enabled.
• <dot_phone>: If Device ManageR is configured to use a voice modem to send notifications, it can send them to the phone number saved in this field. In our example, this field is left blank.
• <dot_service>: If Device ManageR is configured to use a TAP service, it uses the service number saved in this field. In our example, this field is left blank.
• <dot_password>: If Device ManageR is configured to use a TAP service, it uses this password. In our example, this field is left blank.
• <gsm_phone>: If Device ManageR is configured to use a GSM modem to send notifications, it can send them to the phone number saved in this field. In our example, this field is left blank.

Show more information about the contacts.xml file

Show less

Shown below is an example actions.xml file loaded in Notepad++:

This file shows us that we currently have two actions configured and enabled: one to email our IT Mgr and one to email Facilities.

The following elements make up each <action> in the XML file:

• <id>: When this action is used in an Action/Notification List, this ID number is referenced in the action_schedules.xml as <action_id>.
• <name>: In our example, the name of our first action is Email IT Mgr.
• <description>: Description is always an optional field in Device ManageR. In our example, this field is left blank.
• <enabled>: This field reads true if the action is enabled and false if the action is disabled. (Device ManageR will not perform a disabled action.) In our example, both action are enabled.
• <type>: There are different types of actions that can be set up in Device ManageR. In our example, both actions types are NotifyContact.
• <retry_count>: This value tells us how many times Device ManageR will retry the action if it fails.
• <schedule_id>: In Device ManageR, you may associate schedules with your contacts, actions, alerts, etc. If you do, then the schedule’s ID number appears here. In our example, there is no schedule associated with either action.
• <contact_id>: This is the ID number of the contact associated with this action.

Show more information about the actions.xml file

Show less

Shown below is an example action_schedules.xml file loaded in Notepad++:

This file shows us that we currently have two Action/Notification Lists configured and enabled. One list notifies our IT team every minute (60 seconds) for a maximum of 5 times. The other list notifies our Facilities team every 5 minutes (300 seconds) for a maximum of 2 times.

The following elements make up each <action_schedule> in the XML file:

• <id>: When this action is used in an Action/Notification List, this ID number is referenced in the action_schedules.xml as <action_id>.
• <name>: In our example, the name of our first action is Email IT Mgr.
• <description>: Description is always an optional field in Device ManageR. In our example, this field is left blank.
• <enabled>: This field reads true if the action is enabled and false if the action is disabled. (Device ManageR will not perform a disabled action.) In our example, both actions are enabled.
• <type>: There are different types of actions that can be set up in Device ManageR. In our example, both actions types are NotifyContact.
• <action_schedule_items>: In our example, both of our Action/Notification Lists only contains one action each, but yours may contain more.
• <id>: Each Action/Notification list item has its own ID number.
• <interval>: This value controls how frequently the action repeats.
• <delay>: This value controls how many seconds Device ManageR waits after an alert is triggered before performing the action.
• <max_perform>: This value controls how many times an action is allowed to repeat.
• <action_id>: This is the ID number of the action that’s performed when the alert triggers.
• <clear_action_id>: This is the ID number of the action that’s performed when the alert clears. (In each of our lists, the trigger and clear actions are the same.)

Show more information about the action_schedules.xml file

Show less

Shown below is an example alerts.xml file loaded in Notepad++. (In order to keep our screenshot small, we collapsed some of the information.)

This file shows us that we currently have two alerts configured and enabled, although our second alert is hidden in this screenshot. We can see that our first alert, Data Center Too Hot, triggers when the internal sensor on our device, Example RA32E, goes above 78° Fahrenheit.

The following elements in the XML file make up our temperature* alert:

• <id>: Each alerts gets a unique ID number.
• <name>: In our example, the name of our first alert is Data Center Too Hot.
• <description>: Description is always an optional field in Device ManageR. In our example, this field is left blank.
• <devname>: This is the name of the device associated with the alert.
• <sen_name>: This is the name of the sensor associated with the alert.
• <enabled>: This field reads true if the alert is enabled and false if the alert is disabled. In our example, both alerts are enabled.
• <item_missing>: When set to true, the alert will notify you if your device or sensor is no longer available.
• <perform_on_missing>: This element can be left set to false. It controls the way that Device ManageR notifies you when an <item_missing> alarm is triggered.
• <missing_timeout>: This controls how many scans the device/sensor needs to miss before Device ManageR sends an alert notification.
• <schedule_id>: In Device ManageR, you may associate schedules with your contacts, actions, alerts, etc. If you do, then the schedule’s ID number appears here. In our example, there is no schedule associated with our alert.
• <sen_id>: This is the ID number associated with the sensor.
• <snametype>: This value tells us the sensor label and sensor channel.
• <devmac>: This is the MAC address of the device associated with the alert.
• <action_schedule_id>: This is the ID number of the Action / Notification List associated with the alert.
• <alert_email>: When expanded, this section shows the contents of the alert email.
• <last_alarm>: This is the timestamp of when the alert last triggered.
• <alarm_cnt>: This is a count of how many times the alert has triggered.
• <threshold hysteresis=“1.0” id=”1″ oper=”gt” type=”1″ value=”78.0″/>: We can tell a couple key pieces of information from this element. In our example, our alert operator, gt, means greater than. Our alert value is 78 (° Fahrenheit).

* Different types of alerts have different elements.

Show more information about the alerts.xml file

Show less

You may view your Device ManageR settings by viewing the software’s .XML files in your web browser or in a text editor.

1. First, locate Device ManageR’s installation directory.
   • By default, you can find it at C:\Program Files\AVTECH Device ManageR or C:\Program Files (x86)\AVTECH Device ManageR.
2. In Device ManageR’s installation directory, open the “conf” folder.
3. In the “conf” folder, you’ll see program files containing Device ManageR’s settings and alert configurations, as show below:
   
4. To view Device ManageR’s settings, open the settings.xml file.
   • You may view the contents of the .xml file through your browser or open it in a text editing program, such as Notepad or Notepad++.
5. Shown below is an example settings.xml file loaded in Notepad++:
   
6. For our example, we’re going to focus on our primary mail server settings:
   
7. In the <mailserver1> section of the settings.xml file, we see the following:
   • <username>: the username is encoded, so we cannot easily view or edit this.
   • <timeout>: the mail server timeout value is 15 seconds.
   • <server>: our mail server domain is mail.example.com.
   • <pass>: our password has been encoded, so we cannot easily view or edit this.
   • <sender>: our emails are configured to send from Sender@Example.com.
   • <use_ssl>: our mail server is not using SSL encryption, so this is set to false.
   • <use_tls>: our mail server is not using TLS encryption, so this is set to false.
   • <port>: our mail server port is 25.
   • <test_recipient>: you can view the test email recipient, but this email address would only be used if a test email was sent through Device ManageR’s web interface.

If you simply want to know if your discovered device stops communicating with Device ManageR, this is generally the easiest method.

With this method, you can modify any alert (such as a temperature alert), so that it also checks the Room Alert Monitor’s connection status and sensor’s connection status.

Ping alerts allow for quicker, more sensitive connection status monitoring. You can also use this method to monitor the connection status of other types of devices on your network.

First, restart the Device ManageR service. This FAQ shows you how: How To Stop, Start And Restart The Device ManageR Service.

When the program restarts, it will rediscover all of your devices, including the new one.

1. Open Device ManageR in your web browser. You may open it by entering ‘localhost:8080’ or ‘<IP address of host system>:8080’ in your browser’s address bar.

2. Select Alerts / Tasks in the navigation bar to the left of your screen.

3. Then re-point the Actions and Alerts to the new device by following the instructions below:

Before you can set up staggered Light Tower audio actions in Device ManageR, you must enable your Light Tower in your Room Alert Monitor’s web interface. This FAQ shows you how: How To Enable Your External Light Tower Or Relay Switch In Your Room Alert Monitor.

Once you’ve enabled your Light Tower in Room Alert, create two Light Tower actions in Device ManageR:

• Audio 1 On
• Audio 1 Off

For step-by-step instructions on setting up actions, please see How To Configure A Light Tower Action In Device ManageR.

Your two actions should look similar to the examples below when they are completed:

Once you’ve saved each, you’ll see your two audio toggle actions in your Actions list:

Once you’ve saved your two audio toggle actions, the next step is to group them in an Action/Notification List. This FAQ shows you how: How To Configure Action/Notification Lists In Device ManageR.

Sample Action/Notification List – Staggered Audio

Our sample Action/Notification List, called Light Tower – Staggered Audio, does the following:

• Turns the audio alarm on twice for 30 seconds; leaves the audio on if the alert condition persists for more than 2 minutes (120 seconds).
• Turns the audio completely off at whatever point the alert condition clears.

Audio Action/Notification List Items

These are the specifics you’ll need when setting up your staggered audio list items:

– Set your first Alert Action to Audio On. Have subsequent Alert Actions alternate between Audio Off and Audio On.

– Keep increasing the Start the Action after ___ seconds for each item in your list. (In our example, we increase it each time by 30 seconds.)

– Set Perform the action a maximum of ___ times to 1 for each item in your list.

– Set all of your Clear Actions to Audio Off so that no matter what, the sound will cease when the alarm condition no longer exists.

– Set your last Alert Action to the state you want to end the series with. In our example below, the series ends with Audio On.

Below you see the first two Action/Notification List Items in our series:

Once you’ve saved your Action / Notification List, the next step is to associate it with an alert. You can find instructions in our FAQ, How To Create An Alert In Device ManageR.

Your Alerts may look similar to the one shown below. Note that we chose our Light Tower – Staggered Audio list in the Action / Notification List field. This alert will trigger the staggered audio actions when the temperature exceeds 80° Fahrenheit.

First, create the necessary Toggle Light Tower actions in Device ManageR. For instructions, please see our FAQ, How To Configure A Light Tower Action In Device ManageR.

In our example, we’ve created light tower actions to meet the following conditions:

– Green LED is on when the temperature is less than 75°F

– Yellow LED is on when the temperature is between 75°F and 80°F

– Red LED is on when the temperature is above 80°F

This required a total of six toggle actions—1 to turn off each LED and 1 to turn on each LED—as shown below.

Once you’ve saved your toggle actions, the next step is to put them in Action/Notification Lists. For complete instructions, please see our FAQ, How To Configure Action/Notification Lists In Device ManageR.

When you get to Step 6 in the FAQ, you’ll need to change the Perform the Action setting to A maximum of 1 times.

Your completed Action/Notification Lists may look look similar to the examples below when they are completed:

Once you’ve saved your Action/Notification Lists, the next step is to associate them with the proper alerts. You can find instructions to create your alerts in our FAQ, How To Create An Alert In Device ManageR.

Your Alerts may look similar to the examples below when they are completed:

Before you can set up Digital Active Power sensor alerts in Device ManageR, you must first configure the sensor in your Room Alert Monitor. Your Digital Active Power Sensor will not appear in Device ManageR unless you first configure it in your Room Alert Monitor.

To configure your Digital Active Power Sensor, follow these steps:

1. Open your Room Alert Monitor’s web interface. You may open the interface using Device Discovery, Device ManageR, or your account at RoomAlert.com. You may also type the IP address of the unit directly into the address bar of your web browser.

2. Navigate to Settings→Network in the navigation bar to the left.

3. Find the digital sensor interface that matches the port you connected your Digital Active Power Sensor to. For example, if you used the first digital port on your Room Alert Monitor, look for Sensor 1 Alarm Configuration; if you used the second, look for Sensor 2 Alarm Configuration, and so on.

4. In the Sensor Type drop-down menu, select Temp/Active Power.

5. In Sensor Label, you may leave the default, Ext Sensor X, or name your Digital Active Power Sensor. In our example, we’re calling it DAP Server 1.

6. In Power, make a selection in the drop-down menu depending on how you intend to alert:

– If you wish alerts to come only from Device ManageR, leave the default Alert Disabled. This means the Room Alert itself will not go into an alert state for the Power portion of the Digital Active Power Sensor.

– If you wish also to alert from the Room Alert unit itself, select No Power Detected or Power Detected.

7. Select Save Settings at the top or bottom of the page. Your Room Alert Monitor will automatically reboot and commit your changes.

Once you have configured your mail server, your contacts, your actions and your Action/Notification Lists in Device ManageR , you may set up an alert for your Digital Active Power Sensor by following the instructions below:

1. Open Device ManageR in your web browser. You may open it by entering ‘localhost:8080’ or ‘<IP address of Device ManageR’s host system>:8080’ in your browser’s address bar.

2. Select Alerts / Tasks in the navigation bar to the left.

3. In the Alerts / Tasks menu, select Alerts.

4. Select Add to add a new alert.

5. In the Add New Alert screen that appears:

– In Name, enter a name for your alert. Our example is called DAP Server 1 – No Power Detected.

– In Device, select your Room Alert Monitor from the drop-down list. We’re choosing the Room Alert 32E in our data center.

– In Alarm when…, you’ll then see a drop-down list with all of the unit’s individual sensors. Select your Digital Active Power Sensor – Volts. (Ext Sensor 1 – Volts, for example.)

– In is, set the threshold for the Digital Active Power Sensor:

To alert for power OFF, enter ‘less than (<) 0.18.’

The Digital Active Power Sensor considers power to be off when it detects less than 0.18 volts.

With this setting, when the voltage reaches 0.17 or lower, Device ManageR will go into an alert state; this alert state will clear when the voltage reaches 0.18 or higher.

To alert for power ON, enter ‘greater than or equal to (>=) 0.18.’

The Digital Active Power Sensor considers power to be on when it detects 0.18 or more volts.

With this setting, when the voltage reaches 0.18 or higher, Device ManageR will go into an alert state; this alert state will clear when the voltage reaches 0.17 or lower.

– In Alarm if item is unavailable for X scans, you may leave the default, 4 scans, or enter another value. You may also disable this feature if you wish by unchecking the check box. In our example, we’re leaving the default.

– In Action / Notification List, select an already-configured list from the drop-down menu or create a new one by selecting Add. Here we’re choosing a List we called Notify IT Staff.

– Then select Save.