Didactum Monitoring & LiveAction LiveNX Integration

Complete step-by-step guide for integrating Didactum monitoring devices and sensors into LiveAction LiveNX via SNMP — including device discovery, SNMP credential store, OID polling, custom metric definition file (YAML), alert configuration, and email notification.

Product note: LiveAction is primarily focused on network performance monitoring (NPM) for routers, switches, and flow data. For environmental sensors such as Didactum devices, two integration approaches are relevant: OID polling (LiveNX 23.x — query custom SNMP OIDs and set alarms on them) and custom metric definition files (LiveNX 25.x — file-based configuration to adapt the OIDs to be polled per vendor and model without requiring a LiveNX upgrade). This guide covers both variants.

Software: LiveAction LiveNX 23.x / 25.x
Protocol: SNMP v1 / v2c / v3
Devices: Didactum Monitoring System 100T / 300T / 500T / 550T
Sensors: Temperature, leak, humidity, door contact, smoke

1. Prerequisites & system overview

LiveNX server

LiveAction LiveNX installed (on-premises appliance or VM)
LiveNX web interface reachable: <server-IP>
LiveNX node configured (processes SNMP data)
UDP port 161 open outbound for SNMP polling
UDP port 162 open inbound for SNMP traps (optional)
Network access to the Didactum device

Didactum device

Monitoring System 100T, 300T, 500T, or 550T
SNMP enabled (v2c recommended)
Device reachable by ICMP from the LiveNX server
MIB file available in the web interface

Architecture & data flow

[LiveNX Server]                      [Didactum Monitoring System]
  IP: 192.168.1.10                     IP: 192.168.1.50
  Web interface: 192.168.1.10
  LiveNX Node (Collector)
                    --SNMP polling UDP 161 (every 5 min.)-->
                    <-- SNMP traps UDP 162 (optional) -----

LiveNX architecture

LiveNX consists of several components:

LiveNX Server: Central management and analysis component
LiveNX Node: Local collector, performs SNMP polling (there can be several)
LiveNA: AI-supported network analysis (optional, builds on LiveNX)
Operations Dashboard: Real-time overview and alert management

2. Enable SNMP on the Didactum device

Step 1 – Open web interface

Open in browser: 192.168.1.50 (adjust the Didactum device IP accordingly)

Step 2 – Open SNMP settings

System settings → SNMP

Step 3 – Enter the following values

Field in the Didactum web interface	Value
Enable SNMP	Enabled
SNMP version	v2c (recommended)
Community string	didactum_livenx (do not use “public”!)
SNMP port	161
Trap receiver IP	192.168.1.10 (LiveNX server IP)
Trap port	162
Trap version	v2c

SNMPv3 settings (optional)

Field	Value
Security name	livenx_user
Auth protocol	SHA
Auth password	at least 8 characters
Priv protocol	AES
Priv password	at least 8 characters
Security level	authPriv

Save the settings. Test the SNMP connection from the LiveNX server beforehand:

snmpwalk -v 2c -c didactum_livenx 192.168.1.50 .1.3.6.1.4.1.46501.5.1.1

3. Configure SNMP credential store

The default SNMP credentials can be managed through the SNMP Credential Store Configuration Page. These credentials are used automatically during discovery and polling for matching devices.

Navigation

LiveNX web interface → Settings → Device Settings → SNMP Credentials
→ open "SNMP Credential Store Configuration Page"

Create a new credential entry

Field	Value (SNMPv2c)
Credential name	Didactum SNMPv2c
SNMP version	v2c
Read community	didactum_livenx
Write community	empty (read-only access only)
SNMP port	161
Timeout (sec)	5
Retries	3

Click Save.

Create SNMPv3 credential (if used)

Field	Value
Credential name	Didactum SNMPv3
SNMP version	v3
Security name	livenx_user
Auth protocol	SHA
Auth password	your auth password
Privacy protocol	AES
Privacy password	your priv password
Security level	authPriv

4. Add Didactum device to LiveNX (Discover Devices)

To add an SNMP-monitored device in LiveNX, select the Discover Devices button. Devices can be added either by specifying an IP address or IP range, or by discovery via seed device and hop count.

