Building a Home Assistant energy dashboard from scratch is a rewarding way to see where your power goes while keeping the data on your own network. Home Assistant ships with a built-in Energy dashboard (Settings > Dashboards > Energy), so most of the work is choosing hardware that reports accurate kWh and feeding those sensors in. This guide focuses on Home Assistant and notes where Hubitat or HomeKit fit in.

How the built-in Energy dashboard works

Home Assistant’s Energy dashboard is not a generic chart. It expects sensors that report cumulative energy (kWh) with the correct device_class: energy and state_class: total_increasing. You configure grid consumption, return to grid (solar export), solar production, individual devices, and gas/water in the Energy settings page. Once configured, it builds daily, monthly, and yearly views automatically, plus a “monitor individual devices” section.

The practical takeaway: pick hardware that exposes a proper energy (kWh) sensor, not just instantaneous watts. Most devices below do both.

Start with the right hardware

Whole-home: P1 smart meter reader

If your utility meter has a P1 port (common in the Netherlands, Belgium, and parts of the EU), the HomeWizard P1 Meter clips onto that port and reads your entire home’s import/export over a fully local API. If you have rooftop solar, our guide to energy monitoring for solar homes covers tracking production and export too. The official HomeWizard integration creates power and energy sensors that drop straight into the Energy dashboard’s grid section. No panel work required.

Per-outlet: smart plugs with metering

For tracking a single appliance, a metering smart plug is the easiest entry point:

• HomeWizard Energy Socket — Wi-Fi plug with a local API and per-outlet energy reporting. EU socket only: HomeWizard sells it in a single Type-F (Netherlands/Belgium) form factor, with no US or UK version.
• Shelly Plug US Gen4 — Wi-Fi plug that reports power and energy. It is Shelly’s current US plug (15 A / 1800 W), it runs Shelly’s own (Allterco) firmware, and it is read locally via the Shelly integration or MQTT; that firmware is Matter-certified by default and switches to Zigbee with five presses of the device button. The older Gen2 Shelly Plus Plug US is still a fine plug if you already own one, but it is Wi-Fi and MQTT only with no native Matter, and flashing Tasmota on it is an optional advanced step, not the default. Do not confuse it with the Shelly Plug S, which is the European Type-F version of that plug and does not fit a US outlet.
• Sonoff S31 — Wi-Fi plug commonly flashed to ESPHome or Tasmota for fully local metering; the stock firmware is eWeLink/cloud-oriented.

Per-circuit / whole-panel

To measure circuits in your breaker panel you need a panel meter with current transformer (CT) clamps. The Shelly Pro 3EM is a DIN-rail three-phase meter that ships with CT clamps and reports per-phase voltage, current, and energy locally - see how to build a power monitoring dashboard with Shelly for a full walkthrough, and how to add energy monitoring to an old panel if your breaker box predates smart metering. Note: the inline Shelly Plus 2PM has built-in metering for its two switched channels (no external clamps) and is meant for controlling/monitoring specific loads, not clamping around panel busbars.

The Pro 3EM is a three-phase meter, so for the split-phase panel in a typical North American home the more common circuit-level answer is the Emporia Vue 3: a main CT plus a set of branch CTs in 8- or 16-circuit kits. It runs through Emporia’s own app out of the box, but you can flash it with ESPHome and turn it into a fully local Home Assistant sensor with no cloud. Both the Gen 2 and Gen 3 need a one-time wired serial flash with a USB-to-TTL adapter on the board’s UART pads (do not connect the Vue’s own power lead while flashing); only later updates go over Wi-Fi.

Hubitat and HomeKit notes

Hubitat (e.g. the Hubitat Elevation C-8, which Hubitat replaced with the same-radio C-8 Pro in March 2026) runs automations locally and supports Z-Wave and Zigbee metering devices. Zooz makes metering Z-Wave hardware — for example the Zooz ZEN30 Double Switch for control, or Zooz’s energy-monitoring smart plugs for plug-in loads. You can bridge Hubitat into Home Assistant via the community Hubitat integration to surface those sensors on the Energy dashboard. (Note: the Zooz ZEN72 is a Z-Wave dimmer switch, not a plug or energy meter — don’t rely on it for consumption data.)

HomeKit has a basic energy view but no dashboard comparable to Home Assistant’s. Thread-capable HomePods (the mini and the second-generation model) act as Thread border routers and speakers — they cannot run Home Assistant. Run Home Assistant on a Home Assistant Green, a Raspberry Pi, or a mini PC, and add a Home Assistant Connect ZBT-1 (now discontinued and replaced by the Connect ZBT-2, which is the one to buy new) for Zigbee/Thread devices.

Build the dashboard

Once your energy sensors exist, configure the Energy dashboard in Settings > Dashboards > Energy. Assign grid sensors, any solar production, and individual devices. For custom views beyond the built-in dashboard, add Energy cards, the Statistics graph card, or the History/Statistics cards to any normal dashboard.

Real-world tradeoffs

• Cost — A P1 reader or a couple of metering plugs is cheap; a panel meter with CTs plus (ideally) an electrician costs more.
• Granularity vs. effort — Whole-home (P1) is easiest but won’t tell you which circuit is expensive. Per-circuit metering is more work and may require opening your panel.
• Maintenance — Keep Home Assistant and Z-Wave JS / Zigbee firmware updated, and back up your config regularly.

Quick verdict

Start with a P1 reader for instant whole-home visibility, or a metering smart plug for a single appliance, then add a panel meter with CT clamps when you want circuit-level detail. Because the Energy dashboard is built in, the hard part is just picking hardware that reports real kWh locally.

If you already own a NAS, running Home Assistant on it is tempting: one box, always on, one place to manage. Synology, Unraid, and TrueNAS can all host Home Assistant, but the experience differs in one decision that matters more than the rest — can you run full Home Assistant OS in a VM, or are you stuck with the Container install? That choice determines whether you get the add-on store. This guide keeps that distinction front and center.

The one tradeoff that drives everything: Container vs HAOS-in-a-VM

Home Assistant has a few install types. On a NAS, two are relevant:

• Home Assistant Container — the official Docker image (ghcr.io/home-assistant/home-assistant). It runs Home Assistant core and all integrations, but it has no Supervisor, which means no add-on store. Add-ons (Mosquitto, ESPHome, Zigbee2MQTT, the Tailscale/cloudflared add-ons, etc.) are one-click Docker services managed by the Supervisor — and they simply aren’t available here. You can still run those same services as your own separate containers; you just manage them yourself.
• Home Assistant OS (HAOS) in a virtual machine — this gives you the full, supported experience including the add-on store, because the Supervisor comes along for the ride. On a NAS this means running the HAOS disk image inside the platform’s hypervisor.

(Note: the older “Supervised” install-on-your-own-OS method was deprecated on May 22, 2025 and has been unsupported since release 2025.12, so on a NAS your realistic choices are Container or HAOS-in-a-VM.)

So the platform question really becomes: how easily can each NAS run a VM?

Synology

Synology is the most polished and beginner-friendly NAS OS. Since DSM 7.2, Docker is provided through Container Manager, the package that replaced the old Docker one and added a Compose UI, so the Home Assistant Container install is straightforward on most models. On DSM 7.0 and 7.1 you are still looking for the package called Docker.

For the full add-on experience you need Virtual Machine Manager (VMM) to run HAOS in a VM. VMM is available on Synology’s Intel/AMD ”+” models — the 2025 DS225+/DS425+/DS925+ class as well as older units like the DS224+/DS923+ — and not on the lower-end ARM units, so check your specific model before counting on it. Synology also requires more than 2 GB of memory before a virtual machine will run at all, and VM data can only be stored on a Btrfs volume. Where VMM is available, importing the HAOS image as a VM works and is a common setup.

Tradeoffs: Synology’s strength is stability and simplicity; its weakness is that you’re working within DSM’s constraints, and lower-tier models lack the CPU/VM support for the HAOS-VM route. The USB radio question is the one to check carefully, and it cuts the opposite way from what you might guess: DSM 7 does not ship the USB-serial kernel modules that most Zigbee and Z-Wave sticks depend on (cp210x, ch341, pl2303), so the stick never shows up as a /dev/ttyUSB* device and the Container install simply cannot see the radio until you add community-built driver packages and load the modules at boot. Only sticks that present themselves as USB CDC-ACM are handled natively. Passing that same stick through to a VMM virtual machine sidesteps the problem, because VMM hands the raw USB device to the guest rather than relying on a host serial driver. If your radios live on the NAS, that one detail can settle the Container-versus-VM question for you.

Unraid

Unraid is built for exactly this kind of “do many things on one box” use. It has first-class Docker support (Community Applications makes the Home Assistant Container a couple of clicks) and built-in KVM virtual machines, so running HAOS in a VM — with the full add-on store — is well-trodden territory. Community templates exist for both approaches.

Unraid also tends to handle USB device pass-through to VMs more gracefully, which matters if you’re plugging a Zigbee or Z-Wave coordinator into the server. The cost is that Unraid is a paid product and assumes a bit more comfort with Docker/VM concepts than Synology’s appliance feel.

TrueNAS

TrueNAS is the most “full Linux” of the three, with ZFS, snapshots, and strong storage features. The naming is worth pinning down first: the Linux/Debian-based line was called TrueNAS SCALE until the 25.04 “Fangtooth” release in April 2025 dropped the SCALE suffix and rebranded the free build TrueNAS Community Edition, while the FreeBSD-based TrueNAS CORE moved into maintenance-only status at the same time — so guidance framed as “SCALE vs CORE” predates the current product. It supports virtual machines, and the recommended way to get full-featured Home Assistant here is to run HAOS in a VM — that’s what gets you the add-on store. Container-based deployments exist but, like everywhere else, drop the Supervisor and add-ons.

One version caveat matters more here than on the other two platforms: TrueNAS rebuilt its virtualization layer mid-generation, then partly rebuilt it back. Releases up to 24.10 “Electric Eel” ran VMs on libvirt/KVM; 25.04.0 “Fangtooth” retired that screen in favor of an Incus-based Instances feature; then 25.04.2 (July 2025) reintroduced classic virtualization and split the UI into a Virtual Machines screen (full KVM virtual machines — the one you want for HAOS) and a Containers screen (LXC system containers, which TrueNAS still labels experimental). 25.10 “Goldeye” keeps that split. TrueNAS says virtual machines migrate automatically from 24.10 to 25.04.2 with no manual step, but a VM that passes a Zigbee or Z-Wave stick through is still the configuration to check first — confirm the device is still attached, and the mesh is back, before you trust it again.

TrueNAS rewards users who want control and don’t mind more setup. It’s the most flexible and the most demanding of technical comfort; ZFS and the VM workflow are powerful but not “appliance simple.”

Integrating local ecosystems (and clearing up some myths)

Whichever platform you pick, a few facts worth getting right:

• HomeKit is exposed by Home Assistant via the built-in HomeKit Bridge integration (to make HA entities show up in Apple Home), and HA can import HomeKit accessories via HomeKit Controller. Neither requires MQTT, and an Apple HomePod/Echo does not run Home Assistant.
• Hubitat integrates with Home Assistant via a community integration (commonly the Hubitat-to-HA bridge) — not via MQTT by default. It’s a separate hub you link to, not something MQTT-bridged out of the box.
• Zigbee and Z-Wave need a USB coordinator/radio plugged into the host, then ZHA/Zigbee2MQTT (Zigbee) or Z-Wave JS (Z-Wave). Good current examples: a Home Assistant Connect ZBT-2 or a ConBee III for Zigbee (the older SkyConnect, renamed the Connect ZBT-1, was discontinued in November 2025 — it still works and still receives software updates, but the ZBT-2 is the one to buy new), and a Zooz 800-series stick (e.g. ZST39) for Z-Wave. Note that something like the Zooz ZAC36 Titan is a Z-Wave water-valve end device, not a coordinator, and the Aeotec Smart Home Hub is a standalone SmartThings-based hub — neither is a USB radio you “run in a container.” Because radios are USB, USB pass-through to your VM/container is the real constraint when picking a platform.

Hardware notes

For a typical home (a few hundred entities), any of these on modest hardware is fine. Give a HAOS VM at least ~2 GB RAM and 2 vCPUs, and put the Home Assistant database on an SSD — recorder write load chews up spinning disks and makes the UI sluggish. If you plan to scale to many hundreds of entities or run heavy add-ons (Frigate NVR, etc.), spec accordingly or consider a dedicated mini-PC (see the best mini PCs for Home Assistant).

Quick verdict

• Synology — easiest day-to-day, great if a ”+” model lets you run the HAOS VM; the Container route works everywhere but loses the add-on store, and on DSM 7 it cannot see a USB Zigbee or Z-Wave radio at all without community serial drivers.
• Unraid — the most balanced for this job: easy Docker and easy HAOS-in-a-VM, with friendlier USB pass-through. Paid, slightly more to learn.
• TrueNAS — most powerful and flexible (ZFS, VMs), best if you want full control and don’t mind setup.

Bottom line: if you want the full Home Assistant experience with add-ons, run HAOS in a VM — which makes Unraid or TrueNAS (or a ”+“-series Synology with VMM) the natural choices. If you’re happy managing your own supporting containers, the Container install runs anywhere. And honestly, if remote radios and reliability matter most, a small dedicated HAOS device alongside the NAS is often the least-fuss path of all.

Adding temperature sensors to your fridge and freezer is a practical way to catch problems before food spoils, like a door left ajar or a failing compressor. For a local-first setup with Home Assistant, HomeKit, or Hubitat, the right sensor will alert you early. The catch is that a freezer is a harsh environment, so sensor choice matters more than usual. If you also want ambient monitoring elsewhere, see how to add temperature sensing to every room cheaply.

Choose a Sensor That Can Handle the Cold

This is the most important decision. Most indoor temperature/humidity sensors are only rated to roughly -10°C (14°F), which is fine for a fridge but not cold enough for a freezer (typically -18°C / 0°F). Putting a standard sensor in a freezer can give wrong readings, kill the battery fast, or stop it working entirely. Condensation and frost are also a problem for sensors sitting in the cold air.

There are two good approaches:

1. Probe sensors (best for freezers). These keep the electronics and battery outside, with only a waterproof probe inside the cold space. The SONOFF SNZB-02LD is a Zigbee thermometer with an IP65-rated 1.5 m probe designed exactly for this. Generic Zigbee “probe” sensors with a probe rated to -40°C are also available and work well for freezers. Run the thin probe cable past the door gasket and keep the body outside.

2. Standard sensors (fridge only). For a fridge, a sealed indoor sensor placed inside is usually fine. The Sonoff SNZB-02P (Zigbee, ±0.2°C, working range -10°C to 60°C) is cheap and accurate for fridge temperatures. Expect somewhat shorter battery life in the cold and occasional condensation.

A correction worth flagging: the SONOFF SNZB-01P is a wireless button, not a temperature sensor, so don’t use it for this. The temperature model is the SNZB-02P (or the SNZB-02LD with a probe).

Pick Sensors That Match Your Setup

These are all battery sensors that run locally. The first two are Zigbee and need a Zigbee coordinator; the Aqara W100 is dual-protocol, so read its note before you buy:

• Sonoff SNZB-02P / SNZB-02LD — Zigbee, CR2477 battery, pair via ZHA or Zigbee2MQTT.
• Third Reality Temperature and Humidity Sensor — Zigbee, runs on 2x AAA batteries (it is not USB-powered and not Z-Wave). The plain model has an LCD; the Lite version drops the display for a lower price.
• Aqara Climate Sensor W100 — runs either Zigbee 3.0 or Thread (Matter-over-Thread), never both at once, and never Z-Wave. It ships in Thread firmware, so pairing it to ZHA or Zigbee2MQTT takes a one-time protocol switch in the Aqara Home app - no Aqara hub required. Good if you also want a display.

Whichever you choose, you need a coordinator on your network, such as the Home Assistant Connect ZBT-1 (a Zigbee coordinator or, on Thread firmware, a border router - one role at a time, not both; now discontinued and replaced by the Connect ZBT-2), the ConBee III, or the radios built into a Hubitat Elevation C-8 (Hubitat stopped making the plain C-8 in March 2026; the same-radio C-8 Pro is the one to buy new) or an Aqara hub. The Philips Hue Bridge is a closed Zigbee gateway for Hue accessories and won’t pair these third-party sensors.

Install and Integrate

Place the sensor (or probe tip) in a spot that reflects the average internal temperature, not pressed against the back wall and not right by the door. Secure cables so the door still seals.

In Home Assistant, pair Zigbee sensors through ZHA or Zigbee2MQTT; they’ll appear under Devices & Services. For Matter-over-Thread (Aqara W100 in Thread mode), add via the Matter integration with a Thread border router available.

For HomeKit, use a sensor that’s HomeKit- or Matter-compatible and join it through a Home hub (HomePod or Apple TV); these hubs do not run Home Assistant. Hubitat pairs Zigbee/Z-Wave sensors directly through its built-in radios.

Monitor and Automate

Once data is flowing, create alerts. In Home Assistant, notify your phone if the fridge rises above about 4°C (39°F) or the freezer above -15°C (5°F) for more than a few minutes, which filters out normal defrost cycles and door openings. Home Assistant also keeps history, so you can chart temperature trends and spot a struggling appliance. The same sensor data can also flag humidity problems — see how to detect mold risk with Home Assistant.

In HomeKit, a Home automation can send a notification when a threshold is crossed. In Hubitat, use Rule Machine plus notifications (or webhooks) for the same alerts.

A short averaging window or a minimum-duration condition is the key to avoiding false alarms from routine defrost and door-open events.

Tradeoffs and Considerations

• Cold rating is the big one: use a probe sensor for freezers, and only a fridge-rated sensor inside a fridge.
• Battery life drops in the cold; probe sensors help because the battery stays at room temperature.
• Condensation/frost can affect sensors placed directly in cold, humid air; probes avoid this.
• Protocol matters: a Zigbee coordinator won’t pair Z-Wave devices, so match the sensor to the radio you have.

Quick Verdict

For a freezer, use a probe sensor like the SONOFF SNZB-02LD so the battery and electronics stay warm. For a fridge, a sealed Zigbee sensor such as the Sonoff SNZB-02P or a Third Reality unit works well. Pair them to a Zigbee coordinator, integrate with Home Assistant (or HomeKit/Hubitat), and set duration-based alerts to catch real problems without nuisance pings. For sensors ranked by accuracy and battery life, see the best Zigbee temperature and humidity sensors.

Presence detection is one of the most impactful upgrades you can make to a smart home. It lets you automate lighting, climate, and security based on whether a room is actually occupied. Combining mmWave and PIR sensors gives you reliable, low-latency detection that runs entirely on your local network. This guide walks through setting both up in Home Assistant, with notes for HomeKit and Hubitat users.

Why combine mmWave and PIR

The two sensor types are complementary, which is exactly why good presence sensors include both.

PIR (passive infrared) sensors detect the heat signature of a moving body. They are fast, cheap, and very low power, which makes them ideal for triggering lights on the instant someone enters. Their weakness is that they only see motion, so a still person eventually reads as “no one here,” and they can occasionally be fooled by warm air or sunlight.

mmWave (millimeter-wave radar) sensors emit radio waves and measure reflections, so they detect even tiny movements, including breathing. That means they keep a room marked “occupied” while you sit still on the couch or work at a desk. The trade-off is that they respond a touch slower and need careful tuning to avoid false triggers from fans or moving curtains.

The classic pattern: use PIR to turn lights on fast, and mmWave to keep them on (and turn them off only when the room is truly empty).

Choosing the right sensors

For a local-first setup, you want sensors that run locally and integrate cleanly with Home Assistant. If you’d rather compare a full field of options before deciding, see our best mmWave presence sensors for Home Assistant roundup and the broader best local presence sensors guide; the two picks below are simply the sensors this walkthrough uses.

• All-in-one (mmWave + PIR), Wi-Fi/ESPHome: The Everything Presence One combines an mmWave radar, an industrial PIR, plus light, temperature, and humidity sensors. It runs ESPHome over Wi-Fi, so it connects directly to Home Assistant with no hub or proprietary cloud. (Its newer sibling, the Everything Presence Lite, adds multi-target, multi-zone tracking if you need per-zone occupancy.)
• PIR over Zigbee: The Aqara Motion Sensor P1 is a low-power Zigbee PIR sensor. It pairs with any Zigbee coordinator and works well for fast on-triggers. (Note: the newer Aqara Motion Sensor P2 is Matter-over-Thread, not Zigbee.)

A note on protocols, because product marketing often muddies this: the Everything Presence One is a Wi-Fi/ESPHome device, not a Zigbee or Z-Wave device. The Aqara Motion Sensor P1 is Zigbee (its P2 sibling is Matter-over-Thread). And the Aqara Hub M3, if you use one, is a Zigbee + Thread + Matter hub. It does not support Z-Wave. If you want Z-Wave sensors, you need a Z-Wave controller (such as a Z-Wave USB stick), which is a separate radio entirely.

Setting up in Home Assistant

Step 1: Add the sensors

For the ESPHome-based Everything Presence One, flash/adopt it in the ESPHome dashboard, connect it to your Wi-Fi, and it appears in Home Assistant as a set of entities (mmWave occupancy, PIR motion, illuminance, temperature, humidity). No hub required.

