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.