Step 1 – Start Discover Devices

LiveNX → Settings → Monitored Devices → SNMP Monitored Devices
→ click "Discover Devices" button

Step 2 – Fill in the “What to Scan” tab

Field	Value
Scan type	IP Address (single device)
IP address	192.168.1.50

Click Save & Next.

Step 3 – Fill in the “SNMP Configuration” tab

Field	Value
SNMP credentials	Didactum SNMPv2c (from credential store)
SNMP version	v2c
Community string	didactum_livenx
SNMP port	161

Click Save & Next.

Step 4 – Select LiveNX node

Select the LiveNX node that should monitor the Didactum device (usually the node in the same network segment).

Click Discover. A progress bar appears.

Step 5 – Configure monitoring options for the device

These checkboxes define which technologies LiveNX uses for monitoring the device: Poll (master switch for SNMP polling), IP SLA, QoS, routing, and flow.

Monitored Devices → select device "192.168.1.50" → click "Edit"

Option	Setting for Didactum
Poll (SNMP)	✅ Enabled (required)
IP SLA	❌ Disabled (not relevant)
QoS	❌ Disabled (not relevant)
Routing	❌ Disabled (not relevant)
Flow	❌ Disabled (Didactum does not send flow)

Click Save.

5. OID polling for Didactum sensors (LiveNX 23.x)

OID polling makes it possible to monitor SNMP KPIs and set alerts on them that are not monitored by LiveNX by default. This is the primary method for Didactum sensors in LiveNX 23.x.

Navigation

LiveNX → Alerts → Alert Management → OID Polling
→ click "Add OID"

OID polling: temperature sensor

Field	Value
Name	Didactum Temperature Sensor 01
Description	Room temperature – raw value ÷ 10 = degrees Celsius
Device	192.168.1.50 (select Didactum device)
OID	.1.3.6.1.4.1.46501.5.1.1.7.101001
Poll interval	300 seconds (5 minutes)
Units	0.1 degrees C (raw value)
Warning threshold high	280 (= 28.0 °C – raw value × 10)
Critical threshold high	350 (= 35.0 °C – raw value × 10)

Important – temperature thresholds:

LiveNX compares the raw OID value directly. Because Didactum transmits temperatures as raw value × 10, all thresholds must also be entered × 10. 28.0 °C = threshold 280.

OID polling: leak sensor

Field	Value
Name	Didactum Leak Sensor 01
Device	192.168.1.50
OID	.1.3.6.1.4.1.46501.5.1.1.7.107001
Poll interval	120 seconds (2 minutes)
Critical threshold high	0.5 (from value 1 = water = critical)

OID polling: temperature sensor status

Field	Value
Name	Didactum Temp-Status Sensor 01
OID	.1.3.6.1.4.1.46501.5.1.1.6.101001
Critical threshold high	0.5 (status > 0 = alarm or no signal)

OID polling: humidity

Field	Value
Name	Didactum Humidity Sensor 01
OID	.1.3.6.1.4.1.46501.5.1.1.7.102001
Poll interval	300 seconds
Warning threshold high	80
Critical threshold high	90

OID polling: door contact

Field	Value
Name	Didactum Door Contact 01
OID	.1.3.6.1.4.1.46501.5.1.1.7.104001
Poll interval	60 seconds
Warning threshold high	0.5 (from value 1 = door open)

OID polling: smoke detector

Field	Value
Name	Didactum Smoke Detector 01
OID	.1.3.6.1.4.1.46501.5.1.1.7.106001
Poll interval	60 seconds
Critical threshold high	0.5 (from value 1 = alarm)

6. Custom metric definition file (LiveNX 25.x)

LiveNX 25.x includes a responsive SNMP data collector that loads file-based configurations to adapt the OIDs to be polled by vendor, model, or even specific device. Support for additional vendors and models can be added through additional metric definition files without needing to upgrade LiveNX.

Step 1 – Create metric definition file

Save as didactum-metrics.yaml and place it in the metric definitions directory on the LiveNX server:

