Last Will and Testament (LWT) in IOT Protocols - Cheat Sheet & Quick Revision

Recall & Review

beginner

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

LWT is a message that a client sets up to be sent by the broker if the client disconnects unexpectedly. It informs other clients about the abnormal disconnection.

beginner

How does LWT help in IoT device communication?

LWT helps by notifying other devices or systems when a device goes offline unexpectedly, allowing them to take appropriate actions like alerts or failover.

intermediate

Which MQTT client action triggers the broker to send the LWT message?

The broker sends the LWT message when the client disconnects without sending a proper disconnect message, indicating an unplanned disconnection.

intermediate

What information is typically included in an LWT message?

An LWT message usually includes the topic, the message payload describing the disconnection, and the Quality of Service (QoS) level.

intermediate

Can LWT messages be customized by the MQTT client?

Yes, the MQTT client can customize the LWT message content, topic, and QoS when it connects to the broker.

What does LWT stand for in MQTT?

A Last Will and Testament

B Live Wireless Transmission

C Local Web Transport

D Last Wireless Token

LWT stands for Last Will and Testament, a message sent by the broker if a client disconnects unexpectedly.

When is the LWT message sent by the MQTT broker?

A When the client sends a proper disconnect message

B When the client publishes a message

C When the client disconnects unexpectedly

D When the broker restarts

The broker sends the LWT message only if the client disconnects without a proper disconnect message.

What is a common use of LWT in IoT devices?

A To update firmware automatically

B To notify other devices of unexpected disconnection

C To encrypt messages

D To schedule device tasks

LWT notifies other devices or systems when a device disconnects unexpectedly.

Can the content of an LWT message be changed by the client?

A Yes, the client sets it when connecting

B No, it is fixed by the broker

C Only the broker can change it

D It changes automatically based on network

The client can customize the LWT message content, topic, and QoS during connection setup.

Which MQTT feature is closely related to LWT?

A Last Will and Testament

B Clean session

C Retained messages

D Quality of Service (QoS)

LWT messages include a QoS level to control delivery guarantees.

Explain what Last Will and Testament (LWT) is and why it is important in MQTT communication.

Think about what happens if a device suddenly stops working without warning.

Describe how an MQTT client sets up an LWT message and what happens when the client disconnects unexpectedly.

Consider the steps from client connection to unexpected disconnection.

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