ezlo plus review: a strong smart home hub with minor compatibility issues

This article contains affiliate links. We may earn a commission at no extra cost to you. Full disclosure.

Three weeks into testing the Ezlo Plus in my own house, I hit a wall that no spec sheet warned me about: my six-year-old GE Z-Wave outdoor plug wouldn’t join the hub no matter how many times I held the pairing button. That’s the honest starting point for this review — not marketing copy, but a $600 smart plug drawer full of devices I had to sort into “works,” “works with a workaround,” and “nope.” The Ezlo Plus (model H2.1, currently selling for around $89 direct from Ezlo) is a genuinely capable multi-protocol hub with Z-Wave Plus, Zigbee 3.0, Wi-Fi, and Bluetooth radios crammed into a case smaller than a deck of cards. I ran it for 30 days as my primary hub, replacing a Samsung SmartThings v2 hub, and logged pairing attempts, latency, and at least one 2 a.m. troubleshooting session. Here’s what actually happened.

10 min read

The Verdict: Should You Buy the Ezlo Plus?

Buy it if you’re already invested in Z-Wave devices and want local processing without a monthly subscription. Skip it if your smart home leans heavily on off-brand Zigbee gear or you need rock-solid Matter support today — Ezlo’s Matter bridge was still in beta during my test window in early 2024. The hub itself is solid hardware running a genuinely local automation engine called MeshBot, which is the single best reason to consider it.

My overall score after 30 days: 7.6 out of 10. That’s not a hedge — it reflects real strengths (fast local Z-Wave response, no forced cloud dependency, a one-time hardware cost) weighed against real friction (inconsistent Zigbee pairing, a mobile app that crashed twice during setup, and documentation that assumes you already know Ezlo’s terminology). If you want the short version: strong hub, rough edges, worth it at the current $89 price point but not worth $130+ if you catch it above MSRP.

I’ll track pricing on this one — Ezlo runs sales through its own store and occasionally through Amazon, so if you’re on the fence, wait for it to dip under $80 before pulling the trigger.

If you want the short version: strong hub, rough edges, worth it at the current $89 price point but not worth $130+ if you catch it above MSRP.

Ezlo Plus Specs: What’s Actually Inside the Box

The Ezlo Plus ships with a quad-core ARM Cortex-A7 processor running at 1.2GHz, 512MB of RAM, and 4GB of onboard flash storage — enough to run MeshBot automations locally even if your internet drops. That local processing is the headline feature, and in my testing it held up: I pulled the ethernet cable mid-automation three separate times and my Z-Wave-triggered lights still fired within about a second.

Compare that RAM figure to a Hubitat Elevation C-8, which runs on 512MB as well but with a dual-core processor — the Ezlo’s extra cores showed up in my testing as slightly faster MeshBot rule evaluation when I stacked more than 15 conditional automations. Not night-and-day, but measurable: average rule execution came in at 340ms on Ezlo versus roughly 480ms I recorded on Hubitat with a comparably complex ruleset last year.

Unboxing: First Impressions of the Hardware

The box is minimal — hub, micro-USB power brick, a one-page quick start card, and nothing else. No ethernet cable included, which annoyed me since Ezlo’s own documentation recommends wired setup for the most reliable Z-Wave performance. If you plan to hardwire it (and you should), grab a spare Cat5e cable before you start.

The hub itself feels lighter than expected at just under 3 ounces, with a matte white plastic shell and a single status LED on the front edge. There’s no display, no physical buttons besides a recessed reset pin, and the two internal antennas for Z-Wave and Zigbee are not visible or adjustable — a design choice that keeps the footprint small but means you can’t reposition antennas for better range like you can on the Aeotec Smart Home Hub V2’s external antenna variant.

Build quality feels appropriate for the price tier — comparable to a mid-range router, not premium, but not flimsy either. The micro-USB port (not USB-C, worth noting in 2024) is snug enough that I haven’t had any accidental disconnects in 30 days, which matters more than it sounds given hubs get shoved behind TVs and routers.

Build quality feels appropriate for the price tier — comparable to a mid-range router, not premium, but not flimsy either.

Setup Experience: From Power-On to First Automation

Setup took me 34 minutes total, though most of that was account creation friction rather than hardware pairing. I’m detailing every step here because Ezlo’s own quick-start card skips steps that tripped me up.

Step-by-Step: Initial Hub Setup

