Smart home devices, chosen for compatibility

The feature list on the box is the part most likely to disappear. Buy for the connection underneath it.

Updated 23 October 2026 Fact-checked 7 September 2026 Editorial standards5 min read

The four questions that decide every purchase#

Everything on this site's device pages comes back to these.

What is the radio? Wi-Fi, Thread, Zigbee, Z-Wave and Bluetooth behave differently under load, on batteries and during an internet outage. Which radio for which job is the framework.
Who holds the credentials? A device paired straight to your controller answers your controller. A device behind a vendor bridge answers the vendor first. That difference shows up the day the vendor's servers go away, as Wemo owners found on 31 January 2026.
What crosses the standard? Matter defines device types built from standard clusters. Anything outside those clusters, animations, gradients, maps, guest schedules, stays in the vendor app. What Matter still cannot do is the honest list.
What happens when the internet stops? Some categories keep working locally, some do not. The outage table is device by device.

Category by category#

Category	Usually the right radio	What the standard carries	Where it falls down
Lighting	Zigbee or Thread for bulbs, Zigbee, Z-Wave or Thread for switches	On, off, brightness, color temperature, one solid color	Gradients, per-zone effects, dynamic scenes, sync modes
Switches and dimmers	Z-Wave at 908.42 MHz, or Thread	On, off, level, and usually the scene button as a generic switch	Multi-tap gestures and LED bar behavior, which are vendor-defined
Plugs	Wi-Fi is acceptable here, Thread is better	On, off, plus power and energy measurement on newer devices	Few controllers display the measurement, and inrush loads break relays
Sensors	Thread or Zigbee, both battery friendly	Motion, contact, temperature, humidity, leak, air quality, smoke and CO	Reporting intervals, composed devices split apart, no keypad or panel type
Locks	Z-Wave or Thread	Lock, unlock, state, battery, and PIN credentials where the controller implements them	Controller support for codes and schedules varies hugely, and fingerprint enrollment never crosses

Wi-Fi is not disqualifying, but it is the wrong default. It costs airtime on the band your phone shares, it will not run on a coin cell, and it puts every device on the same failure domain as your router. The hidden costs of Wi-Fi devices covers the tradeoff, and Thread versus Wi-Fi covers when Wi-Fi is genuinely the better answer.

Where the standard is strong, and where it is thin#

Matter covers the boring parts of a home well. Lights, plugs, switches, contact and motion sensors, thermostats and locks all have mature device types, and a certified product in one of those categories will work in most platforms on day one.

It gets thin fast at the edges. Security and alarm panels, keypads and sirens have no device type at all, and neither does presence or mmWave detection, so radar sensors show up as plain occupancy sensors with a single yes-or-no bit. Vendor lighting effects reduce to a solid color. Robot vacuum maps do not exist in the data model. And support lags the specification by a long way: ecosystems typically take six to twelve months to implement a new release, and the Matter feature gap tracker shows how far behind the major controllers actually run.

Buy through a bridge or buy direct?#

Bridging is how Zigbee, Z-Wave and cloud gear reaches a modern controller, and it is the right call for hardware you already own. It is the wrong call for hardware you are buying now, because bridges drop features: no firmware updates for bridged devices, no vendor scenes, and endpoint numbers that are not reused, so a re-paired device often comes back as a brand new accessory with its automations gone.

If you are starting from nothing, your first five devices puts them in an order that avoids most of this.

Everything in this cluster#

Before you check out#

Run the compatibility checker for a device class and platform combination, and the outage audit if local control is the point. If you are choosing a platform too, do that first: the seven platforms compared narrows the hardware list more than any device review will.

Should I buy Matter devices or stick with Zigbee and Z-Wave?

Both, deliberately. Matter is the safest choice for devices you want to share across ecosystems, because multi-admin lets one device answer several controllers. Zigbee and Z-Wave remain better for large fleets of battery sensors and for locks, because the tooling is mature and the mesh behavior is well understood. Mixing them is normal and works fine through a hub.

Do I need a hub to use smart home devices?

Only for some. Wi-Fi devices and Matter over Wi-Fi need no hub. Thread devices need a border router, Zigbee and Z-Wave need a coordinator, and running automations during an internet outage needs something local to store them. Do you need a hub walks the decision.

Why do features disappear when I add a device to Apple Home or Alexa?

Because the controller only understands standard clusters. Anything the manufacturer invented, an animation engine, a gradient, a guest schedule, has nowhere to live in the standard data model, so the controller shows a reduced version. The vendor app keeps the full feature set, which is why you rarely get to delete it.

What is the single most common buying mistake?

Buying on the app screenshot. The app is the part the manufacturer controls and can change, and it is the part that stops working when a company shuts down. The radio and the certification are what you are actually buying.

Primary sources

Specification and vendor documentation we checked while writing this page. Where a claim depends on firmware behaviour rather than a published spec, the page says so inline.