For the Zigbee Aqara Motion Sensor P1, you need a Zigbee coordinator. A USB stick like the ConBee III works with ZHA, deCONZ, or Zigbee2MQTT. You don’t edit configuration.yaml for this; you set up the coordinator through the ZHA integration (or your chosen Zigbee stack) in the Home Assistant UI, then put it into pairing mode and press the sensor’s pairing button.

Step 2: Build a combined occupancy helper

The most reliable approach is to derive a single “occupied” state from both sensors. A simple template binary sensor reads occupied if either the PIR or the mmWave sensor is active:

template:
  - binary_sensor:
      - name: "Office Occupancy"
        device_class: occupancy
        state: >
          {{ is_state('binary_sensor.office_pir', 'on')
             or is_state('binary_sensor.office_mmwave', 'on') }}
        delay_off:
          minutes: 2

The delay_off adds a short grace period so the room doesn’t flip to “empty” the instant the radar drops out.

Step 3: Automate on the combined state

Now drive your lights from the combined occupancy sensor, not the raw PIR. Turn on the moment occupancy goes on, and off only after it has been off (for example, the helper above stays on for 2 minutes after last detection):

automation:
  - alias: Office lights follow occupancy
    triggers:
      - trigger: state
        entity_id: binary_sensor.office_occupancy
        to: "on"
    actions:
      - action: light.turn_on
        target:
          entity_id: light.office

  - alias: Office lights off when empty
    triggers:
      - trigger: state
        entity_id: binary_sensor.office_occupancy
        to: "off"
    actions:
      - action: light.turn_off
        target:
          entity_id: light.office

This gives you the fast on-response of PIR and the “stay on while I’m still” reliability of mmWave.

Step 4: Tune the radar

mmWave sensors usually expose distance and sensitivity settings. Reduce the maximum detection distance so the radar doesn’t see through a wall into the hallway, and dial back sensitivity if fans or curtains cause false occupancy. The Everything Presence One exposes these as adjustable entities in Home Assistant.

Cross-platform notes: HomeKit and Hubitat

For HomeKit, the cleanest path is to keep Home Assistant as your sensor hub and expose your combined occupancy sensor to Apple Home via Home Assistant’s built-in HomeKit Bridge integration. (Note: Home Assistant Green has no built-in radio and is not a HomeKit hub, so it can’t pair sensors or serve as an Apple Home hub on its own.)

For Hubitat, the Hubitat Elevation C-8 pairs Zigbee and Z-Wave sensors natively and is a flexible automation platform. If you are buying new, get the C-8 Pro: Hubitat stopped making the plain C-8 in March 2026, and the Pro carries the same Zigbee 3.0, Z-Wave 800 Long Range and Matter radios with a faster CPU and more RAM. ESPHome/Wi-Fi sensors like the Everything Presence One aren’t native to Hubitat, so most people keep those on Home Assistant and bridge states between the two if needed.

Quick verdict

For the best results with the least fuss, use a combined mmWave + PIR sensor like the Everything Presence One, which runs locally over ESPHome and exposes both sensor types plus environmental data. Merge PIR and mmWave into one occupancy helper, automate off that helper, and tune the radar’s range and sensitivity. The payoff is lighting that turns on instantly and never leaves you sitting in the dark, all running locally with no cloud.

A smart home doesn’t become useful because of fancy dashboards. It becomes useful because the house notices boring important things early.

That usually means three sensor jobs:

• catch leaks before they become expensive
• know whether doors and windows are open
• track temperature and humidity in rooms that matter

The sensors worth buying first:

• Best budget leak sensor: Third Reality Water Leak Sensor
• Best all-purpose contact sensor: Aqara Door and Window Sensor P2
• Best cheap environment sensor with a display: SONOFF SNZB-02D

Quick verdict

If you only buy one class of sensor after motion and presence, buy water leak sensors first. They prevent real damage, and they don’t require clever automations to justify themselves.

For leak alerts, the Third Reality Water Leak Sensor is the most immediately useful thing on this page.

For general door and window state, Aqara Door and Window Sensor P2 is the most flexible buy.

For room temperature and humidity without spending much, SONOFF SNZB-02D is the easy value play.

How we judge simple sensors

The standards are harsher than the boxes suggest.

We care about:

1. True local operation
2. Battery life and reliability
3. How well the sensor fits Zigbee2MQTT or ZHA
4. Whether the device solves a real household problem
5. Whether buying several of them is financially sane

Best “buy several right now” pick: Third Reality Water Leak Sensor

Leak sensors aren’t glamorous, but they’re the kind of smart-home gear that can pay for themselves in one incident.

Why this is the first recommendation:

• cheap enough to scatter around the house
• fully local Zigbee behavior
• good fit for Home Assistant alerts and automations
• ideal for sinks, water heaters, laundry areas, and anywhere plumbing likes to become a surprise

The limitation is simple: it detects leaks. It doesn’t shut water off by itself. That is still fine. Detection beats ignorance.

Best contact sensor: Aqara Door and Window Sensor P2

Contact sensors are the quiet workhorses of a useful smart home.

The Aqara Door and Window Sensor P2 stands out because it’s compact, reliable, and more flexible than a lot of budget contact sensors.

Why it makes sense:

• native Matter-over-Thread connection, no manufacturer hub or bridge required
• strong cross-ecosystem story: joins Home Assistant, Apple Home, Google Home, Alexa, or SmartThings over Matter
• easy bulk deployment for doors, windows, cabinets, and garage side doors

The caveat is that it needs a Thread border router (a HomePod mini or second-generation HomePod, a Thread-capable Apple TV 4K, or Home Assistant’s own Thread support), so it is not a fit if you have no Thread network and do not want to add one.

Best cheap room sensor: SONOFF SNZB-02D

The SONOFF SNZB-02D is the kind of low-cost sensor that makes a Home Assistant setup feel more observant without becoming a project.

Why it’s easy to like:

• fully local Zigbee support
• built-in display means the data is visible without opening an app
• inexpensive enough to place in bedrooms, nurseries, offices, and utility spaces

If what you want is glamorous automation theater, this isn’t it. If what you want is useful room data for very little money, it absolutely works.

What to avoid

Avoid sensor shopping that chases ecosystem badges before basic reliability.

A sensor that works locally, reports consistently, and doesn’t chew through batteries is usually more valuable than a flashier product that only looks good in the vendor app.

Also: don’t buy exactly one leak sensor. That misses the point.

Final recommendation

If you want the biggest practical win, buy Third Reality Water Leak Sensors in multiples and place them anywhere water might quietly ruin your week.

Then add Aqara Door and Window Sensor P2 units for entry points and SONOFF SNZB-02D sensors where room climate matters.

Product notes:

• Third Reality Water Leak Sensor
• Aqara Door and Window Sensor P2
• SONOFF SNZB-02D

Related reading

• What “local-first” actually means in smart home tech
• Best Zigbee coordinators for Home Assistant
• Best local presence sensors
• Best local smart thermostats
• Best Zigbee temperature and humidity sensors, ranked
• How to build a noise monitor with Home Assistant
• Local aquarium monitoring with Home Assistant

Matter was supposed to fix smart home compatibility forever. One protocol, every ecosystem, no more guessing whether your new gadget would work with your hub. The pitch was compelling. The reality has been messier.

Most Matter devices shipping today are rebranded Wi-Fi products with a Matter logo slapped on the box. They technically comply with the spec, but they don’t deliver the kind of reliability improvement that justifies the price premium. And while Matter 1.5 finally added cameras to the spec in late 2025, certified Matter cameras are still rare on shelves, and plenty of device categories people actually want remain thin.

That said, the good Matter devices are solid. The ones built on Thread are especially interesting: low power, mesh networking, and real local control that doesn’t depend on someone’s cloud staying online. If you pick carefully, Matter can be a solid part of a local-first smart home today. You just have to be picky.

Quick picks

• Best Matter smart plug: Eve Energy (Thread)
• Best Matter light: Nanoleaf Essentials A19 (Thread)
• Best Matter lock: Aqara Smart Lock U200 (Matter over Thread)
• Best Matter sensor: Aqara Door/Window Sensor P2 (Thread)
• Best Matter hub/bridge: Aqara Hub M3

What to know before buying Matter

Matter runs over Wi-Fi or Thread. Wi-Fi Matter devices work like any other Wi-Fi gadget on your network. They’re fine for plugs and lights that have wall power, but they add to your Wi-Fi congestion. Thread is an 802.15.4 mesh protocol that’s better for battery devices and avoids clogging your router. If you have a choice, Thread is almost always the better transport.

You need a Matter controller. Home Assistant, Apple Home, and Google Home all work as Matter controllers. Home Assistant gives you the most flexibility. Apple Home is the most polished for iPhone households. Google Home works but has been the slowest to mature its Matter support.

Multi-admin is real but imperfect. One Matter device can be controlled by multiple ecosystems at the same time. Your Eve plug can show up in both Home Assistant and Apple Home simultaneously. This mostly works, though pairing can be finicky and some combinations are more stable than others.

Current limitations are real. Camera support only entered the spec with Matter 1.5 in late 2025, and certified products are still scarce. Sensor coverage has grown (air quality, smoke/CO, water leak), but some features that exist in native Zigbee or Z-Wave versions still get lost when a device speaks Matter instead. If a manufacturer already has a great Zigbee product, the Matter version isn’t automatically better.

Best Matter smart plug: Eve Energy

Eve Energy is the smart plug pick because it does Thread right. It runs on Thread natively, which means it joins your Thread mesh, extends the network for other devices, and operates locally without depending on Eve’s cloud.

For Apple Home households, this is the cleanest plug experience available. It pairs easily, reports energy data, and stays responsive. In Home Assistant, it works well through the Matter integration, though you lose a few Eve-specific features that only surface in the Eve app.

The honest caveat: Eve Energy costs more than a basic Zigbee plug. If you’re running Home Assistant with a solid Zigbee coordinator, a ThirdReality Smart Plug Gen2 is a genuine Zigbee 3.0 plug with energy reporting and does the same job for less money. Eve Energy makes the most sense when you want something that works natively across Apple Home and Home Assistant without a bridge.

Eve Energy product notes

Best Matter light: Nanoleaf Essentials A19

The Nanoleaf Essentials A19 is a Thread-native bulb that was one of the earliest decent Matter lights. It pairs reliably, dims smoothly, and supports color temperature adjustment without the lag that plagues some Wi-Fi bulbs.

The local control story is solid. Thread means the bulb communicates locally through your border router. No cloud round-trips for basic on/off and dimming. Response times feel noticeably snappier than comparable Wi-Fi bulbs.

The caveat is that Nanoleaf’s app experience is mediocre, and if you’re deep into the Philips Hue ecosystem you probably won’t want to switch. But if you’re building around Home Assistant or Apple Home and want Matter-native lighting, this is the most reliable option at a reasonable price.

Best Matter lock: Aqara Smart Lock U200

The Aqara Smart Lock U200 is one of the few mainstream deadbolt locks that supports Matter natively over Thread. It’s a retrofit smart lock with a fingerprint reader and keypad, and it joins Home Assistant, Apple Home, Google Home, SmartThings, or Alexa directly as a Matter device.

The local control angle is the real draw. With a Thread border router on your network, the U200 runs entirely locally over Matter - no Aqara hub or cloud account required for lock and unlock. (Aqara’s own Hub M3 is optional and only adds extra Aqara-app features.) Thread’s low power keeps battery life reasonable, and the mesh means you don’t need line-of-sight to a single hub.

The caveats: Matter lock support is still maturing, so some advanced features (auto-lock schedules, user-code management) are currently easier in the Aqara app than over Matter. And like any Thread device, it needs a working Thread border router (a HomePod mini or second-generation HomePod, a Thread-capable Apple TV 4K, or Home Assistant’s own Thread support). If you specifically want Apple Home Key tap-to-unlock, the Schlage Encode Plus is the better pick - but note it works over HomeKit-over-Thread and Wi-Fi, not Matter.

Aqara Smart Lock U200 product notes

Best Matter sensor: Aqara Door/Window Sensor P2

Aqara’s Door/Window Sensor P2 is one of the first Thread-based contact sensors that actually works well over Matter. It’s small, battery-powered, and reports open/close state reliably.

Thread is the right transport for a battery sensor. Low power consumption means the CR123A battery lasts a reasonable amount of time, and the mesh network means you don’t need line-of-sight to a hub. It pairs directly with Home Assistant, Apple Home, or Google Home as a Matter device without needing an Aqara hub.

The caveat is that Matter’s sensor support is still limited. You get basic open/close reporting, but if you’re used to Zigbee sensors that expose temperature, battery percentage, and tamper alerts with fine-grained control, the Matter version feels stripped down. For simple door and window monitoring, though, it works.

Aqara Door/Window Sensor P2 product notes

Best Matter hub/bridge: Aqara Hub M3

The Aqara Hub M3 earns its spot by doing something clever: it bridges Aqara’s extensive Zigbee sensor lineup into Matter. If you have a bunch of Aqara Zigbee devices, the M3 exposes them as Matter devices to whatever controller you’re using.

This is useful if you want your Aqara sensors to appear natively in Apple Home or Google Home without requiring cloud integrations. It also functions as a Thread border router, so it pulls double duty in your network. The hub runs locally and doesn’t require Aqara’s cloud for basic operations.

The caveat is that bridging adds a layer of complexity. If you’re running Home Assistant with a good Zigbee coordinator, you can already use Aqara’s Zigbee devices directly, and the M3 doesn’t add much in that scenario. It’s most valuable for multi-ecosystem households that want Aqara hardware accessible everywhere.

Aqara Hub M3 product notes

What we’d avoid

Generic Wi-Fi-only Matter plugs. The marketplace is filling up with cheap Wi-Fi plugs that have a Matter badge but offer nothing you can’t get from a $10 Zigbee plug. They still congest your Wi-Fi, they don’t form a mesh, and the “Matter compatible” label doesn’t make them more reliable. If it’s Wi-Fi-only and not from a brand with a track record, skip it.

Overpriced Thread sensors with limited functionality. Some Thread sensors cost three times what a comparable Zigbee sensor costs and expose fewer data points over Matter. Until the Matter spec catches up to what Zigbee sensors already report, the premium isn’t justified for most people.

Anything marketed as “Matter-ready” with a firmware update coming later. If it doesn’t have Matter today, don’t pay for the promise.

When to buy Matter vs stick with Zigbee/Z-Wave

Buy Matter when you run multiple ecosystems and want one device visible in all of them. If your household uses Apple Home in the kitchen and Home Assistant in the office, Matter’s multi-admin is useful.

Buy Matter when you’re starting fresh and don’t want to buy a Zigbee coordinator or Z-Wave stick. Matter devices pair directly with Home Assistant, Apple Home, or Google Home without extra hardware (assuming you have a Thread border router for Thread devices).

Stick with Zigbee when you already have a working Zigbee mesh and coordinator. The device selection is larger, the prices are lower, and the feature exposure in Home Assistant is more mature. Zigbee sensors report more data, Zigbee lights have more options, and the protocol is battle-tested.

Stick with Z-Wave when reliability and range matter more than ecosystem flexibility. Z-Wave’s managed frequency band means less interference, and the device certification program means fewer compatibility surprises. For locks, sensors, and switches in a Home Assistant household, Z-Wave is still hard to beat.

The practical answer: most people building a local-first smart home today will end up with a mix. That’s fine. Home Assistant handles all of these protocols well. Buy the best device for each job, regardless of which protocol it speaks.

Related

• Zigbee vs Z-Wave vs Matter vs Thread
• Best local-first smart home hubs
• What “local-first” actually means

PoE (Power over Ethernet) cameras are the backbone of any serious local smart home video setup. Unlike WiFi cameras that depend on cloud services or struggle with bandwidth, PoE cameras run entirely on your local network—exactly what Home Assistant users need.

Why PoE for Home Assistant

The big advantage of PoE cameras is reliability and privacy. You control the footage, not a company server somewhere. A PoE camera needs only one cable for both power and data, runs through your network switch, and integrates directly with Home Assistant via ONVIF or RTSP streams.

The tradeoffs? You need PoE equipment (a switch or injector), running ethernet cable to camera locations, and some cameras require more setup than plug-and-play WiFi options. But the payoff is rock-solid performance and true local control. (Still weighing the wiring? See when to use PoE vs Wi-Fi for home cameras.)

Best Overall: Reolink PoE Line

Reolink offers the best balance of price, features, and local integration. Their Reolink PoE Camera Line covers most use cases with solid ONVIF support and free local recording.

The Reolink Duo 3 PoE is excellent for wide-area coverage—dual lenses give you a 180-degree field of view, reducing the number of cameras you need. Picture quality is crisp, and you get person/vehicle detection that works locally without cloud processing.

For doorbell coverage, the Reolink Video Doorbell PoE works well if you can run ethernet to your door. It provides reliable chime functionality and integrates via RTSP for Home Assistant. The Reolink TrackMix PoE adds pan-tilt functionality if you need motorized tracking.

Reolink’s real limitation is not cloud lock-in. A Reolink NVR records to its own hard drive, and Reolink states plainly that a cloud subscription is optional rather than mandatory, so a Reolink stack can run entirely on your LAN. What does bite people is connection count: each camera supports only a limited number of simultaneous streams, so Home Assistant, Frigate, and a phone app all pulling at once can exhaust it. Point one consumer at the camera and fan the stream out from there (go2rtc is the usual answer), or move to the lighter FLV stream that Home Assistant recommends when connections start dropping.

Budget Option: Amcrest

Amcrest cameras are the budget alternative that still deliver decent results. The Amcrest IP8M-2496E gives you 4K resolution at a reasonable price point. ONVIF support is solid, and they work reliably with Home Assistant’s ONVIF integration.

The Reolink Video Doorbell PoE is a solid choice if you need PoE at the door - a single Ethernet run carries power and video, with local RTSP/ONVIF and on-device person detection. (Note: Amcrest’s AD410 doorbell is Wi-Fi only, not PoE.)

Amcrest’s tradeoff: the mobile app is clunky and pushes cloud features. Ignore it. Configure everything through the camera’s web interface and stream directly to Home Assistant.

Pro Grade: UniFi Protect

If you already run UniFi networking, the UniFi Protect ecosystem is worth considering. It’s not just cameras—it’s a complete local video system with excellent Home Assistant integration via the UniFi Protect integration.

UniFi cameras are pricier, but you get enterprise-grade build quality, native local recording without any cloud requirement, and tight integration if you’re already in the UniFi ecosystem. The downside is it’s a bigger commitment—you need a console that actually runs the Protect application: a UDM Pro, UDM SE, UDM Pro Max, Dream Router, or a UNVR/UNVR Pro (a CloudKey Gen2+ also runs Protect but is the legacy option). The base UniFi Dream Machine does not run Protect at all and has no video storage, so check the model before you buy.

Integration Tips

For Reolink cameras, reach for the official Reolink integration first. It is Local Push, needs no cloud account, and it also covers cameras that sit behind a Reolink NVR or Home Hub rather than on the network directly. For other brands, add the camera through the ONVIF integration or point an ffmpeg camera at its RTSP URL. ONVIF is easier for basic motion detection; a raw RTSP stream gives you more control over video quality and frame rate.

Store footage locally using Home Assistant’s native camera recording: the camera.record action saves .mp4 clips to an allowed local directory or a mounted NFS/SMB share. Avoid cloud NVR subscriptions—local storage is the point.

If you need person/vehicle detection without cloud AI, look at Frigate (separate Add-on) running on the same Home Assistant machine, or see how to run Frigate on an old PC. It processes video locally and sends reliable motion events to Home Assistant.

Quick Verdict

For most Home Assistant users, Reolink delivers the best value—good quality, reliable local integration, reasonable price. Go with the Reolink Duo 3 PoE for broad coverage or a single Reolink PoE Camera Line camera for specific spots. Budget users should grab an Amcrest IP8M-2496E and call it a day. UniFi Protect is only worth it if you’re already all-in on UniFi networking.

Living in an apartment means living in close quarters. Shared walls, shared hallways, sometimes shared Wi-Fi. Every cloud-connected device you add is another data stream leaving your home and passing through infrastructure you don’t control. In an apartment, that should bother you more than it would in a detached house.

The good news: the best privacy-respecting smart home devices also happen to be the best devices for renters. They’re wireless, non-permanent, and don’t need cloud accounts to function. You get smart home features without handing your daily routine to a server farm.

This guide covers the devices that actually make sense for apartments, and what to avoid.

Why privacy matters more in apartments

A few things are different when you’re not in a standalone house:

• Shared networks. Some apartments have shared or landlord-managed Wi-Fi. Even on your own network, your traffic passes through building infrastructure. Cloud-dependent devices send data constantly.
• Proximity to neighbors. A camera pointed at your front door also captures your neighbor’s door. A voice assistant picks up conversations through thin walls. These aren’t hypothetical problems.
• Landlord access. If your smart home depends on cloud accounts, anyone with access to those accounts has visibility into your space. Local-only devices don’t have this attack surface.
• Smaller spaces, less room to hide sensors. In a studio or one-bedroom, a camera covers most of your living area. That’s surveillance, not security.

The solution is simple: choose devices that process everything locally and don’t phone home.

Hub: the foundation

You need a local hub to tie everything together. No cloud account required for either of these.

Home Assistant Green is the simplest option. A small box, power cable, Ethernet cable. Plug it into your router and you have a fully local smart home controller. No account creation, no cloud dependency. Everything stays on your network.

For more horsepower, a mini PC running Home Assistant OS does the same job with headroom for add-ons and local voice processing. Either way, the hub is a box that plugs in and unplugs when you move.

