> For the complete documentation index, see [llms.txt](https://docs.mobiusflow.com/help/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.mobiusflow.com/help/user-guides/deploying-mobiusflow-on-prem/deploying-mobiusflow-to-approved-hardware-using-balenacloud/device-variables.md).

# Device Variables

Understanding the MobiusFlow® balenaCloud Device Variables

balenaCloud devices are configured using Device Variables. When deploying **Mobius**Flow® to a balenaCloud fleet a number of Device Variables are created with default values. These are defined at the fleet level but can be overridden at the device level. More information about working with balenaCloud Device Variables can be found [here](https://docs.balena.io/learn/manage/variables/#device-variables).

{% hint style="info" %}
For most devices the only Device Variables that require changing are listed below. The rest can be left at their default values.

* **MOBIUS\_LICENCE**
* **MOBIUS\_HUB\_ID**
  {% endhint %}

{% hint style="danger" %}
Remember to override the Device Variables at the device level and not at the fleet level.

Any changes at the fleet level will apply to all devices in the fleet.
{% endhint %}

## MobiusFlow Device Variables

The image below shows the Device Variables created when **Mobius**Flow® is deployed to balenaCloud.

<figure><img src="https://241296614-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FQoV8xVJhcESUhdKQWDcm%2Fuploads%2FlIczwITBNoO2t4LYOKXh%2FBalena%20Variables.png?alt=media&amp;token=9cf1ed97-5c75-44f7-8e6c-ee2f1f125a2d" alt=""><figcaption></figcaption></figure>

Expand the items below for detailed information on each Device Variable

<details>

<summary>MOBIUS_ENABLE_CONFIG_UI</summary>

Enable or disable the MobiusFlow® configuration user interface

**Possible Values:** (default shown in bold)

* **true** *- Enable the configuration user interface*
* false *- Disable the configuration user interface*

</details>

<details>

<summary>MOBIUS_ENGINE_API_AUTH_PROVIDER</summary>

Select which authentication provider to use for the Engine Rest API.

**Possible Values:** (default shown in bold)

* **local** *- Use the local user database*

</details>

<details>

<summary>MOBIUS_ENGINE_API_PORT</summary>

The Engine Rest API port

**Possible Values:** (default shown in bold)

* **8443**

</details>

<details>

<summary>MOBIUS_HUB_ID</summary>

The HUB ID used by this **Mobius**Flow® instance

**Possible Values:** (default shown in bold)

* **000001** *- Can be any six digit hex number*

</details>

<details>

<summary>MOBIUS_HUB_RESET_PSKS</summary>

Reset all **Mobius**Flow® Service pre-shared keys on startup

**Possible Values:** (default shown in bold)

* **true** *- reset the pre-shared keys on startup*
* false *- do not reset the pre-shared keys on startup*

</details>

<details>

<summary>MOBIUS_LICENCE</summary>

The **Mobius**Flow® licence code for this device

**Possible Values:** *a valid licence code*

</details>

<details>

<summary>MOBIUS_LICENCE_RENEW</summary>

Change the **Mobius**Flow® licence code. Set this to **true** when replacing an licence code

**Possible Values:** (default shown in bold)

* true *- Change the licence code*
* **false** *- Use existing licence code*

</details>

<details>

<summary>MOBIUS_LOCAL_TIMEOUT</summary>

The maximum time in milliseconds that any **Mobius**Flow® Service will wait for a response to a **Mobius**Flow® message

**Possible Values:** (default shown in bold)

* **10000** *- any number greater than 1000*

</details>

<details>

<summary>MOBIUS_LOG_SERVICE_STATUS</summary>

Log changes of MobiusFlow® Services status to the standard logs

**Possible Values:** (default shown in bold)

* true *- log the service status changes to the standard logs*
* **false** *- do not log the service statis changes to the standard logs*

</details>


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.mobiusflow.com/help/user-guides/deploying-mobiusflow-on-prem/deploying-mobiusflow-to-approved-hardware-using-balenacloud/device-variables.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.