From 22c9abdba9961f2088999cb40d6906dc7ba01d2f Mon Sep 17 00:00:00 2001 From: xengineering Date: Wed, 30 Jul 2025 19:39:32 +0200 Subject: doc: api: future: Order MQTT topic by alphabet --- doc/api/future.md | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git a/doc/api/future.md b/doc/api/future.md index c2e01f7..0430e22 100644 --- a/doc/api/future.md +++ b/doc/api/future.md @@ -96,17 +96,17 @@ noted down explicitly in the following MQTT API documentation. These are the topics to which the device publishes. Users should not publish to these and only subscribe. -- `heartbeat` QoS 0 not retained (period in milliseconds, "on-time" in milliseconds) -- `update/required` QoS 2 not retained (`true`, `false`) -- `contact/state` QoS 1 retained (`open`, `closed`) - `blind/closure` QoS 1 retained (`0`, `1`, ... `100`) - `blind/motion` QoS 1 retained (`up`, `down`, `stopped`) +- `contact/state` QoS 1 retained (`open`, `closed`) +- `heartbeat` QoS 0 not retained (period in milliseconds, "on-time" in milliseconds) +- `update/required` QoS 2 not retained (`true`, `false`) These are the topics the device subscribes to. Users can publish there and optionally subscribe to them to see messages from other users if required. The annotations according Quality of Service (QoS) and the retained flag should be followed. -- `update/trigger` QoS 2 not retained -- `request/blind/motion` QoS 2 not retained (`up`, `down`, `stopped`) - `request/blind/closure` QoS 2 not retained (`0`, `1`, ... `100`) +- `request/blind/motion` QoS 2 not retained (`up`, `down`, `stopped`) +- `update/trigger` QoS 2 not retained -- cgit v1.2.3-70-g09d2