Last Will and Testament (LWT) in IOT Protocols - Step-by-Step Execution

Process Flow - Last Will and Testament (LWT)

Client Connects to Broker

↓

Client Sets LWT Message

↓

Client Publishes LWT on Unexpected Disconnect

↓

Broker Sends LWT to Subscribers

↓

Subscribers Receive LWT Message

↓

End

This flow shows how a client sets a Last Will message when connecting, which the broker sends to subscribers if the client disconnects unexpectedly.

Execution Sample

IOT Protocols

client.connect(broker, will_topic, will_message)
# Client connects and sets LWT

# Unexpected disconnect occurs
client.disconnect(unexpected=True)

# Broker publishes LWT to subscribers

This code connects a client to a broker with an LWT message, then simulates an unexpected disconnect causing the broker to publish the LWT.

Process Table

Step	Action	Client State	Broker Action	Subscribers Receive
1	Client connects and sets LWT	Connected, LWT set	Stores LWT for client	None
2	Client operates normally	Connected	No action	None
3	Client disconnects unexpectedly	Disconnected unexpectedly	Publishes LWT message	Receives LWT message
4	Subscribers process LWT	N/A	N/A	Handle client offline notification
5	Client reconnects normally	Connected, LWT reset	Updates LWT	None

💡 Client reconnects or stays disconnected; LWT sent only on unexpected disconnect

Status Tracker

Variable	Start	After Step 1	After Step 3	After Step 5
Client Connection	Disconnected	Connected	Disconnected unexpectedly	Connected
LWT Message Stored	None	Set	Published	Reset or Updated
Subscribers Notification	None	None	Received LWT	None

Key Moments - 2 Insights

Why does the broker send the LWT message only on unexpected disconnects?

Because the LWT is designed to notify subscribers only if the client disconnects without telling the broker properly, as shown in step 3 of the execution_table.

What happens to the LWT message when the client reconnects normally?

The LWT is reset or updated with the new connection, so no LWT message is sent, as seen in step 5 of the execution_table.

Visual Quiz - 3 Questions

Look at the execution_table, at which step does the broker publish the LWT message?

A Step 1

B Step 4

C Step 3

D Step 5

💡 Hint

Check the 'Broker Action' column for when the LWT is published.

According to variable_tracker, what is the client connection state after step 3?

A Disconnected unexpectedly

B Connected

C Disconnected normally

D Connecting

💡 Hint

Look at the 'Client Connection' row under 'After Step 3'.

If the client disconnects normally instead of unexpectedly, what would change in the execution_table?

A Subscribers would receive LWT message

B Broker would not publish LWT message

C Broker would still publish LWT message

D Client state would be 'Disconnected unexpectedly'

💡 Hint

Refer to the exit_note and step 3 where unexpected disconnect triggers LWT.

Concept Snapshot

Last Will and Testament (LWT) in IoT:
- Client sets LWT message on connect
- Broker stores LWT for client
- If client disconnects unexpectedly, broker publishes LWT
- Subscribers receive LWT as offline notification
- Normal disconnect or reconnect resets LWT

Full Transcript

The Last Will and Testament (LWT) is a special message a client sets when connecting to an IoT broker. It tells the broker what to send to other clients if this client disconnects without warning. The flow starts with the client connecting and setting the LWT. If the client disconnects unexpectedly, the broker publishes the LWT message to subscribers. Subscribers then know the client is offline unexpectedly. If the client disconnects normally or reconnects, the LWT is reset and no message is sent. This helps keep all devices informed about unexpected offline events.

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