Skip to content

SIoT v1.1.0 — optional deployment controls

Choose a tag to compare

@yzy726 yzy726 released this 18 Nov 13:49

Optional deployment controls for SIoT and compatible MQTT brokers.

  • Select individual-device, group and deployment-wide command channels in Kconfig, with a selectable retained-command policy. The routing layer defaults to off, preserving the original client API and legacy example topics.
  • Keep per-device state and acknowledgements separate. Subscribe again after reconnecting; runtime route masks cannot enable compiled-out scopes.
  • Add an independent Python teacher web controller with feature switches, roster, action allowlist, authenticated APIs, per-device acknowledgement tracking and explicit Mosquitto 2.x ACL export. SIoT server itself is unchanged.
  • Document configuration, deployment, scope/permission boundaries and the difference between PUBACK and actual device execution.

Validation: 8 transport broker scenarios, 16 actual C channel configurations, 8 controller policy/HTTP tests, 2 real-Paho local MQTT integration tests, default and channel-enabled public example ARM builds, all lab platform ARM builds, and RT-Thread Studio import/build (0 errors; 6 pre-existing WLAN warnings). Desktop and phone layouts were checked with a simulated local preview.

No physical board actuation or classroom-scale load test has been performed. Shared SIoT v1 credentials do not provide per-user MQTT authorization; broker ACLs require a separately configured compatible broker.