Didactum Monitoring & Kaseya Network Monitor Integration

Complete step-by-step guide for integrating Didactum monitoring devices and sensors into Kaseya Network Monitor (KNM) and Kaseya VSA via SNMP – including asset creation, MIB browser, SNMP monitor for all sensor types, SNMP trap monitor, SNMP profile in VSA 10, and email alerting.

Product note: Kaseya offers two relevant products for SNMP monitoring. Kaseya Network Monitor (KNM) is the dedicated network monitoring solution with extensive SNMP functions. Kaseya VSA (Virtual System Administrator) also includes integrated SNMP monitoring starting with version 9.5. This guide covers both variants. Where the configuration differs, this is clearly indicated.

• Software: Kaseya Network Monitor (KNM) 4.x / Kaseya VSA 9.x / VSA 10
• Protocol: SNMP v1 / v2c / v3
• Devices: Didactum Monitoring System 100T / 300T / 500T / 550T
• Sensors: Temperature, leak, humidity, door contact, smoke

1. Requirements & System Overview

Kaseya server

• Kaseya Network Monitor (KNM) installed and started
• KNM web interface accessible: <server>
• Or: Kaseya VSA with the Network Monitor module enabled
• UDP port 161 open outbound for SNMP polling
• UDP port 162 open inbound for SNMP traps
• Network access to the Didactum device

Didactum device

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

Architecture & data flow

[Kaseya Network Monitor / VSA]    [Didactum Monitoring System]
  IP: 192.168.1.10                  IP: 192.168.1.50
  KNM web interface port 8080
  VSA web interface port 443
                    --SNMP Polling UDP 161-->
                    <--SNMP Traps  UDP 162--

2. Enable SNMP on the Didactum device

Step 1 – Open web interface

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

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_kaseya (do not use "public"!)
SNMP port	161
Trap receiver IP	192.168.1.10 (IP of the Kaseya server)
Trap port	162
Trap version	v2c

SNMPv3 settings (optional)

Field	Value
Security name	kaseya_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 in advance:

snmpwalk -v 2c -c didactum_kaseya 192.168.1.50 .1.3.6.1.4.1.46501.5.1.1

3. Import MIB file (KNM MIB Browser)

Kaseya Network Monitor uses compiled MIBs to resolve OID names automatically. In the SNMP Monitor and SNMP Trap Monitor, the MIB database can be searched via the MIB Browser button.

Step 1 – Download MIB from the Didactum web interface

System settings → SNMP → "Download MIB file" → didactum.mib

Step 2 – Import MIB into KNM

KNM web interface → Administration → MIB Management
→ click "Upload MIB"
→ select file didactum.mib → Upload
→ click "Compile MIBs"
→ check for success message

Step 3 – Import MIB into VSA (VSA 9.x)

VSA → Network Monitor → MIB Manager
→ click "Import MIB"
→ upload didactum.mib → Import

Step 4 – Test MIB import (KNM)

KNM → Monitor creation → SNMP Monitor → OID field
→ click MIB Browser button ([...])
→ connect asset: 192.168.1.50
→ navigate the MIB hierarchy:
   enterprises → 46501 → Sensor table
→ OID values appear with plain-text names

4. Create asset in Kaseya Network Monitor (KNM)

Step 1 – Create asset node

KNM web interface → Node Tree (left panel)
→ right-click desired folder → "Add Node" → "Network Asset"

Field	Value
Node name	Didactum-Monitor-01
IP address	192.168.1.50
Description	Didactum Monitoring System 01 – server room

Step 2 – Store SNMP credentials on the asset

The community name, SNMP version, and port that Kaseya Network Monitor uses to connect to an SNMP asset are configured in the Authentication tab of the asset node.

Asset "Didactum-Monitor-01" → tab "Authentication"

Field	Value
SNMP community	didactum_kaseya
SNMP version	SNMPv2c
SNMP port	161
Timeout (sec)	5
Retries	3

For SNMPv3 additionally:

Field	Value
SNMP version	SNMPv3
Username	kaseya_user
Auth protocol	SHA
Auth password	your auth password
Privacy protocol	AES
Privacy password	your priv password

Click Save.

Step 3 – Organize asset into a group

Node Tree → right-click folder → "Add Group Node"
  Group name: Didactum Monitoring Systems
→ drag & drop Didactum-Monitor-01 into the group

5. Create SNMP monitor for Didactum sensors (KNM)

The SNMP Monitor is a dynamic tool to query multiple OIDs from an SNMP agent and perform calculations on the returned values. Both named OIDs and numeric OIDs can be used.

