Why Retained messages in IOT Protocols? - Purpose & Use Cases

The Big Idea

What if your smart devices always knew the latest settings the moment they woke up?

The Scenario

Imagine you have a smart home system where devices like lights and thermostats need to know the latest settings immediately after they connect.

Without retained messages, every time a device restarts or connects, it has to ask for the current settings manually.

The Problem

This manual approach is slow because devices wait for updates instead of getting them instantly.

It also causes errors if devices miss messages sent before they connected, leading to outdated or missing information.

The Solution

Retained messages keep the last important message stored on the server.

When a device connects, it immediately receives the latest retained message without waiting.

This ensures devices always start with the current state, making communication smooth and reliable.

Before vs After

✗ Before

device subscribes; waits for update; may miss last message

✓ After

device subscribes; receives last retained message instantly

What It Enables

Devices can always start with the latest information, making IoT systems more responsive and reliable.

Real Life Example

A smart thermostat connects and instantly knows the current temperature setting without waiting for a new message.

Key Takeaways

Manual message delivery can cause delays and missed updates.

Retained messages store the last message for immediate delivery on connection.

This improves device synchronization and user experience in IoT systems.

Practice

1. What is the main purpose of a retained message in MQTT?

easy

A. To delete all messages from the broker

B. To store the last message on a topic for new subscribers

C. To encrypt messages during transmission

D. To limit the message size to 256 bytes

Solution

1. Step 1: Understand retained message concept

   Retained messages keep the last message sent on a topic stored on the broker.

2. Step 2: Identify the purpose for new subscribers

   New subscribers receive the last retained message immediately upon subscribing, ensuring they have the latest state.

3. Final Answer:

   To store the last message on a topic for new subscribers -> Option B

4. Quick Check:

   Retained message = last stored message [OK]

Hint: Retained means broker keeps last message for new subscribers [OK]

Common Mistakes:

• Confusing retained messages with message encryption
• Thinking retained messages delete old messages
• Assuming retained messages limit message size

2. Which MQTT publish option must be set to true to create a retained message?

easy

A. retain

B. qos

C. cleanSession

D. willFlag

Solution

1. Step 1: Identify publish options related to message retention

   The retain flag controls whether the broker stores the message as retained.

2. Step 2: Confirm correct flag for retention

   Setting retain=true tells the broker to keep the message for future subscribers.

3. Final Answer:

   retain -> Option A

4. Quick Check:

   retain flag true = retained message [OK]

Hint: Set retain flag true to keep message on broker [OK]

Common Mistakes:

• Confusing retain with cleanSession flag
• Using qos instead of retain for message storage
• Mistaking willFlag for retention control

3. Given the following MQTT publish code snippet, what will a new subscriber receive immediately after subscribing to topic home/temperature?

client.publish('home/temperature', '22°C', retain=True)
client.publish('home/temperature', '23°C', retain=False)

medium

A. The message '22°C' because it was retained

B. The message '23°C' because it was the last published

C. No message because retain is false on last publish

D. Both messages '22°C' and '23°C'

Solution

1. Step 1: Analyze retained flag on each publish

   The first message '22°C' is published with retain=True, so it is stored on the broker.

2. Step 2: Understand effect of second publish with retain=False

   The second message '23°C' is published without retain, so it is sent but not stored as retained. Importantly, publishing with retain=False on the same topic clears the retained message.

3. Step 3: Determine what new subscribers receive

   New subscribers get no retained message because the last retained message was cleared by the second publish.

4. Final Answer:

   No message because retain is false on last publish -> Option C

5. Quick Check:

   Retain=False on last publish clears retained message [OK]

Hint: Retain=False on last publish clears retained message [OK]

Common Mistakes:

• Assuming last published message is always retained
• Thinking retain=False messages overwrite retained messages
• Expecting multiple retained messages per topic

4. You want to clear a retained message on topic device/status. Which publish command will correctly clear it?

medium

A. client.publish('device/status', '', retain=True)

B. client.publish('device/status', '', retain=False)

C. client.publish('device/status', None, retain=True)

D. client.publish('device/status', None, retain=False)

Solution

1. Step 1: Understand how to clear retained messages

   Publishing an empty payload with retain=True clears the retained message on that topic.

2. Step 2: Analyze the options

   Publishing with retain=False does not update or clear the retained message. Using None as payload is invalid. Only publishing an empty string ('') with retain=True clears the retained message.

3. Final Answer:

   client.publish('device/status', '', retain=True) -> Option A

4. Quick Check:

   Empty payload + retain=True clears retained message [OK]

Hint: Publish empty message with retain=True to clear retained message [OK]

Common Mistakes:

• Using retain=False when trying to clear retained message
• Sending None as payload which causes error
• Expecting retain=False to remove retained message

5. You have multiple IoT devices publishing their status to devices/+/status with retained messages. A new device subscribes to devices/device123/status. What will it receive and why?

hard

A. It receives only non-retained messages published after subscription

B. It receives all retained messages from all devices under devices/+/status

C. It receives no messages until a new status is published

D. It receives the last retained status message for device123 immediately

Solution

1. Step 1: Understand MQTT wildcard subscription

   The subscription to devices/device123/status matches only that specific topic, not all devices.

2. Step 2: Understand retained message delivery

   The broker sends the last retained message on that exact topic immediately upon subscription.

3. Step 3: Determine what the new device receives

   The new device receives the last retained status message for device123 immediately, not messages from other devices.

4. Final Answer:

   It receives the last retained status message for device123 immediately -> Option D

5. Quick Check:

   Retained message sent on exact subscribed topic [OK]

Hint: New subscriber gets last retained message on exact topic [OK]

Common Mistakes:

• Thinking wildcard subscription delivers all retained messages
• Expecting no retained messages on subscription
• Confusing retained with non-retained message delivery