---
title: "MQTT Broker"
description: "Run the MQTT broker directly on the TapHome controller: set port, client ID prefix, user and password, then connect Shelly, Tasmota or Zigbee2MQTT locally."
url: "https://taphome.com/en/docs/integration/packet-parser/mqtt-broker/"
language: en
lastmod: 2026-11-06
generator: hugo
ai:
  topics: ["mqtt","mqtt-broker","iot-integration","packet-parser","publish-subscribe","third-party-devices"]
  questions: ["What is MQTT and how does the publish/subscribe model work?","How do I enable MQTT Broker in TapHome?","How to integrate Shelly devices with TapHome using MQTT?","Where do I configure MQTT Broker port, username and password?","How do MQTT topic wildcards like # work?","Does TapHome MQTT Broker work locally without cloud?","What third-party devices can I connect via MQTT?"]
---

# MQTT Broker

Introduction to the MQTT protocol and activation of MQTT Broker service in TapHome system for communication with third-party devices.

Last updated: 2026-11-06

TapHome can run an MQTT broker directly on its controller, so third-party devices such as Shelly, Zigbee2MQTT or Tasmota can exchange messages with TapHome through publish/subscribe topics. You activate it in **Settings** → **Hardware** by entering a port number, client ID prefix, username and password. All communication stays in your network and no data is sent to the cloud. After activation, you define the MQTT communication in **Hardware** → Packet parser.

## What is MQTT?

**MQTT (Message Queuing Telemetry Transport)** is a lightweight publish/subscribe communication protocol specifically designed for the Internet of Things (IoT) and Machine-to-Machine (M2M) communication.

### Basic MQTT Concepts

**Publish/Subscribe Model:**
- Unlike traditional client-server communication, MQTT uses a model where devices don't need to know each other's addresses
- Devices communicate through a central point - the MQTT Broker
- One device **publishes** messages to a specific **topic**
- Other devices **subscribe** to these topics and automatically receive messages

**Topics:**
- An organizational structure for messages, similar to folders in a file system
- Example: `home/living_room/temperature`, `home/kitchen/light/status`
- Devices can subscribe to specific topics or use wildcards (`home/#` = everything in home)

**MQTT Advantages:**
- Extremely low data and energy consumption
- Works on slow or unstable networks
- Simple to implement
- Scalable from small to large systems

## MQTT Broker in TapHome

MQTT Broker is a service for managing MQTT communication between devices. The Broker can be run on an external machine or directly on the TapHome controller.

**TapHome MQTT Broker functions as:**
- **Central mediator** for all MQTT messages in the system
- **Bridge** between TapHome and third-party devices (Shelly, Zigbee2MQTT, Tasmota, and others)
- **Local service** - all communication stays in your network, no data is sent to the cloud

## How to activate MQTT Broker in TapHome

1. Go to **Settings** → **Hardware** and select MQTT Broker
2. Enter configuration details including port number, client ID prefix, username, and password
3. Save the settings to activate the service

![MQTT Broker Configuration - Settings](https://taphome.com/documentation/compatibility/packet-parser/mqtt-broker-settings.jpeg)

## Configuration Details

After activation, the MQTT communication configuration is defined in **Hardware** → Packet parser.

![MQTT Broker Configuration - Application](https://taphome.com/documentation/compatibility/packet-parser/mqtt-broker-config.png)

## Practical Usage Example

**Scenario:** You have a Shelly device (smart plug) and want to integrate it into TapHome.

1. **Activate MQTT Broker** in TapHome (following the steps above)
2. **Configure the Shelly device** - in its web interface, enter the TapHome controller's IP address and MQTT broker port
3. **Create a Packet Parser module** in TapHome with MQTT protocol
4. **Set up MQTT topics** - for example, `shellies/shellyplug-s-12345/relay/0` for the relay state and `shellies/shellyplug-s-12345/relay/0/command` for relay control
5. **Device is connected** - now you can control Shelly through the TapHome app and create smart rules

**Result:** Shelly publishes its state to an MQTT topic, TapHome receives notifications about changes. When you want to turn Shelly on/off, TapHome publishes a command to the corresponding topic.

## Related Links

- [Manual Packet Parser Configuration](https://taphome.com/en/docs/integration/packet-parser/manual/)
- [Application Settings](https://taphome.com/en/docs/applications/settings/)