Run sheet · MQTT Python: Reliable Client Patterns · 110 min
| Time | Teacher does | Learners do | Link |
|---|---|---|---|
| 0–5 min | Open the Reliable Clients deck at the reconnect timeline | Estimate the first two backoff delays | Chapter |
| 5–12 min | Show how a client's callbacks and network loop report a connection and a received message | Tell a connection event from a received-message event in a trace | Chapter |
| 12–20 min | Work through reconnect backoff and the Last Will message after a dropped link | Predict the next retry delay and what the broker publishes when a client vanishes | Chapter |
| 20–40 min | Run the First MQTT Message lab and compare the sender and receiver output | Record the line that shows the connection and the line that shows the received payload | Lab |
| 40–100 min | Run the First MQTT Message lab and compare the sender and receiver output | Record the line that shows the connection and the line that shows the received payload | Lab |
| 105–110 min | Ask which printed line proves a message arrived | State the next retry interval and why jitter is added | Chapter |
Break: 5 minutes after the lab
If the lab fails: Trace the lab's printed output on paper and mark the connect line, the received line and the retry delays. Camera off: Ask pairs to write the retry sequence and the will message they expect.
Next move: If many learners treat a publish print as proof of delivery, trace one message to a subscriber again.