# ================================================================
# LiveNX custom metric definition file for Didactum Monitoring System
# File name: didactum-metrics.yaml
# Location: /opt/livenx/config/metric-definitions/
# (adjust path depending on LiveNX installation)
# ================================================================
vendor: Didactum
description: Didactum Environmental Monitoring System

# Device detection via sysObjectID
device_types:
  - name: DidactumMonitoringOld
    sys_object_id: ".1.3.6.1.4.1.46501"
    description: "Didactum Monitoring System (older firmware)"
  - name: DidactumMonitoringNew
    sys_object_id: ".1.3.6.1.4.1.39052"
    description: "Didactum Monitoring System (newer firmware)"

# Metric definitions
metrics:

  # ----------------------------------------------------------
  # Temperature sensor (digital, sensor ID 101001)
  # Raw value: OID value ÷ 10 = degrees Celsius
  # Example: OID value 235 = 23.5 degrees Celsius
  # ----------------------------------------------------------
  - name: didactum_temperature_sensor_01
    display_name: "Temperature Sensor 01"
    description: "Room temperature – raw value divided by 10 gives degrees Celsius"
    oid: ".1.3.6.1.4.1.46501.5.1.1.7.101001"
    unit: "0.1 degrees C"
    scale_factor: 0.1
    type: gauge
    thresholds:
      warning_high: 28.0    # 28.0 degrees C (after scaling)
      critical_high: 35.0   # 35.0 degrees C (after scaling)
      warning_low: 5.0
      critical_low: 2.0
    poll_interval: 300
  # ----------------------------------------------------------
  # Temperature sensor status
  # 0 = OK, 1 = Alarm, 2 = No signal
  # ----------------------------------------------------------
  - name: didactum_temperature_status_01
    display_name: "Temperature Sensor 01 – Status"
    description: "Sensor status: 0=OK, 1=Alarm, 2=No signal"
    oid: ".1.3.6.1.4.1.46501.5.1.1.6.101001"
    unit: ""
    type: gauge
    thresholds:
      critical_high: 0.5    # value > 0 = problem
    poll_interval: 300

  # ----------------------------------------------------------
  # Leak sensor (sensor ID 107001)
  # 0 = dry = OK, 1 = water detected = CRITICAL
  # ----------------------------------------------------------
  - name: didactum_leakage_sensor_01
    display_name: "Leak Sensor 01"
    description: "Water sensor: 0=dry, 1=water detected"
    oid: ".1.3.6.1.4.1.46501.5.1.1.7.107001"
    unit: ""
    type: gauge
    thresholds:
      critical_high: 0.5    # value >= 1 = water = immediately critical
    poll_interval: 120

  # ----------------------------------------------------------
  # Humidity (sensor ID 102001)
  # Direct value in percent – no divisor
  # ----------------------------------------------------------
  - name: didactum_humidity_sensor_01
    display_name: "Humidity Sensor 01"
    description: "Relative humidity in percent"
    oid: ".1.3.6.1.4.1.46501.5.1.1.7.102001"
    unit: "%"
    type: gauge
    thresholds:
      warning_high: 80
      critical_high: 90
      warning_low: 20
      critical_low: 10
    poll_interval: 300

  # ----------------------------------------------------------
  # Door contact (sensor ID 104001)
  # 0 = closed = OK, 1 = open = WARNING
  # ----------------------------------------------------------
  - name: didactum_door_sensor_01
    display_name: "Door Contact 01"
    description: "Door contact: 0=closed, 1=open"
    oid: ".1.3.6.1.4.1.46501.5.1.1.7.104001"
    unit: ""
    type: gauge
    thresholds:
      warning_high: 0.5     # value >= 1 = door open = warning
    poll_interval: 60

  # ----------------------------------------------------------
  # Smoke detector (sensor ID 106001)
  # 0 = no smoke = OK, 1 = alarm = CRITICAL
  # ----------------------------------------------------------
  - name: didactum_smoke_sensor_01
    display_name: "Smoke Detector 01"
    description: "Smoke detector: 0=OK, 1=alarm"
    oid: ".1.3.6.1.4.1.46501.5.1.1.7.106001"
    unit: ""
    type: gauge
    thresholds:
      critical_high: 0.5    # value >= 1 = smoke = immediately critical
    poll_interval: 60

  # ----------------------------------------------------------
  # Analog temperature sensor (newer models, OID .39052)
  # ----------------------------------------------------------
  - name: didactum_temp_analog_sensor_01
    display_name: "Temp Analog Sensor 01 (newer models)"
    description: "Analog temperature sensor – raw value ÷ 10 = degrees C"
    oid: ".1.3.6.1.4.1.39052.5.2.1.7.201001"
    unit: "0.1 degrees C"
    scale_factor: 0.1
    type: gauge
    thresholds:
      warning_high: 28.0
      critical_high: 35.0
    poll_interval: 300