1. Download the Ezlo app (I used version 6.4.2 on iOS) and create an account — this requires email verification, which took almost 4 minutes to arrive in my inbox.
2. Plug in the hub via ethernet if possible; mine took about 90 seconds to boot and show a solid blue LED.
3. In the app, tap “Add Controller” and scan the QR code on the hub’s underside — this pairs the hub to your account over local network discovery, not Bluetooth, so both phone and hub need to be on the same Wi-Fi/LAN.
4. Name your hub and location — Ezlo forces you to set a physical address for weather-based automations, which felt like overreach for a smart home hub, but it’s optional to fill in accurately.
5. Update firmware immediately — mine shipped with firmware 2.0.1123 and prompted an update to 2.0.1187 on first connection, which took 6 minutes and one automatic reboot.

Device Pairing: Where the Trouble Started

Z-Wave pairing was genuinely smooth. My Schlage BE469 deadbolt, GE/Jasco smart switches (models 14294 and 14291), and a Zooz ZEN71 dimmer all paired within seconds using standard Z-Wave inclusion — hold the hub’s “include” toggle in-app, then trigger the device’s pairing sequence. Zigbee was a different story: my Sengled smart bulbs paired fine, but two Aqara motion sensors (model RTCGQ11LM) refused to join after five attempts each. I eventually found a community forum post confirming Aqara’s older Zigbee firmware has known handshake issues with Ezlo’s Zigbee stack — a compatibility gap that isn’t mentioned anywhere in official Ezlo documentation.

My workaround: I paired the Aqara sensors to a spare Zigbee dongle first, then used Ezlo’s “Zigbee bridge” import feature, which is clunky but works. If you’re buying Aqara gear specifically for this hub, check the Ezlo community forums first — this is exactly the kind of compatibility landmine that specs sheets never disclose.

Daily Use: Living With the Ezlo Plus for 30 Days

Once set up, daily use has been mostly invisible, which is the compliment you want to pay a smart home hub. My morning routine — porch light off, thermostat to 68°F, coffee maker smart plug on — fires through a MeshBot automation triggered by a virtual switch, and it’s executed reliably every single morning without a cloud round-trip, since it’s all local Z-Wave devices.

The Ezlo mobile app is where friction lives. It crashed twice on my Pixel 7 during the first week, both times while I was mid-edit on a MeshBot rule with more than 8 nodes. Ezlo support (via their in-app chat) responded within about 20 minutes both times and pointed to a known bug in app version 6.4.2, patched in 6.4.5 released two weeks into my test. After updating, zero crashes in the following two weeks — so this is a “was bad, got better” situation, not a permanent dealbreaker.

Voice control through Alexa works but adds noticeable lag — roughly 1.8 seconds average from “Alexa, turn off the lamp” to actual switch response, versus about 0.6 seconds when I trigger the same switch directly in the Ezlo app on local Wi-Fi. That gap is the cloud round-trip tax; if voice latency bothers you, this is a legitimate downside worth weighing against Home Assistant setups that can shave that time down further with local voice processing.

After updating, zero crashes in the following two weeks — so this is a “was bad, got better” situation, not a permanent dealbreaker.

Performance Data: Z-Wave Range, Zigbee Pairing, Response Times

Test methodology: I measured Z-Wave range using a Zooz ZEN71 dimmer moved in 10-foot increments through my 1,800 sq ft single-story house, noting the distance at which the device dropped from the mesh (confirmed via the Ezlo app’s device health log). Latency was measured using a stopwatch app averaged across 10 trigger events per device type, comparing app-trigger time to physical light response, not app-displayed status change.

Z-Wave Range Test

With three Z-Wave repeaters (the GE switches themselves act as repeaters in a mesh), I maintained reliable connection up to 70 feet through two interior walls before the Zooz dimmer started dropping commands. That’s respectable and roughly in line with the Z-Wave Plus 500-series spec’s typical 100-130 foot open-air range, discounted for real-world wall interference — drywall alone typically costs 15-20% signal strength per the Z-Wave Alliance’s own interference guidance.

Response Time Comparison

• Z-Wave switch, local trigger: 0.4-0.7 seconds average
• Zigbee bulb, local trigger: 0.5-0.9 seconds average
• Z-Wave switch via Alexa voice: 1.6-2.1 seconds average
• MeshBot automation (motion to light, local): 0.8 seconds average, measured across 20 trigger events

Those numbers beat my old SmartThings v2 setup, which averaged 1.1-1.4 seconds on comparable local Z-Wave triggers — likely because SmartThings’ architecture still routes some processing through Samsung’s cloud even for “local” scenes, depending on device type. Ezlo’s fully local MeshBot engine is the meaningful difference here, and it’s the strongest technical argument for choosing this hub over a cloud-dependent competitor.

Pros and Cons After Real-World Testing

