MQTT client capability: QoS1, QoS2

[zephyrbot]

Reported by Anas Nashif:

As a user, I want to use Zephyr to send data using MQTT to a broker with quality of services 1 and 2.

MQTT uses a “publish/subscribe” model and requires a central MQTT broker to manage and route messages among an MQTT network’s nodes. Eclipse describes MQTT as “a many-to-many communication protocol for passing messages between multiple clients through a central broker.” It uses TCP for its transport layer, which is characterised as “reliable, ordered and error-checked.”

QoS1, At least once: The message is always delivered at least once. It might be delivered multiple times if there is a failure before an acknowledgment is received by the sender. The message must be stored locally at the sender, until the sender receives confirmation that the message has been published by the receiver. The message is stored in case the message must be sent again.

QoS2, Exactly once: The message is always delivered exactly once. The message must be stored locally at the sender, until the sender receives confirmation that the message has been published by the receiver. The message is stored in case the message must be sent again. QoS2 is the safest, but slowest mode of transfer. A more sophisticated handshaking and acknowledgement sequence is used than for QoS1 to ensure no duplication of messages occurs.

(Imported from Jira ZEP-416)

[zephyrbot]

by Flavio Santes:

MQTT QoS 0, 1 and 2 is in testing. This code is on top of GH-2015.

[zephyrbot]

by Flavio Santes:

So far, we are blocked by GH-2067. This issue breaks the build system for applications requiring source files in directories other than src.

[zephyrbot]

by Flavio Santes:

GH-2067 was fixed by https://gerrit.zephyrproject.org/r/#/c/2923/

[zephyrbot]

by Lei Liu:

MQTT Publish QoS0, QoS1, QoS2 message.
{code:title=Server log|borderStyle=solid}
1470580627: New client connected from 192.168.2.100 as zephyr (c1, k0).
1470580627: Sending CONNACK to zephyr (0, 0)
1470580627: Received PUBLISH from zephyr (d0, q0, r0, m0, 'zephyr', ... (3 bytes))
1470580642: Received PUBLISH from zephyr (d0, q1, r0, m1, 'zephyr', ... (3 bytes))
1470580642: Sending PUBACK to zephyr (Mid: 1)
1470580671: New connection from 127.0.0.1 on port 1883.
1470580671: New client connected from 127.0.0.1 as mosq_sub_30810_alvin (c1, k60).
1470580671: Sending CONNACK to mosq_sub_30810_alvin (0, 0)
1470580671: Received SUBSCRIBE from mosq_sub_30810_alvin
1470580671: zephyr (QoS 0)
1470580671: mosq_sub_30810_alvin 0 zephyr
1470580671: Sending SUBACK to mosq_sub_30810_alvin
1470580675: Received PUBLISH from zephyr (d0, q2, r0, m2, 'zephyr', ... (3 bytes))
1470580675: Sending PUBREC to zephyr (Mid: 2)
1470580675: Received PUBREL from zephyr (Mid: 2)
1470580675: Sending PUBCOMP to zephyr (Mid: 2)
{code}

MQTT subscribe QoS0, QoS1, QoS2 topic
{code:title=Server log|borderStyle=solid}
1470580792: Received SUBSCRIBE from zephyr
1470580792: sensors (QoS 0)
1470580792: zephyr 0 sensors
1470580792: Sending SUBACK to zephyr

1470581266: Received SUBSCRIBE from zephyr
1470581266: sensors (QoS 1)
1470581266: zephyr 1 sensors
1470581266: Sending SUBACK to zephyr
1470581268: New connection from 127.0.0.1 on port 1883.
1470581268: New client connected from 127.0.0.1 as mosq_pub_30843_alvin (c1, k60).
1470581268: Sending CONNACK to mosq_pub_30843_alvin (0, 0)
1470581268: Received PUBLISH from mosq_pub_30843_alvin (d0, q1, r0, m1, 'sensors', ... (2 bytes))
1470581268: Sending PUBACK to mosq_pub_30843_alvin (Mid: 1)
1470581268: Sending PUBLISH to zephyr (d0, q1, r0, m1, 'sensors', ... (2 bytes))
1470581268: Received DISCONNECT from mosq_pub_30843_alvin
1470581268: Client mosq_pub_30843_alvin disconnected.
1470581268: Received PUBACK from zephyr (Mid: 1)
1470581306: Received SUBSCRIBE from zephyr
1470581306: sensors (QoS 2)
1470581306: zephyr 2 sensors
1470581306: Sending SUBACK to zephyr
{code}

Zephyr: v1.5.0-rc1

[zephyrbot]

References GH-1779

[zephyrbot]

Related to GH-1779

[zephyrbot]

Related to GH-2099

[zephyrbot]

Related to GH-2104