Sensors

Sensors are the highest-value, lowest-risk category for apartments. They’re small, battery-powered, adhesive-mounted, and collect only the data you decide to use locally.

Aqara Door/Window Sensor P2 monitors entry points over Matter (running on Thread) — note it is not a Zigbee sensor, so it needs a Thread border router on your network (a HomePod mini or second-generation HomePod, a Thread-capable Apple TV 4K, Home Assistant’s own Thread support, or another border router). Once joined via Home Assistant’s Matter integration, automations run locally with no cloud account. Stick one on your front door, balcony door, and any windows accessible from outside.

If you’d rather stay purely Zigbee, Aqara’s older Door and Window Sensor (the Zigbee T1/MCCGQ-series) and other plain Zigbee contact sensors pair to a Zigbee coordinator instead — same local, no-cloud result without needing Thread.

Third Reality sensors are solid Zigbee options for temperature, humidity, and contact sensing. Cheap, reliable, and completely local when paired with a Zigbee coordinator.

Aqara and SwitchBot leak sensors belong under every sink, next to the washing machine, and near any water heater access. A leak in an apartment can damage the unit below you and cost thousands. These are tiny, battery-powered, and sit on the floor. No installation at all.

For a deeper look at sensor options, see best local home sensors.

Presence detection instead of cameras

This is the big one for apartments. Cameras in a small living space are privacy nightmares, even when they’re local-only. You don’t need a camera watching your living room. You need to know if someone is there.

Everything Presence One uses mmWave radar to detect presence without a camera. It knows if someone is in a room, how many people, and roughly where. No video, no images, no recordings. Just presence data processed entirely on your local network. This is the privacy-respecting alternative to indoor cameras for apartments.

Use presence sensors for lighting automations, HVAC control, and occupancy-based security. They give you most of what a camera would, minus the surveillance. See best local presence sensors for more options.

Smart plugs

Plug-in devices are inherently renter-friendly and apartment-friendly. No modification, no wiring.

Shelly Plus Plug US runs on local Wi-Fi with energy monitoring, and Shelly’s current US model, the Plug US Gen4, does the same for about $20. No cloud account needed. It works standalone or with Home Assistant.

Zooz ZEN15 is a Z-Wave plug with energy monitoring and high power capacity. Good for window AC units or space heaters where you want both control and usage tracking.

Both stay entirely local. No data leaves your network.

Eve’s Thread devices

Eve deserves a specific mention. Their Thread-based devices are designed privacy-first: no cloud, no account creation, no data collection. Period.

Eve Thermo is a Thread-based radiator valve, useful in apartments with radiator heating. Local control, no bridge required with a Thread border router.

Eve also makes door/window sensors, motion sensors, and energy monitoring plugs, all with the same no-cloud philosophy. If your apartment has a Thread border router (most HomePods and some other devices act as one), Eve devices work without any hub at all.

Locks

Apartments usually mean you can’t replace the deadbolt. Retrofit locks solve this.

August Wi-Fi Smart Lock attaches to the inside of your existing deadbolt. Your landlord’s key still works. It does lean on cloud features, but the physical installation is fully reversible.

Level Lock+ hides inside the existing deadbolt mechanism. Nearly invisible. Older Level Lock+ “Previous Model” units run their local path through Apple Home, while Level Lock+ (Matter) units (and existing Level Lock+ units updated via Level’s free Matter firmware) add a native Matter-over-Thread path. The cleanest option for apartments where you don’t want hardware visible on the door.

Neither requires replacing landlord hardware. Both come off cleanly at move-out.

What to avoid in an apartment

• Cloud-only devices. If it requires an account to function, your data is leaving your home. In an apartment with shared infrastructure, that’s an unnecessary risk.
• Hardwired anything. In-wall relays, wired cameras, smart switches. You don’t own the walls.
• Indoor cameras. In a small space, a camera covers your entire life. Use presence sensors instead.
• Devices that modify switches or outlets. Even “easy” switch replacements are a hassle in a rental and leave you liable for electrical work.
• Voice assistants with cloud processing. Alexa and Google Home process audio on remote servers. In an apartment with thin walls, that means your neighbors’ conversations might end up there too.

The apartment privacy stack

A complete, privacy-respecting apartment setup looks like this:

1. Hub: Home Assistant Green plugged into your router
2. Sensors: Zigbee contact and leak sensors (or Aqara P2 over Thread if you have a border router) on every entry point and water source
3. Presence: Everything Presence One in main living areas
4. Plugs: Shelly or Zooz on lamps, fans, and appliances
5. Lock: August or Level retrofit on the front door

No cameras. No cloud accounts. No permanent modifications. Everything processes locally, everything comes with you when you move, and nothing reports your habits to a server you don’t control.

Related links

• Best local-first smart home gear for renters
• What “local-first” actually means
• Best local presence sensors
• Best local home sensors

Building a local-first smart home doesn’t require expensive hardware. You can get solid sensors, switches, and bulbs well under $50 that work directly with Home Assistant without cloud dependencies. Here are my picks for the best budget-friendly gear, and a few honest notes on where the “$50” line gets blurry once you account for the radio or hub you need to talk to them.

Sensors and Automation Triggers

Start here. Sensors are the backbone of any automation, and you don’t need to spend much to get reliable performance.

Aqara Door and Window Sensor P2 is a great budget contact sensor and a modern one: it’s Matter-over-Thread, so it connects directly to a Matter controller and Thread border router without an Aqara hub. In Home Assistant that means adding it to the Matter integration with an HA-supported Thread border router (Home Assistant Connect ZBT-2 / Yellow, a HomePod mini or second-generation HomePod, a Thread-capable Apple TV 4K, or similar). It runs about $20 and lasts for years on a coin cell. The catch is the Thread requirement: if you don’t already have a border router, factor that in.

Sonoff SNZB-02D is the cheaper, simpler path if you’d rather stay on plain Zigbee. These run about $12 and pair with any Zigbee coordinator (the SONOFF Zigbee 3.0 USB Dongle Plus (ZBDongle-P) is around $20) through ZHA or Zigbee2MQTT. No cloud required—everything stays local. It reports temperature and humidity on a small 2.5-inch LCD out of the box.

For motion, Sonoff SNZB-03P at around $13 is hard to beat. It’s a basic Zigbee PIR—a fairly standard detection cone, and a built-in light sensor that only reports a coarse bright/dim level (Zigbee2MQTT exposes it, and it refreshes only when the sensor sees motion) rather than a numeric lux value—but for “lights on when I enter a room” it’s perfectly adequate. Pair it with a relay like the Sonoff Mini R4 Matter (the “M” variant speaks Matter; the plain Mini R4 is Wi-Fi/eWeLink with local LAN control) for fast in-wall switching.

Third Reality Motion Sensor is another solid Zigbee option around $15. Small form factor, works well under both ZHA and Zigbee2MQTT.

Switches and Plugs

This is where you actually control things. Budget options exist, but you trade some features.

Shelly 1 Mini Gen3 at roughly $13 is the best budget in-wall switch. It’s a tiny Wi-Fi relay (no hub needed) rated up to 8A, supports local MQTT and on-device scripting, and fits in most junction boxes. Two honest caveats: this base “1 Mini” does not have power metering (the 1PM Mini Gen3 does, for a couple dollars more), and Wi-Fi can be less predictable than Zigbee in RF-crowded homes.

Shelly Plug US Gen4 at about $20 is a Wi-Fi smart plug with real power metering—useful for finding out what a device actually draws. It ships with Matter-certified firmware by default and switches to Zigbee with five presses of the device button; either way, turn off the Shelly cloud and drive it over local MQTT or the Shelly HA integration if you want it fully local. The similarly named Shelly Plug S is the European Type-F model and will not fit a US outlet.

TP-Link Kasa KP125M at ~$15 is a Matter-capable plug and worth a look on sale. It can run locally via Matter, but the out-of-box experience leans on the Kasa app/cloud and takes more fiddling than the Shelly options.

Sonoff Mini R4 Matter at ~$15 is tiny and Matter-native, good for behind-switch installs. The tradeoff is that you need a Matter controller (Home Assistant has one built in), and Matter-over-Wi-Fi locks are still maturing in places—but for a relay it works well.

Hubs and Coordinators

Here’s the honest correction to a claim you’ll see repeated online: the Home Assistant Voice Preview Edition (~$60, often listed around $59) is a voice satellite, not a hub. It’s an ESP32-S3 board with an XMOS audio front-end, a speaker, a mic array, a rotary dial and a mute switch. It does not run Home Assistant, has no Zigbee/Thread radio, and has no “LED matrix”—it talks to a separate Home Assistant server over Wi-Fi and the speech-to-text/intent handling runs on that server (or Nabu Casa). It’s a great local voice add-on, but you still need an actual HA install somewhere to point it at.

So for a real local hub on a budget, the move is a small computer (a Raspberry Pi or an old mini-PC) running Home Assistant plus a Zigbee or Thread radio. For Zigbee/Thread, the SONOFF Zigbee 3.0 USB Dongle Plus (E) (~$20) and the ConBee III (~$40, and notably it can also run Thread firmware) are both solid coordinators. Don’t overthink the choice—either works well with ZHA or Zigbee2MQTT.

Lighting (Budget Picks)

Nanoleaf Essentials A19 at ~$20 is Matter-over-Thread—no proprietary bridge needed. Good color, reliable, and a fair deal even if you only ever use it as a decent bulb. You will need a Thread border router and a Matter controller (Home Assistant covers the controller side).

Third Reality Color Bulb at ~$15 is the cheaper option. It’s a Zigbee bulb—dimmer and with a narrower color gamut than the Nanoleaf—but it pairs straight into ZHA/Zigbee2MQTT with no Thread requirement, which can actually be simpler.

For LED strips on a budget, look for a Zigbee or ESP-based (ESPHome/WLED) controller you can drive locally rather than a Wi-Fi strip that only works through the vendor app—the latter defeats the point of going local.

What to Skip

Some things aren’t worth the savings:

• No-name Zigbee sensors with no quirk/converter support — you’ll lose hours troubleshooting. Stick with Sonoff, Aqara, or Third Reality.
• Cloud-only switches and plugs — if the device stops working when the vendor app or internet is down, it isn’t really local.
• Treating a voice satellite as a hub — the HA Voice PE is excellent at what it is, but it can’t be your only “brain.”

Bottom Line

You can build a capable local smart home for well under $50 per room once the coordinator is in place. A reasonable starter stack: a SONOFF Zigbee 3.0 USB Dongle Plus (ZBDongle-P), a few Sonoff SNZB-02D sensors, and a Shelly 1 Mini Gen3 or two—that’s roughly $60 for sensing plus control, all running locally with no subscription and no cloud. If you’d rather follow a full parts list, see beginner local-first stacks by budget.

If you want voice on top, the Home Assistant Voice Preview Edition is a great local satellite—just remember it plugs into a Home Assistant server, it doesn’t replace one.

When you’re building a local-first smart home, the choice between Thread and Zigbee for your light bulbs affects reliability, how you integrate with your ecosystem, and how future-proof your kit is. Both are low-power mesh protocols that share the same underlying radio, but they differ in how they connect to the rest of your house. Here’s an honest breakdown for a Home Assistant, HomeKit, or Hubitat setup.

What the two protocols actually are

Zigbee has been around since the mid-2000s and has a huge device ecosystem - Philips Hue, IKEA, Sonoff, Aqara, Third Reality, and many more. It runs on 2.4 GHz using the 802.15.4 radio standard, draws very little power, and forms a self-healing mesh where mains-powered devices (bulbs, plugs) relay traffic for battery devices. To use Zigbee you need a coordinator - a radio that runs the network. In Home Assistant that’s a USB stick driven by ZHA or Zigbee2MQTT; in Hubitat or a SmartThings hub it’s the radio built into the hub.

Thread is newer and also runs on 2.4 GHz / 802.15.4 - it is the same kind of radio as Zigbee, not a different band. The big difference is that Thread is IP-based: every Thread device gets an IPv6 address and is reachable over your network. Thread is the transport that Matter most often rides on for low-power devices, which is why it matters for a future-proof setup. Instead of a coordinator, a Thread network needs a border router, which bridges the Thread mesh onto your home IP network. Mains-powered Thread devices act as routers within the mesh, just like Zigbee’s mains devices do.

So the honest framing: these are siblings, not opposites. The practical question is which one a given bulb speaks and how cleanly it lands in your ecosystem.

Zigbee: the established, deep ecosystem

If you already run Zigbee in Home Assistant, you’re on solid ground. The device selection is the largest in the smart home world, prices are low, and ZHA or Zigbee2MQTT control it all locally with no cloud.

A few ecosystem notes worth getting right:

• Hubitat has both a built-in Zigbee radio and a built-in Z-Wave radio, so it handles Zigbee bulbs natively.
• HomeKit has no native Zigbee support. To get Zigbee bulbs into Apple Home you go through a bridge - the Philips Hue Bridge exposes Hue’s Zigbee bulbs to HomeKit, or you can use Home Assistant’s HomeKit Bridge integration to expose any HA device.
• The Philips Hue Bridge is local - it does not require the cloud to control your lights on your LAN - but it is a closed Zigbee gateway. It only manages Hue and Hue-friendly devices and cannot act as a generic Zigbee coordinator for arbitrary brands. If you want one coordinator for everything, use a generic stick with ZHA or Zigbee2MQTT instead of (or alongside) the Hue Bridge.
• For a generic Zigbee coordinator, sticks like the ConBee III or the Sonoff Zigbee 3.0 USB Dongle Plus are common picks; our guide to the best Zigbee coordinators for Home Assistant compares the options in depth. (Note: Aeotec is best known for Z-Wave, but it now makes Zigbee gear too - its Z-Stick 10 Pro is a single USB dongle that runs both Z-Wave and Zigbee, usable with ZHA or Zigbee2MQTT.)

Zigbee’s main weakness is that network health depends on layout. The mesh routes around a failed node in most cases, but a poorly placed coordinator or too few mains-powered routers can cause dropouts. Good router placement matters.

Thread: the Matter-era option

Thread shines when you’re building around Matter. Because it’s IP-based, Matter-over-Thread bulbs can be commissioned into Apple Home, Google Home, SmartThings, or Home Assistant (via the Matter integration plus a Thread border router) without a brand-specific bridge. That’s the real “future-proof” appeal: one device, several ecosystems, all local.

For bulbs, your Thread/Matter options today include the Nanoleaf Essentials Matter-over-Thread bulbs and the Aqara LED Bulb T2, which is a dual-radio bulb - it can run as Matter-over-Thread (no hub, direct to a Matter ecosystem) or as Zigbee, in which case it joins any ordinary coordinator through ZHA or Zigbee2MQTT (2.7.2 or later) with no Aqara hub involved. It ships with the Thread firmware active, so Zigbee mode takes a one-time trip through the Aqara Home app over Bluetooth, and you have to remove the bulb from your Aqara account before it will join a third-party Zigbee network. Even Philips Hue’s newest-generation bulbs have started adding Thread radios alongside Zigbee and Bluetooth, so a bulb can support more than one protocol.

To use Thread you need a border router. In a Home Assistant setup that’s commonly the Home Assistant Connect ZBT-2 (running Thread firmware) or a HomePod mini, a second-generation HomePod, a Thread-capable Apple TV 4K, or a recent Google Nest Hub acting as a border router. Make sure you actually have one before buying Thread bulbs.

Real-world tradeoffs

• Device availability. Zigbee still has a far larger catalog of bulbs and accessories. Thread/Matter bulbs are growing but remain a smaller selection.
• Maturity. Zigbee is battle-tested. Matter-over-Thread is solid and improving, but commissioning quirks and uneven manufacturer implementations still show up - check reviews for the specific bulb.
• Ecosystem reach. Thread/Matter reaches Apple Home, Google, and others without a brand bridge. Zigbee reaches HomeKit only through a bridge, but works natively in Home Assistant and Hubitat.
• Both are local. Neither protocol requires the cloud for on-LAN control. This is not a local-vs-cloud decision.

Quick verdict

If you already have a working Zigbee setup, there’s no urgency to switch - it’s local, deep, and cheap. Keep buying Zigbee bulbs.

If you’re starting fresh and want to lean into Matter across multiple ecosystems, Thread/Matter bulbs (with a border router in place) are the more future-proof choice. See our best Matter-over-Thread light bulbs roundup for specific picks. A dual-radio bulb like the Aqara LED Bulb T2 is a nice hedge: run it on Thread now, or fall back to Zigbee if that suits your hub better.

Either way, you’re staying local. Pick based on what your hub speaks, what your ecosystem needs, and which protocol the bulbs you actually want to buy support.

Smart switches with physical buttons matter when your internet goes down. They matter when you have guests who don’t want to open an app. They matter when automation fails and you need to flip a switch like it’s 1995. If you’re building a local-first smart home with Home Assistant—or running Hubitat or a HomeKit hub locally—you need switches that work even when the cloud doesn’t.

Here’s the reality: most “smart” switches nowadays are touch-only panels that break the moment your internet hiccups. That’s not acceptable for a real local setup. These switches keep the physical button working, locally, without dependency on cloud servers.

What makes a switch work locally

The key is Z-Wave or Zigbee with a local hub. WiFi switches can work locally with some setups, but they often phone home on first boot or lose functionality without cloud access. Z-Wave and Zigbee switches communicate directly with your Home Assistant instance (or Hubitat), and they keep working when your router dies. For a wider roundup of local paddle switches and dimmers, see the best local smart switches and dimmers.

Look for switches that support Z-Wave S2 security or Zigbee 3.0. These standards have local control baked in. Avoid anything that requires a cloud account to function—your automations shouldn’t depend on a company’s servers staying online.

Top picks for local control

Inovelli Blue Series 2-1

The Inovelli Blue Series 2-1 is one of the most feature-packed Zigbee switches you can buy. It works with Zigbee2MQTT and ZHA in Home Assistant out of the box, supports Zigbee 3.0 with secure binding, and has a physical paddle that works even when your network is down. The LED bar gives you visual feedback without needing the app. It works with Hubitat and SmartThings natively too.

Tradeoff: parameter configuration is done through Zigbee2MQTT or ZHA rather than a phone app, and the paddle click sound is louder than traditional switches. Some users disable the LED indicator to reduce light pollution in bedrooms.

Zooz Z-Wave family

Zooz makes several switches worth considering. The Zooz Zen72 800LR is a solid dimmer with physical controls and Z-Wave Long Range support for larger homes. The Zooz Zen77 Dimmer works similarly.

The trade-off with Zooz: firmware updates have been historically slow, and some models have had issues with association groups in Home Assistant. They’re fine for basic on/off/dimming but may lack the advanced features Inovelli offers. Worth noting: Zooz support has improved recently, and their 800LR line has better range than standard Z-Wave.

Leviton Z-Wave switches

If you want something boring and reliable, Leviton makes solid Z-Wave hardware. The Leviton ZW15S Switch and Leviton ZW6HD Dimmer work well with Home Assistant and Hubitat. They feel like standard Decora switches—no weird touch panels, just a regular paddle.

Tradeoff: these are boring. No LED bars, no fancy features, no app-driven extras. That’s the point. They just work. That predictability is the entire appeal.

Budget option: Shelly

Shelly answers this question differently: these are relay modules, not switches. The Shelly Plus 1 and Shelly Plus 2PM mount in the wall box behind the switch you already have, so the physical control stays exactly what it was before. Both support local control through the Shelly integration or MQTT. If you are weighing Shelly against flashed firmware, our guide on choosing between Shelly and Sonoff for relays digs into the tradeoffs.

The catch is narrower than it first sounds. In the default input mode the switch position maps straight to the relay inside the device’s own firmware, so the light still turns on from the wall with the network down; what an outage costs you is remote and automation control, not the paddle. The real trap is detached mode, where the input is deliberately separated from the output and only fires automations. Set that up and a Wi-Fi or Home Assistant outage does take the wall switch with it. Wi-Fi is also more prone to interference than Z-Wave, so keep expectations realistic in a house already running a healthy Z-Wave or Zigbee mesh.

For HomeKit and ecosystem flexibility

If you’re running HomeKit locally with a HomePod or Apple TV as your hub, the Lutron Caseta Diva Smart Dimmer is a solid choice. It uses Lutron’s proprietary protocol (not Z-Wave or Zigbee), but it works locally and doesn’t require internet. The physical dimmer paddle works even when your HomePod is offline.

The Aqara Light Switch H2 US is a dual-protocol switch, and it ships in Thread mode: out of the box it joins Home Assistant over Matter through any Thread border router. You can switch it to Zigbee firmware from the Aqara app, after which it pairs to ZHA or Zigbee2MQTT like any other Zigbee 3.0 device. No Aqara hub is required on either path. The buttons are physical clicky switches, not touch panels.

Tradeoff: the Lutron needs its Smart Bridge, because Clear Connect is a proprietary protocol with no generic coordinator. The Aqara needs no Aqara hub at all - just a Thread border router in Matter mode, or a Zigbee coordinator you probably already run. Both companies have decent track records for keeping their local APIs functional.

Quick verdict

For most local-first Home Assistant setups, the Inovelli Blue Series 2-1 is the best balance of features, local reliability, and physical button feel. If budget matters more than features, grab a Zooz Zen72 and accept slightly less polish. Want zero fuss? The Leviton ZW15S is unsexy but bulletproof.

