<rss xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title>Mqtt - Tag - vo.rs</title><link>https://vo.rs/tags/mqtt/</link><description>Mqtt - Tag - vo.rs</description><generator>Hugo -- gohugo.io</generator><language>en</language><copyright>This work is licensed under a Creative Commons Attribution-NonCommercial 4.0 International License.</copyright><lastBuildDate>Mon, 11 May 2026 14:00:00 +0000</lastBuildDate><atom:link href="https://vo.rs/tags/mqtt/" rel="self" type="application/rss+xml"/><item><title>MQTT Essentials: The Protocol Behind Every Smart Home</title><link>https://vo.rs/story/mqtt-essentials-the-protocol-behind-every-smart-home/</link><description>&lt;p&gt;If you&amp;rsquo;ve spent any time poking at a smart home, you&amp;rsquo;ve bumped into MQTT whether you meant to or not. Zigbee2MQTT, ESPHome, Tasmota, Home Assistant&amp;rsquo;s own internal bus — they all lean on it. It&amp;rsquo;s worth understanding properly, because once you do, an awful lot of &amp;ldquo;magic&amp;rdquo; stops being magic and starts being a handful of topics and a tiny broker process.&lt;/p&gt;
&lt;h2 id="what-it-actually-is" class="headerLink"&gt;
&lt;a href="#what-it-actually-is" class="header-mark"&gt;&lt;/a&gt;11 What it actually is&lt;/h2&gt;&lt;p&gt;MQTT is a publish/subscribe messaging protocol. It was designed in 1999 for oil pipeline telemetry over satellite links, which tells you everything about its priorities: tiny payloads, low overhead, and tolerance for flaky connections. Devices don&amp;rsquo;t talk to each other directly. They talk to a &lt;strong&gt;broker&lt;/strong&gt; — a small server that receives messages and fans them out to whoever has subscribed.&lt;/p&gt;</description><pubDate>Mon, 11 May 2026 14:00:00 +0000</pubDate></item></channel></rss>