Matter vs MQTT is one of the most common questions from people building a smart home in 2026, and the honest answer is that they are not really competitors. Matter is a standard for how consumer devices are discovered, secured and controlled on your local network; MQTT is a lightweight messaging protocol for moving data between any clients through a broker. This article explains both, compares them side by side, and shows how a Home Assistant setup can use each where it is strongest.
What Matter Is
Matter is an application-layer standard maintained by the Connectivity Standards Alliance and backed by the major smart home platforms. Its goals are practical: buy a light bulb, scan a QR code, and have it work with whichever ecosystem you use, locally and securely.
Key characteristics:
- IP-based. Matter runs over Wi-Fi, Ethernet and Thread (a low-power IPv6 mesh). Thread devices reach the rest of the network through a border router, often built into a smart speaker or hub.
- Standard device data model. A Matter light exposes defined clusters such as On/Off and Level Control. Any certified controller knows how to operate it without vendor-specific integrations.
- Commissioning and security built in. Devices are onboarded with a setup code, usually over Bluetooth LE, and receive certificates for that fabric.
- Multi-admin. One device can be controlled by several ecosystems at the same time.
- Local first. Control does not require a vendor cloud.
What Matter does not try to be is a general data pipeline. It is designed for controllers talking to devices on the same home network, not for streaming telemetry to remote services or connecting arbitrary software.
What MQTT Is
MQTT is a publish/subscribe messaging protocol standardised by OASIS. Clients connect to a broker, publish messages to topics, and subscribe to topics they care about. If the broker concept is new, our explainer on what an MQTT broker does covers the basics.
Key characteristics:
- Transport, not a device model. MQTT does not define what a "light" is. Payloads are bytes; topics and formats are up to you or the software you use.
- Runs anywhere TCP runs. Microcontrollers, servers, browsers via WebSocket, cloud services.
- Decoupled. Publishers and subscribers do not know about each other, which makes it easy to add dashboards, loggers and automations later.
- Local or remote. A broker can sit on your network or in the cloud.
In smart homes, MQTT is the glue behind Zigbee2MQTT, Tasmota, ESPHome (optionally), Shelly devices and countless DIY sensors.
Matter vs MQTT Side by Side
| Aspect | Matter | MQTT |
|---|---|---|
| Type | Device interoperability standard | Messaging protocol |
| Standards body | Connectivity Standards Alliance | OASIS |
| Device data model | Yes, standardised clusters | No, application-defined |
| Network | Wi-Fi, Ethernet, Thread (via border router) | Any TCP/IP network, TLS, WebSocket |
| Discovery and onboarding | QR or setup code, BLE commissioning | Manual configuration or conventions like Home Assistant discovery |
| Security model | Device certificates, per-fabric credentials | TLS plus broker credentials |
| Typical scope | Local home network | Local, cloud or both |
| Remote access | Via your controller or ecosystem | Directly, through an internet-reachable broker |
| Best for | Buying certified consumer devices that just work | DIY devices, telemetry, integrations, remote data |
| Certification | Required for the Matter logo | None; any client can connect |
Where Matter Wins
Matter is the better choice when you buy off-the-shelf devices and want them to work across ecosystems with minimal setup. Locks, thermostats, plugs and lights with Matter support can be added to Home Assistant, Apple Home, Google Home and Alexa at once, without vendor clouds in the loop. Thread-based Matter devices also bring low power and a self-healing mesh, which suits battery sensors.
For non-technical household members, the standard data model is a real advantage: a light behaves like a light in every app.
Where MQTT Wins
MQTT is the better choice when you build or modify devices, need data to leave the house, or want many independent programs to share the same events:
- An ESP32 sensor you wrote yourself is a few lines away from publishing to a broker; building a certified Matter device is a much larger project, even with SDK support.
- A cloud dashboard, a time-series database and Node-RED can all subscribe to the same topics without touching the device.
- Data from multiple sites, such as a holiday home or a parent's flat, can meet on one internet-reachable broker.
- Non-consumer equipment such as solar inverters, heat pumps or weather stations often speaks MQTT or can be bridged to it.
If you are designing those topics, our guide to smart home MQTT topic structure gives a layout that scales.
How Matter and MQTT Coexist in Home Assistant
Home Assistant is the most common place where the two meet. It has a Matter integration that acts as a Matter controller, and an MQTT integration that connects to a broker. Inside Home Assistant both become ordinary entities, so automations can mix them freely. The Home Assistant MQTT guide covers the MQTT side, including pointing it at an external MQTT broker.
The interesting part is moving data out of Matter devices. Matter itself is local, so if you want a Matter thermostat's readings in a cloud dashboard or another site, Home Assistant can republish its state to MQTT. The built-in mqtt_statestream integration does this with a few lines of YAML:
# configuration.yaml
mqtt_statestream:
base_topic: home1/statestream
publish_attributes: true
publish_timestamps: true
include:
entity_globs:
- sensor.living_room_*
- climate.*
Each included entity's state then appears on a topic such as home1/statestream/climate/living_room/state. For more control over format, use an automation with the MQTT publish action:
automation:
- alias: "Publish Matter thermostat to MQTT"
triggers:
- trigger: state
entity_id: climate.living_room
actions:
- action: mqtt.publish
data:
topic: home1/livingroom/thermostat/state
retain: true
payload: >
{"current": {{ state_attr('climate.living_room', 'current_temperature') }},
"target": {{ state_attr('climate.living_room', 'temperature') }},
"mode": "{{ states('climate.living_room') }}"}
The reverse also works: an automation triggered by an MQTT message can call a service on a Matter device, so a DIY wall panel publishing over MQTT can switch a Matter light.
Testing the Bridge with a Public Broker
Before pointing Home Assistant at a private broker, you can watch the flow on the public test broker with a random prefix. Configure the MQTT integration with broker broker.connectmq.com, port 1883, a unique client ID and no credentials, change the base_topic to something like connectmq/demo/m6t3w1/statestream, then watch:
mosquitto_sub -h broker.connectmq.com -p 1883 -i watch-m6t3w1 -t "connectmq/demo/m6t3w1/#" -v
Remember that the public area is readable by anyone who guesses your topic, so use it only with test entities, never with locks, alarms or presence data. Our page on the free public MQTT broker lists its limits.
Decision Guide
- Buying consumer devices for everyday control? Prefer Matter, ideally over Thread for battery devices.
- Building your own sensors or controllers? Use MQTT.
- Need data outside the home network? Use MQTT, with Home Assistant bridging Matter states if needed.
- Multiple software consumers for the same data? MQTT's publish/subscribe model fits.
- Existing Zigbee or Z-Wave devices? Bridge them to MQTT or Home Assistant; see Zigbee vs Wi-Fi for MQTT smart homes.
In practice most advanced homes end up with both: Matter for certified devices, MQTT as the data backbone.
A Reliable Broker for the MQTT Side
When the MQTT side of the house grows to include remote sites, cloud dashboards or phone access, a broker you do not have to maintain becomes attractive. ConnectMQ is a hosted MQTT broker with TLS on port 8883, secure WebSocket on 8084 and a live topic explorer, and Home Assistant connects to it like any other broker. For a comparison of hosting approaches see the cloud MQTT broker guide, and for more projects browse the IoT automation guide.
Connect Home Assistant to ConnectMQ
Create a free Serverless broker at app.connectmq.com, no credit card required, enter the generated credentials in the Home Assistant MQTT integration with TLS enabled, and start streaming Matter and DIY device states to your ConnectMQ broker.
Frequently Asked Questions
Is Matter replacing MQTT?
No. Matter standardises how consumer devices are controlled on a local network, while MQTT moves messages between any software and devices. They solve different problems and often run side by side.
Can a Matter device publish to MQTT directly?
Not as part of the Matter standard. A controller such as Home Assistant reads the Matter device and republishes its state to MQTT through mqtt_statestream or an automation.
Should I build my DIY sensors with Matter or MQTT?
MQTT is far simpler for DIY devices and lets you send data anywhere. Matter makes sense for products that need to work in every consumer ecosystem.
Does Matter need the internet?
No. Matter is designed for local control. Remote access goes through your controller or ecosystem app, which is where an internet-reachable MQTT broker can complement it.
