Why MQTT is the IoT standard in Raspberry Pi

Introduction

MQTT is a simple way for devices to talk to each other over the internet. It uses very little data and works well even if the connection is slow or unreliable.

When you want smart home devices like lights and sensors to communicate easily.

When you have many small devices sending small messages often.

When your devices have limited power and need to save battery.

When you want to control devices remotely with low delay.

When your internet connection is not very stable or fast.

Syntax

Raspberry Pi

client = mqtt.Client()
client.connect('broker.hivemq.com', 1883)
client.publish('home/livingroom/temperature', '22')
client.loop_forever()

This example shows how a device connects to a broker and sends a message.

The broker is like a post office that forwards messages to devices that want them.

Examples

This code turns on a kitchen light by sending 'ON' to the topic 'home/kitchen/light'.

Raspberry Pi

import paho.mqtt.client as mqtt

client = mqtt.Client()
client.connect('broker.hivemq.com', 1883)
client.publish('home/kitchen/light', 'ON')
client.loop_start()

This code listens for temperature messages from any room and prints them.

Raspberry Pi

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

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

Sample Program

This program connects to a public MQTT broker, sends a temperature value, and listens for messages on the same topic.

Raspberry Pi

import paho.mqtt.client as mqtt

# Called when a message is received
def on_message(client, userdata, message):
    print(f"Message received on {message.topic}: {message.payload.decode()}")

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

# Publish a temperature reading
client.publish('home/livingroom/temperature', '23')

client.loop_start()

import time
# Wait a bit to receive messages
time.sleep(2)
client.loop_stop()

Important Notes

MQTT uses a 'publish-subscribe' model, which means devices send messages to topics and others listen to those topics.

It is lightweight, so it works well on small devices like Raspberry Pi or sensors.

MQTT brokers handle message delivery, so devices don't need to know about each other directly.

Summary

MQTT is simple and uses little data, perfect for small devices.

It works well even with slow or unreliable internet.

It helps many devices talk easily by sending messages to topics.

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