Details
-
Add New Device / OS
-
Resolution: Fixed
-
Minor
-
None
-
None
-
None
Description
Kentix MultiSensor-LAN devices (first generation, firmware 5.6x) are detected as
Digi Connect devices (digios), because they report the sysObjectID and sysDescr of
their embedded Digi module (.1.3.6.1.4.1.332.11.6, "Digi Connect Device, Version
Unknown"). The Kentix enterprise tree (KMX-LAN, .1.3.6.1.4.1.37954.2) is therefore
not polled. The Kentix AlarmManager (firmware 06.25.02, sysObjectID
.1.3.6.1.4.1.37954.5) is detected as a generic device, although it exposes the
values of all connected sensors via KENTIXDEVICES.
The attached patch adds two OS definitions and the MIB definitions (the MIBs are
already in mibs/kentix):
- kentix-multisensor: Digi sysObjectID plus KMX-LAN::temperatureValue.0 (same
approach as tsl-mdu12), so other Digi based devices are not affected - kentix-alarmmanager: sysObjectID .1.3.6.1.4.1.37954.5 plus sysDescr, hardware
and version from sysDescr
Sensors and statuses:
- MultiSensor-LAN: temperature, humidity and dew point (factor 0.1), temperature
and humidity thresholds taken from the device - AlarmManager: temperature, humidity and dew point for every connected sensor,
named by sensorName, thresholds taken from the device; alarm state per
measurement (temperature, humidity, dew point, CO, motion, vibration) and the
communication state of each sensor
Tested on Observium Professional 26.10 (r15351) with 28 MultiSensor-LAN and one
AlarmManager with 41 sensors:
- all devices detected, values match the AlarmManager web UI
- a temperature max lowered on the device (30 -> 20 C) is taken over at discovery,
the sensor goes to alert on both paths (direct and via the AlarmManager) - AlarmManager tempAlarm went 0 -> 1 -> 0, shown as alarm / ok
- poller time about 1.1 s per MultiSensor-LAN and 5.5 s for the AlarmManager
(123 sensors, 285 statuses)
Notes:
- The KMX-LAN alarm objects (temperatureAlarm etc.) are not used: on a
MultiSensor-LAN managed by an AlarmManager, temperatureAlarm.0 stayed 0 while the
value exceeded temperatureMax.0 and the AlarmManager raised the alarm. A
standalone MultiSensor-LAN is untested. Threshold alerting is covered by the
sensor limits. - The KENTIXDEVICES revision shipped with Observium (2017) lacks several objects
exposed by firmware 06.25; the patch only uses objects defined in it. - sensorName values with non-ASCII characters (UTF-8) are shown as hex string.
- Values are scaled with a fixed factor of 0.1; the device also exposes
multiplierTemperature/Humidity/Dewpoint (default 10). - Current generation Kentix MultiSensors (firmware 06.x) offer no SNMP in our
setup; their values are available via the AlarmManager.
Attached: patch, snmpwalk of a MultiSensor-LAN (firmware 5.63), snmpwalk of the
AlarmManager (firmware 06.25.02) with sensor names, IPs and MACs anonymized.
Related: OBS-5068
Attachments
Issue Links
- mentions
-
OBS-5068 Cant Retrive Data from Sensors (Kentix)
-
- Resolved
-