MQTT broker setup (Mosquitto) in Raspberry Pi - Step-by-Step Execution

Concept Flow - MQTT broker setup (Mosquitto)

Install Mosquitto

↓

Start Mosquitto service

↓

Configure Mosquitto (optional)

↓

Broker listens on port 1883

↓

Clients connect and exchange messages

↓

Broker routes messages to subscribers

↓

End

This flow shows the steps to install, start, configure, and run the Mosquitto MQTT broker on a Raspberry Pi.

Execution Sample

Raspberry Pi

sudo apt update
sudo apt install mosquitto mosquitto-clients
sudo systemctl start mosquitto
sudo systemctl enable mosquitto
sudo systemctl stop mosquitto && mosquitto -v

This code installs Mosquitto, starts the broker service, enables it to start on boot, stops the service, and runs it in verbose foreground mode.

Execution Table

Step	Command	Action	Result
1	sudo apt update	Update package list	Package list updated
2	sudo apt install mosquitto mosquitto-clients	Install Mosquitto broker and clients	Mosquitto installed
3	sudo systemctl start mosquitto	Start Mosquitto service	Mosquitto service running
4	sudo systemctl enable mosquitto	Enable Mosquitto to start on boot	Mosquitto enabled on boot
5	sudo systemctl stop mosquitto && mosquitto -v	Stop service and run in verbose mode	Broker listens on port 1883, verbose logs shown
6	Client connects	Client subscribes or publishes	Broker routes messages
7	Client disconnects	Connection closed	Broker waits for new clients

💡 Setup complete, broker running and ready for clients

Variable Tracker

Variable	Start	After Step 2	After Step 3	After Step 4	After Step 5	Final
Mosquitto Service Status	Not installed	Installed but stopped	Running	Running and enabled	Running verbose	Running and ready

Key Moments - 3 Insights

Why do we run 'sudo systemctl enable mosquitto' after starting the service?

Starting the service runs it now, but enabling it makes sure Mosquitto starts automatically after reboot, as shown in execution_table step 4.

What does 'mosquitto -v' do differently than just starting the service?

'mosquitto -v' runs the broker in the foreground with verbose logging, so you can see messages and connections live, as in step 5.

Why is port 1883 important in this setup?

Port 1883 is the default MQTT port where the broker listens for client connections, mentioned in the concept_flow and step 5.

Visual Quiz - 3 Questions

Look at the execution_table, what is the Mosquitto service status after step 3?

A Running

B Stopped

C Not installed

D Enabled on boot

💡 Hint

Check the 'Result' column for step 3 in the execution_table.

At which step does Mosquitto get enabled to start automatically on boot?

A Step 2

B Step 4

C Step 3

D Step 5

💡 Hint

Look for the command 'sudo systemctl enable mosquitto' in the execution_table.

If you skip 'sudo systemctl start mosquitto', what will happen when you run 'mosquitto -v'?

A Broker will fail to start

B Broker will start but no logs shown

C Broker will start in verbose mode anyway

D Broker will start as a background service

💡 Hint

Step 5 shows 'mosquitto -v' runs the broker in verbose mode independently.

Concept Snapshot

MQTT Broker Setup with Mosquitto on Raspberry Pi:
1. Update packages: sudo apt update
2. Install Mosquitto: sudo apt install mosquitto mosquitto-clients
3. Start broker: sudo systemctl start mosquitto
4. Enable auto-start: sudo systemctl enable mosquitto
5. Stop service & run verbose: sudo systemctl stop mosquitto && mosquitto -v
Broker listens on port 1883 for client connections.

Full Transcript

This visual execution shows how to set up the Mosquitto MQTT broker on a Raspberry Pi. First, you update the package list to get the latest software versions. Then, you install Mosquitto and its client tools. After installation, you start the Mosquitto service so the broker runs in the background. To make sure Mosquitto starts automatically after the Raspberry Pi reboots, you enable it with systemctl. Then you stop the service and run 'mosquitto -v' in verbose foreground mode, showing live logs and confirming it listens on port 1883. Clients can then connect, publish, and subscribe to messages through the broker. The variable tracker shows the Mosquitto service status changing from not installed to running and enabled. Key moments clarify why enabling the service is important, what verbose mode does, and the significance of port 1883. The quiz tests understanding of service status, enabling steps, and running the broker in verbose mode.

Practice

1. What is the primary role of the Mosquitto MQTT broker on a Raspberry Pi?

easy

A. To receive and forward messages between devices

B. To act as a web server for hosting websites

C. To store large files for backup

