HomeKit Compatible Devices: The Full 2026 List

“HomeKit compatible” means one of four different things, and the box rarely tells you which one you’re getting. A device either pairs straight into Apple Home with no extra hardware (native), needs a physical bridge to translate its real protocol into something HomeKit understands, joins over Matter (Apple’s newer, cross-platform standard), or has no official path in at all – any “compatibility” you’ve read online for that last group is an unofficial workaround. The table below runs every major smart home brand through those four buckets, verdict by verdict; the sections after it explain why the categories exist and why buying the wrong one gets you a device that only half-works.

  • Native HomeKit: pairs directly with the Home app, no hub required, using Apple’s own HAP protocol.
  • Works via a bridge or hub: needs a piece of hardware in the middle translating Zigbee, Z-Wave, or a cloud API into something HomeKit can read.
  • Works via Matter: joins Apple Home directly over the newer universal protocol, usually over Wi-Fi or Thread, no vendor-specific bridge needed.
  • Not compatible: no official path in. The only route is an unofficial project like Homebridge, running on hardware you provide yourself.

HomeKit Compatible Devices: The Full List (2026)

Verdicts below are current as of mid-2026 and checked against each brand’s own current support pages, not just the box copy. Where a brand’s status changed recently, we’ve noted it.

BrandCategoryVerdictDetails
Philips HueLightingWorks via a bridgeHue Bridge v2 or Bridge Pro required. The Bridge also exposes bulbs as Matter accessories since a 2024 firmware update.
GoveeLighting & plugsWorks via Matter (select models)Only specific SKUs (M1 strip, Floor Lamp 3, Smart Plug Pro, and a handful of others) ship with the Matter chip. Everything else needs Homebridge.
LIFXLightingNative HomeKitPairs directly, no hub. Current bulbs also support Matter over Thread.
SengledLightingBridge or Matter (model-dependent)Older Zigbee bulbs need the Sengled Hub E39-G8C. Newer Matter-enabled bulbs skip the hub entirely.
Feit ElectricLightingNative HomeKit (HK models only)Only bulbs with “/HK” in the model number are HomeKit-certified. Standard Feit Smart Wi-Fi bulbs are not.
C by GE (now Cync)LightingNot compatibleC by GE was discontinued and rebranded Cync in 2021. Cync now supports Matter, but only on products designed for it since 2023 – no retroactive support for older bulbs.
LevitonSwitchesNative HomeKitDecora Smart Wi-Fi 2nd Gen switches and dimmers pair directly, no bridge.
Lutron CasetaSwitchesWorks via a bridgeNeeds a 2nd-generation Smart Hub (model number contains a “2”). First-gen bridges do not support HomeKit.
Kasa (TP-Link)Switches & plugsWorks via Matter (select models)Matter-certified Kasa devices pair directly into Apple Home. Older Kasa hardware needs Homebridge.
Amazon Smart PlugsPlugsWorks via Matter (specific SKU only)The Matter-certified Amazon Basics Smart Plug works in Apple Home. The original Amazon Smart Plug does not and has no Matter path.
iottySwitchesNot compatibleWorks with Alexa and Google Home out of the box. HomeKit requires Homebridge as middleware.
Google NestThermostats & camerasWorks via Matter (limited)Only the current Nest Learning Thermostat and Nest Temperature Sensor connect to Apple Home over Matter, and only for basic temperature control. Nest cameras and speakers still do not connect.
RingSecurityNot compatibleAmazon-owned. No Matter certification on any Ring device as of mid-2026, no announced timeline.
ArloCamerasNative HomeKit (no Secure Video)Full Home app control, Siri, and motion alerts – but no HomeKit Secure Video. Recordings stay in Arlo’s own cloud.
EufyCameras & locksWorks via a bridgeHomeBase 2 or 3 required, and only on specific camera models (Indoor Cam 2K/Pan&Tilt, eufyCam 2/2C/2 Pro, eufyCam S3 Pro) plus the E30/E31/C34 smart locks.
WyzeCamerasNot compatibleNever added HomeKit despite years of user requests. Alexa and Google Assistant only.
BlinkCamerasNot compatibleAmazon-owned, same story as Ring.
SimpliSafeSecurityNot compatibleNo HomeKit or Matter support, and none announced.
ADTSecurityNot compatibleNo official integration through any ADT hardware.
VivintSecurityNot compatibleNo HomeKit certification, no stated plans.
SonosSpeakersNot compatibleUses AirPlay 2 instead, which covers audio streaming but doesn’t put a Sonos tile in the Home app.
Ecobee3 LiteThermostatsNative HomeKitFull Siri, scenes, and automation support since launch.
Honeywell T9ThermostatsNative HomeKitAdded via a firmware update in late 2021. Needs current firmware to work.
AugustLocksNative HomeKitWi-Fi Smart Lock 4th Gen works with no extra hardware. The older Smart Lock Pro needs the August Connect bridge for remote access.
SmartThingsHub platformWorks via Matter (shared, not native)No direct SmartThings-to-HomeKit integration. A Matter device paired to SmartThings can be shared into Apple Home as a second controller.
Harmony HubRemote/hubNot compatible (discontinued)Logitech killed the entire product line in April 2021. Existing units still work if you already own one.
eeroRouterNative HomeKit (network only)Select eero models act as a HomeKit Secure Router, managing network-level security for your other HomeKit gear. The router itself isn’t a lightswitch-style accessory.
Smart Life (Tuya)MultipleNot compatibleRuns on Tuya’s cloud platform, which has never pursued Apple’s MFi certification.
GeeniLighting & plugsNot compatibleSame Tuya platform as Smart Life, same answer.
SomfyShades & motorsWorks via a bridgeNeeds the TaHoma Switch bridge. Without one, Somfy motors and covers are invisible to Apple Home.
iRobot (Roomba)Robot vacuumsWorks via Matter (select models)Roomba Combo 10 Max, Plus 500 Combo, Max 700 Vac, and Max 700 Combo, via the Connected Services setting. Needs iOS 18.4 or later.
DysonFansNot compatibleNo Dyson fan has ever shipped with HomeKit support.

