> For the complete documentation index, see [llms.txt](https://developer.magtek.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://developer.magtek.com/api-and-command-reference/dynafamily-programmers-manual/notifications/qwantifi-configuration-device-settings.md).
# QwantiFi Configuration (device settings)
This page documents the on-device settings that put a DynaFlex / MMS reader onto the QwantiFi MQTT broker. These are **device configuration properties** — part of the device command protocol — which is why they live in the DynaFamily Programmer's Manual rather than with the cloud-side QwantiFi material. For the end-to-end feature and the cloud side, start at the [**QwantiFi Overview**](https://developer.magtek.com/services/qwantifi/qwantifi-overview).
{% hint style="warning" %}
**How these are applied in practice.** In a normal deployment you do **not** hand-author these settings. RMS generates the exact command sequence and the QwantiFi tooling applies it to the device. This page documents *what* each setting is so the generated commands and the device's reported configuration can be understood.
{% endhint %}
### Configuration Groups
QwantiFi provisioning writes two related configuration groups to the device:
1. **QwantiFi configuration** — the broker connection and topic settings (below).
2. **Trust configuration** — the TLS trust material (certificate) the device uses to validate the broker connection when TLS is in use.
Both are delivered as secured commands. The command envelope, sequencing (`WAIT`), and secured-command mechanics are the standard ones described in [**Send Secured Command to Device**](https://developer.magtek.com/api-and-command-reference/dynafamily-programmers-manual/commands/0xennn-security/0xeeee-send-secured-command-to-device) and [**Set Property.**](https://developer.magtek.com/api-and-command-reference/dynafamily-programmers-manual/commands/0xd1nn-settings-and-information/0xd111-set-property-unsecured)
### QwantiFi Settings
Each row is one settable property. Values shown are examples.
| Setting | Meaning | Example |
| ------------------------ | ----------------------------------------------------------------------------- | --------------------------------------------- |
| `WlanProtocol` | Selects the WLAN transport mode (e.g.QwantiFi vs. WebSocket Server). | `00` |
| `Broker` | Broker host the device connects to. | `dev-mqtt.magensa.dev` |
| `Port` | Broker port (`1883` plain, `8883` TLS). | `8883` |
| `QoS` | QwantiFi quality of service for the device's messages. | `1` |
| `SubscribeTopic` | The command topic the device listens on (`…/{sn}/SendCommand`). | `MagTek/13204/2026213/B563215/SendCommand` |
| `SubscribeTopicExtended` | Optional secondary subscribe topic. | *(empty)* |
| `PublishTopic` | The topic branch the device publishes responses to (`…/device/publish/{sn}`). | `MagTek/13204/2026213/device/publish/B563215` |
| `PublishTopicExtended` | Optional secondary publish topic. | *(empty)* |
| `ClientId` | The device's MQTT client identifier (typically the serial number). | `B563215` |
| `Username` | The device's MQTT username (`{reseller}-{customer}-{sn}`). | `13204-2026213-B563215` |
| `Password` | The device's MQTT password. Masked in responses. | `******` |
| `PeerCommonName` | Expected TLS certificate common name (when TLS is used). | `dev-mqtt.magensa.dev` |
| `KeepAlive` | MQTT keep-alive interval. | *(empty)* |
| `OperatingMode` | Transport hint reported by the device. | `mqtt` |
{% hint style="info" %}
**Device topics vs. POS topics.** The device is provisioned to listen on the concrete `…/{sn}/SendCommand` leaf and to publish on `…/device/publish/{sn}`. This is the device's side of the same topic model the POS uses from the other direction — see the topic model in the [**POS Integration Guide.**](https://developer.magtek.com/guides/guides/qwantifi/pos-integration-guide)
{% endhint %}
### Trust (TLS) Configuration
When TLS is used, a Trust configuration command loads the TLS trust material (a certificate) onto the device so it can validate the broker. RMS supplies this as a secured command carrying the certificate payload. Non-TLS and TLS trust profiles are maintained separately on the RMS side.
### Reading the Current Configuration Back
The device reports its current MQTT settings when queried (the QwantiFi tooling's [**Get Config**](https://developer.magtek.com/api-and-command-reference/dynafamily-programmers-manual/commands/0xd1nn-settings-and-information/0xd101-get-property) action, and RMS's `Claims` object, both reflect these properties). Reading properties from the device uses Get Property.
---
# 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://developer.magtek.com/api-and-command-reference/dynafamily-programmers-manual/notifications/qwantifi-configuration-device-settings.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.