Skip to content

Releases

SIoT v1.1.1 — SIoT v1 publishing compatibility

Choose a tag to compare

@yzy726 yzy726 released this 18 Nov 14:49

Fix publishing compatibility with SIoT v1 brokers that close QoS 1 connections.

  • Add explicit config.publish_qos0 mode. Zero-initialized API configurations
    retain the QoS 1 default; the optional shell example has a separate switch.
  • Support QoS 0 transmission without pretending a PUBACK was received. Tolerate
    the SIoT v1 zero-ID acknowledgement through the existing unsolicited-ACK path.
  • Teacher configuration can select broker.publish_qos 0 or 1. Its example uses
    0, and the page/API distinguish socket transmission from PUBACK and execution.
  • Add QoS 0 C transport, host-policy and real-Paho integration regressions.

Validated with Windows/Linux tests, ARM/Studio builds and an actual C client
against a deployed SIoT v1 service (publish, echo, persistent storage verified).
Application execution still requires per-device acknowledgements.

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.

SIoT v1.0.1

Choose a tag to compare

@yzy726 yzy726 released this 18 Nov 10:55

Fix the optional example's thread priority so it also works with configurations
that use 8 or 16 priority levels. The priority now follows
RT_THREAD_PRIORITY_MAX / 2 instead of a fixed value of 20.

The client remains independent of any board, sensor, Wi-Fi driver or personal
SIoT server. Configure the broker, credentials and topics for your own server.

Validation: Windows and Linux transport/Kconfig tests; STM32F407 / RT-Thread
4.1.1 integration build with the optional example enabled. Hardware behavior
and SIoT 2.x have not been verified.

SIoT v1.0.0

Choose a tag to compare

@yzy726 yzy726 released this 18 Nov 10:20

Initial release of the configurable SIoT MQTT client for RT-Thread.

  • Caller-supplied server, port, unique client ID, credentials and topics.
  • MQTT 3.1.1; QoS 1 publish/PUBACK and QoS 0/1 receive.
  • Checked SUBACK, bounded packet buffers, partial-frame handling and timeouts.
  • Optional Mbed TLS 2.x with CA, hostname and certificate-date verification.
  • Generic shell example, no board GPIO/sensor/Wi-Fi code or personal credentials.
  • Vendored Paho MQTTPacket codec with original EPL/EDL license files.

Validation: eight adversarial local-broker scenarios and standalone Kconfig tests passed on Windows/MinGW and GitHub's Linux runner. The public package and example compiled in an isolated STM32F407 / RT-Thread 4.1.1 BSP. A SIoT v1.3 service was checked for login/subscription. Actual target hardware operation, SIoT 2.x service integration and target-specific TLS entropy/clock integration remain the user's responsibility.