Whatever you choose, make sure it works with your hub before you buy. Z-Wave switches need your hub to include them. Zigbee switches need a coordinator. WiFi switches need reliable WiFi. The “smart” part only matters when the physical button works—that’s the whole point of going local.

Traditional motion sensors (PIR) detect movement. That is fine for hallways and doorways, but terrible for rooms where you sit still: offices, living rooms, bathrooms. You stop moving for a few minutes, the lights turn off, and you wave your arms like a fool.

mmWave presence sensors solve this. They detect the presence of a person in a room, even when they’re sitting perfectly still, by sensing micro-movements like breathing.

Our picks:

• Best overall: Aqara FP2
• Best budget option: Aqara FP1E
• Best for Home Assistant tinkerers: Everything Presence One

Why mmWave matters vs PIR

PIR sensors detect infrared radiation changes caused by movement. They are cheap, reliable for what they do, and perfectly fine for triggering lights when you walk into a room.

But PIR can’t tell the difference between an empty room and a room with someone sitting still in it. That is a fundamental limitation, not a product flaw.

mmWave radar sends out radio waves and detects reflections from objects, including the tiny movements of a breathing human. This means:

• lights stay on while you’re reading in a chair
• bathroom fans keep running while you’re in the shower
• office automations stay active during focused work
• rooms can truly know whether they’re occupied

The tradeoff is that mmWave sensors are more expensive, can be trickier to configure, and sometimes produce false positives from things like fans or pets. But when dialed in properly, they’re transformative for room-aware automation.

Best overall: Aqara FP2

The Aqara FP2 is the best mmWave presence sensor for most Home Assistant users right now. It combines good detection quality with practical features that make it useful out of the box.

Why it wins:

• zone-based detection, which lets you define multiple detection zones within a single room
• good Home Assistant integration via HomeKit Controller (it is a Wi-Fi device, so no Aqara hub or Zigbee coordinator is needed)
• reasonable false positive behavior once configured
• presence, motion, and light level sensing in one device
• Wi-Fi connected, no Zigbee coordinator required for this one

The zone detection is the standout feature. You can set up zones for different areas of a room (desk, couch, doorway) and trigger different automations based on which zone is occupied. Few sensors at this price offer zone tracking at all, though the cheaper ESPHome-based Everything Presence Lite does, with zones configured in Home Assistant instead of a vendor app.

The caveat is that initial setup and zone calibration takes patience. The Aqara app is required for configuration, and the detection zones need real-world tuning. It isn’t plug-and-play, but the result is worth the setup time.

Aqara FP2 product notes

Best budget option: Aqara FP1E

The Aqara FP1E is the simpler, cheaper single-area option, and the globally available successor to the original China-only FP1. It does basic mmWave presence detection without the multi-zone features of the FP2.

Why it makes sense:

• lower price point for rooms where zone detection isn’t needed
• Zigbee-based, which means it integrates directly with your Zigbee coordinator
• clean presence/absence detection
• good Home Assistant support via ZHA or Zigbee2MQTT

The FP1E is the right pick for rooms where you just need to know “is someone in here or not” without caring about where exactly they’re sitting. Bathrooms, small offices, and utility rooms are good candidates.

The downside compared to the FP2 is no zone support, less configurability, and a narrower detection field. For simple presence detection in smaller rooms, that’s fine. For larger rooms or complex automation, spend up for the FP2.

Aqara FP1E product notes

Best for Home Assistant tinkerers: Everything Presence One

Everything Presence One is a community-designed sensor built specifically for the Home Assistant ecosystem. It runs on ESPHome, which means it’s fully local, fully customizable, and speaks directly to Home Assistant without any vendor cloud or app.

Why tinkerers love it:

• ESPHome-based, fully local, no cloud, no vendor app
• completely open and customizable
• combines mmWave with PIR, temperature, humidity, and light sensors
• designed by and for the Home Assistant community

This is the most local-first option on the list by a wide margin. There is no vendor cloud involved at any point. Configuration happens in ESPHome YAML, and everything runs locally.

The tradeoff is that it requires more setup effort than the Aqara sensors. You need to be comfortable with ESPHome, and tuning the mmWave sensitivity takes experimentation. The detection quality is good, but the out-of-box experience isn’t as polished as the FP2.

If you’re the kind of person who reads ESPHome documentation for fun, this is your sensor. If you want something that works well with less fiddling, start with the Aqara FP2.

Everything Presence One product notes

Also worth knowing: two newer options

The three picks above predate two sensors that are now worth checking before you buy:

• Aqara FP300 is a battery-powered 5-in-1 sensor (mmWave, PIR, light, temperature, and humidity) that speaks both Thread/Matter and Zigbee, so it needs no Aqara hub on either radio. It ships with the Thread firmware active, so pairing it to ZHA or Zigbee2MQTT takes a one-time protocol switch in the Aqara Home app first. It does not do FP2-style multi-zone positioning, but it goes where you cannot run a USB cable.
• Everything Presence Lite is the cheaper ESPHome sibling of the Presence One. It tracks up to three targets at once and lets you configure detection zones directly from Home Assistant, with no vendor app involved.

For a fuller comparison of these, including current prices, see best mmWave presence sensors 2026.

Practical tips for mmWave sensors

• Mount them high and angled down for the best coverage pattern.
• Keep them away from fans and HVAC vents because moving air can cause false triggers on some sensors.
• Start with conservative sensitivity and tune up if needed. False negatives are annoying. False positives that turn lights on at 3 AM are worse.
• Test with the room in actual use before finalizing your automation. Sitting at your desk for 30 minutes is a better test than waving your hand in front of the sensor.

Final recommendation

Buy the Aqara FP2 if you want the best balance of features and usability. Buy the Aqara FP1E for simpler rooms where basic presence detection is enough. Buy the Everything Presence One if you want the most local-first, customizable option and are comfortable with ESPHome. If you need a wire-free sensor, or want zone tracking on a fully local ESPHome device, check the Aqara FP300 and Everything Presence Lite above first.

Related:

• Best mmWave presence sensors for 2026
• Best local-first smart home hubs
• Best Zigbee coordinators for Home Assistant

If you’re running Home Assistant and want your sprinkler system to automatically skip watering when it rains, the honest truth is that most “smart” irrigation controllers are cloud-first. A few are fully local, and even cloud controllers can be made smarter with Home Assistant doing the rain-skip logic. Rain skip is arguably the most valuable feature for any controller—it saves water, protects your lawn, and actually justifies the “smart” label.

What Makes a Good Local-First Irrigation Controller

Before diving into specific products, here’s what matters for a Home Assistant setup:

How “local” really is local. Many popular Wi-Fi controllers only expose a cloud API—Home Assistant talks to the vendor’s servers, not the device on your LAN. That works, but it depends on the internet and the vendor keeping the API alive. A handful of products offer a true local API or use Zigbee/Thread, which keeps everything on your network.

Where rain-skip logic lives. Some controllers run their own weather-based skip in the cloud. The more reliable approach for a local-first home is to let Home Assistant decide—pull rain data from a weather integration (Met.no, Open-Meteo) or a local rain sensor, and have an automation hold the watering. That way the logic doesn’t depend on the controller’s cloud at all.

Zone count. Residential controllers typically support 4–16 zones. Don’t overpay for capacity you won’t use.

OpenSprinkler – The Local Multi-Zone Controller

If you have an in-ground system with real 24V AC valves and you want it off the cloud entirely, the OpenSprinkler is the one to start with, and it is the piece this category is usually missing. It is an open-source controller that drives 8 zones on the main board and expands to 72 with zone expanders, and it exposes a documented local HTTP JSON API on your LAN. On the Home Assistant side you install the mature hass-opensprinkler custom integration from HACS and point it at the controller’s IP address and password — there is no vendor account and no cloud relay anywhere in the path.

Rain skip can go either way here, which is the point. The controller has SN1/SN2 sensor terminals for a physical rain or soil-moisture sensor wired straight to it, and it also has its own weather-based watering adjustment that calls an online weather service. For a local-first build the cleanest arrangement is to leave that built-in weather adjustment off and let a Home Assistant automation hold the program using your weather integration or a local sensor — the same pattern as everything else on this list, except that here the controller never needed the cloud to begin with.

Expect roughly $140 to $185 depending on which variant you pick (AC, DC or latching solenoid) and whether you add the wired Ethernet module. The AC model expects the 24V AC transformer your old controller already used, and you buy it direct from the OpenSprinkler store.

Tradeoff: You’re wiring into valve terminals, not screwing a timer onto a hose bib. It’s the most capable local option here and also the most involved to install.

FrankEver FK-06X – Six Local Zones Without the DIY

If OpenSprinkler feels too hands-on, the FrankEver Smart Sprinkler Controller FK-06X is a 6-zone 24V AC controller built on Shelly hardware and running Shelly’s firmware. That matters practically: it has an on-device web interface, speaks MQTT, and is driven by Home Assistant’s built-in Shelly integration over the LAN — so you get a multi-zone local setup on a core integration, with no custom component to maintain. It runs around $130 and is stocked by US retailers.

Rain skip is the same story as OpenSprinkler: it has weather-aware scheduling of its own, but the resilient version is a Home Assistant automation gating the zones.

Tradeoff: Much newer and less battle-tested than OpenSprinkler, and Wi-Fi only.

Rachio 3 – Popular, but Cloud-Only

The Rachio 3 Smart Sprinkler Controller is among the best-known smart sprinkler controllers in the US. It works reliably, has polished app software, and includes weather-based “Weather Intelligence” rain skip.

Be clear-eyed about the integration, though: Rachio is cloud-only for Home Assistant. The official integration is Cloud Push—it requires your HA instance to be reachable from the internet to receive updates, and there is no stable, documented local API. Community plugins exist, but they still go through Rachio’s cloud (just via outbound calls). Rachio has also changed its API in the past in ways that temporarily broke HA integrations.

So Rachio is a fine choice if you accept the cloud dependency and want a turnkey experience—but it is not a local-first product, and you can’t run it offline.

Eve Aqua – The Local-First Valve

If you want the most local experience possible, the Eve Aqua is a Thread smart water valve. It works locally with Home Assistant through the HomeKit Controller integration (HomeKit over Thread) - Eve has not yet shipped its promised Matter upgrade for the Aqua - and needs no cloud account for core control. You need a Thread border router on the network; Home Assistant then pairs the valve through that same HomeKit Controller integration, not through Matter.

It’s a single-outlet hose/valve controller rather than a multi-zone manifold timer—it threads onto a tap and is great for drip lines, a soaker, or a Gardena/Kärcher-style distributor. Rain skip isn’t automatic; you build it as a Home Assistant automation: pull rain from your weather integration (Met.no/Open-Meteo) and close the valve. Slightly more setup, but it’s fully local and very reliable.

Tradeoff: Effectively single-zone. For a real multi-zone in-ground system you’d want the OpenSprinkler or the FK-06X above rather than a stack of these.

LinkTap – Local API and MQTT

The LinkTap Smart Water Timer is a battery-powered tap timer that talks to a small LinkTap Gateway. Unusually for this category, it offers a genuine local HTTP API and a documented local MQTT integration, so Home Assistant can control it without going through LinkTap’s cloud. A community custom component drives the local “instant watering” path directly.

Rain skip can be handled either by LinkTap’s own weather features or—better for local-first—by a Home Assistant automation. Note the community local integration focuses on instant on/off; full schedule editing over the local API is more limited, so many people keep schedules simple and let HA gate them.

Tradeoff: Less mainstream in the US and smaller English-language community than the big brands, but the local story is one of the best here.

Orbit B-hyve XR – Budget Wi-Fi, Cloud Integration

The Orbit B-hyve XR Smart Sprinkler Timer is an affordable multi-zone Wi-Fi controller with a rain-sensor input and weather-based skip in its app. It’s a reasonable value pick.

For Home Assistant, integration is via a community (HACS) custom component, and like Rachio it’s cloud-based—it connects to Orbit’s servers over a WebSocket; there’s no supported local API. The app is less polished than Rachio’s and some users see occasional connectivity hiccups, but for the price it’s a solid multi-zone option if you’re OK with the cloud dependency.

Third Reality Smart Watering Kit – Local Zigbee, but for Pots

The ThirdReality Smart Watering Kit is worth knowing about, but set expectations: it’s a battery-powered Zigbee 3.0 kit for indoor potted plants, not a sprinkler or in-ground irrigation controller. It pumps from a reservoir and pairs nicely with a Third Reality soil-moisture sensor.

The upside for local-first homes is real: it has excellent ZHA and Zigbee2MQTT support, so it runs entirely on your Zigbee network with no cloud. If your “irrigation” is houseplants or a small balcony garden, it’s a cheap, fully local option.

Tradeoff: Not a lawn/zone controller. Best as a supplemental, indoor watering solution.

Quick Verdict

For true local-first control of a multi-zone in-ground system, OpenSprinkler is the pick — open firmware, a documented local HTTP JSON API, 8 zones expandable to 72 — with the FrankEver FK-06X as the less-DIY, Shelly-based alternative. For a single tap or drip line, the Eve Aqua (HomeKit-over-Thread, HA-driven rain skip) and the LinkTap system (local HTTP/MQTT API) are both fully local. For indoor plants on Zigbee, the Third Reality Smart Watering Kit is the most local-native option.

If you want a polished, multi-zone, turnkey controller and can accept a cloud dependency, Rachio 3 is the easy default—just know it’s cloud-only with no stable local API. Orbit B-hyve XR is the budget multi-zone alternative, also cloud-based.

Whatever you pick, the most resilient setup puts the rain-skip decision in Home Assistant using a weather integration, so a single controller’s cloud outage can’t leave your sprinklers running in the rain. For the full picture on keeping the watering logic off the cloud entirely, see how to control irrigation without the cloud.

Frigate is a local network video recorder with real-time object detection, and it pairs tightly with Home Assistant. Built on a budget it’s one of the best-value upgrades a local-first home can make — no subscription, no cloud, footage stays on your hardware. The trick to keeping it cheap without making it miserable is matching the hardware to how detection actually works, and feeding it the kind of camera streams it actually wants.

What Frigate Actually Needs

Two jobs dominate Frigate’s workload: decoding video streams and running object detection on the frames. Decoding is best handled by hardware video acceleration — Intel QuickSync on Intel iGPUs is the common, cheap option. Detection is best offloaded to an accelerator, and the guidance here has shifted. Frigate’s documentation now states that the Google Coral is no longer recommended for new installations except where power draw is the overriding constraint; a recent Intel iGPU running OpenVINO, a discrete GPU, or a Hailo-8/8L module is the current starting point. A Coral still works and is still supported, so an existing one is not wasted. You can run detection on the CPU alone, but it limits how many cameras and how high a resolution you can sustain.

Frigate runs as software on a Linux host, normally in Docker. That rules out appliances that aren’t general-purpose Linux machines — an Android TV box or a streaming stick can’t run it. You need a real x86 mini PC, an SBC, or a server.

Picking the Hardware

A used or new Intel mini PC with QuickSync is the sweet spot, because the same iGPU that decodes the streams can also run detection through OpenVINO. The Intel NUC 12 Pro is a strong choice: it ships as a barebones kit built around the 12-core Core i5-1240P (4 performance + 8 efficiency cores) with Intel Iris Xe graphics for QuickSync decoding, and you add your own DDR4 RAM and an NVMe SSD. Budget for at least 16GB of RAM and an SSD when you price it out — the kit doesn’t include them. With the iGPU running OpenVINO detection, a machine like this comfortably runs many cameras.

If the NUC is over budget, an Intel N100 or N150 mini PC is excellent value: it has QuickSync, sips power, and its iGPU handles OpenVINO detection for a handful of cameras. If you want more detection headroom later, a free M.2 slot can take a Hailo-8/8L module. If you’d rather reuse a machine you already own, see how to run Frigate on an old PC. A Raspberry Pi 5 with an M.2 AI accelerator (the Raspberry Pi AI HAT+ pairs the board with a Hailo-8L at 13 TOPS or a Hailo-8 at 26 TOPS, from $70) can work for a couple of low-resolution feeds, but it lacks the decode horsepower of an Intel iGPU and will struggle as you scale up.

For storage, recordings are the space hog. A 2TB NVMe or SATA SSD is a sane starting point; size it to your retention. Roughly, a single 1080p H.264 stream recording continuously runs on the order of tens of gigabytes per day, so multiply by camera count and retention days and add headroom. A USB 3.0 external drive can hold recordings on a tight budget, but keep Frigate’s database and cache on the internal SSD for responsiveness.

Feeding Frigate the Right Streams

Frigate ingests RTSP streams, and you add each camera by hand in the config — there is no auto-discovery step. ONVIF matters for a different reason: it is the protocol Frigate uses to drive a PTZ camera and to autotrack, so if you buy a PTZ, check that it advertises ONVIF relative pan/tilt. It does not take a phone plugged in over USB or a random USB webcam as a “camera” the way an NVR appliance might — give it network cameras that expose an RTSP URL. Cheap, well-supported options include Amcrest and Reolink models; the Amcrest IP8M-2496E is a solid higher-resolution pick when budget allows.

The standard pattern is to point Frigate’s detection at a camera’s low-resolution substream (to keep CPU/decode load down) and record from the high-resolution main stream. Most IP cameras expose both. Configure cameras, streams, and detection in Frigate’s config.yml, mapped to /config/config.yml inside the container (config.yaml is also accepted, but config.yml wins if both exist, and there’s a config editor built into the web UI); a Docker compose.yaml defines the container, volumes, and device passthrough for the iGPU or whichever detector you use.

Integrating with Home Assistant

Install the official Frigate integration in Home Assistant (it’s available through HACS) to pull in camera entities, detection sensors, and event clips. From there you automate normally — for example, a person-detection event on the Amcrest turning on a Philips Hue White A19 at night through the Hue integration, or switching a plain non-smart floodlight with a Philips Hue Smart Plug. Don’t put the Hue bulb itself behind the plug — cutting its power drops it off the Zigbee mesh. Running Home Assistant on something like a Home Assistant Green is fine; Frigate itself should live on the Intel box with QuickSync, not on the lightweight HA appliance.

A Note on HomeKit and Hubitat

Frigate has no native HomeKit or Hubitat integration. If you want Frigate cameras to appear in Apple Home, the usual route is Home Assistant’s HomeKit bridge re-exposing the camera entities; HomeKit Secure Video is a separate Apple feature and not what Frigate provides. Hubitat has no real Frigate support — most people who run both let Home Assistant own the camera/NVR side and use Hubitat only for whatever automations already live there.

Quick Verdict

The budget Frigate build that doesn’t disappoint is an Intel mini PC with QuickSync, using the iGPU for both decoding and OpenVINO detection — an Intel NUC 12 Pro kit (add RAM and an SSD) or an N100/N150 box if money is tighter — feeding off RTSP IP cameras with a low-res detect stream and high-res record stream, recordings on a 2TB SSD sized to your retention. Skip the Android boxes and USB-webcam ideas; give Frigate a real Linux host and proper network cameras and it will run reliably for years with no subscription.

Thread border routers are the backbone of modern Matter-over-Thread setups, but running them in a local-first Home Assistant environment is messier than the marketing suggests. Here’s what you actually need to know.

The Thread Border Router Landscape

Not all border routers are created equal, and the differences matter for local control. For a straight buying guide, see the best Thread border routers.

Apple devices (Apple TV 4K and HomePod mini) are widely regarded as stable Thread border routers, but check the model before you count on one: the 2nd-generation Apple TV 4K (2021) and the 3rd-generation 128GB Wi-Fi + Ethernet model carry Thread radios, while the 3rd-generation 64GB Wi-Fi-only model does not. Every HomePod mini does. They are also HomeKit-first. They work with Home Assistant via Matter, but you get limited visibility into the Thread network’s health from the HA side.

Amazon Echo devices (Echo 4th gen, Echo Show 8 (3rd gen)) can act as Thread border routers, though again only on specific generations, and real-world reliability is reported as inconsistent. The upside is Alexa integration if you use voice control. The catch for a Home Assistant build: Amazon keeps its Thread network inside its own hardware and does not expose the dataset, so Home Assistant cannot import an Echo’s Thread credentials. An Echo will run a Thread mesh for Alexa, but it cannot be the border router your Home Assistant devices join. Budget for your own.

Google Nest border routers exist too—Thread border routers are built into devices like the second-gen Nest Hub, Nest Hub Max, Nest Wifi Pro, and the Google TV Streamer (4K). Worth a correction many guides get wrong: the Google Pixel Tablet is not a Thread border router. A Pixel phone or tablet can control Thread/Matter devices, but it does not route the Thread mesh.

Home Assistant-native option: the Home Assistant Yellow (discontinued October 2025, still excellent if you own one) has a built-in Silicon Labs 802.15.4 radio that can be configured for Thread (it ships running Zigbee; switching it to Thread is a deliberate change, and that radio does one role at a time). If you want to keep the Yellow on Zigbee and still run Thread, add a separate radio such as the Home Assistant Connect ZBT-1 (now discontinued and replaced by the Connect ZBT-2, the one to buy new). This route gives you the most local control but takes more setup. There is no inherent Apple “silicon” advantage in Thread mesh quality—reliability comes down to radio placement, firmware, and how many border routers you run, not the brand’s CPU.

What Actually Matters for Reliability

Forget the marketing. Here’s what determines whether your Thread network stays up:

Multiple border routers - Thread supports more than one border router on the same network, and modern Thread/Matter setups can fail over between them. That failover isn’t always instant or flawless across vendors, so for critical devices it’s still wise to test and plan fallback automations.

