Configure a TLS broker under Integrations on the sensor's website. For a private broker,
import its verified CA certificate; optional client certificates give mutual TLS. Hostname
verification stays on. Give the sensor a publish-only identity on your broker, limited to its own
wlancommander/devices/<device-id> prefix.
| Topic | Contents | Delivery |
|---|---|---|
…/availability |
Online or offline; also the last will | QoS 1, retained |
…/health |
A current health sample, every 30 seconds | QoS 0, not retained |
…/jobs |
Job state changes | QoS 1, not retained |
- Job messages carry opaque IDs and states: no packet payloads, SSIDs or client MAC addresses.
- QoS 1 can deliver a message twice; de-duplicate by event ID.
- Undelivered events wait in an outbox of up to 16 MiB or 24 hours.
- The sensor only publishes. It subscribes to nothing, so MQTT cannot be used to command it.