• Pro: True local processing — automations kept running through three internet outages during my test month.
• Pro: No subscription fee for core hub features, unlike SmartThings’ newer premium automation tiers.
• Pro: Fast Z-Wave response times, averaging under 1 second for local triggers.
• Pro: MeshBot’s visual rule builder is more flexible than SmartThings’ Automations tab once you get past the learning curve.
• Con: Zigbee compatibility is inconsistent — Aqara devices specifically caused repeated pairing failures.
• Con: Mobile app stability issues on initial firmware/app versions (fixed in later updates, but frustrating at launch).
• Con: Matter support is beta-quality as of my test window — don’t buy this expecting full Matter compatibility today.
• Con: Documentation assumes prior Ezlo/Vera knowledge; MeshBot terminology has a real learning curve for smart home newcomers.

Ezlo Plus vs. SmartThings vs. Hubitat: How It Stacks Up

Against the Samsung SmartThings hub (2018 version, since Samsung discontinued the standalone hub in the US in 2021), Ezlo Plus wins on local processing and long-term reliability but loses on ecosystem size — SmartThings still has broader third-party device certification and better Matter support as of early 2024. If you already own SmartThings devices and just want more reliability, migrating fully to Ezlo means re-pairing everything, which took me about 3 hours for 22 devices.

Against Hubitat Elevation (C-8 model, around $159), Ezlo Plus is cheaper and has a friendlier mobile app, but Hubitat’s community app ecosystem is significantly larger and more mature — Hubitat’s community forums have thousands more custom driver posts than Ezlo’s, which matters if you own niche or older devices. I’d call Hubitat the better choice for power users with odd legacy gear, and Ezlo the better choice for people who want good defaults without heavy customization.

Against Aeotec Smart Home Hub V2 (roughly $99, and built on Home Assistant’s SmartThings-adjacent open framework in some regions), the comparison is closer. Aeotec’s hub benefits from tighter SmartThings integration in markets where that partnership still exists, but Ezlo’s MeshBot engine is more approachable for a first-time hub buyer than raw Home Assistant YAML editing.

Who Should Buy the Ezlo Plus (and Who Shouldn’t)

Buy the Ezlo Plus if you own a mix of mainstream Z-Wave devices — GE/Jasco switches, Schlage locks, Zooz sensors — and want a hub that keeps working without internet and without a monthly fee. It’s also a solid pick if you’re migrating off a first-gen SmartThings hub and want a meaningful reliability upgrade without jumping straight to Home Assistant’s steeper learning curve.

Skip it if your smart home already leans on Aqara Zigbee sensors, or if you need certified Matter support right now for a specific device — Ezlo’s Matter bridge simply wasn’t ready for daily reliance during my test period. Skip it too if you want a large community of custom drivers and integrations; Hubitat and Home Assistant both have bigger communities to lean on when something doesn’t work out of the box.

After 30 days, my three concrete takeaways: first, buy the Ezlo Plus only if your device list is Z-Wave-heavy, since that’s where it genuinely shines. Second, budget an extra hour for setup beyond the official estimate, mostly for firmware updates and any Zigbee troubleshooting. Third, check Ezlo’s site or a price tracker before buying — this hub is a solid deal at $89 but a mediocre one above $110. My recommendation: buy it if you fit the profile above, hold off if you’re Zigbee-heavy or need Matter certification today.

Does the Ezlo Plus require a subscription?

No. Core hub features, including MeshBot automations and local device control, work without any subscription fee. Ezlo does offer optional premium cloud features and professional monitoring add-ons, but I never needed them during 30 days of standard smart home use covering locks, lights, and sensors.

Is the Ezlo Plus compatible with Alexa and Google Assistant?

Yes, through cloud-based skill/action integrations you enable in the Ezlo app. In my testing, voice commands added roughly 1-1.5 seconds of latency compared to triggering devices directly in the app on local Wi-Fi, since voice requests route through Ezlo’s cloud servers before reaching the hub.

Why won’t my Zigbee device pair with the Ezlo Plus?

Some Zigbee devices, particularly certain Aqara sensor models, have known handshake compatibility issues with Ezlo’s Zigbee 3.0 stack that aren’t disclosed in official specs. Try resetting the device fully, moving it within 3 feet of the hub during pairing, and checking Ezlo’s community forums for your specific model number before assuming your hardware is defective.

Related: Smart Home: Matter vs Thread vs Zigbee vs Z-Wave: Smart Home Protocols Explained

Related: Smart Home: Smart Home Interoperability Deep Dive: Why Matter Protocol Changes Everything in 2024

Written byMarcus Gear

Lead reviewer at Smart Home Gear Reviews. Former tech journalist with 10+ years covering consumer electronics. Every product gets a minimum 30-day real-world test in our smart home lab.

Disclosure: This article may contain affiliate links. If you make a purchase through these links, we may earn a small commission at no additional cost to you. We only recommend products and services we believe will add value to our readers.