Repository navigation
Fix publishing compatibility with SIoT v1 brokers that close QoS 1 connections.
- Add explicit
config.publish_qos0mode. 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_qos0 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.