summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorxengineering <me@xengineering.eu>2025-07-29 22:41:39 +0200
committerxengineering <me@xengineering.eu>2025-07-30 19:50:18 +0200
commite5da3cfc1869899c7c6c84ffd218d9397f89be3a (patch)
tree890ddd0ac8add86f99c1728f756b2a71c4090c4e
parent03d0280c79ab67d0e714334bad71f3677bfcdd91 (diff)
downloadiot-contact-e5da3cfc1869899c7c6c84ffd218d9397f89be3a.tar
iot-contact-e5da3cfc1869899c7c6c84ffd218d9397f89be3a.tar.zst
iot-contact-e5da3cfc1869899c7c6c84ffd218d9397f89be3a.zip
doc: api: future: Remove update automation
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.
-rw-r--r--doc/api/future.md8
1 files changed, 1 insertions, 7 deletions
diff --git a/doc/api/future.md b/doc/api/future.md
index bc870b8..c2e01f7 100644
--- a/doc/api/future.md
+++ b/doc/api/future.md
@@ -54,13 +54,7 @@ accessed directly with its link-local address.
{
"hostname": "mydevice",
"update": {
- "url": "https://deploy.xengineering.eu/git/iot-contact/latest/",
- "automation": {
- "enable": false,
- "hour": null,
- "minute": null,
- "second": null
- }
+ "url": "https://deploy.xengineering.eu/git/iot-contact/latest/"
},
"mqtt": {
"broker": "mqtt://...",