diff options
| author | xengineering <me@xengineering.eu> | 2025-07-30 19:41:03 +0200 |
|---|---|---|
| committer | xengineering <me@xengineering.eu> | 2025-07-30 19:50:18 +0200 |
| commit | 8e722f61a6ba8e56b7a0a93fa41f5b9b23bff6c4 (patch) | |
| tree | 442a3a374bf5ddd201801e4a409008e275b419b8 | |
| parent | 22c9abdba9961f2088999cb40d6906dc7ba01d2f (diff) | |
| download | iot-contact-8e722f61a6ba8e56b7a0a93fa41f5b9b23bff6c4.tar iot-contact-8e722f61a6ba8e56b7a0a93fa41f5b9b23bff6c4.tar.zst iot-contact-8e722f61a6ba8e56b7a0a93fa41f5b9b23bff6c4.zip | |
doc: api: future: Switch to `set` topic suffix
If a writable topic should correlate to a readable topic the new
convention is a suffix (`my/topic/set`) instead of the old prefix
(`request/my/topic`).
This keeps the alphabetical ordering the same.
| -rw-r--r-- | doc/api/future.md | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/doc/api/future.md b/doc/api/future.md index 0430e22..2ac66fc 100644 --- a/doc/api/future.md +++ b/doc/api/future.md @@ -107,6 +107,6 @@ 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. -- `request/blind/closure` QoS 2 not retained (`0`, `1`, ... `100`) -- `request/blind/motion` QoS 2 not retained (`up`, `down`, `stopped`) +- `blind/closure/set` QoS 2 not retained (`0`, `1`, ... `100`) +- `blind/motion/set` QoS 2 not retained (`up`, `down`, `stopped`) - `update/trigger` QoS 2 not retained |