> 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 (available for inference and manager services) to automatically update during your configured maintenance windows. > **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.
--- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.roboflow.com/deploy/device-manager/making-changes/update-device-configuration.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.