D. To compile Python programs

Solution

1. Step 1: Understand MQTT broker function

   The MQTT broker acts as a middleman that receives messages from one device and forwards them to others subscribed to the same topic.

2. Step 2: Compare with other options

   The other options describe unrelated functions like web hosting, file storage, and compiling, which are not roles of Mosquitto.

3. Final Answer:

   To receive and forward messages between devices -> Option A

4. Quick Check:

   MQTT broker = message forwarding [OK]

Hint: Broker forwards messages between devices [OK]

Common Mistakes:

• Confusing broker with web server
• Thinking Mosquitto stores files
• Assuming it compiles code

2. Which command correctly installs Mosquitto on a Raspberry Pi running Raspberry Pi OS?

easy

A. install mosquitto sudo

B. sudo mosquitto install apt-get

C. mosquitto install sudo apt-get

D. sudo apt-get install mosquitto

Solution

1. Step 1: Recall correct package installation syntax

   On Raspberry Pi OS, the correct command to install a package is 'sudo apt-get install package-name'. Here, the package is mosquitto.

2. Step 2: Check each option's syntax

   Only sudo apt-get install mosquitto follows the correct syntax. The other options have incorrect word order or missing keywords.

3. Final Answer:

   sudo apt-get install mosquitto -> Option D

4. Quick Check:

   Install command = sudo apt-get install [OK]

Hint: Use 'sudo apt-get install mosquitto' exactly [OK]

Common Mistakes:

• Mixing command word order
• Omitting 'sudo' or 'install'
• Using incorrect package manager commands

3. After installing Mosquitto, you run the command mosquitto_sub -h localhost -t test/topic in one terminal and mosquitto_pub -h localhost -t test/topic -m "Hello" in another. What will appear in the subscriber terminal?

medium

A. Error: Connection refused

B. Hello

C. mosquitto_sub

D. test/topic

Solution

1. Step 1: Understand subscriber and publisher commands

   The subscriber listens on topic 'test/topic' on localhost. The publisher sends message 'Hello' to the same topic.

2. Step 2: Predict subscriber output

   The subscriber will receive and display the message 'Hello' published to 'test/topic'. No error occurs if Mosquitto is running.

3. Final Answer:

   Hello -> Option B

4. Quick Check:

   Subscriber shows published message [OK]

Hint: Subscriber shows message sent to its topic [OK]

Common Mistakes:

• Expecting topic name instead of message
• Confusing command names with output
• Assuming connection error without checking broker status

4. You try to start Mosquitto with sudo systemctl start mosquitto but get an error saying the service is not found. What is the likely cause?

medium

A. Mosquitto is not installed or service not enabled

B. You need to run the command without sudo

C. The Raspberry Pi is out of storage space

D. The MQTT topic name is incorrect

Solution

1. Step 1: Analyze the error message

   The error 'service not found' means the system does not recognize the mosquitto service, usually because it is not installed or the service is not enabled.

2. Step 2: Evaluate other options

   Running without sudo won't help as service commands require sudo. Storage space or topic name do not affect service recognition.

3. Final Answer:

   Mosquitto is not installed or service not enabled -> Option A

4. Quick Check:

   Service error = missing install or enable [OK]

Hint: Check if Mosquitto is installed and service enabled [OK]

Common Mistakes:

• Trying without sudo
• Blaming storage space
• Confusing service error with topic issues

5. You want to allow remote devices to connect to your Mosquitto broker on Raspberry Pi. Which configuration change is necessary?

hard

A. Install a web server alongside Mosquitto

B. Change the MQTT topic to a public name

C. Edit /etc/mosquitto/mosquitto.conf to allow connections on all interfaces

D. Disable the Raspberry Pi firewall completely

Solution

1. Step 1: Identify how Mosquitto listens for connections

   By default, Mosquitto listens only on localhost (127.0.0.1). To allow remote devices, you must configure it to listen on all network interfaces.

2. Step 2: Understand configuration changes

   This is done by editing /etc/mosquitto/mosquitto.conf to set 'bind_address' or comment it out to listen on all interfaces. Changing topic names or installing web servers does not affect network access. Disabling firewall completely is unsafe and unnecessary if configured properly.

3. Final Answer:

   Edit /etc/mosquitto/mosquitto.conf to allow connections on all interfaces -> Option C

4. Quick Check:

   Config file change = allow remote connections [OK]

Hint: Edit config to listen on all interfaces [OK]

Common Mistakes:

• Changing topic names instead of network settings
• Thinking web server is needed
• Disabling firewall without proper rules