Subscribing to control commands in IOT Protocols - Mini Project: Build & Apply

Subscribing to Control Commands

📖 Scenario: You are working on a smart home device that needs to listen for control commands sent from a central server. These commands tell the device to turn on or off lights, adjust temperature, or perform other actions.

🎯 Goal: Build a simple program that subscribes to a control command topic and processes incoming messages.

📋 What You'll Learn

Create a variable called topic with the exact value "home/device/control"

Create a variable called client_id with the exact value "device123"

Write a function called subscribe_to_topic that takes topic and client_id as parameters

Inside the function, print a message showing subscription to the topic with the client ID

Call the function with the variables topic and client_id

Print the message "Waiting for control commands..." after subscribing

💡 Why This Matters

🌍 Real World

Smart home devices and IoT gadgets often subscribe to control commands to perform actions remotely.

💼 Career

Understanding how to subscribe and listen for control commands is essential for IoT developers and DevOps engineers managing connected devices.

1

Create subscription variables

Create a variable called topic and set it to the string "home/device/control". Also create a variable called client_id and set it to the string "device123".

IOT Protocols

# Your code here

Hint

Use simple assignment to create the variables with the exact string values.

2

Define subscription function

Write a function called subscribe_to_topic that takes two parameters: topic and client_id. Inside the function, print the message "Subscribed to {topic} with client ID {client_id}" using an f-string.

IOT Protocols

topic = "home/device/control"
client_id = "device123"

# Your code here

Hint

Define the function with the exact name and parameters. Use an f-string to format the print message.

3

Call subscription function

Call the function subscribe_to_topic with the variables topic and client_id as arguments.

IOT Protocols

topic = "home/device/control"
client_id = "device123"

def subscribe_to_topic(topic, client_id):
    print(f"Subscribed to {topic} with client ID {client_id}")

# Your code here

Hint

Call the function with the exact variable names as arguments.

4

Print waiting message

After calling subscribe_to_topic, write a print statement that outputs exactly "Waiting for control commands...".

IOT Protocols

topic = "home/device/control"
client_id = "device123"

def subscribe_to_topic(topic, client_id):
    print(f"Subscribed to {topic} with client ID {client_id}")

subscribe_to_topic(topic, client_id)

# Your code here

Hint

Use a print statement with the exact text after the function call.

Practice

1. What is the main purpose of subscribing to control commands in IoT devices?

easy

A. To update the device firmware manually

B. To listen and respond automatically to commands sent from a controller

C. To send data continuously to the cloud

D. To disconnect the device from the network

Solution

1. Step 1: Understand the role of subscribing

   Subscribing means the device listens for messages or commands sent to it.

2. Step 2: Identify the purpose of control commands

   Control commands tell the device what actions to perform automatically.

3. Final Answer:

   To listen and respond automatically to commands sent from a controller -> Option B

4. Quick Check:

   Subscribing = Listening for commands [OK]

Hint: Subscribing means listening for commands to act automatically [OK]

Common Mistakes:

• Confusing subscribing with sending data
• Thinking subscribing updates firmware
• Assuming subscribing disconnects device

2. Which of the following is the correct syntax to subscribe to a topic named device/control using an MQTT client in Python?

easy

A. client.subscribe('device/control')

B. client.sub('device/control')

C. subscribe(client, 'device/control')

D. client.listen('device/control')

Solution

1. Step 1: Recall MQTT client subscription method

   The standard method to subscribe is client.subscribe(topic).

2. Step 2: Match the correct syntax

   client.subscribe('device/control') uses the correct method and topic string format.

3. Final Answer:

   client.subscribe('device/control') -> Option A

4. Quick Check:

   Subscribe method = client.subscribe(topic) [OK]

Hint: Use client.subscribe('topic') to subscribe in MQTT Python [OK]

Common Mistakes:

• Using incorrect method names like sub or listen
• Passing client as first argument to subscribe
• Using wrong topic string format

3. Given this Python MQTT subscription code snippet, what will be printed when a message with payload ON arrives on topic device/control?

def on_message(client, userdata, message):
    if message.payload.decode() == 'ON':
        print('Turning device ON')
    else:
        print('Unknown command')

client.subscribe('device/control')
client.on_message = on_message

medium

A. Turning device ON

B. Unknown command

C. Error: decode() not found

D. No output

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 output

   Since payload is 'ON', it matches the if condition and prints 'Turning device ON'.

3. Final Answer:

   Turning device ON -> Option A

4. Quick Check:

   Payload 'ON' triggers print 'Turning device ON' [OK]

Hint: Decode payload and compare string to decide output [OK]

Common Mistakes:

• Forgetting to decode payload bytes
• Assuming payload is already string
• Ignoring else branch output

4. Identify the error in this MQTT subscription code snippet that prevents receiving messages:

client = mqtt.Client()
client.on_message = on_message
client.subscribe('device/control')
client.loop_start()

medium

A. loop_start() should be loop_forever()

B. Incorrect topic name format

C. Missing client.connect() call before subscribing

D. on_message function not defined

Solution

1. Step 1: Check connection setup

   MQTT client must connect to broker before subscribing.

2. Step 2: Identify missing connect call

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

3. Final Answer:

   Missing client.connect() call before subscribing -> Option C

4. Quick Check:

   Connect before subscribe to receive messages [OK]

Hint: Always connect client before subscribing to topics [OK]

Common Mistakes:

• Skipping client.connect() call
• Assuming subscribe works without connection
• Confusing loop_start() with connection

5. You want your IoT device to subscribe to control commands on topic home/lights/command and turn lights ON or OFF accordingly. Which code snippet correctly subscribes and handles these commands in Python using MQTT?

hard

A. client = mqtt.Client()
client.connect('broker.hivemq.com')
client.subscribe('home/lights/command')
client.loop_forever()

B. client = mqtt.Client()
client.subscribe('home/lights/command')
client.on_message = lambda c,u,m: print('Lights ON' if m.payload == 'ON' else 'Lights OFF')
client.loop_start()

C. def on_message(client, userdata, message):
if message.payload == 'ON':
print('Lights ON')
client = mqtt.Client()
client.connect('broker.hivemq.com')
client.subscribe('home/lights/command')
client.on_message = on_message
client.loop_forever()

D. def on_message(client, userdata, message):
cmd = message.payload.decode()
if cmd == 'ON':
print('Lights ON')
elif cmd == 'OFF':
print('Lights OFF')
client = mqtt.Client()
client.connect('broker.hivemq.com')
client.subscribe('home/lights/command')
client.on_message = on_message
client.loop_forever()

Solution

1. Step 1: Verify subscription and connection

   def on_message(client, userdata, message): cmd = message.payload.decode() if cmd == 'ON': print('Lights ON') elif cmd == 'OFF': print('Lights OFF') client = mqtt.Client() client.connect('broker.hivemq.com') client.subscribe('home/lights/command') client.on_message = on_message client.loop_forever() connects to broker, subscribes to correct topic, and sets message handler.

2. Step 2: Check message handling logic

   It decodes payload and handles both 'ON' and 'OFF' commands properly.

3. Final Answer:

   Complete subscription with connection and proper message handling -> Option D

4. Quick Check:

   Connect, subscribe, decode payload, handle ON/OFF [OK]

Hint: Connect, subscribe, decode payload, handle commands in on_message [OK]

Common Mistakes:

• Not decoding payload bytes to string
• Missing client.connect() call
• Ignoring OFF command handling
• Not assigning on_message callback