Step 2 – Provide metric definition file on the LiveNX server

# Copy via SCP to the LiveNX server:
scp didactum-metrics.yaml admin@192.168.1.10:/opt/livenx/config/metric-definitions/
# Or create directly on the server:
ssh admin@192.168.1.10
sudo nano /opt/livenx/config/metric-definitions/didactum-metrics.yaml
# Paste content → Ctrl+X → save

Step 3 – Load metric definitions in LiveNX

LiveNX web interface → Settings → Device Monitoring → Metric Definitions
→ click "Reload Definitions"
→ Didactum metrics appear in the list

Alternatively restart the LiveNX service:

sudo systemctl restart livenx

Step 4 – Assign metric definitions to the Didactum device

LiveNX → Settings → Monitored Devices → 192.168.1.50
→ "Device Metrics" tab
→ "Add Metric Definition" → select "Didactum Environmental Monitoring System"
→ Save

7. Alert configuration for Didactum sensors

LiveNX associates device events with alerts that are generated when certain criteria such as threshold violations are met and displayed in the Operations Dashboard. With the event-to-alert mapping concept, LiveNX eliminates the common problem of too many alerts.

Step 1 – Configure alert policies for OID polling

LiveNX → Alerts → Alert Management → Alert Policies
→ click "Add Policy"

Field	Value
Policy name	Didactum Sensor Alarms
Description	Alert policy for all Didactum monitoring sensors
Device group / scope	IP: 192.168.1.50 or device group
Alert types	OID threshold, device unreachable
Severity levels	Enable warning and critical
Notifications	Email (configured in section 8)

Step 2 – Configure batch email alerts (LiveNX 25.x)

Batch alerts combine multiple alert events into a single email. The batch configuration applies to all alerts. Email configuration is a prerequisite for this feature.

LiveNX → Settings → Alert Configuration
→ "Batch alerts" toggle: enable
→ Batch interval: 5 minutes (one summary every 5 minutes)
→ Save

Step 3 – Severity levels and event-to-alert mapping

Alerts are categorized into three severity levels. The following mapping is recommended for Didactum sensors:

Didactum sensor / event	Recommended severity
Temperature sensor > 28 °C	Warning
Temperature sensor > 35 °C	Critical
Leak detected (value = 1)	Critical (immediately)
Smoke detector (value = 1)	Critical (immediately)
Door contact open	Warning
Humidity > 80 %	Warning
Humidity > 90 %	Critical
Device unreachable	Critical

8. Configure email notification

Step 1 – Email configuration

LiveNX → Settings → Email Configuration

Field	Value
SMTP server	mail.yourdomain.com
SMTP port	587
Use TLS	Yes (STARTTLS)
From address	livenx@yourdomain.com
Auth username	livenx@yourdomain.com
Auth password	your SMTP password

Click Test Email → check inbox → save.

Step 2 – Define recipients for Didactum alerts

LiveNX → Settings → Alert Configuration → E-mail Recipients
→ click "Add Recipient"
  Email:       admin@yourdomain.com
  Alert types:  OID threshold, device unreachable
  Severity:     Warning, Critical
  Devices:      192.168.1.50 (or all)
→ Save

Step 3 – Adjust email template (optional)

