Monitoring temperature and humidity with Sensatronics environmental sensors
Note Copied
Monitoring of Sensatronics sensors is not included in OP5 Monitor version 9.0 and above.
Introduction Copied
If you want to monitor temperature, humidity or wetness, OP5 have tested the Sensatronics E series of environmental monitors.
In this how-to we will configure the EM2 model, connect the sensor probes and add relevant services in OP5 Monitor.
Many of the following steps can be used for other Sensatronics products, but be aware of minor differences and consult the included manuals.
Prerequisites Copied
- Sensatronics EM2 environmental monitor with included accessories
- Computer with serial port or USB-to-serial converter
- Terminal emulator like Minicom, HyperTerminal or similar for serial access
- Needle-nose pliers are recommended for mounting of probe connections
Instructions Copied
Connecting probes and cables Copied
Read the included “Quick start guide” and follow the instructions covering connecting your probes, serial, network and PSU cables. In this example we are using the combined humidity and temperature probe in combination with the wetness sensor.
IP, hostname and SNMP configuration Copied
-
Connect the serial cable to a serial port or converter and connect the power to the device
-
Launch a terminal emulator like Minicom or HyperTerminal
-
Connect to the device with the following settings:
- BPS: 9600
- Data Bits: 8
- Parity: None
- Stop Bits: 1
- Flow Control: None
Use the keyboard to configure IP Address (A), Hostname (B), SNMP Community and Temperature Units (C). Make sure to set “Temperature Units” to your desired measurement system, since this will be used for thresholds and graphing. If you need more help, please consult the product manual found on the Sensatronics website.
You should now be able to ping the device and access the internal web server.
Service configuration in OP5 Monitor Copied
Add the device as a new host in Monitor. The following services will use the check_em1 which is included with op5 Monitor.
Temperature Copied
Create a new service and give it an apt description, in this example we will use “Temperature sensor - Server room”. The pre-configured check command check_em1_temperature needs three arguments:
| $ARG1$ | $ARG2$ | $ARG3$ |
|---|---|---|
| Environment zone - In this example we use zone number 3, so the first argument should simply be “3” | Warning threshold - In this example we will use 26 degrees Celsius, therefore the second argument should be “26” | Critical threshold - In this example we will use 30 degrees Celsius, therefore the third argument should be “30” |
This configuration looks something like this in the configuration dialog:
Submit and save the configuration. When the first service check has been run you should hopefully see something like this on the status detail page:
Humidity Copied
Create a new service and give it an apt description, in this example we will use “Humidity sensor - Server room”. The pre-configured check command check_em1_humidity needs three arguments:
| $ARG1$ | $ARG2$ | $ARG3$ |
|---|---|---|
| Environment zone - In this example we use zone number 3, so the first argument should simply be “3” | Warning threshold - In this example we will use 52% humidity, therefore the second argument should be “52” | Critical threshold - In this example we will use 60% humidity, therefore the third argument should be “60” |
This configuration looks something like this in the configuration dialog:
Submit and save the configuration. When the first service check has been run you should hopefully see something like this on the status detail page:
Wetness Copied
Create a new service and give it an apt description, in this example we will use “Wetness sensor - Server room”. The pre-configured check command check_em1_wetness needs three arguments:
| $ARG1$ | $ARG2$ | $ARG3$ |
|---|---|---|
| Environment zone - In this example we use zone number 3, so the first argument should simply be “3” | Warning threshold - In this example we will use 25 Senturion, therefore the second argument should be “25” | Critical threshold - In this example we will use 30 Senturion, therefore the third argument should be “30” |
This configuration looks something like this in the configuration dialog:
Submit and save the configuration.
Note on thresholds Copied
In the examples above we configure upper warning and critical thresholds, but double valued thresholds can also be used. If you were to configure the warning threshold to be 10:40 and the critical threshold to be -5:66 the plugin will change status accordingly if the values were to go outside the defined limits.
Graphing Copied
The check_em1 plugin also generates performance data which can be used for graphing - here is an example from one of our server rooms:
