> For the complete documentation index, see [llms.txt](https://docs.roboflow.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.roboflow.com/deploy/device-manager/making-changes/update-device-configuration.md). # Update Device Configuration ### Configuring Your Deployment The Configuration page in Deployment Manager lets you manage services running on your device. This guide provides an overview of the key configuration options. #### Device Settings You can rename your device or update its timezone. The device name is purely for display in the Deployment Manager user interface and will not break any integrations. The timezone is used to help display logs and coordinate the scheduling other other device actions. We highly recommend you keep this in line with the physical location of the deployment
#### Updates / Performance Settings Versions of services can be configured on the tab for each service. Versions are usually updated by the Roboflow team.
**Version indicators:** * **Green checkmark** — Running the latest version * **"Update available"** — A newer version exists **Automatic Updates** - Enable this toggle to automatically update a service during your configured [Maintenance Windows](/deploy/device-manager/setting-up/setup-maintenance-windows.md). It is available for the inference and manager services, and for the app-managed edge services (PLC Relay, OPC UA Server, and the RTSP simulator), which roll forward to the version shipped with Roboflow. If you save configuration changes outside a maintenance window, deploy-affecting changes are queued and applied at the next window. > **Note:** If your device reports a different version than configured, you'll see a mismatch indicator. **Inference Engine** — Controls which runtime the inference service uses. Select one of four modes: * **Auto** (recommended) — Uses Roboflow's default model registry and lets the system choose the best available runtime, including TensorRT when applicable. * **ONNX** — Forces ONNX Runtime with CUDA acceleration. Bypasses the Roboflow model registry. * **TRT** — Forces ONNX Runtime with the TensorRT execution provider. Model compilation can take up to 10 minutes on first run. TensorRT engine caching is always enabled. * **CPU** — Forces CPU-only inference. Useful for debugging GPU-related issues. **RTSP Stream Capture** — Controls how the inference service connects to RTSP cameras. Choose a preset instead of hand-editing capture options: * **Default** — FFmpeg defaults with auto-negotiated transport. Works for most cameras. * **TCP** — Forces TCP transport with generous stream probing. More reliable on lossy networks but slower to start. Adds "Probe Size" and "Analyze Duration" inputs so you can tune buffering. * **UDP** — Forces UDP transport. Lower latency, and some cameras only support UDP. Packets may drop on congested networks. * **Custom** — Passes raw options to FFmpeg as `key;value` pairs separated by `|` (ex: `rtsp_transport;tcp|probesize;10000000`). Use this when a stream needs keys the presets do not cover. If a stream stays unstable on TCP, start with the suggested tuning values and reduce them until instability appears. Values that do not match a preset show up as Custom so an existing configuration is never rewritten. *** #### OPC UA Server The OPC UA Server config modal includes a "Configuration Source" toggle that sets where the tag, folder, and server configuration comes from: * **Web UI** — Enter tags, folders, and server settings directly in the modal. * **File** — Point the service at a configuration file path on the device. Use this when the configuration is too large to store inline, such as deployments with thousands of tags. Only one source applies at a time, so switching sources clears the other side when you save. A file path is required before you can save in File mode. Authentication settings stay editable in both modes. In File mode, the service card shows the configured file path in place of the inline tag list. *** #### CA Certificates Manage trusted CA certificates for your device. This is useful when communicating with services that use custom or internal certificates (e.g., corporate proxies or private registries). You can add, edit, and remove certificates in PEM format. Certificate names may only contain letters, numbers, dots, hyphens, and underscores. Click **Edit** to make changes, then **Save** to apply. *** #### Additional Services Roboflow also allows you to add preconfigured additional services to your device, like a local event store, a default HMI UI, and an RTSP simulator for testing. Each of these has their own configuration options. You'll be prompted as needed when you try to add each service.