> 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/deployment/edge-devices/deployment-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

<figure><img src="/files/uQVxeSRdT1VVK2KyEu9a" alt="" width="375"><figcaption></figcaption></figure>

#### Updates / Performance Settings

Versions of services can be configured on the tab for each service. Versions are usually updated by the Roboflow team.

<figure><img src="/files/jclfUCEkDIL1to37Qr0k" alt=""><figcaption></figcaption></figure>

**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](/deployment/edge-devices/deployment-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.

***

#### 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.

<figure><img src="/files/eHqnBkZfg2g5yp4BVYtK" alt="" width="563"><figcaption></figcaption></figure>