Device placement - Thread runs on 2.4 GHz 802.15.4 and, like Zigbee, doesn’t punch through walls indefinitely. A border router buried in a basement corner while sensors sit across the house will struggle. Keep border routers reasonably central, and remember mains-powered Thread devices act as routers to extend the mesh.

Firmware updates - Apple and Google border routers update automatically. The Yellow’s radio is updated through Home Assistant on your schedule. Different maintenance models, neither inherently wrong.

Controller vs. border router - A Matter controller is not automatically a Thread border router. To put Thread devices on a mesh you need an actual border router; the controller just commissions and talks to them. This trips up a lot of people.

The Home Assistant Integration Reality

Getting Thread devices into Home Assistant reliably means understanding how the pieces fit:

Home Assistant’s Matter integration commissions and controls Thread devices, but the Thread mesh itself lives on your border routers. If you only have one border router and it goes offline, those Thread devices can lose connectivity until it returns. Running more than one border router on the same Thread network is the real mitigation.

For HomeKit-first users, Apple handles the Thread plumbing for you—at the cost of some cloud involvement and less local visibility.

Hubitat (Hubitat Elevation C-8) supports Matter, but the hub has no Thread radio of its own, so it cannot act as a border router. Matter-over-Thread devices still need a separate border router on your network before Hubitat can reach them. Its Matter support is also newer than its mature Zigbee and Z-Wave support, so expect more rough edges.

Practical Recommendations

1. Run more than one border router - Add a second HomePod mini or a second Nest border router, and make sure the extras sit on the same Thread network as Home Assistant. Redundancy only counts within one network, which is why an Echo cannot provide it here.

2. Test before committing - Live with your Thread devices on your chosen border router for a week before building automations around them. Reliability varies by device and environment.

3. Keep Zigbee around - Thread is solid but Zigbee is more mature in Home Assistant. Many people run both—for example an Aqara Hub M3 (a Zigbee hub that is also a Thread border router and Matter controller) alongside a Sonoff Zigbee 3.0 USB Dongle Plus for a dedicated Zigbee network. It’s not either-or.

4. Mind low batteries - Thread end devices are power-efficient, but some misbehave as batteries drain. Replace proactively.

5. Thread isn’t Z-Wave or Zigbee - It’s IP-based and behaves differently. Don’t assume your Z-Wave range or placement habits transfer directly.

Bottom line

Thread border routers work, but none are perfectly plug-and-play. Apple’s are a stable default with some lock-in; the (discontinued) Home Assistant Yellow offers the most local control with more hands-on setup; Nest devices are a workable middle ground, since Home Assistant can import their Thread credentials on Android; an Echo is not, because Home Assistant cannot join the Thread network it runs.

For a local-first Home Assistant setup, run multiple border routers and treat Thread as a maturing addition to your stack rather than a drop-in replacement for Z-Wave or Zigbee. For how the two protocols actually differ day to day, see Zigbee vs Thread real-world differences.

Smart cameras are where a lot of so-called smart homes become annoying surveillance subscriptions with pretty packaging.

If you care about Home Assistant, local recording, and not getting trapped in somebody else’s cloud roadmap, camera choices need a much harsher filter than most gadget sites use.

Two options worth recommending:

• Best overall value for local camera setups: Reolink PoE Camera Line
• Best polished controller-based ecosystem: UniFi Protect

Quick verdict

If you want the best balance of local flexibility, value, and Home Assistant usefulness, buy into Reolink PoE cameras first. (Not sure which to wire up? See when to use PoE vs Wi-Fi for home cameras.)

If you already like the Ubiquiti ecosystem and want a more managed local platform, UniFi Protect can make sense, as long as you buy a console that runs Protect, but it’s a much more committed ecosystem purchase.

How we judge local cameras

We care about:

1. RTSP / ONVIF / local stream reality
2. NVR and Frigate friendliness
3. Home Assistant integration quality
4. Cloud dependence
5. Value over time, not just first-impression app polish

Best overall for most local-first buyers: Reolink PoE Camera Line

Reolink is the easy recommendation because it keeps showing up in the zone where practical buyers actually live:

• good value
• strong local-stream support
• solid Home Assistant usefulness
• easy fit for NVR and Frigate-style setups

The nice thing about Reolink is that it makes sense even if you’re gradually building the rest of the stack. You don’t need to marry an entire camera empire on day one.

Best managed local camera ecosystem: UniFi Protect

UniFi Protect is better seen as a platform decision than a single camera recommendation.

Why people buy it:

• cleaner integrated experience
• good local recording posture
• strong fit if the house already uses UniFi networking gear, provided that gear includes a console that runs Protect

Why I would hesitate:

• you need a console that actually runs the Protect application: a UDM Pro, UDM SE, UDM Pro Max, Dream Router, or a UNVR (a CloudKey Gen2+ also runs Protect but is the legacy option). The base UniFi Dream Machine does not run Protect at all and has no video storage, so check the model before you buy.
• higher cost
• more ecosystem lock-in
• worse value than a pragmatic Reolink-heavy setup for many homes

What to avoid

Avoid camera systems that only feel good when everything runs through the vendor app and cloud account.

That usually means:

• weaker local recording options
• shallower Home Assistant usefulness
• more risk that a future pricing or feature change makes the product worse after you buy it

Compatibility notes

Home Assistant

Both Reolink and UniFi Protect are workable in Home Assistant, but Reolink is usually the more practical first recommendation.

Apple Home / Google Home / Alexa

If your top priority is polished native voice-assistant camera UX, this page isn’t trying to flatter you. It’s biased toward local camera quality, not cloud-first convenience theater.

Frigate and local NVRs

Reolink is usually the easier value pick for local recording projects. UniFi Protect can be very good, but it’s more opinionated and more expensive.

Final recommendation

For most readers: start with Reolink PoE cameras.

If you already want the broader Ubiquiti stack and accept the cost, consider UniFi Protect.

Product notes:

• Reolink PoE Camera Line
• UniFi Protect
• Amcrest IP8M-2496E
• Reolink Video Doorbell WiFi

Related reading

• What “local-first” actually means in smart home tech
• Best mini PCs for Home Assistant
• Best local-first smart home hubs
• Devices that work when the internet dies
• Local smart home security setup from scratch

If Home Assistant is the brain of your smart home, buttons and remotes are the fingertips: a physical press to trigger a scene, toggle lights, or fire an automation without reaching for your phone. The catch is that “smart button” gets slapped on a lot of different things. This guide sticks to buttons that work locally with Home Assistant, and is honest about the radio each one speaks — because that’s what decides whether it keeps working when the internet is down.

Most good local buttons are still Zigbee, and that is where this guide spends most of its time. It is no longer the only option, though. Z-Wave has a good battery remote if your hub already speaks that radio, and Matter-over-Thread buttons arrived in force when IKEA moved its remote line over in early 2026. Wi-Fi buttons remain mostly cloud-tethered. (If you want a fuller control surface than a single button, see the best Zigbee button keypads for scene control.)

Zigbee buttons (the local-first default)

These pair to a local Zigbee coordinator via ZHA or Zigbee2MQTT and fire events (single / double / long press) straight into Home Assistant. No cloud, no account.

Aqara Wireless Mini Switch / Wireless Remote Switch H1

The Aqara Wireless Mini Switch is a compact, single-button Zigbee remote that exposes single, double, and long-press actions. It pairs to ZHA or Zigbee2MQTT directly (an Aqara hub is optional, not required). The newer Wireless Remote Switch H1 is Zigbee 3.0 with a satisfying click, longer battery life, and lower latency; by default the H1 only sends single-press, but you can unlock double/long press in ZHA or Zigbee2MQTT. Either is a great no-frills scene button, and its small size makes it a good fit for the nightstand — see the best Zigbee buttons for bedside control if that’s your use case.

Third Reality Smart Button

The Third Reality Smart Button is a Zigbee 3.0 button (it is not a Z-Wave device, despite what some listings imply). It works directly with ZHA and Zigbee2MQTT, exposes single/double/hold, runs on AAA batteries for years, and is one of the cheapest reliable buttons you can buy. A Zigbee coordinator is required and sold separately. No HomeKit support natively, but you can expose it through Home Assistant’s HomeKit bridge.

Philips Hue Tap Dial Switch

If you’re already running a Philips Hue Bridge, the Tap Dial Switch is excellent: four tap zones plus a rotary dial for smooth dimming. It’s Zigbee. You can either keep it on the Hue Bridge (and pull events into HA via the Hue integration, which is local) or pair it directly to your own Zigbee2MQTT/ZHA coordinator. It shines for light/scene control specifically; it’s not a universal remote.

Z-Wave buttons

If your hub already has a Z-Wave radio, you do not need to add Zigbee just to get a button.

Zooz ZEN34 Remote Switch

The Zooz ZEN34 Remote Switch is a battery-powered Z-Wave remote shaped like an ordinary paddle switch, so it reads as a real wall control rather than a plastic remote. It mounts anywhere with adhesive, which makes it the usual answer for adding a second switch point to a three-way setup without pulling a traveler wire. It pairs locally through Z-Wave JS, supports multi-tap scene events, and can drive another Z-Wave device directly through Direct Association, with the hub out of the path entirely. It has no relay of its own, so it switches other devices rather than a load at its own box, and being battery powered it does not repeat for your mesh. If you want a five-button wall controller instead of a paddle, the mains-powered Zooz ZEN32 Scene Controller is the sibling to look at.

Matter-over-Thread buttons

This is the newest category, and the one that changed most recently. IKEA discontinued its RODRET and STYRBAR Zigbee remotes in January 2026 and replaced them with a Matter device, so the cheapest mainstream button brand is now a Thread brand rather than a Zigbee one. (Its Zigbee SOMRIG shortcut button is still listed in the US, but as last-chance stock — fine to buy if you see one, not something to plan around.)

IKEA BILRESA Dual Button

The BILRESA is a two-button remote that joins your Thread network and is controlled locally through a Matter controller — Home Assistant works as one. There is no IKEA hub and no cloud account in the path, and at around $7 it is the cheapest button in this guide. What you do need is a Thread border router and a Matter controller already running.

One caveat worth knowing before you buy: Home Assistant currently exposes the BILRESA as a generic event entity rather than as proper device triggers. You build automations from that entity’s state and its press-type attribute (single press, double press, long press and long release) instead of picking the button out of the device-trigger list, and community blueprints exist that wrap this up for you. It works and it is fully local, but it is a rougher setup than a Zigbee button’s ready-made triggers.

A note on what these are not

A few devices get miscategorized as “smart buttons” and they shouldn’t be:

• Shelly Plus/Pro relays (incl. the Plus 1 Mini Gen3) are Wi-Fi relay modules, not buttons and not Zigbee/Z-Wave. They’re great for putting a dumb switch or fixture under local control (the Shelly integration is fully local), and you can wire a physical wall switch to their input — but you buy a Shelly to switch a load, not as a battery scene remote.
• Voice speakers (HomePod mini, Nest Mini) are controllers/voice front-ends, not buttons. A HomePod mini is useful as a Thread border router for Matter, and a Nest Mini can voice-control HA via the Google Assistant integration (which routes through Google’s cloud). Neither is a local push-button.

Hubs vs. buttons

You don’t buy a button by buying a hub. To use any Zigbee button you need a Zigbee coordinator — that can be a USB stick (Home Assistant Connect ZBT-2, Sonoff/SMLIGHT dongles) running ZHA or Zigbee2MQTT. Z-Wave is a separate radio: if you ever add Z-Wave gear, Home Assistant talks to it through Z-Wave JS and its own stick, such as the Home Assistant Connect ZWA-2. What you don’t want for the Zigbee buttons above is a Z-Wave coordinator — and a SmartThings-style all-in-one box like the Aeotec Smart Home Hub isn’t the answer either, since it’s cloud-first and doesn’t act as a local Z-Wave adapter for HA.

Quick verdict

• Best all-round local button: Aqara Wireless Mini Switch (or the H1 if you want a nicer click and dial-free multi-press).
• Cheapest reliable button: Third Reality Smart Button — Zigbee, plentiful, AAA-powered.
• Already on Hue, want dimming: Philips Hue Tap Dial Switch.
• Already on Z-Wave: Zooz ZEN34 Remote Switch — a battery paddle you can stick anywhere, no Zigbee radio needed.
• Cheapest local button of the lot: IKEA BILRESA Dual Button — about $7 over Matter-over-Thread, if you already run a Thread border router and can live with an event-entity automation.

Whatever you pick, confirm it’s Zigbee, pair it to a local coordinator with ZHA or Zigbee2MQTT, and your button presses will keep firing automations whether or not the internet is up. Want tactile or audible confirmation when a press lands? See how to get clear feedback from smart home buttons.

If you’re a renter who wants a smart home that stays local, private, and fully under your control, Home Assistant is the ideal hub — and nothing here requires drilling, rewiring, or anything you can’t take with you. This guide focuses on a local-first setup with Home Assistant, with notes on HomeKit and Hubitat as alternatives. The goal is to avoid cloud dependencies and keep your data on your own network. See also our roundups of the best local smart home gear for renters and the best portable smart home hubs for renters.

Choose a local hub

The hub is what manages your devices without phoning home to a vendor cloud.

Home Assistant is the most capable choice. You can run it on a Raspberry Pi 4 (low power, quiet, runs 24/7) or on a purpose-built appliance like the Home Assistant Green for a plug-and-play experience (the Home Assistant Yellow was discontinued in October 2025 but still works if you already own one). Note that “local-first” describes how you use Home Assistant — the optional Nabu Casa cloud subscription only adds remote access and voice; the automations themselves run locally on your hardware either way.

Hubitat Elevation is a fine alternative: a local, cloud-optional hub with built-in Z-Wave and Zigbee radios. It’s more streamlined but less flexible than Home Assistant.

HomeKit needs an always-on Apple home hub — an Apple TV 4K or a HomePod / HomePod mini (an iPad is no longer supported as a hub). It’s solid for Apple households but supports fewer third-party devices.

Recommendation: Start with Home Assistant on a Raspberry Pi 4 or a Home Assistant Green appliance (the Yellow was discontinued in October 2025).

Add Zigbee and Z-Wave the right way

Both Zigbee and Z-Wave are low-power mesh protocols — mains-powered devices repeat the signal, extending range without new wiring (great for renters). Each protocol needs its own coordinator plugged into your hub. Get these right; this is where a lot of bad advice circulates:

• For Zigbee (and Thread/Matter), the Home Assistant Connect ZBT-2 is the current model and the one to buy new, a USB Zigbee or Thread adapter (one firmware at a time) — it is not a Z-Wave controller. (Its predecessor, the Connect ZBT-1, was discontinued in November 2025; it still works and still receives software updates, so keep using one you already own.) A ConBee III USB stick is another good Zigbee coordinator.
• For Z-Wave, use a dedicated Z-Wave USB stick (for example a Zooz 800-series Z-Wave stick, or Aeotec’s 700-series Z-Stick 7) with Z-Wave JS. Two single-protocol sticks is the simplest arrangement, but it is not the only one: the Aeotec Z-Stick 10 Pro ($59.99) carries two separate Silicon Labs radios on one dongle — an EFR32ZG23 for Z-Wave 800 and an EFR32MG21 for Zigbee 3.0 — so one stick can serve Z-Wave JS and ZHA or Zigbee2MQTT at the same time.

Skip the Abode Iota for this. The Abode Iota is a cloud-dependent security system; its Z-Wave/Zigbee automation features require an Abode subscription, and it isn’t a clean local coordinator for Home Assistant. Use plain USB coordinators instead.

Recommendation: A ConBee III or the current HA Connect ZBT-2 for Zigbee, plus a dedicated Z-Wave stick if you have Z-Wave devices — or a single Aeotec Z-Stick 10 Pro in place of both if you would rather spend one USB port.

Pick renter-friendly devices

Choose devices that pair locally to your own coordinator and don’t require permanent installation:

• Sensors: Aqara Zigbee motion, contact, and presence sensors (e.g. the FP1E presence sensor — Zigbee, no wiring) pair to your Zigbee coordinator. Note the Aqara FP1/FP1E are Zigbee presence sensors, not Z-Wave.
• Lighting: smart bulbs (Philips Hue over Zigbee, or LIFX over Wi-Fi) need no wiring and travel with you. Plug-in smart plugs add control to lamps and appliances without touching the wall.
• Buttons/remotes: a Zooz ZEN34 (Z-Wave) or an Aqara/Third Reality Zigbee button gives you wall controls that mount with adhesive — no electrical work.

Avoid hardwired switches and in-wall relays unless your lease allows it; stick to plug-in and battery devices so everything is reversible.

Recommendation: Build around battery and plug-in Zigbee/Z-Wave devices so your whole setup is removable.

Privacy and security

A local-only setup keeps your data on your network, but you own the security:

• Put smart devices on a separate VLAN or guest Wi-Fi if your router supports it. Apartment dwellers can go further with our guide to privacy-friendly devices for apartments.
• Keep Home Assistant and device firmware updated. HA Green/Yellow and the HA OS make updates easy.
• Don’t expose Home Assistant to the internet directly — use the Companion app over your LAN, a VPN, or Nabu Casa for remote access.

Use open-source tools for full control

Home Assistant is open source, so you can customize integrations, write automations and scenes, and add community integrations for devices that aren’t officially supported. You can manage Zigbee and Z-Wave side by side, and add MQTT (via Zigbee2MQTT or ESPHome) when you want more advanced local control. The UI handles most setup without any coding.

Quick verdict

As a renter, Home Assistant on a Raspberry Pi 4 or a Home Assistant Green appliance (the Yellow was discontinued in October 2025) gives you a private, no-cloud smart home that’s fully removable. Add a Zigbee coordinator (ConBee III or the current HA Connect ZBT-2) and, if needed, a separate Z-Wave stick — not the cloud-tied Abode Iota. Stick to battery and plug-in Aqara, Hue, and similar devices so nothing is permanent, keep firmware current, and isolate your IoT network for security.

A local-first smart home that dies every time the power blinks is not actually resilient. You’ve done the work to keep everything off the cloud. Now keep it off the floor when the lights go out.

Here’s where we’d start:

• Budget pick: APC Back-UPS BE600M1
• Mid-range pick: CyberPower CP1500PFCLCD
• Premium pick: APC Smart-UPS SMT1500C

What actually needs a UPS

Battery-powered Zigbee and Z-Wave sensors keep running during an outage, but the mesh they report through does not. Routing is done by your mains-powered devices — bulbs, plugs, in-wall switches — and those die with the power, while battery sensors are end devices that never route for themselves. So a UPS buys you the brain and the path to it, not the whole mesh. That means your hub, your router, and the switch connecting them.

Plug these in:

• your Home Assistant box (a Green, a mini PC, or an older Yellow - the Yellow was discontinued in October 2025) - see choosing the right power supply for Home Assistant if you also run one off a bare DC brick
• your router
• one PoE switch if you run PoE access points or cameras
• a mains-powered Zigbee or Z-Wave router near any sensor that must keep reporting through a cut — a single smart plug is enough to keep that hop alive

Do not plug these in:

• monitors
• printers
• laser printers especially (massive draw on startup)
• anything with a heating element
• anything you wouldn’t miss for an hour

The goal is runtime, not convenience. Every watt you waste on a monitor is a minute your automations lose.

What matters in a smart home UPS

Sine wave output. Simulated sine wave (stepped approximation) is fine for routers and most hubs. But if you’re running a mini PC or NAS, a pure sine wave UPS avoids weird shutdowns and power supply stress. The CyberPower CP1500PFCLCD and APC Smart-UPS lines are pure sine wave. The budget APC BE600M1 is simulated, which is acceptable for a hub and router but not ideal for more sensitive gear.

Runtime at your actual load. A Home Assistant Green, a router, and a small switch together pull maybe 30-40W. At that load even a 600VA unit gives you 30+ minutes. A 1500VA pure sine wave unit can keep a mini PC and full network stack alive for over an hour. Check the manufacturer’s runtime charts at your expected wattage, not the headline VA number.

USB or network management port. This is the piece most people skip. A UPS with a USB HID interface lets your system detect power loss and shut down gracefully. Better yet, it feeds into NUT (Network UPS Tools), which integrates directly with Home Assistant.

NUT integration with Home Assistant. The Home Assistant NUT integration exposes battery level, load, runtime remaining, and power state as sensors. You can build automations around it: send a notification when power drops, trigger a graceful shutdown at 20% battery, or log outage duration. If your UPS supports NUT over USB, this is nearly zero effort to set up.

Budget: APC Back-UPS BE600M1

APC Back-UPS BE600M1 is the right choice when you just need to keep a hub and a router alive. It’s small, cheap, has a USB charging port on the front, and provides a USB HID interface for NUT.

The tradeoffs: simulated sine wave, limited runtime under heavier loads, and no network management card. For a Home Assistant Green or Hubitat plus a router, it’s plenty. For a mini PC setup, step up.

Mid-range: CyberPower CP1500PFCLCD

CyberPower CP1500PFCLCD is the sweet spot for most serious smart home setups. Pure sine wave output, 1500VA/1000W capacity, an LCD panel showing real-time stats, and USB HID support for NUT.

This comfortably handles a mini PC running Home Assistant, a router, a PoE switch, and a few peripherals. At a typical smart home load of 80-100W, you’re looking at well over an hour of runtime. It’s the one we’d pick for most people running a local-first stack.

Premium: APC Smart-UPS SMT1500C

