Getting Started Cameras & Video Detection & Recording Automation & Events Actions Integration & Connectivity Network & Discovery AI & Remote Control MQTT Modbus ZeroMQ System & Administration Use Cases Troubleshooting About & Legal
Home / Documentation / Reboot ONVIF Device
Onvif actions

Reboot ONVIF Device

Send a remote reboot command to an ONVIF-compatible IP camera or recording device. Use as an administrative recovery action to restore a device that has stopped streaming, stopped responding to PTZ commands, or entered a degraded state.

Remote reboot for camera recovery

Reboot ONVIF Device calls the ONVIF device management reboot operation on the selected camera. The action is intended for recovery scenarios — not routine operation. When a camera stops streaming, stops sending events, or enters a known-bad state that a reboot fixes, this action can be triggered automatically or manually from the UI.

Important: A reboot interrupts all camera-dependent tasks — RTSP streams, event polling, PTZ control, continuous recordings, and motion recordings — until the device comes back online and tasks reconnect. Recovery time depends on the camera model and network.

Add and configure the reboot action

01

Verify device management permissions

The credentials configured on the ONVIF Camera component must have device management permissions. The reboot operation requires an account that is specifically allowed to restart the device.

02

Create the action

Click + next to Reboot ONVIF Device under the Actions sub-menu. The configuration panel opens for the new action instance.

03

Select device

Choose the ONVIF camera to reboot from the Device drop-down. Only cameras configured as ONVIF Camera components are listed.

04

Test manually before wiring to rules

Use the manual execution button to confirm the action reaches the camera and that the camera reboots successfully. Verify that dependent tasks recover automatically after restart.

05

Add to Event Manager rules

Wire the action to failure-detection rules or operator confirmation flows. Consider adding a cooldown or confirmation step to prevent repeated reboots from a false-positive trigger.

Configuration parameters

ParameterRequiredDescriptionDefault
Restart on failure
Yes Restart behavior if the action encounters an error:
  • Stop on failure — not restarted until triggered manually.
  • Immediately — restarts right after an error.
  • 10 sec — restarts after a 10-second delay.
  • 30 sec — restarts after a 30-second delay.
  • 1 min — restarts after a 1-minute delay.
10 sec
Title
Yes Display name for this action instance. Used in the UI, logs, and action group lists. Set a descriptive name such as Reboot Entrance Camera so operators can identify it without reading the device reference. —
Device
Yes The ONVIF camera to reboot. The action calls the ONVIF reboot operation on this device, so it should only be used with trusted cameras and credentials that are permitted to perform a device reboot. Select the correct ONVIF Camera from the drop-down. —

When and how to use this action

01

Automated camera recovery

Wire the action to a detection rule that identifies camera degradation — for example when the capture task fails and restarts multiple times within a short window. Pair with a cooldown rule to avoid repeated reboots during a deeper infrastructure failure.

02

Operator-triggered reboot

Expose the action as a manual trigger in the UI. When an operator sees the camera is frozen or unresponsive, they can issue a one-click reboot without accessing the camera's web interface directly.

03

Scheduled maintenance reboot

Use a scheduler-triggered rule to restart the camera during a low-activity window, such as 03:00 AM. Ensure recordings and detection tasks tolerate the brief downtime and recover automatically after restart.

04

Post-failure recovery chain

Combine with Execute Action Group: first stop dependent tasks, reboot the camera, wait for recovery, then restart tasks. This prevents partial-state errors when the camera is briefly offline.

Safety note: Avoid triggering reboots on every transient frame drop or short network glitch. Use this action after repeated confirmed failures or explicit operator confirmation. Camera reboot during an active evidence recording may result in lost footage.