LiveNX → Settings → Email Configuration → Alert E-mail template
  Subject: [LiveNX ALARM] ${device_name}: ${alert_name} – ${severity}
  Body:     Time:      ${alert_time}
            Device:     ${device_name} (${device_ip})
            Alert:      ${alert_name}
            Severity:   ${severity}
            Value:      ${current_value}
            Threshold:  ${threshold}
            Descr.:     ${description}
→ Save

9. SNMP OID reference

All Didactum OIDs begin with .1.3.6.1.4.1.46501 (older firmware) or .1.3.6.1.4.1.39052 (newer models). The sensor ID is appended at the end.

OID fields per sensor

Field	Meaning	Example
.1.x.SENSOR_ID	Sensor ID	.1.3.6.1.4.1.46501.5.1.1.1.101001
.5.x.SENSOR_ID	Sensor name	.1.3.6.1.4.1.46501.5.1.1.5.101001
.6.x.SENSOR_ID	Status (0=OK, 1=Alarm, 2=No signal)	.1.3.6.1.4.1.46501.5.1.1.6.101001
.7.x.SENSOR_ID	Measurement value (current)	.1.3.6.1.4.1.46501.5.1.1.7.101001

Sensor types with OIDs and LiveNX thresholds

Sensor type	Sensor ID	OID measurement value	OID polling threshold	Metric file scale_factor
Temperature sensor (digital)	101001	.1.3.6.1.4.1.46501.5.1.1.7.101001	Warn: 280 / Crit: 350 (raw value × 10)	0.1 → Celsius
Temperature sensor (analog)	201001	.1.3.6.1.4.1.39052.5.2.1.7.201001	Warn: 280 / Crit: 350	0.1 → Celsius
Water sensor / leak	107001	.1.3.6.1.4.1.46501.5.1.1.7.107001	Crit: 0.5 (from 1 = water)	1 (no divisor)
Humidity	102001	.1.3.6.1.4.1.46501.5.1.1.7.102001	Warn: 80 / Crit: 90 (direct %)	1 (no divisor)
Dry contact	101003	.1.3.6.1.4.1.39052.5.1.1.7.101003	Warn: 0.5 (from 1 = active)	1
Door contact	104001	.1.3.6.1.4.1.46501.5.1.1.7.104001	Warn: 0.5 (from 1 = open)	1
Smoke detector	106001	.1.3.6.1.4.1.46501.5.1.1.7.106001	Crit: 0.5 (from 1 = alarm)	1

Find sensor ID:

In the Didactum web interface under System tree → select sensor → details. This ID is appended to the end of the OID.

Temperature thresholds in OID polling (LiveNX 23.x):

Enter raw value × 10 (28 °C = 280, 35 °C = 350). LiveNX compares the OID raw value directly without scaling.

Metric definition file (LiveNX 25.x):

Configure scale_factor: 0.1 — LiveNX automatically divides the raw value by 10. Enter thresholds in real Celsius values then (28.0, 35.0).

MIB prefix per model:

Older devices use .1.3.6.1.4.1.46501, newer ones may use .1.3.6.1.4.1.39052. Refer to your device’s MIB file for the exact OIDs.

10. Test & troubleshooting

Test SNMP connection

# From the LiveNX server:
snmpwalk -v 2c -c didactum_livenx 192.168.1.50 \
    .1.3.6.1.4.1.46501.5.1.1

# Temperature value (raw value ÷ 10 = degrees Celsius)
snmpget -v 2c -c didactum_livenx 192.168.1.50 \
    .1.3.6.1.4.1.46501.5.1.1.7.101001
# Leak status (0=dry, 1=water)
snmpget -v 2c -c didactum_livenx 192.168.1.50 \
    .1.3.6.1.4.1.46501.5.1.1.7.107001

Check OID polling values in LiveNX

LiveNX → Alerts → Alert Management → OID Polling
→ select OID "Didactum Temperature Sensor 01"
→ "Latest Value" shows current raw value
→ "History" shows trend data

Device status in the Operations Dashboard

LiveNX → Operations Dashboard
→ search for device 192.168.1.50
→ status badges show active alerts in red/yellow
→ click device → detail view with all OID values

Error messages and solutions

