Smart Home Devices: The No-Subscription, Local-Control Starter Guide (2026)

Disclosure: Some links in this article are affiliate links. We may earn a commission on qualifying purchases at no extra cost to you.

Smart home devices are only as trustworthy as the path between a sensor and the thing it controls. The no-subscription setups worth building don't just avoid monthly fees—they keep that path local, so a light still turns on when your internet drops or a vendor shuts down. If you're starting from scratch, our Home Assistant beginner's guide explains the platform behind this architecture.

Most starter guides tell you to buy a speaker and a few bulbs, then lock you into a manufacturer's app. This one takes the opposite approach: choose a controller that stores automations locally, add a radio you control, and only then attach sensors and lights that speak an open protocol.

What you'll get below is a deliberate build order—Home Assistant Green as the brain, a Zigbee radio, one mains-powered router, then sensors, a bulb, and two automations that prove the system works. We also cover exactly when to add mmWave presence, Z-Wave, and advanced switches, so you don't overbuild on day one.

This guide is for renters, apartment dwellers, and homeowners who want a smart home that respects their privacy, works without a subscription, and keeps running locally. No marketing specs, no fluff—just the architecture, the devices, and the order to buy them.

What You'll Need for This Starter Build

• Home Assistant Green — the local controller
• Connect ZBT-2 — the Zigbee radio
• THIRDREALITY Smart Plug Gen3 — the first mains-powered router
• Aqara Motion Sensor P1 — motion and daylight sensing
• THIRDREALITY Door/Window Sensor — open/close state
• SONOFF SNZB-02P — temperature and humidity
• Philips Hue White and Color Ambiance A19 — local smart lighting
• Optional upgrades: Connect ZWA-2 for Z-Wave, SONOFF SNZB-06P for presence, Inovelli Blue Series switch for wall control

What "No Subscription" Actually Means: Local Control, Not Just No Fees

The phrase "no subscription" gets thrown around as if dodging a monthly bill is the goal. The more useful test is whether the core automation path stays inside your home: sensor → local radio → Home Assistant → local action, with the internet and manufacturer cloud optional rather than operationally required.

Home Assistant stores its data locally and keeps running when internet access is down. Matter devices can also run locally, but Matter is an application-layer control protocol that rides on IP networks such as Wi-Fi, Ethernet, or Thread—not a radio technology of its own. This distinction matters because plenty of "Matter" products still need a Thread border router or working IPv6/mDNS to function. Our Matter explainer unpacks that in detail, and the Zigbee vs Z-Wave vs Matter comparison shows where each protocol earns its place.

Optional cloud services exist in this build, but they are just that—optional. Home Assistant Cloud can simplify Google or Alexa voice integration, but it is not required for local automations. SONOFF's six-month history service and Hue's cloud or Bridge ecosystem can be ignored when the devices are paired directly to your local Zigbee coordinator. The difference between a truly local system and a cloud-dependent one is architecture, not a badge on the box.

The Starter Architecture: Hub, Radio, and One Powered Router

The coherent first build has three load-bearing pieces:

1. Home Assistant Green — the controller that stores automations and coordinates devices. It is not a Zigbee radio.
2. Connect ZBT-2 — a dedicated Zigbee radio that gives Home Assistant direct wireless control of sensors and bulbs. It must be configured for one protocol at a time.
3. THIRDREALITY Smart Plug Gen3 — a mains-powered Zigbee router placed near your first automation area. It strengthens the mesh before you scatter battery sensors around the house.

After that, add sensors on the now-stable mesh, then a Zigbee bulb, then automations. If you want to explore hardware options first, see Home Assistant Green vs Yellow and our Zigbee coordinator roundup.

Step 1 — Home Assistant Green: The Controller, Not the Radio

Home Assistant Green is an appliance-grade way to run Home Assistant without maintaining a Raspberry Pi or DIY host. It is the plug-and-play choice for local control, with expansion via USB.

• Key specs: Rockchip RK3566 quad-core Cortex-A55 at 1.8 GHz, 4 GB LPDDR4X RAM, 32 GB eMMC storage, Gigabit Ethernet, 2× USB 2.0 Type-A ports (5 V / up to 2 A combined), HDMI for diagnostics only, microSD for recovery only, 12 V DC / 1 A supply. Idle draw is about 1.7 W, rising to about 3 W under load. Dimensions: 112 × 112 × 32 mm, 340 g.
• Local path: Initial setup requires internet, but after that Home Assistant stores smart-home data locally and remains usable when the internet goes down.
• Critical distinction: Green itself has no Zigbee radio. The common beginner mistake is buying Zigbee sensors and assuming Green alone can pair them. You need the ZBT-2 adapter in Step 2.