Check current status before buying if a brand shows a model-dependent verdict above – Matter and native HomeKit support are usually gated to specific SKUs, and the non-compatible version often looks identical on the shelf.

Smart home automation control panel with connected lighting and devices

What “Native HomeKit” Really Means

Apple’s HomeKit Accessory Protocol spec documents exactly what “native” means at the byte level, and it’s stricter than most people assume. Pairing runs a modified version of Stanford’s Secure Remote Password protocol – SHA-512 in place of SRP’s original SHA-1, over the 3072-bit group specified in RFC 5054. Every session after that negotiates a fresh Curve25519 key exchange, derives a session key with HKDF-SHA-512, and encrypts traffic with ChaCha20-Poly1305. None of that touches your Wi-Fi password, a Zigbee network key, or a cloud account – it’s a closed cryptographic handshake between your iPhone and the accessory’s own chip.

That’s the bar a device has to clear to earn “Native HomeKit” in the table above. It’s also why Apple gates the whole thing behind hardware licensing (the MFi program) instead of publishing an open SDK: HAP-native means a specific chip and a specific handshake baked in at the factory, not a firmware toggle a vendor can flip after the fact. That’s the same reason a Feit bulb without “/HK” in the model number can’t just get a software update that makes it HomeKit-native – the silicon and the pairing keys aren’t there.

The Bridge Path: Translating a Foreign Protocol

A lot of the “compatible” devices in that table aren’t HomeKit-native at all – they’re Zigbee, Z-Wave, or a vendor’s cloud API wearing a HomeKit costume. That’s what a bridge does: sit on your network, speak the accessory’s real protocol, and re-present it to your iPhone as though it were HAP-native the whole time. What Is A HomeKit Bridge? covers the setup mechanics in full – the short version here is that it only works because the protocol on the other side of the bridge is well-documented and bounded.

Zigbee’s own spec caps a mesh network at 15 hops deep and gives every network exactly 9 seconds to get a broadcast delivered to every listening device on it. Z-Wave’s ceiling is smaller and shaped differently: a hard limit of 232 nodes and four hops maximum, because the protocol only has an 8-bit space to assign node IDs in. A bridge has to know these limits and manage around them – which is why a cheap no-name Zigbee bridge behaves worse than a Hue Bridge even though both are nominally doing the same translation job.

Matter and Thread: The Protocol Built to Skip the Bridge

Matter exists to make the bridge unnecessary, and for a growing slice of new hardware, it has. What Is Matter? The Smart Home Standard Explained covers the bigger picture; here’s the part that explains why it’s more than marketing. The spec doesn’t leave device capacity to chance – Matter 1.4 requires every certified device to guarantee at least four Access Control Entries per fabric it supports (so a device that supports 5 fabrics needs at least 20 ACL entries), guarantee it can service a single Read request touching at least 9 paths, and support at least three simultaneous Subscribe interactions with at least 3 attribute or event paths apiece. None of that is optional – it’s a floor every certified device has to clear before it can carry the Matter logo.