Navigation

Asset "Didactum-Monitor-01" → right-click → "Add Monitor" → "SNMP Monitor"

SNMP monitor: temperature sensor

Tab "General":

Field	Value
Monitor name	Didactum Temperature Sensor 01
Description	Room temperature – raw value ÷ 10 = degrees Celsius
Schedule / interval	5 minutes

Tab "Monitor" – OID configuration:

→ click "Add OID"

Field	Value
OID1	.1.3.6.1.4.1.46501.5.1.1.7.101001
Calculation	{OID1} / 10 (gives degrees Celsius directly)
Value type	Numeric
Compare operation	Over
Alarm threshold	28 (= 28.0 °C – after division by 10)
Warning threshold	25 (= 25.0 °C)
Alarm message	Temperature exceeds threshold: ${value} degrees C

Important – temperature calculation:

The calculation formula allows calculations on the queried OID values. Since Didactum outputs temperature values as raw value × 10, enter {OID1} / 10 in the calculation formula. The threshold is then entered directly in Celsius (28 instead of 280).

SNMP monitor: leak sensor

Field	Value
Monitor name	Didactum Leak Sensor 01
Schedule / interval	2 minutes
OID1	.1.3.6.1.4.1.46501.5.1.1.7.107001
Calculation	{OID1} (no divisor)
Value type	Numeric
Compare operation	Over
Alarm threshold	0 (value > 0 = water detected = alarm)
Alarm message	LEAK ALARM: Water detected! Sensor value: ${value}

SNMP monitor: temperature sensor status

Field	Value
Monitor name	Didactum Temp Status Sensor 01
OID1	.1.3.6.1.4.1.46501.5.1.1.6.101001
Compare operation	Over
Alarm threshold	0 (status > 0 = alarm or no signal)
Result translation	0 = OK / 1 = Alarm / 2 = No signal
Alarm message	Temp status alarm: ${value} (0=OK, 1=Alarm, 2=no signal)

SNMP monitor: humidity

Field	Value
Monitor name	Didactum Humidity Sensor 01
OID1	.1.3.6.1.4.1.46501.5.1.1.7.102001
Calculation	{OID1}
Compare operation	Over
Warning threshold	80
Alarm threshold	90
Alarm message	Humidity: ${value}% (limit: 90%)

SNMP monitor: door contact

Field	Value
Monitor name	Didactum Door Contact 01
Schedule / interval	1 minute
OID1	.1.3.6.1.4.1.46501.5.1.1.7.104001
Compare operation	Over
Warning threshold	0 (value > 0 = door open)
Alarm message	Door contact: door open! Value: ${value}

SNMP monitor: smoke detector

Field	Value
Monitor name	Didactum Smoke Detector 01
Schedule / interval	1 minute
OID1	.1.3.6.1.4.1.46501.5.1.1.7.106001
Compare operation	Over
Alarm threshold	0 (value > 0 = smoke detected)
Alarm message	SMOKE DETECTOR ALARM: Smoke detected! Value: ${value}

6. Configure SNMP Trap Monitor (KNM)

The SNMP Trap Monitor receives trap messages from SNMP agents on remote hosts. The monitor only receives messages originating from the asset’s IP address. The first filter step is performed using the specified enterprise OIDs.

Step 1 – Create SNMP Trap Monitor

Asset "Didactum-Monitor-01" → right-click → "Add Monitor" → "SNMP Trap Monitor"

Field	Value
Monitor name	Didactum SNMP Trap Receiver
Description	Receives all SNMP traps from the Didactum device

Step 2 – Configure enterprise OID filter

OID include filter: enter one or more OIDs separated by commas. The monitor triggers an alarm for the specified enterprise OID.

Field	Value
OID include filter	.1.3.6.1.4.1.46501 (Didactum enterprise OID for older devices)
Community	didactum_kaseya
Include all variables	Check the box (show all varbinds in the alarm)
Match option	At least one (one OID must match)

Step 3 – Variable binding filter for individual sensors

Further inspection of the trap is done with the Variable Binding Filter, which can contain multiple rules. The rules are evaluated either together (AND) or individually (OR).

Rule	OID	Match value	Operation
Leak trap	.1.3.6.1.4.1.46501.5.1.1.7.107001	1	Equal
Temperature alarm trap	.1.3.6.1.4.1.46501.5.1.1.6.101001	1	Equal
Smoke detector trap	.1.3.6.1.4.1.46501.5.1.1.7.106001	1	Equal
Door contact trap	.1.3.6.1.4.1.46501.5.1.1.7.104001	1	Equal