APC Smart-UPS SMT1500C is for the rack crowd - though the SMT1500C itself is a tower unit, so if you actually need it in the rack, buy the 2U SMT1500RM2UC instead. Pure sine wave, 1500VA/1000W, and a SmartSlot for a network management card (sold separately - that card is what gets you SNMP and NUT over the network instead of USB), plus a SmartConnect port for APC’s cloud monitoring if you want it.

This is overkill for a single hub and router. It makes sense when you have a proper network rack, multiple switches, a NAS, and a dedicated Home Assistant server. The network management card also means the UPS itself can be monitored from any machine on the network, not just the one plugged into the USB port.

Setting up NUT in Home Assistant

If the UPS plugs into the Home Assistant machine itself, install the Network UPS Tools community add-on (Home Assistant OS or Supervised only), then add the NUT integration and point it at the add-on. If the UPS is plugged into a NAS that already runs a NUT server, skip the add-on and point the integration straight at the NAS. Either way you get sensors for:

• battery charge percentage
• estimated runtime remaining
• input/output voltage
• UPS load percentage
• UPS status (online, on battery, low battery)

From there, build a simple automation: if UPS status switches to “on battery,” send a push notification. If battery drops below 20%, trigger a graceful shutdown script. This closes the loop on a properly resilient local-first setup.

Related

• Devices that work when the internet dies
• Best mini PCs for Home Assistant
• Best local-first smart home hubs

When you set up Home Assistant, one of the first decisions is how to run it. People often phrase this as “add-ons vs HAOS vs Docker,” but that comparison mixes up two different things. Let’s fix the framing first, because getting this right saves a lot of confusion.

First, the important correction

Add-ons are not an installation method. Add-ons are optional software packages (Zigbee2MQTT, ESPHome, Node-RED, Mosquitto, and so on) that the Home Assistant Supervisor installs and manages for you as extra containers. They are a feature of certain installations, not an alternative to them.

The actual installation methods are:

1. Home Assistant OS (HAOS) - a complete, dedicated appliance OS.
2. Home Assistant Container - the official Docker image, run yourself.
3. Home Assistant Supervised - Home Assistant plus the Supervisor running on your own Debian system. Deprecated in May 2025 and unsupported since release 2025.12, so it is not an option for a new build.

The key consequence: the Add-on Store is available on HAOS and on Supervised, but not on plain Container. On Docker Container you simply run those same tools as their own containers (via Docker Compose) instead of clicking “install” in an add-on store. So the real choice for a new build is HAOS vs Container - and add-on availability follows from that choice.

1. Home Assistant OS (HAOS): the recommended default

HAOS is a purpose-built Linux appliance that runs Home Assistant, the Supervisor, and your add-ons. It’s what the project officially recommends for most people. You flash it to a device and it manages itself.

Pros

• Add-on Store included - one-click install of Zigbee2MQTT, ESPHome, Node-RED, Mosquitto, etc. (for a starting shortlist, see the Home Assistant add-ons I actually use).
• Managed updates and backups built in.
• Lowest maintenance - it’s an appliance; you don’t manage the OS underneath.

Cons

• It wants to own the device. HAOS is happiest as the only thing on the machine (or in a dedicated VM). It’s not meant to share a general-purpose Linux box with other apps.

Runs well on

• Raspberry Pi 4 or 5
• A small x86 box like the Intel NUC 12 Pro or Lenovo ThinkCentre M75Q Gen5. Weighing a Pi against a mini PC? Raspberry Pi vs a mini PC compares them.
• A VM on a NAS or hypervisor (Proxmox, ESXi, etc.) — see how to run Home Assistant on Proxmox for a step-by-step VM walkthrough

Choose it if

You want the full Home Assistant experience with add-ons and the least fuss. This is the right answer for the large majority of users.

2. Home Assistant Container (Docker): flexible, you manage the rest

This is the official Docker image. You run Home Assistant as one container alongside whatever else lives on your server. There is no Supervisor and no Add-on Store - so you run Zigbee2MQTT, Mosquitto, Node-RED, etc. as their own containers.

Pros

• Fits an existing server. Ideal if you already run a NAS or Docker host and want Home Assistant to be one service among many.
• Full control over networking, volumes, and versions via Docker Compose.

Cons

• No add-on store - you assemble the supporting services yourself.
• More hands-on - you own updates, container orchestration, and troubleshooting.

Runs well on

• A NAS that runs Docker (Synology, Lenovo ThinkCentre M75Q Gen5, or similar), the Intel NUC 12 Pro, or any Linux server you already maintain. If that NAS is a Synology, Unraid, or TrueNAS box, Home Assistant on Synology vs Unraid vs TrueNAS covers whether you can get the add-on store on each one.

Choose it if

You’re comfortable with Docker, already run a server, and prefer to manage your own stack of containers.

3. Home Assistant Supervised: deprecated, not for new builds

Supervised installs Home Assistant and the Supervisor (so you keep the Add-on Store) on top of your own Debian system. It is no longer a supported choice. Home Assistant deprecated the Supervised (and Core) install methods on May 22, 2025, and both became unsupported with the 2025.12 release, which means the project no longer accepts issue reports for them. An existing Supervised install keeps working and can still be updated, but if you are standing up something new, pick HAOS or Container instead.

What it gave you

• Add-on Store on your own OS - the convenience of HAOS with a Debian base you control. That is still true of an install you already run.

Why not to start here

• Unsupported, and picky even when it was supported - it expects a clean, supported Debian setup, drift can break it, and the project no longer takes bug reports for it. If what you actually want is the add-on store without dedicating a whole machine to Home Assistant, run HAOS in a VM instead — that is a supported install type and it keeps the add-on store, one-click updates, and the built-in backup tool.

A note on HomeKit and Hubitat

None of these install methods change how Home Assistant talks to HomeKit or Hubitat - that’s handled by integrations regardless of how HA is installed. Home Assistant can expose its devices to Apple Home via the HomeKit Bridge integration, and it can integrate with a Hubitat hub via the Hubitat integration, on HAOS, Container, or Supervised alike. Don’t pick an install method for HomeKit/Hubitat reasons; pick it for how you want to run and maintain the server.

Quick verdict

• Most people: Home Assistant OS (HAOS). Add-ons included, minimal maintenance, runs on a Pi, a mini PC, or a VM.
• Already run a Docker server: Home Assistant Container. No add-on store, but it slots into your existing stack; you run supporting tools as containers.
• Want add-ons without dedicating the machine: run HAOS in a VM. Supervised used to be the answer here, but it has been unsupported since release 2025.12. A HAOS VM on Proxmox or another hypervisor keeps the add-on store and the managed updates.

Bottom line

“Add-ons” isn’t a third installation option - it’s a feature the Supervisor gives you, which for a new build means HAOS. Pick HAOS (on dedicated hardware or in a VM) for the easiest full-featured setup and Container for flexibility on a server you already maintain. Supervised has been unsupported since release 2025.12, so leave it to the people already running one.

Shelly devices are one of the easiest ways to get real, local power data into Home Assistant — but only if you buy the models that actually meter power. This trips people up constantly, so the most important step happens before you write any dashboard YAML: pick a Shelly with a power-metering channel. Get that right and the rest is quick.

Buy a Shelly That Meters Power (this is the part that matters)

Not every Shelly measures consumption. The distinction is in the model name: “PM” means power metering.

• The Shelly Plus 1 is a relay with dry-contact support. It switches a load but has no power metering — it cannot report watts, voltage, or current. It’s a fine switch; it is the wrong device for a power dashboard.
• For a single circuit you want a one-channel metered relay. The current model is the Shelly 1PM Gen4 (16A/3680W, Wi-Fi and Bluetooth, Matter-certified out of the box and switchable to Zigbee with five presses of the device button). The older Gen2 Shelly Plus 1PM does the same metering job and is still a fine choice if you already own one — just note that Gen2 “Plus” hardware has no native Matter. Either reports power, voltage, current, and energy, with overload and temperature protection.
• The Shelly Plus 2PM has two independently metered channels (10A per channel, 16A total), so it’s ideal where you want to monitor two loads from one device. Its current-generation counterpart, the Shelly 2PM Gen4, keeps the same 2x10A metering and adds Matter and Zigbee 3.0 as alternative radio profiles, though only one runs at a time (five presses switch it from Matter-over-Wi-Fi to Zigbee, and Zigbee mode drops Wi-Fi).

If your goal is whole-circuit or appliance energy data, choose a 1PM or 2PM. For metering at the breaker panel across both legs of a split-phase supply, Shelly’s clamp-based energy meter line (the Shelly Pro 3EM) is the dedicated tool, but a 1PM/2PM on individual circuits is the simplest starting point for most homes.

Add Shelly to Home Assistant

Home Assistant has a native Shelly integration, and setup does not involve scanning a QR code. Two paths:

1. Auto-discovery. Once your Shelly is on your Wi-Fi, Home Assistant usually finds it via mDNS and shows a “new device discovered” prompt under Settings - Devices & Services. Click Configure.
2. Manual by IP. If it isn’t discovered, add the Shelly integration and enter the device’s IP address or hostname (find it in your router).

Either way, assign each Shelly a static or DHCP-reserved IP in your router — the integration relies on a stable address, and a changed lease after a reboot is the most common cause of a device going “unavailable.” Note the protocol detail if you ever troubleshoot: newer Plus/Gen2+ Shellys talk to Home Assistant over RPC, while first-gen devices use CoIoT (which must be enabled on the device).

Once added, a 1PM or 2PM exposes entities for power (W), voltage (V), current (A), and accumulated energy (kWh) — that’s everything a dashboard needs.

Build the Dashboard

With metering entities flowing in, build the view in Home Assistant’s dashboard (Lovelace) editor:

• Live power — a gauge or entities card showing each circuit’s current watts.
• History — a history-graph card for recent trends; Home Assistant’s long-term statistics keep the data for longer-range views.
• Energy over time — feed the kWh energy sensors into Home Assistant’s built-in Energy dashboard to see daily/monthly consumption (and cost, if you enter a tariff) — see our Home Assistant energy dashboard deep dive for setup details. This is the single best use of Shelly PM data and it’s built in — no add-on needed.

For automations, trigger on the power sensor: e.g. notify when a circuit exceeds a threshold, or cut a non-essential load above a limit. For richer custom cards, HACS offers community dashboard components, but you can do everything described here with stock Home Assistant.

HomeKit and Hubitat

Shelly’s native fit is with Home Assistant. If you want Shelly power data visible in Apple Home, the realistic route is Home Assistant’s HomeKit bridge re-exposing the entities — and be aware HomeKit’s data model doesn’t surface arbitrary energy metering as cleanly as Home Assistant does, so expect a more limited view. On Hubitat, community Shelly drivers exist but generally expose less detail than Home Assistant’s integration. If power monitoring is your priority, let Home Assistant own the Shelly devices and bridge to the other ecosystems only for control.

Quick Verdict

The make-or-break decision is the model: a 1PM (one metered circuit) or 2PM (two metered channels), in either the current Gen4 or the older Plus form, gives you the watts, volts, amps, and kWh a power dashboard needs — the plain Plus 1 does not meter power at all. Add it to Home Assistant by discovery or IP (no QR scan), pin it to a static IP, then route the energy sensors into the built-in Energy dashboard and add gauge/history cards for live and trend views. It’s an inexpensive, fully local way to finally see where your electricity is going.

Plan for Local Operation

When you build a smart home around Home Assistant, the goal is for the important things to keep working when the internet drops. Outages happen — ISP problems, a downed line, a router reboot — and a well-designed local-first setup shrugs them off. The trick is making sure your critical devices and automations don’t route through a vendor cloud for their basic functions.

Start by listing what actually matters day to day: lights, the thermostat, door locks, and any security sensors. For each, prefer devices that speak a local protocol — Zigbee, Z-Wave, Thread/Matter, or a local API over your LAN — rather than Wi-Fi devices that only work through the manufacturer’s app and servers.

Run Home Assistant on local hardware you own. Purpose-built options like the Home Assistant Green (the Home Assistant Yellow was discontinued in October 2025 but still works if you own one) keep the whole system on your network, and the Home Assistant Connect ZBT-1 (now discontinued and replaced by the Connect ZBT-2) adds a local Zigbee (and Thread) radio. Once your automations live on a local box, they run regardless of your internet connection.

Use Local-Only Devices

The most resilient devices are the ones that never needed the cloud in the first place. Zigbee and Z-Wave devices talk to your local coordinator, and Matter devices controlled over Thread or your LAN stay reachable on the local network even when the WAN is down.

For lighting, Zigbee bulbs and switches (Philips Hue, Sonoff, Inovelli, and others) keep working through Home Assistant locally. One important caveat: smart bulbs need mains power to work at all. A Philips Hue or LIFX bulb is not battery-powered — if the power is out, the bulb is off, full stop. For lighting that survives a power outage you need battery lanterns or a UPS, not a smart bulb.

For door locks, Zigbee, Z-Wave, and Matter-over-Thread locks can be controlled locally, and they all have a physical key or keypad as a fallback regardless. For sensors, Zigbee and Z-Wave contact, motion, and leak sensors report straight to your local hub with no internet involved.

Set Up Offline-First Automation

Automations defined in Home Assistant execute on your local server, so they keep running during an internet outage as long as the devices they touch are local. A “turn on the hallway light when motion is detected after sunset” rule doesn’t care about your ISP.

Watch out for the cloud-dependent pieces hiding in otherwise-local setups:

• Voice assistants that send audio to the cloud (Alexa, Google) stop working offline. Home Assistant’s own Assist with local speech-to-text is the local-first alternative.
• Notifications sent through a push service still need some internet path. Push to the Home Assistant Companion app relies on a relay (for Apple devices, Apple’s push servers under push.apple.com). If your home internet is the thing that’s down, those won’t reach you — so back critical alerts with a local siren or speaker announcement that needs no internet.
• Remote access to your dashboard from outside the house (via Nabu Casa or a reverse proxy) depends on internet, but local control from inside the house does not. If you rely on remote access, it’s worth comparing the tradeoffs of Home Assistant Cloud vs Tailscale vs a Cloudflare tunnel, and for a true fallback path, running your smart home on a zero-data cellular link.

Prepare for Power Outages with a UPS

An internet outage and a power outage are different problems, and a smart home plan should cover both. If the power goes out, your Home Assistant server, your network gear, and every mains-powered device go dark — including all your smart bulbs and any mains-powered sensors.

A small UPS (uninterruptible power supply) is the single best investment here. Put your Home Assistant server, your router, and your Zigbee/Z-Wave coordinator on a UPS so the brain and the radios survive a brief outage. Consumer UPS units from brands like APC and CyberPower are inexpensive and will typically run a low-power Home Assistant server and a router for a meaningful stretch — long enough to ride out short outages and shut down cleanly during long ones.

Keep in mind that battery-powered sensors (door/window, motion, leak) keep running during a power outage, but they still need a path back to the hub, and a UPS on the hub is only half of that path. Battery sensors are Zigbee and Z-Wave end devices: they never route traffic themselves, so they reach the coordinator through your mains-powered bulbs, plugs, and in-wall switches. When those go dark, an orphaned sensor does not instantly find another way in — it sleeps through the outage and only looks for a new parent on its next rejoin cycle, which can take hours, and some older models stay isolated until you re-pair them. If particular sensors have to keep reporting through a power cut, put a couple of the mains-powered routers near them on the UPS as well.

Quick Verdict

For a smart home that survives an internet outage: run Home Assistant on local hardware, lean on Zigbee/Z-Wave/Matter devices with local control, and keep automations on your local server. Remember that smart bulbs die with the power and that push notifications still need an internet path, so add a UPS for the server and network plus a local siren for critical alerts. The result is a home that keeps the lights, locks, and sensors working when the connection — or the power — drops.

Radon is a colorless, odorless radioactive gas that seeps up from soil and can build to harmful levels in basements and lower floors. It’s the second-leading cause of lung cancer after smoking. A continuous radon monitor won’t replace a proper short-term test kit for real-estate disclosure, but it tells you how levels move day to day — after rain, when the HVAC runs, when you crack a window — which is exactly the kind of trend data that’s useful in Home Assistant.

The honest catch with radon and local-first: very few continuous consumer radon monitors are designed to run entirely on your own network. Radon sensing is niche and most of the products that do it are tied to a manufacturer cloud. Below is what’s real, and what each one actually requires.

A reality check before you buy

Be skeptical of any “air quality monitor” sold as a radon device. Most popular Home Assistant air sensors — AirGradient ONE and Open Air, the Apollo MSR-2 and similar ESPHome multisensors — do not measure radon at all. They cover PM2.5, CO2, VOCs, temperature and humidity. Those are great devices for general air quality, but radon is a separate, specialized measurement and they don’t do it. If you want radon, you need a purpose-built radon detector.

Monitors that actually measure radon

Airthings View Plus

The Airthings View Plus is the most common smart radon monitor people pair with Home Assistant, and it does measure radon along with CO2, PM2.5, VOCs, humidity, temperature and pressure. Set expectations on “local,” though:

• The official Airthings integration in Home Assistant is cloud-based — it pulls your data from Airthings’ servers. As of recent Home Assistant releases the cloud integration has, at times, omitted the radon and pressure entities, so check the current state before relying on it.
• The separate Airthings BLE integration reads sensors directly over Bluetooth with no cloud, but it supports the Wave series and the Corentium Home 2, not the View Plus.
• Community add-ons exist that poll the device over Bluetooth and republish to your local MQTT broker, which is the most local route for the View Plus today.

So: a real radon monitor, but treat its stock Home Assistant path as cloud-dependent unless you go the community-BLE/MQTT route with a compatible Wave model.

Airthings Wave / Wave Radon / Corentium Home 2

If local operation is the priority, an Airthings Wave (the radon-focused models) is the better pick because it works with the local Airthings BLE integration in Home Assistant — Bluetooth, no cloud account required for the reading. You need a Bluetooth adapter within range (a Bluetooth proxy via an ESPHome device works well for a basement unit far from your server). It measures radon plus temperature and humidity depending on model. Airthings’ current radon-focused unit, the Corentium Home 2, is on the same local Airthings BLE supported-device list and also reports temperature and humidity, so it is a local option alongside the Wave radon models.

Ecosense RadonEye RD200

The RadonEye RD200 is a dedicated radon monitor (radon only, no CO₂/PM extras) with a fast first reading and a Bluetooth interface. It has no first-party HA integration, but two community paths work, both local over BLE: an ESPHome RadonEye sensor component read through an ESP32 Bluetooth proxy, or a HACS custom integration (the rd200v2 project, with variants for V1 and V2 serial ranges). Heads-up: the Ecosense phone app holds an exclusive Bluetooth connection while open, so force-close it on every phone in range or Home Assistant can’t read the device.

Ecosense EcoQube (EQ100)

The EcoQube is Ecosense’s Wi-Fi radon monitor (2.4 GHz only). Unlike the RD200, it is cloud-bound, not local: its Bluetooth is used only for the initial Wi-Fi setup, not for reading data, and it exposes no local API. The way into Home Assistant is a community cloud integration (e.g. hass-ecosense-radon) that polls Ecosense’s servers every few minutes for the current radon level. It’s a fine monitor, but treat it as a cloud device — there’s no local-only path today.

Wiring up alerts in Home Assistant

However you get the reading in, the automation side is the same. Radon is reported in becquerels per cubic meter (Bq/m³) in most of the world or picocuries per liter (pCi/L) in the US — 1 pCi/L is about 37 Bq/m³. The US EPA action level is 4 pCi/L (~148 Bq/m³); the WHO suggests a lower reference of 100 Bq/m³.

A sensible automation: trigger a notification when the multi-day average crosses your chosen threshold rather than on a single spike, since radon readings are noisy hour to hour. Many people pair a high reading with turning on a fan or HVAC circulation and watching whether the trend drops.

For a fully local data path, point the device at a local MQTT broker (Mosquitto) where possible, and keep the dashboard and alerting on your Home Assistant instance so nothing depends on internet access.

Quick verdict

• Best if you want radon data and don’t mind cloud: Airthings View Plus — accurate, multi-sensor, but its stock Home Assistant integration is cloud-based.
• Best for local-only: an Airthings Wave radon model or the Corentium Home 2 via the local Airthings BLE integration, or an Ecosense RadonEye RD200 via ESPHome / the community BLE integration.
• Wi-Fi but cloud-bound: the Ecosense EcoQube (EQ100) through a community cloud integration — convenient, but it polls Ecosense’s servers rather than running locally.
• Don’t buy for radon: general air-quality monitors (AirGradient, Apollo, Awair, Aranet). They’re good devices, but none of them measure radon.

For continuous CO2, PM2.5 and VOC monitoring alongside radon, see our best air quality sensors for Home Assistant guide.

Matter has been a shipping standard for a few years now, and in 2026 it’s real, useful, and still uneven. The spec itself keeps moving—it reached version 1.6 in mid-2026, and cameras and doorbells arrived with Matter 1.5 in late 2025—though certified hardware still trails the spec on store shelves. For local-first builders—especially Home Assistant users—it’s neither the savior the marketing promised nor a dead end. It’s a connectivity layer that does reduce lock-in for some device classes (plugs, lights, some sensors, locks) while remaining clunky for others. The honest take: lean on the protocols that are already mature in Home Assistant—Zigbee and Z-Wave—and add Matter where it actually buys you something.

