"Testing MQTT based IoT Applications"
summary
Explains why HTTP fails for low‑power, intermittent sensors and demonstrates a concrete test: a Python script attaches publisher and subscriber to a broker, publishes messages before and after subscriber disconnects, and compares QoS=0 vs QoS=1 results — QoS0 drops messages sent while subscriber is offline, QoS1 delivers them on reconnect. Notes MQTT versions (3.1.1, 5) and parameters like Keep Alive / Clean Session, and warns that different broker implementations can change observable behavior.
AI-written summary · about
related talks
44mBenefits of MQTT for IoT Messaging and Beyond
55mMQTT Protocol on Intel IoT Architecture
58mLong road from oil pipeline sensors up to millions of TV’s
53mComparing Messaging Techniques for the IoT
16mApache Kafka + MQTT = A Powerpack combination for end-to-end testing
49mOpen Source MQTT Brokers
40mHome Automation with MQTT
54mMQTT Deep Dive: With Berries, Morse and a Drone [zero PowerPoint]