Getting Started Cameras & Video Detection & Recording Automation & Events Actions Integration & Connectivity Network & Discovery AI & Remote Control MQTT Modbus Pi4J & Raspberry Pi GPIO ZeroMQ System & Administration Comparisons Use Cases Troubleshooting About & Legal
Home / Documentation / SNMP Set Action
SNMP action

SNMP Set Action

SNMP Set Action writes one typed OID through an SNMP Device so automation uses the same allowlist, read-back and audit path as an operator write.

Authorise the device before the action

Configure and test an SNMP Device, enable writes on that device, and add the narrowest OID prefix required by this action. The action cannot bypass the device write policy.

01

Confirm the OID contract

Verify the target OID, syntax and writable state in the device MIB or vendor documentation.

02

Test a read first

Read the current value through SNMP Device and record the expected safe range or allowed enumeration.

03

Apply a narrow rule

Attach the action only to a specific Event Manager rule or operator workflow. Avoid broad event sources that can repeat a physical command unexpectedly.

Configuration parameters

ParameterRequiredDescriptionDefault
Title
YesDisplay name for the action.None
SNMP device
YesTarget SNMP Device.Parent device
OID
YesExact object identifier to write. It must match the device write allowlist.None
Value type
YesINTEGER, STRING, GAUGE, COUNTER32, COUNTER64, TIMETICKS, IPADDRESS or OID.INTEGER
Value
YesValue converted to the selected SNMP type.Empty

Write, read back and record the outcome

The action calls the target device’s controlled SET operation. The device checks writeEnabled and the OID allowlist, builds the typed SNMP value, sends SET, reads the OID back and returns the read-back value as the action result.

A policy-approved write emits SnmpValueSetEvent with the target OID, value type, applied value, read-back value and success flag. It does not include the SNMP community or v3 credentials.

Treat SET as a physical-system command

SNMP success is not process safety: a successful read-back confirms the managed object value, not that the machine, relay, service or network has reached a safe real-world state.
01

Use device-side safeguards

Keep interlocks, range limits and fail-safe behaviour in the controlled equipment or authoritative controller.

02

Avoid retry storms

Do not connect failure events directly back to the same action without bounded retries and cooldown.

03

Review audit events

Retain SET audit events at a level appropriate to the operational and compliance risk.