Pros

• Supported Home Assistant OS appliance with straightforward USB expansion
• Low power, fanless, and purpose-built for local control
• No Raspberry Pi maintenance or SD-card fragility

Cons

• No built-in Zigbee/Thread radio
• Less raw compute than a DIY mini PC

Verdict: The right first controller for a local build. Pair it with ZBT-2 to turn it into a direct Zigbee-capable system.

Perfect for: Anyone who wants a supported, low-maintenance Home Assistant hub without building a DIY host.

Check Price on Amazon

For a full setup walkthrough, see our Home Assistant Green review and the hardware comparison guide.

Step 2 — Connect ZBT-2: The Zigbee Radio

The Home Assistant Connect ZBT-2 is the second-generation official Zigbee/Thread adapter, replacing the discontinued ZBT-1/SkyConnect.

• Key specs: Silicon Labs MG24 radio SoC with an ESP32-S3 USB-to-serial bridge. Zigbee 3.0 and Thread support on 2.4 GHz (2400–2483.5 MHz), USB-C 5 V / 500 mA, 10 dBm transmit power in Europe and 8 dBm elsewhere, 4.16 dBi omnidirectional antenna. Interface speed is 460,800 baud, up from 115,200 on the previous model. Dimensions: 83 × 83 × 179 mm, 157 g, includes a 1.5 m USB-C cable.
• Single-protocol rule: One ZBT-2 must be dedicated to either Zigbee or Thread for a given network. It is not a simultaneous dual-protocol radio. For this build, configure it as Zigbee and choose either ZHA or Zigbee2MQTT.

Pros

• First-party Home Assistant support with setup wizard, network migration, and one-click updates
• Modern MG24 radio with a faster USB interface
• Stable choice for a new Zigbee network

Cons

• One protocol per unit; Thread requires a second adapter or another border router
• Amazon US availability has been inconsistent

Verdict: The default radio for a first Zigbee network. Use ZHA for the cleanest beginner path, or Zigbee2MQTT if you want deeper device-specific parameters.

Perfect for: A clean, officially supported way to add Zigbee to Home Assistant Green.

Check Price on Amazon

If you want to compare ZHA and Zigbee2MQTT before committing, our Zigbee2MQTT setup guide and Zigbee coordinator roundup cover the tradeoffs.

Step 3 — THIRDREALITY Smart Plug Gen3: The First Powered Router

Before you scatter battery-powered sensors around a home, establish a mains-powered Zigbee router. The THIRDREALITY Smart Plug Gen3 does two jobs at once: it controls a load and strengthens the mesh.

• Key specs: Zigbee 3.0, model 3RSP02064Z, 15 A outlet rating, ETL certified, enhanced Zigbee router/repeater, real-time power monitoring with ±1% claimed accuracy. Home Assistant support through both ZHA and Zigbee2MQTT. OTA firmware updates, configurable power-on behavior after an outage. Zigbee2MQTT exposes power, voltage, current, frequency, power factor, energy, LED brightness, thresholds, timers, and power-on behavior.
• Why this matters: Battery sensors are end devices—they cannot relay messages for other nodes. Mains-powered plugs, bulbs, and switches normally act as routers. Adding one or two after the ZBT-2 gives the mesh a solid backbone.

Pros

• Dual function: load control plus Zigbee routing
• Real-time power/energy monitoring
• Active firmware line with recent optimization work

Cons

• Default power-reporting thresholds can make instantaneous consumption feel delayed until tuned
• Not a safety-critical control for space heaters or other high-risk inductive loads; load type and local electrical requirements still apply

Verdict: The best low-cost device to anchor a Zigbee mesh before adding battery sensors.

Perfect for: The first powered device in a new Zigbee network, placed near your first automation area.

Check Price on Amazon

For more plug options and energy monitoring details, see our best smart plugs guide and Zigbee & Z-Wave smart plug roundup.

Step 4 — Motion, Contact, and Climate Sensors (The Data Layer)

Sensors are where a smart home becomes useful. Start with three low-risk types: a PIR motion sensor, a contact sensor, and a temperature/humidity sensor. These create the data your first automations will use.

Aqara Motion Sensor P1

