Why MQTT is the IoT standard in Raspberry Pi - Challenge Your Understanding

Challenge - 5 Problems

❓ Predict Output

intermediate

What is the output of this MQTT message publishing code?

Consider this Python code running on a Raspberry Pi that publishes a message to an MQTT broker. What will be printed when the message is successfully published?

Raspberry Pi

import paho.mqtt.client as mqtt

client = mqtt.Client()
client.connect('test.mosquitto.org', 1883, 60)

result = client.publish('home/temperature', '22.5')
print(result.rc)

A 1

B 0

C None

D Exception raised

💡 Hint

The publish() method returns an MQTTMessageInfo object with an rc attribute. 0 means success.

In MQTT, a result code of 0 means the message was accepted for delivery by the client library.

🧠 Conceptual

intermediate

Why is MQTT preferred for IoT devices?

Which of the following reasons best explains why MQTT is widely used as the IoT communication standard?

A It requires devices to maintain constant TCP connections without keep-alive.

B It uses a heavy protocol with large message sizes for reliability.

C It supports a lightweight publish-subscribe model with low bandwidth use.

D It only works with wired Ethernet connections.

💡 Hint

Think about IoT devices often having limited power and network.

MQTT uses a lightweight publish-subscribe model that minimizes bandwidth and power consumption, ideal for IoT.

🔧 Debug

advanced

Identify the error in this MQTT subscriber code

This Python code is intended to subscribe to an MQTT topic and print received messages. What error will it raise when run?

Raspberry Pi

import paho.mqtt.client as mqtt

def on_message(client, userdata, message):
    print(f"Received message: {message.payload.decode()}")

client = mqtt.Client()
client.on_message = on_message
client.connect('broker.hivemq.com', 1883)
client.subscribe('home/temperature')
client.loop_start()

# Missing loop or wait here

A No messages printed because program exits immediately

B RuntimeError because loop_start() is called without loop_forever()

C No error, prints messages as they arrive

D SyntaxError due to missing colon

💡 Hint

Think about what happens after starting the loop in a script that ends immediately.

The script starts the network loop in the background but then exits immediately, so no messages are received or printed.

📝 Syntax

advanced

Which MQTT topic filter is valid for subscribing to all sensors?

You want to subscribe to all topics under 'sensors' using MQTT wildcards. Which subscription topic string is syntactically correct?

A sensors/*

B sensors/+/#

C sensors/+/+/#

D sensors/#

💡 Hint

MQTT uses '#' for multi-level and '+' for single-level wildcards.

The '#' wildcard must be at the end and matches all subtopics. '+' matches exactly one level. '*' is not valid in MQTT.

🚀 Application

expert

How many messages will be received by this MQTT subscriber?

A subscriber subscribes to 'devices/+/status' and the broker receives messages published to these topics: - devices/device1/status - devices/device2/status - devices/device1/temperature - devices/device3/status - devices/device3/battery How many messages will the subscriber receive?

A 3

B 5

C 4

D 2

💡 Hint

The '+' wildcard matches exactly one topic level.

The subscription matches topics with exactly one level between 'devices' and 'status'. Only three topics match: device1/status, device2/status, device3/status.

Practice

1. Why is MQTT considered ideal for small devices in IoT?

easy

A. Because it requires a lot of processing power

B. Because it uses very little data and is simple to implement

C. Because it only works on fast internet connections

D. Because it needs complex setup and configuration

Solution

1. Step 1: Understand MQTT data usage

   MQTT is designed to send small messages, so it uses very little data.

2. Step 2: Consider device capabilities

   Small devices have limited power and memory, so a simple protocol like MQTT fits well.

3. Final Answer:

   Because it uses very little data and is simple to implement -> Option B

4. Quick Check:

   Small data + simplicity = MQTT ideal [OK]

Hint: MQTT is simple and data-light for small devices [OK]

Common Mistakes:

• Thinking MQTT needs fast internet
• Assuming MQTT requires heavy processing
• Believing MQTT setup is complex

2. Which of the following is the correct way to publish a message using MQTT in Python?

easy

A. client.publish('topic/name', 'message')

B. client.send('topic/name', 'message')

C. client.push('topic/name', 'message')

D. client.post('topic/name', 'message')

Solution

1. Step 1: Recall MQTT Python client method

   The standard method to send a message is publish.

2. Step 2: Verify method names

   Methods like send, push, and post are not used in MQTT Python clients.

3. Final Answer:

   client.publish('topic/name', 'message') -> Option A

4. Quick Check:

   Publish method sends messages [OK]

Hint: Use publish() to send MQTT messages in Python [OK]

Common Mistakes:

• Using send() instead of publish()
• Confusing MQTT with HTTP methods
• Using push() or post() which are invalid

3. What will be the output of this Python MQTT client code snippet?

import paho.mqtt.client as mqtt
client = mqtt.Client()
client.connect('broker.hivemq.com', 1883)
client.publish('home/temperature', '22')
print('Message sent')

medium

A. Message sent

B. 22

C. Error: client not connected

D. No output

Solution

1. Step 1: Analyze the code flow

   The code connects to the MQTT broker and publishes a message, then prints 'Message sent'.

2. Step 2: Identify the print output

   The only print statement outputs the string 'Message sent'.

3. Final Answer:

   Message sent -> Option A

4. Quick Check:

   Print statement output = Message sent [OK]

Hint: Look for print() output, not MQTT message content [OK]

Common Mistakes:

• Expecting '22' to print
• Assuming connection error without checking
• Thinking no output because publish is async

4. Identify the error in this MQTT Python code snippet:

import paho.mqtt.client as mqtt
client = mqtt.Client()
client.publish('home/light', 'ON')
client.connect('broker.hivemq.com', 1883)

medium

A. The client object is not created

B. The topic name is invalid

C. The message 'ON' must be an integer

D. The client should connect before publishing

Solution

1. Step 1: Check method order

   MQTT client must connect to the broker before publishing messages.

2. Step 2: Verify topic and message validity

   The topic 'home/light' is valid and message 'ON' can be a string.

3. Final Answer:

   The client should connect before publishing -> Option D

4. Quick Check:

   Connect first, then publish [OK]

Hint: Always connect before publishing MQTT messages [OK]

Common Mistakes:

• Publishing before connecting
• Thinking topic names must be numeric
• Assuming client not created error

5. You want to design an IoT system with many Raspberry Pi devices sending sensor data reliably over unstable internet. Why is MQTT the best choice?

hard

A. Because MQTT messages are always encrypted by default

B. Because MQTT requires all devices to be on the same local network

C. Because MQTT uses a publish-subscribe model that handles unreliable connections well

D. Because MQTT needs high bandwidth to work properly

Solution

1. Step 1: Understand MQTT communication model

   MQTT uses a publish-subscribe system where devices send messages to topics, allowing flexible communication.

2. Step 2: Consider network reliability

   MQTT supports message delivery even with unstable internet by using quality of service levels.

3. Step 3: Evaluate other options

   MQTT does not require devices on the same network, messages are not encrypted by default, and it works well with low bandwidth.

4. Final Answer:

   Because MQTT uses a publish-subscribe model that handles unreliable connections well -> Option C

5. Quick Check:

   Pub-sub + unreliable net = MQTT best [OK]

Hint: MQTT pub-sub fits unstable internet and many devices [OK]

Common Mistakes:

• Thinking MQTT needs local network only
• Assuming MQTT encrypts messages automatically
• Believing MQTT requires high bandwidth