Uladzislau Bayouski

In a utility cupboard somewhere in Manchester, a gas meter fitted in 2015 is still sending a reading every night. Same battery. Nobody has opened the case. Meanwhile, the ESP32 sensor you built last weekend — the one on the windowsill reporting temperature to a dashboard — is dead. Three days on two AA cells. The two devices aren't as different as they look. Both are a microcontroller, a sensor and a radio. Both wake up, take a measurement, send a few bytes and go back to sleep. The difference between three days and fifteen years isn't a better battery — it's what the device does with the 99.8% of its life when nothing is happening. That's what power management in IoT actually is: not a component you buy, but a set of decisions about sleeping, waking and talking. 🔋 The Short Version Every battery-life question comes down to one division: capacity divided by average current. A pair of AA lithium cells holds about 3,000 mAh. Draw 3 mA on average and you get six week...

You've shipped 50,000 smart locks across three continents. A security researcher emails on Tuesday afternoon. There's a buffer overflow in your firmware — exploitable, real, and present on every single lock. Without OTA, your options are recall, truck roll, or hope. Any of those costs millions and takes months. With OTA, you push a signed patch Tuesday evening. By Wednesday morning, 94% of your fleet is fixed. The remaining 6% update themselves when they next connect. That's why OTA isn't a feature. It's a survival mechanism. 🔒 The Short Version OTA (Over-the-Air) updates let you deliver new firmware to deployed IoT devices wirelessly — no physical access, no recall, no technician. The four components every OTA system needs: Update server — hosts firmware images, controls which devices get which version and when Device client — polls the server, downloads, verifies, and applies updates Transport layer — MQTT, HTTPS, or CoAP carrying the image secur...

MQTT: The Tiny Protocol Powering Millions of IoT Devices In 1999, two engineers needed to monitor oil pipelines stretching across remote desert terrain. Thousands of sensors. Hundreds of kilometres. Satellite links that were slow, expensive, and unreliable. Every unnecessary byte of data cost real money. Every dropped connection could mean a missed reading on a pipeline carrying millions of dollars worth of oil. HTTP wasn't going to cut it. So they built something new. Something with a minimum message size of two bytes. Something that assumed the network would fail. They called it MQTT. Twenty-five years later, it runs your smart home, your hospital monitors, your fleet tracking, and your factory floor. Not bad for a protocol built to watch oil flow through a desert pipe. 🔧 The Short Version MQTT is a publish/subscribe messaging protocol — and its architecture is its superpower. Instead of devices talking directly to each other, everything flows through a central broker : ...

 Every IoT device you interact with — your smartwatch, your connected thermostat, the sensor on a factory floor — is controlled by a chip you've almost certainly never thought about. The smart microcontroller. One package. Processor, memory, connectivity, security, and increasingly, AI. All integrated on a single piece of silicon the size of your thumbnail. Here's what's actually inside. The Short Version Unlike a microprocessor that needs external components, a microcontroller integrates everything needed for a control task onto one chip. That integration is what makes IoT devices compact, efficient, and manufacturable at scale. The key building blocks: CPU core — typically ARM Cortex-M or RISC-V; bit width (8/16/32) determines the performance and power trade-off On-chip memory — Flash for program code, SRAM for runtime data, EEPROM for persistent storage; all on die, no external chips needed Power management — active, sleep, deep sleep, and standby modes that can st...

Every IoT product lives or dies by its chip. The wrong choice means your device drains batteries in a week, misses the connectivity standard that just became mainstream, or ships without the security features enterprise buyers now require. In 2025, the IoT chip market is more competitive — and more interesting — than ever. The Short Version Four requirements define what a serious IoT chip needs in 2025: energy efficiency, robust security, support for Matter and next-gen protocols, and on-device AI capability. The chips that nail all four are the ones shaping the next generation of connected products. Here's the list: Qualcomm QCA4020 — tri-mode SoC (BLE + Wi-Fi + 802.15.4) built for multi-protocol smart home ecosystems and Matter compatibility Nordic nRF5340 — dual-core Bluetooth 5.3 powerhouse with LE Audio and direction finding; the go-to for wearables and health monitors Espressif ESP32-C6 — the developer favorite evolves: Wi-Fi 6, BT 5 LE, native Matter support, and l...