• Key specs: PIR motion sensor, Zigbee 3.0, model MS-S02. Up to 170° coverage at close range and 150° at 7 m. Three sensitivity settings, configurable motion reset/detection timeout from 1–200 seconds, integrated illuminance/light sensing, 360° adjustable stand. Operating range -10°C to 55°C, 0–95% RH non-condensing. Aqara claims up to five years of battery life under qualifying settings. Zigbee2MQTT exposes occupancy, illuminance, sensitivity, detection interval, trigger indicator, battery/voltage, and OTA support.
• Why it beats ultra-budget PIR sensors: The reset interval is configurable instead of being fixed for a long cooldown, which makes it far more useful for responsive lighting. Direct ZHA/Zigbee2MQTT use means an Aqara cloud account or Aqara hub is not inherently required.

Pros

• Adjustable reset interval prevents long blind spots between triggers
• Integrated illuminance sensor enables daylight gating
• Direct local integration with ZHA and Zigbee2MQTT

Cons

• PIR detects motion only, not stationary occupancy
• Some bonus features require the Aqara app

Verdict: The default first motion sensor for responsive, local lighting automations.

Perfect for: Entryways, hallways, and rooms where you want lights to react to movement.

Check Price on Amazon

For the full category landscape, see our Zigbee & Z-Wave motion sensor guide.

THIRDREALITY Door/Window Sensor

• Key specs: Zigbee contact/open-close sensor, model 3RDS17BZ. Designed for doors, windows, and any binary open/closed state. Zigbee2MQTT exposes contact state, battery, battery voltage, battery-low state, and configurable delayed-open behavior. OTA firmware support is documented by Zigbee2MQTT, and THIRDREALITY maintains product manuals and firmware history.

Pros

• Reliable and easy to obtain
• Unambiguous open/closed state makes automations simple
• OTA updates and documented firmware history

Cons

• Physically bulkier than very small Aqara or IKEA alternatives

Verdict: The ideal first contact sensor for entry and window automations.

Perfect for: Doors, windows, and any place you want open/close awareness.

Check Price on Amazon

See our door/window sensor roundup for more options and use cases.

SONOFF SNZB-02P Temperature & Humidity Sensor

• Key specs: Zigbee 3.0 temperature and humidity sensor. Temperature accuracy ±0.2°C / ±0.4°F, relative humidity accuracy ±2% RH. CR2477 coin-cell power, claimed up to four years of battery life under lab conditions. Minimum rapid-update behavior around five seconds when values change, with stable conditions periodically reported. Dimensions 45 × 45 × 17.7 mm, about 26.7 g. Operating range -10°C to 60°C, 5–95% RH. Zigbee2MQTT exposes temperature, humidity, battery, and calibration controls with OTA support.
• Optional cloud, ignored here: SONOFF promotes six months of cloud history in its ecosystem, but Home Assistant can record sensor history locally instead. The direct Zigbee path does not require that cloud feature.

Pros

• Strong accuracy specs and calibration controls
• Long battery life claim
• Direct local integration with ZHA and Zigbee2MQTT

Cons

• Lower operating limit of -10°C means it is not a deep-freezer sensor, despite frequent buyer requests
• Amazon US availability has been limited

Verdict: The best value climate sensor for room comfort, bathroom humidity, and HVAC/fan automations.

Perfect for: Monitoring temperature and humidity in living spaces, not sub-freezing environments.

Check Price on Amazon

For more climate sensor picks, see our temperature and humidity sensor guide.

Step 5 — Philips Hue White and Color Ambiance A19: The First Smart Bulb

The Philips Hue White and Color Ambiance A19 (model 563254) demonstrates a key local-first principle: a product can belong to a proprietary ecosystem without requiring that ecosystem for core operation.

• Key specs: A19 form factor, E26 base. White and full-color LED. Marketed 1,100-lumen output; official technical output 1,055 lm at 4000 K and 806 lm at 2700 K. Tunable white 2000–6500 K, 10.5 W, 0.2 W standby, 75 W incandescent-equivalent class, 110–130 V. Rated ~25,000 hours and 50,000 switching cycles. CRI ≥80. Software upgradeable, three-year warranty, and Philips specifies a minimum support period of 60 months after authorized purchase. Zigbee + Bluetooth; works without Wi-Fi because it includes Zigbee/Bluetooth radios.
• Local path: Pair it directly to your Home Assistant Zigbee coordinator through ZHA or Zigbee2MQTT, eliminating the Hue Bridge from the control path. Note that broader Hue Matter support normally comes through a Hue Bridge—this Zigbee bulb is not a native Matter-over-Thread bulb.

