Last Will and Testament (LWT) in IOT Protocols - Mini Project: Build & Apply

Last Will and Testament (LWT) in MQTT

📖 Scenario: You are setting up a simple MQTT client that needs to notify others if it disconnects unexpectedly. This is done using the Last Will and Testament (LWT) feature of MQTT. Think of it like leaving a note for your friends to know you left suddenly.

🎯 Goal: Build a small MQTT client configuration that sets up a Last Will and Testament message. This message will be published automatically by the broker if the client disconnects without warning.

📋 What You'll Learn

Create a dictionary called mqtt_client with basic client info

Add a will_message dictionary with topic, payload, qos, and retain keys

Assign the will_message dictionary to the mqtt_client under the key last_will

Print the mqtt_client dictionary to show the full configuration

💡 Why This Matters

🌍 Real World

MQTT clients use Last Will and Testament messages to notify other devices if they disconnect unexpectedly, which is important in home automation and IoT monitoring.

💼 Career

Understanding LWT helps in configuring reliable IoT systems and troubleshooting unexpected device disconnections in real-world deployments.

1

Create MQTT client dictionary

Create a dictionary called mqtt_client with these exact entries: 'client_id': 'client123' and 'clean_session': true.

IOT Protocols

# Create the mqtt_client dictionary with client_id and clean_session
# Your code here

Hint

Use curly braces to create a dictionary with the exact keys and values.

2

Define the Last Will message

Create a dictionary called will_message with these exact entries: 'topic': 'status/lastwill', 'payload': 'Client disconnected unexpectedly', 'qos': 1, and 'retain': false.

IOT Protocols

mqtt_client = {'client_id': 'client123', 'clean_session': True}
# Create the will_message dictionary with topic, payload, qos, and retain
# Your code here

Hint

Remember to use the exact keys and values as strings or numbers.

3

Attach the Last Will to the client

Add the will_message dictionary to the mqtt_client dictionary under the key 'last_will'.

IOT Protocols

mqtt_client = {'client_id': 'client123', 'clean_session': True}
will_message = {'topic': 'status/lastwill', 'payload': 'Client disconnected unexpectedly', 'qos': 1, 'retain': False}
# Add will_message to mqtt_client under 'last_will'
# Your code here

Hint

Use the dictionary key assignment syntax to add the will_message.

4

Display the MQTT client configuration

Write a print statement to display the mqtt_client dictionary.

IOT Protocols

mqtt_client = {'client_id': 'client123', 'clean_session': True}
will_message = {'topic': 'status/lastwill', 'payload': 'Client disconnected unexpectedly', 'qos': 1, 'retain': False}
mqtt_client['last_will'] = will_message
# Print the mqtt_client dictionary
# Your code here

Hint

Use print(mqtt_client) to show the full dictionary.

Practice

1. What is the main purpose of the Last Will and Testament (LWT) in MQTT?

easy

A. To notify other clients if a device disconnects unexpectedly

B. To encrypt messages between devices

C. To store messages for offline clients

D. To authenticate devices connecting to the broker

Solution

1. Step 1: Understand LWT role in MQTT

   LWT is a message set by a client to be sent by the broker if the client disconnects unexpectedly.

2. Step 2: Identify the purpose of LWT

   This helps notify other clients about the unexpected disconnection, improving system reliability.

3. Final Answer:

   To notify other clients if a device disconnects unexpectedly -> Option A

4. Quick Check:

   LWT notifies disconnections [OK]

Hint: LWT alerts others when a device drops connection unexpectedly [OK]

Common Mistakes:

• Confusing LWT with message encryption
• Thinking LWT stores messages for offline clients
• Assuming LWT is for device authentication

2. Which MQTT client method is used to set the Last Will and Testament (LWT) message when connecting?

easy

A. client.publish(topic, message)

B. client.subscribe(topic)

C. client.setWill(topic, message, qos, retain)

D. client.connect()

Solution

1. Step 1: Identify method to set LWT

   The method setWill is used to define the LWT message before connecting.

2. Step 2: Differentiate from other methods

   publish sends normal messages, subscribe listens to topics, and connect starts connection without setting LWT.

3. Final Answer:

   client.setWill(topic, message, qos, retain) -> Option C

4. Quick Check:

   Set LWT with setWill() method [OK]

Hint: LWT is set before connect using setWill() method [OK]

Common Mistakes:

• Using publish() to set LWT
• Trying to set LWT after connecting
• Confusing subscribe() with setting LWT

3. Given this MQTT client code snippet, what will happen if the client disconnects unexpectedly?

client.setWill('status/device1', 'offline', 1, true);
client.connect();

medium

A. The client reconnects automatically

B. The broker publishes 'offline' to 'status/device1' topic

C. The broker deletes the 'status/device1' topic

D. Nothing happens because LWT is not set

Solution

1. Step 1: Analyze setWill parameters

   The LWT is set to publish 'offline' on topic 'status/device1' with QoS 1 and retain flag true.

2. Step 2: Understand broker behavior on unexpected disconnect

   If the client disconnects unexpectedly, the broker sends the LWT message to the specified topic.

3. Final Answer:

   The broker publishes 'offline' to 'status/device1' topic -> Option B

4. Quick Check:

   LWT message sent on unexpected disconnect [OK]

Hint: LWT message publishes on unexpected disconnect [OK]

Common Mistakes:

• Assuming client auto reconnects
• Thinking broker deletes topics on disconnect
• Believing LWT is not set here

4. Identify the error in this MQTT client code snippet related to LWT setup:

client.connect({
  will: {
    topic: 'device/status',
    payload: 'offline'
  }
});

medium

A. Payload should be a JSON object, not string

B. Incorrect topic name format

C. LWT must be set after connecting

D. Missing QoS and retain flags in LWT configuration

Solution

1. Step 1: Review LWT configuration fields

   MQTT LWT requires topic, payload, QoS, and retain flags to be set for proper behavior.

2. Step 2: Identify missing fields

   The code sets topic and payload but omits QoS and retain, which are important for message delivery and persistence.

3. Final Answer:

   Missing QoS and retain flags in LWT configuration -> Option D

4. Quick Check:

   LWT needs QoS and retain flags [OK]

Hint: Always include QoS and retain when setting LWT [OK]

Common Mistakes:

• Ignoring QoS and retain flags
• Setting LWT after connect call
• Assuming payload must be JSON

5. You want to monitor device connectivity using LWT. Which combination of settings ensures the broker retains the last known status and notifies subscribers if the device disconnects unexpectedly?

hard

A. Set LWT with retain=true and QoS=1; publish online status with retain=true

B. Set LWT with retain=false and QoS=0; publish online status without retain

C. Set LWT with retain=true and QoS=0; publish online status with retain=false

D. Set LWT with retain=false and QoS=1; publish online status with retain=true

Solution

1. Step 1: Understand retain flag usage

   Retain=true ensures the broker keeps the last message on the topic for new subscribers.

2. Step 2: Understand QoS role in LWT

   QoS=1 guarantees message delivery at least once, important for reliable LWT notification.

3. Step 3: Combine settings for monitoring

   Publishing online status with retain=true keeps current status; LWT with retain=true and QoS=1 ensures offline status is sent reliably and retained.

4. Final Answer:

   Set LWT with retain=true and QoS=1; publish online status with retain=true -> Option A

5. Quick Check:

   Retain and QoS=1 for LWT and status [OK]

Hint: Use retain=true and QoS=1 for reliable LWT and status messages [OK]

Common Mistakes:

• Setting retain=false loses last status message
• Using QoS=0 risks missing LWT delivery
• Not retaining online status message