First, a definition, because the marketing blurs it. Matter is an application-layer standard. It runs on top of either Wi-Fi/Ethernet or Thread, a low-power mesh network. Thread is not Matter, and Matter is not a radio. A Thread border router bridges a Thread mesh to your LAN. Zigbee and Z-Wave are entirely separate radios that Matter does not replace or absorb. If you’re standing in a store deciding what to actually buy today, our guide on Matter vs Thread and which to buy now makes the call concrete.

1. Home Assistant is still the core

Home Assistant remains the strongest local-first hub in 2026. It controls Zigbee, Z-Wave, Matter-over-Wi-Fi, and Matter-over-Thread locally, and it can run its own Thread border router and Matter server. A dedicated appliance like the Home Assistant Green is a clean way to host it (as is the Home Assistant Yellow, though it was discontinued in October 2025).

For radios, the Home Assistant Connect ZBT-2 is a single USB stick that handles Zigbee and Thread (it is built on a Silicon Labs MG24). It succeeds the now-discontinued Connect ZBT-1 (EFR32MG21), which still works and gets software updates if you already own one. Neither is a Z-Wave controller, and they have no Z-Wave radio—for Z-Wave you need a separate Z-Wave stick. Used as a Thread radio, the ZBT-2 lets Home Assistant act as a Thread border router so Matter-over-Thread devices join your network. If you want Zigbee, a stick like the SONOFF Zigbee 3.0 USB Dongle Plus or ConBee III works well.

There is no “third-party firmware” that adds Matter to Home Assistant. The Home Assistant Voice Preview Edition is a local voice-control device—not a Matter add-on, not firmware. Matter support in Home Assistant comes from the built-in Matter integration plus a Thread border router, nothing more exotic.

2. Choose protocols by device class

A practical 2026 split:

• Zigbee for the bulk of cheap sensors, bulbs, and switches. Mature mesh, huge device support, fully local in Home Assistant.
• Z-Wave for switches, dimmers, and locks where you want a less-congested sub-GHz band and long range. The current silicon is the 800 series (preceded by 700 and 500); there is no “Z-Wave 1000.”
• Matter where it removes a hub or unlocks cross-ecosystem sharing—e.g., a plug or lock you also want to expose to Apple Home or Google Home without bridges.

Apple’s HomePod mini and HomePod 2nd Gen are useful here as Thread border routers for the Apple Home ecosystem. They are not Z-Wave controllers and do not bridge Zigbee. If you live in Apple Home, they extend Thread coverage; if you live in Home Assistant, you generally run your own border router instead of relying on theirs.

3. Where Matter still frustrates

The rough edges in 2026 are mostly operational, not theoretical:

• Commissioning friction. Sharing a Matter device across two ecosystems (multi-admin) still fails or confuses more often than it should.
• Feature gaps. A device’s native integration frequently exposes more (energy data, advanced settings) than its Matter representation does. A Matter lock or plug can be a lowest-common-denominator version of itself.
• Thread network sprawl. Multiple border routers from different vendors can coexist but make debugging harder.

When you do add a Matter device, it’s worth understanding whether a Matter bridge or native Matter is better for that device class. None of this makes Matter useless—it makes it a tool you reach for deliberately, not a default.

4. Devices worth knowing

For lighting, Zigbee bulbs from the Philips Hue line such as the Philips Hue White A19 or Philips Hue White Ambiance A19 pair cleanly via the Philips Hue Bridge or directly over a Zigbee coordinator. For Z-Wave dimming, the Zooz ZEN74 Toggle Dimmer and Zooz ZEN77 Dimmer are solid Z-Wave switches (not Zigbee); note that Zooz has moved this line to 800-series silicon with Z-Wave Long Range, now sold as ZEN74 800LR and ZEN77 800LR, even though Zooz product pages still carry legacy “700 Series” titles. For a Matter-native relay, the Sonoff MINIR4M is a Wi-Fi Matter device.

A note on hubs: Hubitat Elevation is a capable local hub with Zigbee, Z-Wave, and Matter support, and is a reasonable choice if you prefer its simpler model over Home Assistant. Buy the C-8 Pro if you are buying new: Hubitat stopped manufacturing the plain C-8 in March 2026, though one you already own is still a perfectly good hub.

Quick verdict

In 2026, Matter is a complement, not a replacement. Build your core on Home Assistant with Zigbee and Z-Wave, run your own Thread border router for Matter-over-Thread devices, and add Matter where it removes a hub or unlocks cross-ecosystem sharing. Know what each piece actually is—Matter is a standard, Thread is a radio mesh, the ZBT-2 is a Zigbee/Thread stick, and HomePods are Thread border routers—and the picture gets a lot less confusing.

A lot of Zigbee pain gets blamed on devices when the real problem is the coordinator.

Pick the wrong radio, place it badly, or treat mesh design like an afterthought, and even good sensors start looking flaky.

The coordinators worth buying:

• Best default pick for most Home Assistant users: Home Assistant Connect ZBT-2
• Best value enthusiast pick: SONOFF Zigbee 3.0 USB Dongle Plus (ZBDongle-P)
• Best networked / PoE pick for harder installs: SMLIGHT SLZB-06 (the base CC2652P model)

Quick verdict

If you want the simplest sensible recommendation, buy Home Assistant Connect ZBT-2 (the successor to the now-discontinued ZBT-1).

If you’re comfortable with a slightly more enthusiast-oriented setup and want strong value, the SONOFF Zigbee 3.0 USB Dongle Plus (ZBDongle-P) is still one of the easiest recommendations in the category. Buy the ZBDongle-P specifically — SONOFF sells several different sticks under the “Dongle Plus” name and they are not interchangeable. See the model note below before you click buy.

If your Home Assistant box lives in a rack, closet, or otherwise radio-hostile corner of the house, SMLIGHT SLZB-06 is the more interesting answer because it lets you place the coordinator where the Zigbee network actually wants it.

What a Zigbee coordinator actually does

The coordinator is the radio that forms and manages your Zigbee network.

It matters because it affects:

1. How stable device joins and routing feel
2. How much setup drama you deal with
3. Whether Home Assistant support feels clean or fiddly
4. How well your network scales past a handful of devices
5. How much your physical coordinator placement fights your RF reality

A great coordinator won’t rescue a terrible mesh by itself, but a weak choice can absolutely make everything else worse.

Best default pick: Home Assistant Connect ZBT-2

This is the coordinator I would hand to most beginners first.

Why it stands out:

• excellent Home Assistant support
• easy default setup story
• a cleaner first-party path than many community-favorite dongles

The important caveat: it’s still a radio, not magic. Use a USB extension, keep it away from noisy USB 3 gear, and don’t expect one badly placed dongle to dominate a large house.

Best value enthusiast pick: SONOFF Zigbee 3.0 USB Dongle Plus (ZBDongle-P)

Sonoff’s coordinator is popular for a reason.

Why people keep buying it:

• great value
• strong support in both ZHA and Zigbee2MQTT
• huge amount of community knowledge around it

Which one to actually buy. The downside of this family is that SONOFF puts the words “Zigbee 3.0 USB Dongle Plus” on more than one product, and they run different radios:

• ZBDongle-P — Texas Instruments CC2652P. This is the one meant above, and the one with the deepest pool of community knowledge behind it.
• ZBDongle-E — Silicon Labs EFR32MG21. A different stick, not a revision of the P. It is a perfectly good coordinator, but guides and firmware instructions written for the P do not all transfer to it.
• Dongle Plus MG24 — Silicon Labs EFR32MG24, SONOFF’s newer upgrade of the E line, with more flash and RAM than the EFR32MG21.

The practical point is that flashing tools and firmware are tied to the chip, not to the brand: a CC2652P and an EFR32 do not take the same firmware. Check the exact model name on the listing before you buy, and note which chip you ended up with.

Best PoE / networked pick: SMLIGHT SLZB-06

This is where the advice gets more infrastructure-minded.

SMLIGHT becomes compelling when your Home Assistant server isn’t sitting in a great radio location.

The same model-name caution applies here. “SLZB-06” is a family: the base SLZB-06 runs a CC2652P and is Zigbee only, while the SLZB-06M runs a Silicon Labs EFR32MG21 and can also act as a Thread border router, and there are further P7 and MG variants. The pick above is the base SLZB-06; if you want the same placement flexibility and Thread, look at the 06M instead.

Why it makes sense:

• ethernet and PoE placement flexibility
• strong fit for larger homes
• easier to put the Zigbee radio near the center of the house instead of next to your noisy compute gear

This isn’t the pick I would give every beginner, but it’s the one I would seriously consider for people who already know their server placement is the problem.

Coordinator buying mistakes to avoid

Avoid these traps:

• plugging the coordinator directly into a noisy USB 3 port without an extension cable
• treating coordinator choice as more important than building a healthy mesh with powered routers
• buying based on random marketplace listings without verifying which model and chip you’re actually getting (see the model notes above — “Dongle Plus” and “SLZB-06” are both family names covering different radios)
• putting the coordinator in a rack, cabinet, or networking closet and then acting surprised when the mesh struggles

Final recommendation

For most people, buy Home Assistant Connect ZBT-2 and place it well.

If you want better value and don’t mind a slightly more enthusiast feel, buy the SONOFF Zigbee 3.0 USB Dongle Plus (ZBDongle-P).

If placement is your real constraint, SMLIGHT SLZB-06 is the smarter infrastructure move.

Related reading:

• What “local-first” actually means in smart home tech
• Home Assistant Green vs Yellow
• Zigbee vs Z-Wave vs Matter vs Thread
• How to add Zigbee without replacing your router
• Compare coordinators side by side
• Browse all coordinator product notes

Product notes:

• Home Assistant Connect ZBT-2
• SMLIGHT SLZB-06
• Sonoff Zigbee 3.0 USB Dongle Plus
• ConBee III

Presence detection is one of the most useful automations you can build. Knowing who’s home lets you control heating, lighting, security, and notifications intelligently. But Bluetooth trackers like AirTags or Tile have real drawbacks for whole-home presence: they drain battery, require people to carry them, and add another device to manage.

Good news: you can build reliable presence detection from devices you likely already own.

Network-based detection

The most practical approach for most people is tracking devices on your Wi-Fi network — phones, watches, laptops — through your router or access points.

For Home Assistant, several router integrations create device_tracker entities. ASUS routers (AsusWRT), many TP-Link models, and others are supported; check Home Assistant’s integration list for your specific hardware before buying anything. If you run Ubiquiti UniFi, the UniFi Network integration is the one that does device tracking — it creates device_tracker entities for connected clients and updates in near real time. (UniFi Protect is the camera/NVR side, not presence detection.) There’s also the simple built-in Ping integration if you just want to check whether a known IP responds. For a deeper walkthrough of this method, see network presence detection in Home Assistant.

Tradeoffs worth understanding: network detection misses people who disable Wi-Fi or are on cellular only. It can be slow to mark someone away — the UniFi integration defaults to about 300 seconds since “last seen” before considering a client gone — and a phone that sleeps its radio can briefly drop off. Tuning the away timeout helps.

Motion and occupancy sensors

Motion and presence sensors detect actual human activity rather than a device, which makes them a great complement to network tracking.

Philips Hue motion sensors work well if you’re already in the Hue ecosystem; they’re Zigbee, battery-efficient, and integrate with both Home Assistant and HomeKit. (The Hue Bridge is Zigbee-only — it has no Z-Wave radio.)

For broader options, Aqara sensors like the Aqara Motion Sensor P2 (Matter) or the Aqara Presence Sensor FP1E (mmWave) work with Home Assistant and other platforms. The FP1E detects micro-movements even when someone sits still, so a room stays “occupied” instead of flipping to empty.

Frient Zigbee sensors such as the Motion Sensor Pro and Entry Sensor work with Home Assistant directly and can also feed Hubitat setups.

The key insight: motion/presence sensors are room-level, not person-level. You know someone is in the house, not specifically who. For per-person detection, combine sensors with network tracking. If mmWave is the route you want, compare the best mmWave presence sensors for Home Assistant.

Thermostats and climate-based presence

Some smart thermostats offer occupancy signals. The ecobee Premium ships with a remote SmartSensor that reports occupancy, useful as an extra input. Be clear about what you are buying into, though: Home Assistant’s ecobee integration is cloud polling and ecobee exposes no local API, so unlike every other sensor on this page that signal stops when your internet does. The readings are also slow (often tens of minutes to register absence) and can’t distinguish household members.

Combining signals for reliability

No single method is perfect, and the local smart home community has settled on combining signals. A practical recipe: use network detection as your primary home/away signal, add motion/presence sensors in key rooms (entryway, living room) to catch arrivals and confirm occupancy, and use thermostat occupancy as a fallback. Home Assistant’s Bayesian sensor can blend these probability-weighted inputs into one occupancy state. Our mmWave and PIR presence setup guide shows how to wire these signals together room by room.

For multi-person households, network detection can identify individual devices by client/MAC, which is the most practical route to per-person presence. Motion sensors alone can’t tell people apart, so many households accept “someone is home” automations except where per-person triggers are truly needed.

Related products

Local-first picks from our catalog that fit this topic:

• Apollo MSR-2 — presence sensor
• Apollo MTR-1 Multi-Target Radar — presence sensor
• Aqara Presence Sensor FP1E — presence sensor

Quick verdict

Network detection is the best starting point — it’s free if your router or UniFi controller is supported, needs no extra hardware, and covers the whole house. Supplement with a motion or mmWave presence sensor at your main entry and in rooms where people sit still. Bluetooth trackers are overkill for most households and add maintenance you don’t need.

If you’re building a local-first smart home with Home Assistant, your thermostat is one of the worst places to accept a cloud dependency. A cloud-only thermostat can lose remote control — or worse, scheduling — when your internet drops. The thermostats below talk to Home Assistant over a local protocol (Z-Wave, Zigbee, or Matter over Thread), so core heating and cooling keep working regardless of the internet.

What “locally controllable” really means

It means the device exposes a local interface — Z-Wave, Zigbee, or Matter — that Home Assistant talks to directly, on your network, without routing through the manufacturer’s servers. A lot of Wi-Fi thermostats marketed as “smart home compatible” only offer a cloud API; those don’t count for this list, no matter how good the app is.

This is exactly where a couple of popular names trip people up. Ecobee has no local API — its Home Assistant integration is cloud-based (and even after the 2026 change that dropped the developer-key requirement, it still goes through Ecobee’s servers). Some Ecobee models can be controlled locally over HomeKit Controller if your network supports mDNS, but that’s a workaround, not a documented local API. Mysa has no native local API either, and its own Home Assistant path runs through the Mysa cloud API. But every Mysa model is HomeKit-certified, so the same HomeKit Controller workaround applies and does give local LAN control. Don’t buy either expecting a documented local API.

Top picks for local control

Honeywell/Resideo T6 Pro Z-Wave

The T6 Pro Z-Wave is the dependable choice if you already run a Z-Wave network. It pairs to your Z-Wave coordinator and integrates cleanly with Home Assistant with no cloud dependency at all — setpoints, mode and current temperature all local. The display and on-device UI are utilitarian, but it’s reliable and well-supported. For most low-voltage (24V) heating/cooling systems in North America, this is the safe default. Buy the Z-Wave variant deliberately: the current SKU is the TH6320ZW2007, and the older TH6320ZW2003 is the same hardware but has been discontinued. The near-identically named -WF model is the Wi-Fi and cloud version, not a Z-Wave one.

Honeywell T6 Pro Z-Wave

Sinopé thermostats (Zigbee or Wi-Fi)

Sinopé is the go-to for North American electric heating — line-voltage baseboards, convectors, and low-voltage systems — which most thermostats handle poorly. Choose the Zigbee models for local control — the line-voltage Sinopé TH1123ZB is the baseboard workhorse. They pair straight through ZHA or Zigbee2MQTT with no Sinopé hub in the middle and run entirely on your network; the GT130 gateway and the Neviweb cloud are only needed for Sinopé’s own app, not for Home Assistant. Sinopé also sells Wi-Fi models that talk to Neviweb directly, so stick to the Zigbee line if local-first is the goal. If you heat with electric baseboards and want true local control, this is the strongest option here.

Eve Thermo (Matter over Thread)

The Eve Thermo is a radiator valve (TRV), not a wall thermostat — relevant if you have European-style hydronic radiators. The current Matter generation runs over Thread, stores its schedule on the device, and keeps heating routines and manual control working during an internet outage. You need a Thread border router (a HomePod mini, the built-in radio on a Home Assistant Yellow if you already own one, or another border router) and it joins Home Assistant via the Matter integration. Matter support in HA is solid now but occasionally needs a re-pair; hardware quality is good.

Eve Thermo

A note on whole-house IR / mini-splits

If you have a ductless mini-split with only an IR remote, there isn’t a great fully-local thermostat answer. IR-blaster controllers (Sensibo, Tado, and similar) generally run their smart features through the vendor cloud. The fully local route is an ESPHome-based IR blaster (e.g. a board with the right IR climate component for your unit) flashed yourself — more effort, but fully local. Treat the commercial IR controllers as cloud devices.

What to avoid for local-first builds

• Ecobee — cloud integration, no local API (HomeKit Controller is the only local-ish path, and only on supported models).
• Mysa — no native local API; cloud by default, with the same HomeKit Controller workaround as Ecobee.
• Most Nest models — core functions still lean on Google’s servers.
• Sensibo, tado V3+ and similar IR/Wi-Fi controllers — cloud APIs; your control stops when the internet does. The exception is tado’s newer X line: the tado Smart Thermostat X runs Matter over Thread and keeps working locally without the tado cloud, though it is sold in the EU and UK only.

Bottom line

• Already on Z-Wave, standard 24V system: Honeywell T6 Pro Z-Wave.
• Electric baseboard / line-voltage heat: Sinopé Zigbee models.
• Hydronic radiators: Eve Thermo (Matter over Thread) with a Thread border router.
• Mini-split with IR only: a self-flashed ESPHome IR blaster, not a cloud controller.

Match the thermostat to your heating system and to a protocol you already run, and all of these keep working when your internet doesn’t.

Related reading:

• Best smart thermostats for local-first homes
• Best Z-Wave devices for Home Assistant

Blueprints are one of Home Assistant’s most underrated features. They let you import a ready-made automation, script, or template entity and then fill in a few fields, no YAML required. One blueprint can be reused many times, so the same “motion lights” logic can drive your hallway and your bathroom as two independent automations. Here’s what actually matters when you’re getting started.

First, understand what a blueprint is (and isn’t)

A blueprint is a reusable recipe for an automation, script, or template entity. You import it, pick your entities, and Home Assistant builds the automation for you. Because your automation inherits from the blueprint, updates to the blueprint flow through the next time Home Assistant reloads.

Blueprints live in config/blueprints/ and you import them from Settings → Automations & scenes → Blueprints → Import blueprint, pasting a link from the Home Assistant forums, GitHub, or a gist. A good curated source to browse is the community “Blueprints Exchange” forum and collections like EPMatt’s Awesome HA Blueprints.

What blueprints are not: dashboard cards. Popular tools like Auto-entities (auto-populates cards with entities matching filters) and card-mod (applies CSS styling to cards) are frontend cards you install through HACS, not blueprints. They configure your Lovelace dashboard, not your automations. Worth installing, but in a different part of the app.

Good blueprints to start with

You don’t need many. Pick blueprints that match hardware you actually own:

• Motion-activated light — the classic. Turn a light on with a motion or presence sensor, off after a delay, often with conditions for time of day or sun elevation. This is the single most useful automation pattern in most homes.
• “Everyone left / someone’s home” style presence automations — drive an away mode from your phone device trackers or presence sensors.
• Notify on low battery — scans your battery sensors and pings you before a sensor dies silently. Saves you discovering a dead door sensor at the worst moment.
• Zigbee/Z-Wave remote or button blueprints — most popular remotes (IKEA, Hue, Aqara, etc.) have a community blueprint that maps button presses to actions, which is far easier than wiring up device triggers by hand.

Presence and device tracking

Presence detection is the backbone of useful automations. Start simple: the Home Assistant Companion app on your phone provides a device tracker over GPS and your Wi-Fi network, which is enough for “is anyone home” automations. Router-based tracking (your phone’s connection to Wi-Fi) is another low-effort option.

For room-level detection, mmWave presence sensors are the upgrade. The Aqara FP2 is a capable pick: it’s a Wi-Fi mmWave sensor that supports up to ~30 zones and, once set up, runs locally in Home Assistant through the HomeKit Controller integration. It is a practical compromise rather than a purist local choice, though — initial setup goes through the Aqara app, and it sits on Wi-Fi rather than a mesh protocol. It’s overkill for most rooms, though, so reach for it only where simple motion sensors fall short.

Garage and cover control

Garage door automations are a common need. For Chamberlain/LiftMaster (MyQ) openers, the ratgdo32 control board is a popular local-first fix: it wires to the opener and exposes it to Home Assistant over your LAN via ESPHome or MQTT, no cloud account required. Check your opener’s learn button first: ratgdo speaks Security+ and Security+ 2.0 (purple/red or yellow button), but openers with Security+ 3.0 (round white button, November 2025 and newer) removed the wired data line entirely and moved accessory control to encrypted Bluetooth LE, so no third-party board can drive them (see local-first garage door controllers). Once the door is a normal cover entity, generic cover blueprints (auto-close after N minutes, alert if left open) work fine.

What to skip initially

