Smart Home

A smart garden irrigation system on Home Assistant joins three parts: a Wi-Fi sprinkler controller, a rain sensor, and automations. The automations cancel or adjust watering based on rainfall, soil moisture, and the forecast. With the WiseWater integration and the native scheduler in Home Assistant 2025.12, this setup now beats pricey cloud-bound irrigation systems. Here is how to build one from scratch.

Why DIY Smart Irrigation Beats the Commercial Options

Commercial smart sprinkler controllers like Rachio , Orbit B-hyve , and RainBird Wi-Fi run $100 to $200. Their “smart” features all need a cloud link and often a paid plan. That includes weather skip logic, seasonal tweaks, and soil type awareness. If the vendor shuts down its servers (remember Wink ?), those features revert to dumb timer-only watering. You’re left with an overpriced relay board.

You can wire any microcontroller into Home Assistant over MQTT . Publish sensor data to discovery topics and subscribe to command topics. You get full firmware control without ESPHome’s abstraction layer. The trick works on any chip: ESP32, RP2040, STM32, or a Raspberry Pi Pico W. It’s the right pick when your device needs custom protocols, bare-metal timing, or firmware features ESPHome can’t reach.

This post covers when raw MQTT makes sense, the discovery protocol that auto-registers devices, firmware examples on the ESP32 and RP2040, two-way control patterns, and security hardening.

No, you don’t need Wi-Fi 7 for Matter. Every Matter device on my network connects over 2.4GHz Wi-Fi or Thread, and neither path touches Wi-Fi 7’s headline features. A Wi-Fi 7 router still helps a busy smart home in three indirect ways, but device compatibility is not one of them.

What Matter Actually Runs On

Matter is an application protocol, not a radio. It runs over standard IP networks, and the spec defines three transports: Wi-Fi, Thread, and Ethernet. Bluetooth LE is used only for the initial pairing handshake. Consequently, your router doesn’t need any “Matter support” checkbox; it just needs to move IP packets on a network the device can join.

Flash WLED 0.15 onto an ESP32 over USB in under five minutes using the web installer at install.wled.me , wire up a WS2812B or SK6812 addressable LED strip with a properly sized 5V power supply, then add the device to Home Assistant via auto-discovery and configure voice control through the built-in Assist pipeline. You get hands-free color changes, effects, and brightness control with zero cloud dependency. Total cost is under $30 for a basic setup, and the whole thing takes about an hour.

Placing IoT devices on a dedicated VLAN with firewall rules that block all traffic to your main network - except specific connections to your Home Assistant server - prevents a compromised smart bulb or camera from becoming a pivot point into your personal computers and NAS. This setup works with consumer-grade managed switches and either UniFi or OpenWrt routers, and takes about an hour to configure properly.

The core idea is straightforward: instead of trusting every device on your network, you divide the network into isolated segments and only allow the traffic you explicitly approve. Your smart plugs, cameras, and voice assistants get their own network segment where they can reach the internet and your home automation server, but nothing else. If one of them gets compromised, the attacker is stuck in a sandbox with no path to your laptop or file server.

You can secure your Home Assistant config by pushing your YAML files to a private GitHub repo on a daily schedule. This gives your smart home version control. You can see what changed between the last working state and the broken one, roll back a single file in seconds, and rebuild a fresh HA install from a repo clone. It is faster and far more useful than the built-in snapshot backup for config-level problems.