Pros

• Direct Zigbee pairing without a Hue Bridge
• Wide tunable range, strong output, and long support window
• Premium reliability in a locally controlled install

Cons

• Premium tier; advanced Hue features like scenes and entertainment require the Bridge
• Not native Matter-over-Thread

Verdict: A reliable first smart bulb for local control. Pair it directly to your ZBT-2 and skip the Bridge unless you want the full Hue ecosystem.

Perfect for: A living room or bedroom lamp where you want tunable, colored light without cloud dependency.

Check Price on Amazon

For more bulb options, see our Zigbee smart bulbs guide and best smart light bulbs ranking.

Upgrade Paths: When to Add mmWave, Z-Wave, and Advanced Switches

The starter build above handles motion, entry, climate, and lighting. The three upgrades below are for specific gaps, not day-one purchases.

When to Add mmWave Presence: SONOFF SNZB-06P

PIR detects motion, not stationary occupancy. If you sit still in an office or living room, a PIR sensor can turn lights off while you're still there. That's where mmWave presence sensing enters.

• Key specs: 5.8 GHz microwave/mmWave presence sensing, detects both moving and stationary occupants. Zigbee 3.0, integrated ambient-light sensing, up to about 4 m presence range, three sensitivity settings, USB-powered 5 V / 1 A. Works as a mains-powered Zigbee router/repeater. ZHA and Zigbee2MQTT support. Firmware matters: Zigbee2MQTT documents undesirable behavior on firmware 1.0.3 and recommends 1.0.5 or newer for shorter occupancy timeout configuration and more reliable behavior.
• False-trigger sources: Moving curtains, pets, robot vacuums, and running fans can cause false presence. Positioning and sensitivity tuning are essential—do not treat mmWave as categorically superior to PIR.

Pros

• Detects a motionless person, solving the PIR gap
• Mains-powered router strengthens the mesh
• Firmware line has matured with later releases

Cons

• Needs constant USB power and careful sensitivity tuning
• Known false-trigger sources require placement discipline

Verdict: Add this only where stationary presence makes PIR inadequate—office, living room, or bathroom.

Perfect for: Rooms where you sit still for long periods and want lights to stay on.

Check Price on Amazon

When to Add Z-Wave: Connect ZWA-2

Z-Wave remains compelling, not obsolete. It operates in quieter sub-GHz spectrum and is especially established for switches, locks, and security devices.

• Key specs: Official Home Assistant 800-series Z-Wave adapter. Silicon Labs ZG23 SoC with ESP32-S3 USB bridge. Z-Wave mesh and Z-Wave Long Range support. US examples: 908.42/916 MHz mesh, 912/920 MHz LR. 3.38 dBi omnidirectional antenna, USB-C 5 V / 1 A. Dimensions 125 × 125 × 315 mm, 350 g. Direct USB is recommended because Z-Wave JS communication is latency-sensitive. Home Assistant recommends current 800-series controller firmware and SDK branches, as older 800-series firmware has documented stability issues. No subscription or vendor cloud required.
• When it earns the extra complexity: Add ZWA-2 only after choosing devices that specifically justify a Z-Wave network—often locks, security sensors, or difficult RF environments. Starting with one protocol keeps commissioning and troubleshooting simpler.

Pros

• Mature sub-GHz mesh with Long Range capability
• First-party Home Assistant recommendation for new Z-Wave deployments
• Local operation with no vendor cloud

Cons

• Requires a separate adapter and network
• Older 800-series firmware has stability issues; current firmware is recommended

Verdict: An upgrade path for locks and challenging RF environments, not a day-one requirement.

Perfect for: Users who need Z-Wave locks or devices in RF-difficult parts of the home.

Check Price on Amazon

Advanced Wall Control: Inovelli Blue Series 2-1 Smart Switch/Dimmer

The Inovelli Blue Series VZM31-SN is the tinkerer upgrade for replacing wall switches, not the ideal first-ever smart-home purchase.

• Key specs: Zigbee 3.0, configurable as on/off switch or dimmer. 120 V AC / 60 Hz North American product. Supports neutral and qualifying no-neutral installations, single-pole and multi-way/3-way. Smart Bulb Mode keeps smart bulbs continuously powered while the paddle sends commands/scenes. Advanced scene/multi-tap controls, customizable notification LED bar, and direct Zigbee binding for very low-latency local switch-to-bulb control. Officially tested with ZHA and Zigbee2MQTT. Production firmware was 3.04 as of June 2026, with later beta work continuing.
• Load restrictions: Intended for lighting loads only. Inovelli explicitly warns against using it on outlets, fans, or other inductive loads. No-neutral installations introduce limitations including bypass requirements in some configurations, loss of power metering, and restrictions on multi-way companion switches.