Set Match option to At least one (OR link). Click Save.

7. Configure SNMP monitoring in Kaseya VSA

Kaseya VSA enables SNMP monitoring for network devices. When an alert is triggered, VSA can automatically create an alarm, create a ticket, and/or send an email notification.

Step 1 – Add device to VSA Network Monitor

VSA → Network Monitor → Topology
→ "Scan" → IP range: 192.168.1.50
→ Community: didactum_kaseya
→ start scan
→ Didactum device appears in the result list
→ check it → click "Add to Monitor"

Step 2 – Enable SNMP monitoring on the device (VSA 9.x)

VSA → Network Monitor → SNMP → SNMP Set
→ click "Add"

Field	Value
SNMP set name	Didactum Sensors
Description	SNMP monitoring for Didactum Monitoring System

Step 3 – Add SNMP variables to the set

SNMP instance: The last part of an OID can be represented as a table rather than a single value. Enter 0 for a single value. For table values, enter a range such as 1-5.

SNMP set "Didactum Sensors" → click "Add SNMP Object"

Field	Value (temperature sensor)
MIB object (OID)	.1.3.6.1.4.1.46501.5.1.1.7.101001
SNMP instance	0 (single value)
Object name	Didactum Temperature (raw value)
Alarm operator	Over
Alarm threshold	280 (= 28 °C × 10 – raw value!)

Add further objects using the same pattern:

Sensor	OID	Alarm operator	Threshold
Leak	.1.3.6.1.4.1.46501.5.1.1.7.107001	Over	0
Temp status	.1.3.6.1.4.1.46501.5.1.1.6.101001	Over	0
Humidity	.1.3.6.1.4.1.46501.5.1.1.7.102001	Over	80
Door contact	.1.3.6.1.4.1.46501.5.1.1.7.104001	Over	0
Smoke detector	.1.3.6.1.4.1.46501.5.1.1.7.106001	Over	0

Important for VSA (no calculation formula):

Unlike KNM, VSA does not have a built-in calculation function for OID values. Temperature thresholds must therefore be entered as raw value × 10 (28 °C = 280).

Step 4 – Assign SNMP set to the device

VSA → Network Monitor → SNMP → Assign SNMP
→ select device: didactum-monitor-01
→ select SNMP Set: "Didactum Sensors" → "Apply"

8. Create SNMP profile in VSA 10

SNMP Variables is the area in VSA 10 where the object identifiers (OIDs) to be monitored are defined. In VSA 10, SNMP settings are defined as a profile, which is then applied to devices through policies.

Step 1 – Create SNMP profile

VSA 10 → Administration → Configuration → Profiles → SNMP
→ click "Create Profile"
  Profile name:  Didactum Monitoring Profile
  Description:   Didactum Environmental Sensor Monitoring
→ Save

Step 2 – Add SNMP variables to the profile

Profile "Didactum Monitoring Profile" → tab "SNMP Variables"
→ click "Add Variable"

Field	Value (temperature sensor)
Variable name	didactum_temperature
OID	.1.3.6.1.4.1.46501.5.1.1.7.101001
Display name	Didactum Temperature Sensor 01
Unit	0.1 degree C (raw value)
Threshold high	280 (= 28.0 °C – raw value × 10)
Threshold critical	350 (= 35.0 °C)

Repeat for all other sensors. Then:

VSA 10 → Administration → Configuration → Policies
→ "Create Policy" → assign profile "Didactum Monitoring Profile"
→ Scope: device group "Didactum Monitoring"
→ enable policy → Apply

9. Alerting & notifications

Configure alerting in KNM

Asset "Didactum-Monitor-01" → select monitor → tab "Actions"
→ click "Add Action"

Field	Value
Action type	Send E-mail
To address	admin@ihredomain.de
Subject	[KNM Didactum ALARM] ${node} – ${monitor}
Message	Time: ${time}\nDevice: ${node} (${ip})\nMonitor: ${monitor}\nStatus: ${status}\nMessage: ${message}
Trigger on	Alarm, Warning, Recovery

Configure SMTP settings in KNM

KNM → Administration → Settings → E-Mail Settings
  SMTP server:     mail.ihredomain.de
  SMTP port:       587
  Use TLS:         Yes
  From address:    knm@ihredomain.de
  Auth username:   knm@ihredomain.de
  Auth password:   your password
→ click "Send Test E-Mail" → check inbox

Configure alerting in VSA

VSA → Monitor → Alerts → SNMP Alert
→ click "Add"
  Alert name:    Didactum SNMP Alarm
  SNMP Set:      Didactum Sensors
  Email:         admin@ihredomain.de
  Create alarm:  Yes
  Create ticket: Yes (optional)
