Subscribing to control topics in Raspberry Pi - Cheat Sheet & Quick Revision

Recall & Review

beginner

What does it mean to subscribe to a control topic in Raspberry Pi programming?

Subscribing to a control topic means setting up your Raspberry Pi to listen for messages or commands sent to a specific topic, so it can react or control devices accordingly.

beginner

Which protocol is commonly used for subscribing to control topics on Raspberry Pi?

MQTT (Message Queuing Telemetry Transport) is commonly used because it is lightweight and works well for sending control messages between devices.

beginner

In MQTT, what is a 'topic'?

A topic is like a channel or a label that messages are sent to or received from. Devices subscribe to topics to get messages related to that topic.

intermediate

Why is subscribing to control topics useful in home automation with Raspberry Pi?

It allows the Raspberry Pi to receive commands like turning lights on or off, adjusting temperature, or other controls remotely and automatically.

intermediate

What is a simple Python code snippet to subscribe to a control topic using MQTT on Raspberry Pi?

import paho.mqtt.client as mqtt

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/control")
client.loop_forever()

What does subscribing to a control topic allow your Raspberry Pi to do?

A Send commands to other devices

B Increase its processing speed

C Turn off automatically

D Receive commands sent to that topic

Subscribing means listening for messages sent to a topic, so the Pi can receive commands.

Which protocol is most commonly used for subscribing to control topics on Raspberry Pi?

A FTP

B MQTT

C HTTP

D SMTP

MQTT is lightweight and designed for messaging between devices, ideal for control topics.

In MQTT, what is a 'topic'?

A A channel for messages

B A message content

C A security key

D A type of device

A topic is like a channel where messages are published and subscribed to.

What Python library is commonly used to subscribe to MQTT topics on Raspberry Pi?

A requests

B numpy

C paho-mqtt

D flask

paho-mqtt is a popular Python library for MQTT communication.

What function handles incoming messages when subscribing to a topic in MQTT with Python?

A on_message

B on_publish

C on_connect

D on_disconnect

The on_message function is called when a message arrives on a subscribed topic.

Explain how subscribing to control topics works on a Raspberry Pi and why it is useful.

Think about how your Pi can receive instructions remotely.

Describe the steps to write a simple Python program to subscribe to a control topic using MQTT on Raspberry Pi.

Focus on the main parts of the MQTT subscription process.

Practice

1. What is the main purpose of subscribing to control topics on a Raspberry Pi using MQTT?

easy

A. To send commands from the Raspberry Pi to other devices

B. To update the Raspberry Pi operating system automatically

C. To store data locally on the Raspberry Pi

D. To listen and react to control commands sent to the Raspberry Pi

Solution

1. Step 1: Understand MQTT subscription

   Subscribing means the Raspberry Pi listens to messages on a topic.

2. Step 2: Identify the purpose of control topics

   Control topics send commands that the Raspberry Pi should react to.

3. Final Answer:

   To listen and react to control commands sent to the Raspberry Pi -> Option D

4. Quick Check:

   Subscribing = Listening to commands [OK]

Hint: Subscribing means listening, not sending commands [OK]

Common Mistakes:

• Confusing subscribing with publishing
• Thinking subscription stores data
• Assuming it updates the OS

2. Which of the following is the correct Python syntax to subscribe to an MQTT topic named "home/lights/control" using the Paho MQTT client?

easy

A. client.connect("home/lights/control")

B. client.sub("home/lights/control")

C. client.subscribe("home/lights/control")

D. client.listen("home/lights/control")

Solution

1. Step 1: Recall Paho MQTT subscribe method

   The method to subscribe to a topic is subscribe().

2. Step 2: Match the correct syntax

   Using client.subscribe("home/lights/control") is correct syntax.

3. Final Answer:

   client.subscribe("home/lights/control") -> Option C

4. Quick Check:

   Subscribe method is subscribe() [OK]

Hint: Subscribe uses .subscribe(), not .sub() or .listen() [OK]

Common Mistakes:

• Using .sub() instead of .subscribe()
• Confusing subscribe with connect
• Using non-existent methods like .listen()

3. Given the following code snippet, what will be printed when a message with payload "ON" is received on the topic "home/lights/control"?

def on_message(client, userdata, message):
    if message.payload.decode() == "ON":
        print("Turning lights ON")
    else:
        print("Turning lights OFF")

client.subscribe("home/lights/control")
client.on_message = on_message

medium

A. Turning lights ON

B. Turning lights OFF

C. No output

D. Error: decode() not found

Solution

1. Step 1: Decode the message payload

   The payload is decoded to string and compared to "ON".

2. Step 2: Check the condition and print output

   Since payload is "ON", it prints "Turning lights ON".

3. Final Answer:

   Turning lights ON -> Option A

4. Quick Check:

   Payload "ON" triggers print "Turning lights ON" [OK]

Hint: Decode payload before comparing strings [OK]

Common Mistakes:

• Not decoding payload before comparison
• Assuming no output without explicit print
• Thinking decode() causes error

4. Identify the error in this MQTT subscription code snippet for Raspberry Pi:

def on_message(client, userdata, message):
    print(message.payload)

client.on_message = on_message
client.subscribe("home/lights/control")
client.loop_start()

medium

A. Incorrect callback function name

B. Missing client.connect() before subscribing

C. Using loop_start() instead of loop_forever()

D. No error, code is correct

Solution

1. Step 1: Check connection setup

   Before subscribing, the client must connect to the MQTT broker.

2. Step 2: Identify missing connect call

   The code lacks client.connect() call, so subscription won't work.

3. Final Answer:

   Missing client.connect() before subscribing -> Option B

4. Quick Check:

   Must connect before subscribe [OK]

Hint: Always connect client before subscribing [OK]

Common Mistakes:

• Skipping client.connect() call
• Confusing callback function names
• Thinking loop_start() is wrong here

5. You want your Raspberry Pi to subscribe to multiple control topics: "home/lights/control" and "home/thermostat/control". Which code snippet correctly subscribes to both and handles messages differently based on the topic?

hard

A. client.subscribe(["home/lights/control", "home/thermostat/control"])
def on_message(client, userdata, message):
topic = message.topic
if topic == "home/lights/control":
print("Light control received")
elif topic == "home/thermostat/control":
print("Thermostat control received")
client.on_message = on_message

B. client.subscribe("home/lights/control")
client.subscribe("home/thermostat/control")
def on_message(client, userdata, message):
if message.payload == "light":
print("Light control")
else:
print("Thermostat control")
client.on_message = on_message

C. client.subscribe("home/lights/control", "home/thermostat/control")
def on_message(client, userdata, message):
print("Control received")
client.on_message = on_message

D. client.subscribe("home/lights/control")
def on_message(client, userdata, message):
print("Control received")
client.on_message = on_message
client.subscribe("home/thermostat/control")

Solution

1. Step 1: Subscribe to multiple topics correctly

   client.subscribe(["home/lights/control", "home/thermostat/control"]) def on_message(client, userdata, message): topic = message.topic if topic == "home/lights/control": print("Light control received") elif topic == "home/thermostat/control": print("Thermostat control received") client.on_message = on_message uses a list to subscribe to both topics at once, which is valid.

2. Step 2: Handle messages based on topic

   The on_message function checks message.topic to differentiate actions.

3. Final Answer:

   correctly subscribes to both topics and handles them separately -> Option A

4. Quick Check:

   Subscribe list + topic check = correct [OK]

Hint: Subscribe with list and check message.topic [OK]

Common Mistakes:

• Passing multiple topics as separate arguments
• Checking payload instead of topic for routing
• Subscribing after setting callback incorrectly