Last updated on March 31, 2026
The MQTT broker is the central nervous system of any modern smart home, acting as the communications hub for all your IoT devices. In Home Assistant, the gold standard is the Mosquitto broker, but a common configuration snag can bring your entire system to a grinding halt: a startup failure due to a port conflict. This guide, fully updated for 2026, is your definitive resource for diagnosing and fixing any Home Assistant MQTT Broker Error, ensuring your smart home runs flawlessly.
While the original inspiration for this post focused on a specific issue with an older Home Assistant OS version, the core problem—port conflicts—remains as relevant today as ever. Let’s walk through the modern, clean, and efficient methods to resolve it.
Diagnosing the Problem: The “Error: Cannot create listener…” Log Message
The most common symptom is finding an error message in your Mosquitto broker logs that looks exactly like this:
Error: Cannot create listener on port 1883.
Error: Cannot create listener on port 1884.This error message is crystal clear: the broker tried to start and claim its default ports (1883 for standard MQTT and 1884 for WebSockets), but found another process or service was already using them. In 2026, with the proliferation of Home Assistant Apps (formerly known as Add-ons) that can bundle their own servers, this is an increasingly common scenario.
The 2026 Fix: Changing The MQTT Port Through the UI
Gone are the days of manually editing YAML files for this. Home Assistant has evolved, and managing Apps is now a much more visual and intuitive process. If you’re facing a port conflict, the cleanest solution is to simply assign a new one to Mosquitto.
Follow these steps:
- Navigate to Settings > Apps in your Home Assistant dashboard.
- Find and select the “Mosquitto broker” App.
- Go to the “Configuration” tab.
- You’ll see the exposed network ports here. Locate the port that’s causing the issue (e.g., 1883 or 1884) and change it to a number you know is free. For instance, you could try changing
1884to1885. - Click “Save” and restart the Mosquitto App.
Once it restarts, check the App’s log. If the error is gone, you’ve solved the problem! Just remember to update the configuration of your client devices (like those running Tasmota or ESPHome) to point to the new port.
Advanced Troubleshooting: How to Hunt Down Port Conflicts
If changing the port doesn’t work, or you’re just curious about what’s causing the conflict in the first place, you can use the terminal to investigate. You’ll need the “Terminal & SSH” App installed from the App store for this.
- Open the terminal in Home Assistant.
- Run the following command to see all services that are “listening” on various ports:
netstat -tulpn | grep LISTEN - Examine the output. Look for lines containing the conflicting ports, like
:1883or:1884. The “Program name/PID” column will tell you exactly which process is occupying that port.
With this information, you can identify if another App, like Zigbee2MQTT or Z-Wave JS UI, has enabled its own internal MQTT broker, causing the conflict. In that case, the solution is to either disable the internal broker in that App or change its port, leaving the default free for your main Mosquitto instance.
What About Downgrading? A Hard Pass in 2026
Older articles might have suggested downgrading Home Assistant OS as a fix. In 2026, this is a terrible idea. Rolling back your OS version can expose you to patched security vulnerabilities, cause system-wide instability, and break compatibility with newer versions of Home Assistant Core and other Apps. It should only be considered an absolute last-ditch effort in a catastrophic failure scenario, and even then, you’re playing with fire.
Mosquitto Broker Alternatives in 2026
While Mosquitto is the de facto standard, other valid options exist in 2026, especially those that come bundled with popular tools. Here’s a quick breakdown:
| Broker | Pros | Cons |
|---|---|---|
| Mosquitto Broker (Official App) | The gold standard. Rock-solid, highly configurable, stable, and seamlessly integrates with Home Assistant users. | Requires a dedicated App. Can lead to port conflicts if other services aren’t configured correctly. |
| Zigbee2MQTT’s Built-in Broker | Comes integrated, simplifying installation if your main use is for Zigbee. Zero-fuss setup. | Lacks the power and fine-grained control of Mosquitto. Not ideal if you have many non-Zigbee devices that rely on MQTT. |
| EMQX (Community App) | An absolute powerhouse. Extremely scalable and perfect for very large or complex installations. Includes a comprehensive management dashboard. | Complete overkill for the average smart home. Consumes more system resources than Mosquitto. |
MQTT Broker Errors: Frequently Asked Questions (FAQ)
What are the default MQTT ports?
The standard ports are: 1883 for unencrypted MQTT communication, 8883 for MQTT over TLS/SSL (encrypted), and 1884 for communication via WebSockets.
I changed the port, but my devices won’t connect. What’s wrong?
You must update the configuration of each client device (Tasmota, ESPHome, etc.) to point to your Home Assistant’s IP address and the new port you just configured. If you don’t, they’ll keep trying to connect to the old port and fail.
Do I need an MQTT broker if I only use ZHA for my Zigbee devices?
No. The native ZHA (Zigbee Home Automation) integration communicates directly with your Zigbee coordinator hardware without needing an MQTT middleman. You only need a broker if you’re using Zigbee2MQTT or have other IoT devices that depend on the protocol.
How do I set up MQTT in Home Assistant from scratch?
The process is pretty straightforward. First, you install the “Mosquitto broker” App. Then, in Settings > Devices & Services, you add the “MQTT” integration, which will automatically discover and configure itself to use the broker you just installed. For a complete walkthrough, check out my ultimate guide to installing and configuring the Mosquitto Broker in Home Assistant.