• Don’t import blueprints for hardware you don’t own yet. Collecting blueprints leads to automation sprawl you won’t maintain.
• Be cautious with blueprints that depend on add-ons or extra integrations until you know you need them. (Add-ons, note, are one-click Docker services that require Home Assistant OS or a Supervised install — they aren’t available on a plain Container install.)
• Skip elaborate “AI assistant” blueprints early on. Built-in voice control via Home Assistant Voice Preview Edition handles basic commands without the overhead.

Bottom line: Import a motion-lights blueprint, a low-battery notifier, and a button blueprint for any remote you own. Add Auto-entities and card-mod from HACS to tidy your dashboard. Don’t chase features for hardware you might buy later — start simple and expand when you hit a real need.

Frigate is the best open-source NVR solution for local-first smart homes, but getting it running well requires some upfront planning. Here’s how to build a system that actually works.

Hardware: What Actually Runs Frigate Well

Frigate needs real compute to handle AI object detection in real time. Skip the Raspberry Pi—it’s not viable for anything beyond one or two cameras with basic motion detection.

For 4-8 cameras, a compact mini PC hits the sweet spot between cost and capability. If you’d rather repurpose hardware you already own, see how to build a Frigate server on a budget. The Beelink EQ13 with an Intel N100 processor handles 6-8 1080p streams with hardware acceleration without breaking the bank. If you want more headroom for future cameras or higher resolutions, the Intel NUC 12 Pro is overkill in the best way—it’ll run Home Assistant, Frigate, and more without breaking a sweat. On detection, lean on the Intel iGPU through OpenVINO first, with a discrete GPU or a Hailo-8/8L M.2 module as the step up. Frigate’s documentation no longer recommends the Google Coral as the starting point for a new install, though it remains supported and is still the pick when power draw is the binding constraint.

Storage matters more than most people plan for. Plan on 1TB minimum for a week of continuous recording at 1080p, more if you want longer retention or higher resolution. Use a dedicated SSD—NVR workloads are write-heavy and spinning drives will bottleneck you.

Cameras: What Works and What Doesn’t

Not all cameras play nice with Frigate. Stick to ONVIF cameras for the best experience—Reolink’s PoE camera line is a cost-effective ONVIF option that works reliably. The Reolink Duo 3 PoE is excellent for wide-area coverage with dual lenses.

Avoid cloud-only cameras that don’t support local streaming. You’re building a local system—cameras that require cloud connectivity defeat the purpose.

For the best Frigate experience, enable RTSP streams on your cameras and configure them in Frigate. Most wired Reolink and Amcrest cameras support this out of the box. On the Reolink side power type is what decides it: the PoE and plug-in models expose RTSP and ONVIF, while Reolink’s battery cameras expose neither as standalone devices, so they cannot feed Frigate directly. If you’re using Amcrest IP8M-2496E or similar, the ONVIF integration handles the heavy lifting.

Networking: Don’t Skimp Here

POE (Power over Ethernet) simplifies camera installs dramatically. If you’re running new wiring, go with POE—it’s more reliable than WiFi and eliminates separate power runs. A simple UniFi Protect setup handles both NVR and POE switching if you want an all-in-one solution, though Frigate gives you more flexibility.

For WiFi cameras, expect occasional dropouts. Placement matters—avoid corners and areas with interference. If reliability matters, wired connections aren’t optional.

Integration with Home Assistant

This is where Frigate shines. The Home Assistant integration gives you real-time camera feeds, motion events as automation triggers, and thumbnail generation for notifications. You don’t need a separate dashboard—just add Frigate as an integration and cameras appear automatically.

For presence detection, combine Frigate with the Aqara FP2 or Everything Presence One sensors. Frigate handles exterior monitoring while presence sensors handle indoor occupancy. This separation prevents the “camera everywhere” creep that makes smart homes feel invasive.

Quick Verdict

Once your NVR is running, the same hardware can power other local-first projects—for example a local-first baby monitor with Frigate and alerts. Building a Frigate NVR is straightforward if you don’t overcomplicate it. Hardware requirements are modest, camera selection is wide, and the Home Assistant integration Just Works. Budget $300-500 for a capable NVR server, $50-150 per camera, and plan for storage up front. The tradeoff is straightforward: you’re trading money for privacy. Cloud NVRs are cheaper but you pay with your data. For a local-first smart home, Frigate is the clear answer.

Most popular automatic pet feeders (PetSafe, PETKIT, Petlibro, and similar Wi-Fi models) depend on the manufacturer’s cloud for scheduling and remote dispensing. There is one mainstream exception worth knowing about: the Aqara Smart Pet Feeder C1 is a plain Zigbee 3.0 device that pairs straight to Home Assistant with no hub and no account. Beyond that, the local options are a DIY ESPHome build or repurposing a local-control actuator to drive a feed mechanism. This article focuses on what actually works locally and skips the cloud devices.

The off-the-shelf option: Aqara Smart Pet Feeder C1

The Aqara Smart Pet Feeder C1 (model ZNCWWSQ01LM) is the closest thing to a buy-it-and-be-done local feeder. Retail listings say it requires an Aqara Zigbee 3.0 hub; that is marketing, not a hardware limit. It is an ordinary Zigbee 3.0 device and pairs directly to any Zigbee coordinator through ZHA or Zigbee2MQTT — no Aqara hub, no Aqara account, no cloud. ZHA applies a quirk for it automatically.

What you get locally:

• Dispense on demand, plus portion size, portions-per-day, and daily-weight counters as Home Assistant entities.
• On Zigbee2MQTT the feeding schedule is written to the feeder itself, so meals still happen if Home Assistant is down for maintenance. ZHA cannot push a schedule to the device, so on ZHA you trigger feeding from a Home Assistant automation instead.
• Child lock, LED indicator control, and a manual dispense button on the unit.

Practical notes: it takes a 5V supply (not included) and holds three D-cell batteries as power-outage backup, it handles roughly 1—12mm kibble, and it is sized for cats and small-to-medium dogs. Some owners have reported occasional off-schedule dispenses, so the confirmation sensor and failure alert described below are worth setting up rather than trusting it blind.

The DIY ESPHome route (most control)

If you want to control the mechanism end to end, build a feeder with ESPHome on an ESP32 (new to ESPHome? start with our ESPHome guide for Home Assistant), driving a motor that turns an auger or rotating hopper. ESPHome talks to Home Assistant over your LAN with no cloud at all.

A typical build:

• An ESP32 running ESPHome.
• A stepper or DC gear motor (with a driver board) to advance the feed auger a measured amount per portion.
• Optional: a load cell / HX711 to weigh dispensed food, or a microswitch to confirm a turn completed.

You then expose a “dispense portion” button/service to Home Assistant and schedule it with an automation. Because the schedule lives in Home Assistant (or even on the ESP32 itself), feeding continues even if your internet is down. This is more work than buying a feeder, but it’s fully local, transparent, and repairable.

Repurposing local-control hardware

If you’d rather not design a motor system from scratch, you can drive a simple gravity feeder or trapdoor with an existing local actuator:

• A smart plug or relay that powers a small motorized dispenser on a schedule. A SONOFF Zigbee/ESPHome relay or a Zigbee/Z-Wave plug works locally; a Hue smart plug works locally via the Hue Bridge. (Note: a plug just switches power on/off — it can’t meter a precise portion, so pair it with a feeder that dispenses on power.)
• A linear actuator or servo to open a flap, driven by an ESPHome board.

This is a hack, not a polished product, so test it thoroughly before trusting it with feeding.

What does NOT work for this

To save you from bad advice that’s circulated elsewhere:

• The ratgdo / ratgdo32 is a garage-door opener control board — it is not a pet feeder and does not run on a Raspberry Pi. Don’t buy it for feeding.
• A SwitchBot Lock or SwitchBot Roller Shade are designed for deadbolts and window shades; they’re a poor fit for portioning food and shouldn’t be presented as feeder solutions.
• A Sonoff Zigbee USB Dongle is a Zigbee coordinator (it’s how Home Assistant talks to Zigbee devices) — it is not itself a feeder or a feeder controller.

Home Assistant scheduling and safety

However you build the mechanism, do the scheduling in Home Assistant:

• A time-based automation for regular meals, with a condition to avoid double-feeding after a restart.
• A confirmation sensor (weight or a turn-complete switch) so an automation can alert you if a dispense fails.
• A local push notification if a scheduled feed didn’t register, so an empty bowl doesn’t go unnoticed.

Keep the host on reliable power (a UPS helps; see the best UPS for smart homes) since a feeder that misses meals is worse than no automation.

Compatibility with HomeKit

If you also run HomeKit or Hubitat, the simplest path is to keep the feeder logic in Home Assistant and expose it outward — for example via the Home Assistant HomeKit bridge so a HomeKit scene can trigger a feed. The mechanism still runs locally through HA either way.

Quick verdict

The Aqara Smart Pet Feeder C1 is the one mainstream feeder you can buy and run fully locally — plain Zigbee 3.0, no Aqara hub, and on Zigbee2MQTT the schedule lives on the feeder itself. If you would rather build than buy, a DIY ESPHome + motor build gives you the most control, and repurposing a local relay/actuator can drive a simple dispenser. Schedule it in Home Assistant with a confirmation sensor and a failure alert. Ignore claims that a ratgdo, a SwitchBot lock/shade, or a Zigbee dongle is a “local pet feeder” — those are different products entirely.

If you are building a local-first smart home on a reasonable budget, you are going to run into these three brands constantly: Aqara, Shelly, and Sonoff. They all show up in Home Assistant communities, they all have devices under $30, and they all claim some version of local control.

But they are not interchangeable. They take fundamentally different approaches to protocols, hubs, firmware, and what “local” actually means in practice. Picking the wrong ecosystem for your situation does not ruin anything (you can always mix), but it does waste time and money.

This guide is for people who already know they want local control and Home Assistant compatibility. If you are still deciding on a platform, read Home Assistant vs Hubitat first.

Quick verdict

• Aqara: best polished ecosystem with strong Apple Home and Home Assistant support. Zigbee-first, expanding into Matter and Thread.
• Shelly: best for electricians and DIYers who want in-wall devices with a true local API and no hub requirement. Wi-Fi is the default, but current Gen4 parts can be switched to Zigbee instead.
• Sonoff: some of the cheapest Zigbee devices around, great for HA-only setups where fit and finish do not matter much.

Protocol approach

Aqara

Aqara is a Zigbee-first ecosystem. Most of their sensors, switches, and locks communicate over Zigbee 3.0, which means you need either an Aqara hub (like the Hub M3) or a Zigbee coordinator connected to Home Assistant. Their newer devices are adding Matter and Thread support, which gives you more flexibility, but the bulk of the product line is still Zigbee.

Shelly

Shelly devices are Wi-Fi-first, which means no hub and no coordinator. Each device connects directly to your network and exposes a local HTTP API and optional MQTT. This is fully hub-free local control, not marketing language. Some newer Shelly devices add Bluetooth, their Wave line uses Z-Wave, and the current Gen4 relays, dimmers and plugs also carry Zigbee 3.0 and Matter, so Shelly is no longer a Wi-Fi-only brand. A Gen4 runs one radio profile at a time: it ships in a Matter-over-Wi-Fi profile, and a button sequence on the device switches it to Zigbee, which takes Wi-Fi and Matter away. The core identity is still Wi-Fi relays and switches that work on their own.

Sonoff

Sonoff is split. Their Zigbee line (the SNZB sensors, the ZBMINI-L2) works great with a Zigbee coordinator and Home Assistant. Their Wi-Fi devices are more nuanced than the usual “flash it or live in the cloud” summary. Stock eWeLink firmware does answer on the local network, so there are two local routes: drive the stock firmware over your LAN, or replace the firmware with Tasmota or ESPHome.

Flashing is not always on the table. Newer plugs like the S40 Lite use a Bouffalo Lab BL602 chip, which neither Tasmota nor ESPHome supports, while the older ESP-based S31 flashes fine. Check which chip is inside before you buy a Sonoff plug specifically to flash it.

Home Assistant integration quality

Aqara devices integrate well through ZHA or Zigbee2MQTT. Many of them also work via HomeKit Controller or native Matter, which gives you multiple paths into Home Assistant. The FP2 presence sensor is a good example. It works over Wi-Fi via HomeKit Controller without needing a Zigbee coordinator at all.

Shelly has an excellent native Home Assistant integration with local push updates. No coordinator, no flashing, no workarounds. Devices like the Shelly Plus 1 and Plus Plug US are discovered automatically and report state changes instantly over the local network. This is about as clean as Wi-Fi device integration gets.

Sonoff Zigbee devices work well through ZHA or Zigbee2MQTT, and the SNZB-02D temp sensor is a community favorite. Their Wi-Fi devices ask you to make a choice. Stock firmware can be driven locally, but not by a core Home Assistant integration: you add either the official eWeLink Smart Home add-on or the SonoffLAN custom integration through HACS, and both need your eWeLink account credentials to fetch the per-device encryption keys. Flashing Tasmota or ESPHome drops the account and the cloud from the picture entirely, at the cost of a wired first flash and a device whose chip supports it.

Product range and build quality

Aqara has the widest range of the three: motion sensors, presence sensors, door sensors, temperature sensors, cameras, smart locks like the U200, light switches, LED bulbs, and valve controllers. Build quality is noticeably better than budget competitors. Devices feel solid and look like they belong in a finished home.

Shelly is focused on power control: relays, dimmers, smart plugs, and energy monitoring. The Wave 1PM Mini is a good example of what they do best: compact in-wall relays for electricians and confident DIYers. They are expanding into sensors, but the product line is narrower than Aqara’s. Build quality is functional and industrial rather than pretty.

Sonoff covers a wide range of cheap Zigbee sensors and a few switches and plugs. The build quality is utilitarian. These are not devices you show off, but they work. The SNZB sensor line is useful for filling a house with temperature, humidity, motion, and door sensors without spending much money.

Cloud dependency reality

This is where the three brands differ most, and where marketing claims get slippery.

Aqara Zigbee devices paired directly to a Home Assistant Zigbee coordinator are fully local. No cloud involved, no Aqara account needed. But if you use Aqara’s own hub and app, cloud features are baked in. Firmware updates, remote access, and some automations go through Aqara’s servers. The local story is real, but only if you go through Home Assistant.

Shelly is the most local-first of the three. Every Shelly device has a built-in web UI you can access from a browser. You can control devices, set schedules, and configure MQTT without any app, any cloud account, or any smart home platform. If Home Assistant disappeared tomorrow, your Shelly devices would still work from their own web interfaces. That is a meaningful difference.

Sonoff Zigbee devices paired to a Home Assistant coordinator are fully local, same as Aqara. Their Wi-Fi devices sit in between. Stock firmware gives you no web UI and no MQTT, and the eWeLink app is cloud-first, but the devices do answer on the LAN: the official eWeLink add-on and the SonoffLAN integration both talk to them locally and fall back to the cloud when a device goes quiet. The catch is that the local protocol is encrypted, so you need eWeLink account credentials to get the keys, and Sonoff can change that arrangement in a firmware update. It lands between a cloud-only plug and a Shelly, which owes nothing to any account.

When to pick each one

Pick Aqara if…

• you want polished, good-looking devices that fit a finished home
• you use Apple Home or want Matter/Thread options alongside Home Assistant
• you want a broad product range from one brand (sensors, locks, switches, presence)
• you are fine running a Zigbee coordinator or an Aqara hub

Pick Shelly if…

• you want hub-free Wi-Fi devices with real local APIs that work independently
• you are doing electrical work and want compact in-wall relays and dimmers
• you want devices that do not depend on any platform, not even Home Assistant
• energy monitoring and power control are your main priorities

Pick Sonoff if…

• you want the cheapest reliable Zigbee sensors available
• you are building an HA-only setup and do not care about polish or app experience
• you want to fill a house with sensors without a large budget
• you are comfortable with utilitarian build quality

Can you mix and match?

Yes, and most experienced local-first households do exactly this.

A common setup: Aqara sensors and locks for the devices you interact with or see every day, Shelly relays behind light switches for local power control, and Sonoff Zigbee sensors scattered in closets, garages, and utility areas where cost matters more than aesthetics.

Zigbee devices from Aqara and Sonoff can share the same coordinator in Home Assistant. Shelly Wi-Fi devices exist on a completely separate layer and do not interfere with your Zigbee mesh at all. There is no technical penalty for mixing brands, only the mild annoyance of managing different firmware update processes.

The practical advice: start with whichever brand solves your first problem, and do not feel locked in. These ecosystems overlap more than they compete.

Related:

• Best smart plugs with local control and energy monitoring
• Best local home sensors
• Zigbee vs Z-Wave vs Matter vs Thread

If you are building Home Assistant around local control, sensors are where Zigbee pays for itself fastest.

A good Zigbee sensor network gives you the real inputs that make automations useful: motion in a hallway, a leak under the sink, a door left open, humidity spikes in a bathroom, or occupancy in a room that should stay lit while someone is still there.

This guide focuses on practical sensor picks that work well in local-first setups, not cloud dashboards and notification spam.

Quick verdict

For most Home Assistant users, Zigbee is still the easiest way to deploy lots of battery-powered sensors without relying on vendor clouds.

If you want a short starter stack, buy:

• one reliable motion sensor for lighting automations
• one contact sensor for doors/windows
• one leak sensor for water-risk areas
• one mmWave presence sensor for your most-used room

The best first buys in this list are:

• Best overall motion sensor: Third Reality Motion Sensor
• Best door/window pick: Third Reality Door Sensor
• Best leak sensor value: Third Reality Water Leak Sensor
• Best presence upgrade: Aqara FP1E

Why Zigbee sensors are a strong local-first choice

Zigbee sensors are typically affordable, low-power, and easy to spread across a home. In Home Assistant, they are also mature: you can run them through ZHA or Zigbee2MQTT and keep core automations working even when your internet connection drops.

You still need a solid coordinator and a healthy mesh. Battery sensors do not relay traffic, so add a few mains-powered Zigbee devices (plugs, bulbs, or in-wall relays) to stabilize coverage. Most mains-powered Zigbee devices route for their neighbours, but not all of them do: low-power no-neutral switches such as the SONOFF ZBMINI-L2 stay end devices and will not extend your mesh. Do that early and your automations will feel much more reliable.

Best motion sensor: Third Reality Motion Sensor

The Third Reality Motion Sensor is a practical default recommendation for basic occupancy-triggered automations.

Why it stands out:

• fast enough reporting for lights and occupancy cues
• good value when you need several units
• straightforward Home Assistant behavior for common use cases

Start with hallways, laundry, and garage entry paths. These locations produce immediate quality-of-life gains and are easy to verify.

Best contact sensor: Third Reality Door Sensor

The Third Reality Door Sensor is a strong low-friction option for entry and window state.

Where it helps most:

• door-left-open alerts tied to time windows
• HVAC efficiency automations when windows are open
• security routines that do not depend on cloud arming logic

Contact sensors seem simple, but they are foundational for dependable local automations.

Best leak sensor value: Third Reality Water Leak Sensor

Water detection is one of the highest ROI categories in smart homes. The Third Reality Water Leak Sensor is an easy recommendation for broad coverage at reasonable cost. It also carries a 120 dB alarm in the sensor itself, so a leak makes noise even if your hub is down or your internet is out.

Good placement targets:

• under sinks and behind toilets
• near water heaters and washing machines
• around utility closets or sump areas

Pair leak alerts with escalating local actions in Home Assistant (sirens, repeated announcements, and optional shutoff valves if your setup supports them).

Best presence sensor upgrade: Aqara FP1E

If motion-based lighting keeps turning off while someone is still in the room, add mmWave presence detection. The Aqara FP1E is a strong upgrade path for local occupancy workflows.

Why it matters:

• detects micro-movement better than standard PIR sensors
• reduces false “room empty” events in offices and living rooms
• enables smarter lighting and HVAC hold logic

Use presence sensors where people sit still: desks, media rooms, and bedrooms.

Best environment sensor option: Aqara Climate Sensor W100

For temperature and humidity telemetry, the Aqara Climate Sensor W100 is a useful local data source, with one buying caveat that catches people out. It is a dual-protocol device: it runs either Zigbee 3.0 or Thread, never both at once, and it ships in Thread firmware. Out of the box it will not join ZHA or Zigbee2MQTT at all. Switching it to Zigbee is a one-time step in the Aqara Home app, after which it runs fully local on your own coordinator, with no Aqara hub and no Aqara account in the loop.

Practical automation examples:

• bathroom fan triggers on humidity thresholds
• comfort alerts for nursery or office conditions
• HVAC helper automations using room-level measurements

Environmental sensors are less dramatic than security devices, but they make local automations feel precise instead of generic.

Setup notes for Home Assistant

Protocol choice matters less than implementation quality. For Zigbee sensor reliability, focus on the basics:

1. Use a known-good coordinator and keep firmware current.
2. Build mesh density with mains-powered repeaters in weak zones.
3. Keep 2.4 GHz Wi-Fi channel overlap in mind when placing coordinator hardware.
4. Add sensors category by category, then validate automations before scaling.

You do not need to convert your whole home in one weekend. A gradual rollout produces better automations and fewer debugging sessions.

Final recommendation

If your priority is local-first Home Assistant automations, Zigbee sensors remain one of the best-value upgrades you can make.

Begin with Third Reality Motion Sensor, Third Reality Door Sensor, and Third Reality Water Leak Sensor. Add Aqara FP1E where you need true presence logic.

Related reading:

• Best Zigbee coordinators for Home Assistant
• Best local home sensors
• Zigbee vs Z-Wave vs Matter vs Thread