→ assign device → Save

10. 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	Measured value (current)	.1.3.6.1.4.1.46501.5.1.1.7.101001

Sensor types with OIDs and Kaseya thresholds

Sensor type	Sensor ID	OID measured value	KNM calculation	Alarm threshold
Temperature sensor (digital)	101001	.1.3.6.1.4.1.46501.5.1.1.7.101001	{OID1} / 10	28 (°C after division)
Temperature sensor (analog)	201001	.1.3.6.1.4.1.39052.5.2.1.7.201001	{OID1} / 10	28 (°C after division)
Water sensor / leak	107001	.1.3.6.1.4.1.46501.5.1.1.7.107001	{OID1}	Over 0 (1=water)
Sensor status	any	.1.3.6.1.4.1.46501.5.1.1.6.SENSOR_ID	{OID1}	Over 0 (1=alarm)
Humidity	102001	.1.3.6.1.4.1.46501.5.1.1.7.102001	{OID1}	80 (warning) / 90 (alarm)
Dry contact	101003	.1.3.6.1.4.1.39052.5.1.1.7.101003	{OID1}	Over 0 (1=closed)
Door contact	104001	.1.3.6.1.4.1.46501.5.1.1.7.104001	{OID1}	Over 0 (1=open)
Smoke detector	106001	.1.3.6.1.4.1.46501.5.1.1.7.106001	{OID1}	Over 0 (1=alarm)

Find sensor ID:

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

KNM vs. VSA – temperature thresholds:

In KNM, use the calculation formula {OID1} / 10, then enter the threshold in Celsius (28). In VSA without a calculation function, enter thresholds as raw value × 10 (280).

MIB prefix per model:

Older devices use .1.3.6.1.4.1.46501; newer models may use .1.3.6.1.4.1.39052. Take the exact OIDs from the MIB file of your device.

11. Test & troubleshooting

Test SNMP connection with MIB Browser (KNM)

Create monitor → OID field → click MIB Browser button ([...])
→ connect asset: 192.168.1.50
→ navigate to the Didactum OID in the MIB hierarchy
→ click "Get" → display current sensor value

Check monitor status in KNM

KNM → Node Tree → Didactum-Monitor-01 → monitor list
→ traffic light icon shows current status:
  Green = OK
  Yellow = Warning
  Red = Alarm
→ click monitor → details and last measured value

Error messages and solutions

Problem	Cause & solution
Monitor shows "SNMP Timeout"	Wrong community string; UDP 161 blocked; SNMP not enabled on Didactum → check
Temperature value appears 10x too high (VSA)	VSA has no calculation formula → enter threshold × 10 (28°C = 280)
Leak alarm does not trigger	Alarm operator wrong → "Over" with threshold 0 (not "Equal 1")
MIB Browser shows no Didactum OIDs	MIB not imported → Administration → MIB Management → import didactum.mib
Trap does not arrive	Trap receiver IP wrong in Didactum; UDP 162 blocked; enterprise OID in filter wrong
No email on alarm	Check SMTP settings; action not configured on monitor; send test email
Asset does not appear in VSA topology	Network scan not run yet; device not pingable; community wrong

View KNM logs

KNM → Administration → Logs → Event Log
→ filter: Node = Didactum-Monitor-01
→ all status changes and alarms are logged

KNM → Administration → Logs → SNMP Trap Log
→ all incoming traps are listed here

12. Final checklist

Didactum device

• SNMP enabled (v2c or v3)
• Community string set (not "public"): didactum_kaseya
• Device reachable by ping from the Kaseya server
• Trap receiver IP set to the Kaseya server
• MIB file downloaded

Kaseya Network Monitor (KNM)

• MIB file imported and compiled
• Asset Didactum-Monitor-01 created (IP, SNMP community in the Auth tab)
• SNMP monitor for temperature sensor created with calculation {OID1}/10
• SNMP monitor for leak created (Over 0)
• SNMP monitor for humidity, door contact, smoke detector created
• SNMP Trap Monitor created with enterprise OID .1.3.6.1.4.1.46501
• Actions (email) configured for all monitors
• SMTP settings configured, test email received

Kaseya VSA

• Device added to VSA by network scan
• SNMP set “Didactum Sensors” created (VSA 9.x)
• All OIDs with thresholds entered (raw value × 10 for temperature)
• SNMP set assigned to the device
• Alternatively: VSA 10 SNMP profile and policy created
• Alert rule configured with email notification
• Test alert triggered and email received