What Matter doesn’t automatically hand you is Zigbee’s speed. A 2026 hardware test out of Politecnico di Milano ran identical ESP32-C6 boards on Zigbee and Matter-over-Thread side by side, in a real testbed rather than a simulation. Zigbee recovered from a dead intermediate node in 0.36 seconds on average across 30 destructive trials; Matter-over-Thread took 23.97 seconds to do the same job on the same hardware. Zigbee also held a real edge on raw single-hop latency, with round-trip times running about 30 percent lower than Thread’s. Where Matter-over-Thread won decisively was range and reliability at scale: push a Zigbee chain to five hops and only 94 of 180 test commands got through; push it to six hops and the Zigbee coordinator crashed outright, while Matter over Thread kept working under identical conditions. “Matter is just better” isn’t the honest read of that data – it’s better at surviving a large, sprawling mesh, and slower to react in a small, healthy one.

HomeKit Secure Video: The Feature Most “Compatible” Cameras Skip

“Works with Apple Home” and “works with HomeKit Secure Video” are not the same sentence – the table above lists them separately on purpose. What Is HomeKit Secure Video & How Does It Work? has the full breakdown of the feature that encrypts your camera’s recordings and stores them in iCloud instead of on the vendor’s own servers. Arlo is the clearest example of the gap in the table above: full Home app control, Siri, motion alerts, all native – and zero HomeKit Secure Video, so your clips still live in Arlo’s cloud. Eufy and the wired Hue Secure lineup support Secure Video on a narrower slice of their hardware. Ring, Blink, and Wyze skip both HomeKit and Secure Video entirely, which tends to be the outcome once a camera brand is owned by a company that also sells a competing smart speaker.

Pick the Column, Not the Logo

Stop asking whether a brand “is HomeKit compatible” like it’s a single fact printed on the box. Ask which column of the table it’s in, not what the label promises. Native devices are the safest buy, because Apple’s pairing crypto does the heavy lifting and nothing else is involved. Matter devices are the second-safest bet and getting more common by the month, but check the specific SKU – Govee, Kasa, and Amazon all sell a Matter version and a non-Matter version of a nearly identical-looking product, and the packaging doesn’t always make the difference obvious.

Bridge-dependent gear is fine as long as you genuinely want the bridge – a Hue Bridge earns its keep across dozens of bulbs; a Somfy TaHoma Switch is a single-purpose tax you pay once for your shades. And the “not compatible” brands in that table – Ring, Blink, Wyze, Sonos, most of Nest’s camera lineup – aren’t going to surprise you with a firmware update that fixes this. Amazon and Google are both competing with Apple for the same living room. That fight isn’t ending because you’d like your doorbell in the Home app.

HomeKit Compatibility FAQ

What does “HomeKit compatible” mean, exactly?

It means one of four things: the device pairs natively with no extra hardware, it needs a bridge or hub to translate its real protocol, it joins over Matter, or there’s no official path in at all and any workaround is unofficial. Check which one applies before buying – the label alone doesn’t tell you.

Is Matter the same thing as HomeKit?

No. Matter is a separate, newer standard that Apple Home, Google Home, Amazon Alexa, and Samsung SmartThings all speak. HomeKit is Apple’s own, older, Apple-only protocol. A Matter device will work inside the Apple Home app, but that doesn’t make it “HomeKit” in the original sense – it’s Matter running through Apple’s front end.

Do I need an Apple TV or HomePod for HomeKit to work?

Only for remote access and scheduled automations. Local control on the same Wi-Fi network doesn’t require a hub, but you can’t run scenes on a timer or reach your devices from outside the house without one.

Can I add a “not compatible” device to Apple Home anyway?

Only through an unofficial bridge like Homebridge, running on hardware you provide and maintain yourself – a Raspberry Pi, a spare Mac, a NAS. There’s no official support from Apple or the device vendor if it breaks, and a cloud API change on the vendor’s side can silently stop it working.

Why do some brands only support HomeKit or Matter on certain models?

Native HomeKit and Matter support are usually gated by hardware – a specific chip and secure element have to be present from the factory. A firmware update can add software features, but it can’t retroactively install a radio or a cryptographic element that was never built into the device.