This maintenance release addresses Issue #25 and includes reliability fixes found during the post-v2.2.4 audit.
Issue #25 — UniFi SNMP Temperature and Topology
- Added one automatic retry to all SNMP v2c and v3 requests.
- Keeps the last successful SNMP temperature for up to 60 minutes when sensor polling temporarily fails, marks it as
last known, and does not write retained values as new history points. - Builds the UniFi infrastructure topology from controller-reported uplink relationships: gateway → switch → access point.
- Refreshes UniFi device details approximately every five minutes and reuses the in-memory details between refreshes.
- Merges matching UniFi and SNMP devices by MAC address, IP address or alias, and unique device name.
- Suppresses manual topology links that duplicate an automatically discovered relationship.
Additional Reliability Fixes
- Enables TLS 1.2 before Windows agent download, reinstall, and repair commands.
- Keeps Linux package-update status unavailable when a package-manager command fails instead of reporting a false zero.
- Calculates Docker host memory usage from the host's
MemTotalinstead of container memory limits. - Corrects UCD-SNMP CPU utilization by using the canonical non-overlapping raw counters.
- Uses a safe default history size when an invalid history-point request is received.
- Expands regression coverage for PBS datastore ACL errors, Dockhand multi-environment collection, Docker memory accounting, Synology/UCD CPU data, Windows TLS bootstrapping, and Issue #25.
Validation
- Full OmniSight smoke suite passed.
npm audit --omit=dev --audit-level=highreports 0 vulnerabilities.- The UniFi topology and SNMP device deduplication were visually verified in the demo UI.