summaryrefslogtreecommitdiff
path: root/doc
AgeCommit message (Collapse)Author
4 daysdoc: api: future: Switch to `mqtt/url` settingHEADmainxengineering
4 daysdoc: api: future: Switch to `set` topic suffixxengineering
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.
4 daysdoc: api: future: Order MQTT topic by alphabetxengineering
4 daysdoc: api: future: Remove update automationxengineering
With the change to MQTT the device will not be usable anymore without server infrastructure. This design change allows to reduce the complexity of configuration and implementation here significantly. The device only supports MQTT-triggered HTTP pull updates and the server should take care of regularly triggering this via MQTT.
7 daysdoc: api: future: Update MQTT APIxengineering
8 daysdoc: api: future: Introduce device info conceptxengineering
This reduces the HTTP endpoints and overhead.
8 daysdoc: api: future: Switch to pull updatesxengineering
10 daysdoc: api: Add README.md and flatten future.md structurexengineering
This makes it later possible to diff the planned `current.md` with the `future.md`. When the firmware is feature-complete the diff should be empty.
10 daysdoc: api: future: Add first draftxengineering
10 daysdoc: Add CC-BY-SA licensexengineering