Home Assistant + MQTT: A Local Smart Home That Lasts

Home Assistant plus an MQTT broker is the closest thing to a permanent smart home. Devices integrate themselves, automations run locally, and no vendor shutdown can take your lights hostage. The key is MQTT discovery devices announce themselves.

At a glance: 8 minute guide · part 9 of 10 in the complete IoT and ESP32 guide track · includes a worked example and a quick-reference table.

Connecting the broker

Here is the working theory in one pass. Install the Mosquitto broker add-on, then configure Home Assistant's MQTT integration with the same credentials. The "Listen to a topic" debug panel becomes your oscilloscope for the whole home.

C	o	m	p	o	n	e	n	t
D	i	s	c	o	v	e	r	y		t	o	p	i	c		r	o	o	t
P	u	r	p	o	s	e
sensor	…/sensor/…	Measurements
switch	…/switch/…	Relay-controlled loads
button	…/button/…	Momentary triggers
binary_sensor	…/binary_sensor/…	Open/closed, motion
light	…/light/…	Brightness control

Discovery messages

Publish a retained JSON config to homeassistant///config and the entity appears no YAML, no reboots. A temperature sensor, a switch, a button. Each is one config message that names the state and command topics.

Designing device topics

Structure topics by room and device: home/livingroom/sensor1/state. Publish state on change plus retained, subscribe to set topics. With this discipline, replacing a device is editing one config message, not re-teaching the home.

How to apply this in your build

Work through the sequence below each step assumes the previous one passed. For numbers that need calculating, the linked tools at the end of this guide do the arithmetic instantly.

1. Run Mosquitto and connect Home Assistant with credentials
2. Write discovery configs with unique object IDs
3. Publish retained state and command topics from the device
4. Test each entity from the UI before automating anything

Worked example

An ESP32 relay publishes a switch discovery message once (retained). It survives broker restarts, reappears after Home Assistant updates. Answers commands in under 100 ms on the LAN. Run the numbers yourself with the related calculator and the result should agree to within rounding.

Practical note from the bench. Our reference smart-home build wires every DIY device through discovery topics adding the tenth sensor takes minutes because the first nine enforced the pattern.

Pitfalls that cost real hardware

• Non-retained discovery devices vanish on broker restart
• Colliding object IDs silently merging entities
• Automating before validating raw topics in the debug panel

Key takeaways

• Connecting the broker the foundation of this guide; revisit it if any measurement here surprises you.
• Discovery messages the foundation of this guide; revisit it if any measurement here surprises you.
• Designing device topics the foundation of this guide; revisit it if any measurement here surprises you.

Who this guide is for

Beginners get a single focused topic instead of a whole textbook chapter. It assumes the track’s earlier pages in the complete IoT and ESP32 guide path. Intermediate readers use it as a reference the table, the worked example and the mistake list answer the questions that come up mid-build. If you teach, the structure (theory, application, example, failure modes) maps cleanly onto a lab session.

What you need before starting

Nothing exotic: the parts or tools named in the guide, a multimeter. A notebook for the numbers. Run Mosquitto and connect Home Assistant with credentials before you begin the guide assumes it and keep the quick-reference table above within sight while you work through the steps.

Quick reference card

Aspect	Where to find it in this guide
Core theory	Connecting the broker
Application steps	How to apply this in your build
Worked numbers	Worked example
Failure modes	Pitfalls that cost real hardware

How this fits the complete IoT and ESP32 guide track

This guide is one stop in the structured learning path. Start from the complete IoT and ESP32 guide complete guide for the full map, or continue with MQTT protocol basics and Mosquitto setup.

Frequently asked questions

Does this work when the internet is down? Completely broker, Assistant and devices all run on your LAN.

Can I mix bought Zigbee devices with MQTT? Yes; bridges exist for Zigbee too, and both live side by side inside Home Assistant.

Where do I go next? Back to the complete IoT and ESP32 guide complete guide it indexes every guide in this track and updates as new ones are published.

Continue this track

• Building a foundation? The iot, sensors & esp32 complete guide maps every step in order.
• Next: LoRaWAN for Beginners: Long-Range IoT Without WiFi
• Next: Setting Up a Mosquitto MQTT Broker on Raspberry Pi
• Next: MQTT Explained: The Protocol Behind Practical IoT
• Work the numbers: battery life estimator · LM317 designer · wire gauge checker

Bench verification habits

Keep a lab notebook entry for every build in this track. The measured values, the deviations from the guide and the reason for each. Six months from now, those notes are worth more than any tutorial. They describe your bench and your components rather than a general case.

When a result here disagrees with your expectation, write down both numbers before changing anything. The gap between predicted and measured is where the real engineering lives. It is usually a tolerance, a parasitic or an assumption that was never checked.

Formulas and checks from this guide

Verification checklist for this track: watch RSSI before blaming code, measure supply current during radio bursts. Confirm MQTT topics against the broker log. Wireless bugs are usually power or signal problems wearing a software disguise.

