MQTT in Home Assistant
mqtt
part of Home Assistant since pre 0.7
The MQTT integration connects Home Assistant to MQTT brokers, enabling communication between devices over a local network. It is commonly used for home automation, sensor monitoring, and integrating IoT devices into smart home systems.
Typical uses
- Controlling smart home devices
- Monitoring sensors
- Automating scenes
- Integrating IoT devices
Facts about this integration
- Compatible with Home Assistant
- yes, official integration
- Connection
- Local, push – Talks to the device on your own network and is told about every change straight away.
- Setup
- in the user interface
- Kind
- Online service
- Quality scale
- Platinum – The highest level: fully typed, efficient and maintained to every rule of the project.
- Installations
- 263,552 (38.6 % of the installations that share statistics)
- Provides
- Alarm control panel, Binary sensor, Button, Camera, Climate, Cover, Date, Date and time, Device tracker, Diagnostics, Event, Fan, Humidifier, Image, Infrared, Lawn mower, Light, Lock, Notifications, Number, Scene, Select, Sensor, Siren, Switch, Tag scanner, Text, Time, Update, Vacuum, Valve, Water heater
- Maintained by
- @emontnemery, @jbouwh, @bdraco
- Python packages
paho-mqtt==2.1.0
Setup
- In Home Assistant open Settings → Devices & services.
- Click "Add integration" and search for MQTT.
- Follow the dialog – it asks for everything the integration needs.
The link goes through my.home-assistant.io and opens the setup dialog in your own instance – no address of ours is involved.
Matching add-ons
Add-ons that declare a connection to this integration in their own configuration.
Blueprints that use this integration
- Automation AWTRIX show entity
- Automation Controller - IKEA E2001/E2002 STYRBAR Remote control
- Automation Zigbee2MQTT - Tuya 4-Button Scene Switch
- Automation Controller - IKEA E1524/E1810 TRÅDFRI Wireless 5-Button Remote
- Automation Controller - IKEA E1743 TRÅDFRI On/Off Switch & Dimmer
- Automation Controller - IKEA E1744 SYMFONISK Rotary Remote
Known issues and fixes
5 open issues and 31 bug fixes in the last twelve months are recorded for MQTT in the Home Assistant issue tracker. If something does not work, update first: the most recent fix shipped with Home Assistant 2026.8.0.
Open
- open The MQTT integration cannot properly decode messages from Tasmota devices.
- open Vacuum area mappings created via MQTT-based vacuums do not get removed when no longer needed.
- open The MQTT integration incorrectly reports that the host is unavailable.
- open The MQTT retain toggle in automation settings is misleading about its behavior.
- open The MQTT integration sets an incorrect attribute for device tracker location names.
Fixed
- fixed in 2026.8.0 The MQTT integration now ignores empty JSON strings for IR signal payloads instead of causing errors.
- fixed in 2026.6.4 The MQTT discovery option was incorrectly added to entry data and has been removed.
- fixed in 2026.6.3 MQTT entities discovered through MQTT are no longer enabled if the user has disabled them manually.
- fixed in 2026.6.2 Reloading MQTT configurations now works even if the MQTT entry was not initially set up.
- fixed in 2026.6.1 Certificate files are now created before attempting to migrate MQTT configuration entries.
- fixed in 2026.6.1 The MQTT integration now correctly handles value templates for fan and siren subentries.
- fixed in 2026.6.0 The MQTT device tracker now logs attributes in the correct order.
- fixed in 2026.6.0 The MQTT device tracker now saves state changes when location accuracy updates occur.
- fixed in 2026.6.0 The MQTT protocol setting has been moved to the main configuration options.
- fixed in 2026.6.0 MQTT valve states are now reset correctly when positioned at intermediate points.
- fixed in 2026.5.2 MQTT device settings are now properly recalled when reconfiguring devices.
- fixed in 2026.5.2 MQTT device discovery now uses shared QoS and encoding options as intended.
Source: the issue tracker of Home Assistant, as of September 13, 2026. The sentences are written by a language model from the titles of the issues; the reports themselves are on GitHub.
Check a specific device for known problems in the product check →
Source of this entry: the official documentation of the integration
The description was written by a language model from the facts listed here, not taken from the documentation.