Problem	Cause & solution
Device marked as “Unreachable” after discovery	Community string incorrect; SNMP not enabled on Didactum; UDP 161 blocked → test with snmpwalk
OID polling returns “No Data”	OID not supported by the device; wrong sensor ID → check snmpwalk and determine the correct OID
Temperature value 10× too high (LiveNX 23.x)	Threshold not × 10 → set threshold to 280 instead of 28
Metric definition file not loaded	YAML syntax error; wrong location; LiveNX service restart required
No email on alarm	Check SMTP settings; send test email; verify alert policy recipients
LiveNX node not connected	Check LiveNX node service; verify node connectivity to the LiveNX server

View LiveNX logs

# LiveNX system log
sudo journalctl -u livenx -f --since "1 hour ago"

# SNMP collector log
tail -f /var/log/livenx/snmp-collector.log

# Alert log
tail -f /var/log/livenx/alerts.log

11. Final checklist

Didactum device

SNMP enabled (v2c or v3)
Community string set (not “public”): didactum_livenx
Device reachable by ping from the LiveNX server
Trap receiver IP set to the LiveNX server (optional)
MIB file downloaded
snmpwalk successful from the LiveNX server

LiveNX configuration

SNMP credential “Didactum SNMPv2c” created in credential store
Didactum device added via Discover Devices
Poll option enabled, IP SLA/QoS/Routing/Flow disabled
UDP 161 outbound, UDP 162 inbound open

OID polling (LiveNX 23.x)

OID for temperature sensor created (threshold × 10: 280 / 350)
OID for leak sensor created (critical: 0.5)
OID for humidity created (80 / 90)
OID for door contact and smoke detector created
Current values visible in the OID polling view

Custom metric definition (LiveNX 25.x)

didactum-metrics.yaml created and provided on server
scale_factor: 0.1 set for temperature sensors
Metric definitions reloaded in LiveNX
Metric assigned to the Didactum device

Alerting & notification

SMTP settings configured, test email received
Alert policy “Didactum Sensor Alarms” created
Recipients configured for Didactum alerts
Batch alert interval set (optional)
Test alert triggered and email received

Didactum Monitoring & LiveAction LiveNX Integration

1. Prerequisites & system overview

LiveNX server

Didactum device

Architecture & data flow

LiveNX architecture

2. Enable SNMP on the Didactum device

Step 1 – Open web interface

Step 2 – Open SNMP settings

Step 3 – Enter the following values

SNMPv3 settings (optional)

3. Configure SNMP credential store

Navigation

Create a new credential entry

Create SNMPv3 credential (if used)

4. Add Didactum device to LiveNX (Discover Devices)

Step 1 – Start Discover Devices

Step 2 – Fill in the “What to Scan” tab

Step 3 – Fill in the “SNMP Configuration” tab

Step 4 – Select LiveNX node

Step 5 – Configure monitoring options for the device

5. OID polling for Didactum sensors (LiveNX 23.x)

Navigation

OID polling: temperature sensor

OID polling: leak sensor

OID polling: temperature sensor status

OID polling: humidity

OID polling: door contact

OID polling: smoke detector

6. Custom metric definition file (LiveNX 25.x)

Step 1 – Create metric definition file

Step 2 – Provide metric definition file on the LiveNX server

Step 3 – Load metric definitions in LiveNX

Step 4 – Assign metric definitions to the Didactum device

7. Alert configuration for Didactum sensors

Step 1 – Configure alert policies for OID polling

Step 2 – Configure batch email alerts (LiveNX 25.x)

Step 3 – Severity levels and event-to-alert mapping

8. Configure email notification

Step 1 – Email configuration

Step 2 – Define recipients for Didactum alerts

Step 3 – Adjust email template (optional)

9. SNMP OID reference

OID fields per sensor

Sensor types with OIDs and LiveNX thresholds

10. Test & troubleshooting

Test SNMP connection

Check OID polling values in LiveNX

Device status in the Operations Dashboard

Error messages and solutions

View LiveNX logs

11. Final checklist

Didactum device

LiveNX configuration

OID polling (LiveNX 23.x)

Custom metric definition (LiveNX 25.x)

Alerting & notification

Related Links

Powered by

Hint

This website uses cookies