Pros

• Smart Bulb Mode solves the "switch cuts power to smart bulbs" problem
• Direct Zigbee binding enables low-latency local control
• Active firmware development

Cons

• Lighting-only load restrictions; no fans or outlets
• No-neutral installations have documented tradeoffs
• Premium/tinkerer positioning; validate wiring and load requirements first

Verdict: A powerful advanced switch once you understand Zigbee groups, binding, and scenes. Use a qualified electrician when appropriate.

Perfect for: Enthusiasts ready to replace wall switches and keep smart bulbs permanently powered.

Check Price on Amazon

For more switch options, see our no-neutral switch guide and Zigbee & Z-Wave switch roundup.

Your First Two Automations

The fastest way to validate the architecture is to build two simple automations entirely inside Home Assistant. Both run locally.

Automation 1: Motion + Low Light → Bulb On

Trigger: Aqara Motion Sensor P1 detects occupancy.
Condition: Illuminance from the P1 is below a threshold you set, so lights only fire when it's actually dark.
Action: Turn on the Philips Hue bulb.
Off logic: After no motion for 30–120 seconds, turn the bulb off.

This fast-on, conservative-off pattern is called hysteresis. It prevents lights from shutting off during momentary sensor gaps. The Aqara P1's configurable 1–200 second reset interval makes this far more responsive than a fixed-cooldown PIR. For a deeper dive, see our Home Assistant automations guide.

Automation 2: Door/Window Left Open → Local Notification

Trigger: THIRDREALITY Door/Window Sensor stays open.
Delay: After a few minutes, so quick entries don't trigger it.
Action: Send a notification to your phone through the Home Assistant Companion App using the local notification path.

This automation has no cloud dependency. The sensor state is unambiguous, and the notification can be fully local. It's a perfect first example of the architecture working end to end.

Common Beginner Mistakes to Avoid

1. Treating Matter as a radio. Matter is an application-layer protocol over IP. It does not replace Zigbee or Z-Wave radios. A Thread device is not automatically Matter, and Matter-over-Thread requires a border router.
2. Expecting Green to have built-in Zigbee. Green is a controller. You must add ZBT-2 or another coordinator to pair Zigbee sensors.
3. Buying battery sensors before powered routers. Battery sensors are end devices. A mesh of battery sensors without mains-powered routers is unreliable.
4. Assuming mmWave is always better than PIR. PIR is cheap, battery-powered, and excellent for motion/entry. mmWave detects stationary presence but needs constant power and careful tuning.
5. Believing "compatible with Home Assistant" means fully local. Some integrations are cloud-polled or require vendor accounts. Verify the local path before buying.
6. Running multiple protocols on day one. Zigbee, Z-Wave, Thread, and Matter create four different troubleshooting domains. Start with one.
7. Using a generic smart plug for high-risk loads. A 15 A rating does not make a plug safe for space heaters or motors. Load type and manufacturer restrictions matter.
8. Ignoring firmware. The SONOFF SNZB-06P needs firmware 1.0.5 or newer for reliable presence behavior. Keep device firmware current.
9. Underestimating no-neutral switch limitations. Inovelli's no-neutral mode sacrifices power metering and high-speed fan load support. Validate wiring before buying.

Frequently Asked Questions

Conclusion

The smart home devices worth building around are the ones that keep working when the cloud doesn't. Home Assistant Green, a dedicated ZBT-2 Zigbee radio, one mains-powered router, and a handful of open-protocol sensors and bulbs give you a system with no subscription and no mandatory manufacturer cloud—just a local path from sensor to action.

The build order matters: controller first, radio second, router third, then sensors, then lighting. This sequencing prevents the two most common failures—buying Zigbee devices with no way to pair them, and scattering battery sensors across a mesh with no powered backbone. Add mmWave presence, Z-Wave, and advanced switches only when a specific gap justifies the extra complexity.

If you want to go deeper, start with our Home Assistant beginner's guide, then explore Zigbee vs Z-Wave vs Matter and the Home Assistant Green vs Yellow comparison. When you're ready to buy the controller that anchors this entire architecture, check the current price on Home Assistant Green.