| Age | Commit message (Collapse) | Author |
|---|
|
Removing the full configurability of the device and replacing everything
with (m)DNS makes the API way easier.
There is no need for HTTP, settings parsing and storage and all related
efforts.
Instead the device finds updates via a hard-coded domain name, and all
local services via mDNS.
Configuration might come later for security (setting a TLS-PSK key or
similar) or for fine-tuning but is in general not required.
|
|
|
|
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.
|
|
|
|
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.
|
|
|
|
This reduces the HTTP endpoints and overhead.
|
|
|
|
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.
|
|
|
|
|