Bookmark this page against your next build in the track. The checklist above is the same one used across 23 guides in this series.

From our lab notebook

Measure current during transmit bursts. Sags under load are power problems, no firmware fixes those.

Location, then device, then measurement. Document the tree before flashing the first device.

Final note from the author

A note on radio current, which defines this track: transmit bursts draw in spikes, not averages. Scope the supply or log RSSI before concluding the protocol is at fault.

Working through Connecting the brokerand Discovery messages with that habit in mind takes minutes, and it is the difference between reading about this topic and owning it.

Extended Application Notes

This section expands the practical application of home assistant + mqtt: a local smart home that lasts beyond the worked example, into the situations builders actually meet. Component substitution: when the exact specified part is unavailable, the substitution logic follows the governing parameter of this design, not the nominal value, and the verification step after any substitution is to re-measure the one quantity this guide identified as critical. Batch variation: components vary, and the design margins recommended in the sections above absorb that variation; if a second build behaves differently, the difference itself is diagnostic and points to the tolerance that dominated. Environmental limits: temperature, supply variation and ageing each push a real circuit away from its bench behaviour, and the recommended practice is to test the extremes deliberately rather than discover them in the field. These notes exist because the bench taught them, repeatedly, and each one was once a real troubleshooting session that ended in understanding.

Failure Analysis in Depth

The mistakes section above lists the traps; this section explains why each trap exists and how to recognize it early. Non-retained discovery devices vanish on broker restart Colliding object IDs silently merging entities Automating before validating raw topics in the debug panel. Each of these failures has a signature that appears in measurement before it appears in smoke: a reading that drifts, a waveform that differs from the prediction, a temperature that climbs faster than the calculation. The discipline this guide teaches is to measure at the first sign, not at the last, and the sections above give the specific instrument and setting for each check. Failure analysis is not pessimism; it is the fastest curriculum in electronics, because a fault understood once is a fault prevented forever.

Pre-Build Checklist

Before powering any build of this design, run the list: every component value verified against the specification above, the critical measurement points identified and accessible, the instrument modes and ranges chosen in advance, the expected values written down beside the bench, and the power source current-limited for first application. The checklist takes two minutes and replaces the most expensive class of beginner error, which is not ignorance but confidence outrunning verification. Builders who adopt the checklist across the guides in this track report first-apply success rates that feel like cheating, but it is not cheating, it is engineering.

What Comes Next

Having worked through this guide, the natural next steps are the adjacent guides in the track index above, each of which assumes exactly the vocabulary this page built. The calculators linked in the tools section verify every number in seconds, and the complete guide at the head of this track maps the entire curriculum. Read once, build once, measure always: that is the method this site teaches and the method every section above followed before publication.

Theory in Practice, Extended

The theory section of home assistant + mqtt: a local smart home that lasts deserves one more pass with the bench in mind, because knowing a relationship and applying it under constraint are different skills. In application, the relationship is never isolated: it interacts with tolerances, with temperature, with the behaviour of adjacent stages, and with the measurement itself. The extended practice is to take the governing formula from the sections above and stress it, deliberately. Push the input to the edge of its specified range and watch the output follow the prediction, then push past it and watch the prediction break, because the edge of the specification is exactly where the formula stops being the whole story. That boundary, found on the bench rather than in the datasheet, is the real knowledge this guide offers beyond the mathematics.

Component Sourcing and Substitution Notes

Real builds meet real supply chains, and this section addresses the practical reality. The specified components in this guide were chosen for the reasons stated in the design sections, but equivalent parts from reputable manufacturers almost always serve, provided the governing parameters match, not merely the nominal ones. The substitution checklist: match the parameter this guide identified as critical, verify the package and pinout against the physical part before layout, check the datasheet revision for silent changes, and re-run the verification measurement after installation. Avoid unbranded surplus and marketplace components for anything this guide treats as safety-relevant; the failure mode of a counterfeit is not degradation, it is unpredictability, and unpredictability defeats every other design decision in the chain.

Instrumentation for This Design

Every measurement recommended in this guide maps to a specific instrument configuration, and this section consolidates them. Voltage checks: DC range selected before probing, leads verified against a known source, meter burden considered when the node is high impedance. Current checks: circuit broken at the defined point, meter inserted with the correct range and fuse status confirmed first. Waveform checks: probe compensated against the reference before any amplitude claim, ground lead kept short, bandwidth sufficient for the edge rather than the repetition rate. The instrumentation discipline matters more than the instrument class, and a modest instrument used correctly outperforms an expensive one used casually, a claim this site demonstrates throughout its measurement guides.

Documentation Template for This Build

Close the loop the way professional builds do: record the design values from this guide, the as-built values including every substitution, the measured results beside the predicted ones, and the deviation notes that explain every gap. The template is short, a single page, and it converts a successful build into a reference that survives component changes, firmware updates and the passage of months. Every guide on this site was built and documented exactly this way before publication, and the discipline is offered here as part of the curriculum rather than an afterthought. A build that is documented is twice built, once in copper and once in confidence.