Quick answer

Buy the protocol you already have a radio for. With a Zigbee coordinator running ZHA or Zigbee2MQTT, the Sonoff SNZB-04P is a Zigbee 3.0 contact sensor on a CR2477 battery. With a Z-Wave stick, the Aeotec Door/Window Sensor 7. With a Thread border router, the Aqara P2 or Eve Door & Window. Do not mix up the radio: an Aqara sensor is not automatically Zigbee.

Contents

At a glance

Class
Homelab

Provenance

  • Nov 18, 2026Published

Pick the protocol your Home Assistant machine already has a radio for, then buy a sensor in that protocol. The radio and the software behind it are the commitment; the sensor is the easier part to swap later.

You already runWhat Home Assistant needsA sensor to look at
A Zigbee coordinator (ZHA or Zigbee2MQTT)Nothing more with ZHA; an MQTT broker with Zigbee2MQTTSonoff SNZB-04P
A Z-Wave adapter with the Z-Wave JS appNothing moreAeotec Door/Window Sensor 7
A Thread border router and the Matter Server appNothing moreAqara P2 or Eve Door & Window
A Bluetooth adapter or ESPHome proxyNothing moreShelly BLU Door/Window ZB
None of theseA coordinator firstSee the ZBT-2 guide, then a Zigbee sensor

If you have no radio yet, Home Assistant’s ZHA page says the Home Assistant Connect ZBT-2 is the recommended coordinator for a first Zigbee network, and the ZBT-2 page covers what it can and cannot do. That makes a Zigbee sensor the lowest-friction start. I am not claiming Zigbee is the best protocol; Home Assistant’s documentation does not rank them.

What each protocol needs on the Home Assistant side

Zigbee. Home Assistant’s ZHA page describes the integration as a hardware-independent Zigbee gateway that works through a Zigbee coordinator. The other route is Zigbee2MQTT, whose getting-started page lists a Zigbee adapter, a host system and an MQTT broker (Mosquitto is the one it recommends); Home Assistant’s MQTT integration then connects to that broker. ZHA tells you to use a USB extension cable and a USB 2.0 port, and to keep the adapter away from USB 3.0 devices, which it calls known sources of interference. My Zigbee and Z-Wave tutorial walks through the setup.

Z-Wave. Home Assistant’s Z-Wave JS page lists four parts: a Z-Wave adapter, a Z-Wave server (the Z-Wave JS app, which it notes was formerly called an add-on), the integration and the end devices. It supports 500, 700 and 800 series adapters and recommends an 800 series adapter with firmware 7.23.2 or newer if you are starting out. The adapter has a radio frequency region, and the page says it can talk to devices specified for that region, so match the sensor’s region to the adapter’s.

Thread and Matter. Home Assistant’s Matter page says the integration runs its own Matter controller as the Matter Server app, that running it on Home Assistant OS is the supported option, and that adding a device uses your phone’s Bluetooth connection during commissioning. For Thread devices it requires a Thread border router: a Nest Hub (2nd gen), Nest Wi-Fi Pro, HomePod mini, Apple TV 4K, or Home Assistant with the OpenThread Border Router app on a radio such as the Connect ZBT-2. The Thread page says Home Assistant can act as a border router using the Thread radio of Yellow, ZBT-1, ZBT-2 or another compatible radio. The ZBT-2 page, drawing on Nabu Casa’s documentation, says that one stick runs Zigbee or Thread but not both at once.

Bluetooth. Home Assistant’s Bluetooth integration supports Bluetooth Low Energy devices and not Bluetooth Classic. On Linux it needs D-Bus access and BlueZ 5.43 or newer (it recommends 5.63 or newer); Home Assistant OS 9.0 or later configures this for you. On a Container install, the docs say that without the NET_ADMIN and NET_RAW capabilities Bluetooth runs in a degraded mode with raw advertising data missing, “causing unreliable updates”. Range is extended with ESPHome Bluetooth proxies, which the ESPHome page says Home Assistant aggregates with any USB adapters you have. Bluetooth sensors that broadcast in the BTHome format are discovered by the BTHome integration once Bluetooth works.

Wi-Fi. There is no single Wi-Fi path; each brand has its own integration. The one example I read, the Shelly integration page, says first-generation Shelly devices push updates over a protocol called CoIoT and that setting the CoIoT peer to your Home Assistant address and port 5683 is “mandatory for battery operated devices”. I am not recommending a Wi-Fi contact sensor on this page, because I did not find a current manufacturer page and Home Assistant page pair for one that I could stand behind.

If your Home Assistant box lives in a rack or a VM, the mini PC guide and the Proxmox guide cover where the radio can physically sit.

Batteries and how they report

ZHA’s documentation calls battery door sensors sleepy sensors that only report when triggered, which is why availability settings matter.

  • ZHA has a global option, at Settings > Connectivity > Zigbee > Options, that marks battery-powered devices unavailable after a period with no activity. The default is 6 hours (21,600 seconds), and the docs say to raise it for sleepy sensors such as door sensors that only report when triggered.
  • Zigbee2MQTT has an availability feature that is off by default. When on, it expects battery-powered (“passive”) devices to check in every 25 hours by default and marks them offline if they do not.
  • Z-Wave: Aeotec’s guide says its sensor sends open, close and tamper changes as notification reports, and warns that if the cover is left open the sensor stays permanently awake.
  • Bluetooth sensors broadcast. Shelly’s page describes a regular mode that broadcasts on each open or close and a beacon mode that broadcasts every 30 seconds, and says battery life may be significantly reduced in beacon mode.

Each manufacturer’s battery-life figure is theirs, under their own conditions, and I give those conditions below. I did not measure any.

Five sensors, each from its maker’s pages

Sonoff SNZB-04P (Zigbee)

Sonoff describes it as a Zigbee 3.0 door/window contact sensor with tamper protection and a CR2477 (3 V) battery. Sonoff’s page says it works with Home Assistant through ZHA or Zigbee2MQTT and needs a coordinator dongle for that. Its claimed battery life is over 5 years, which Sonoff calls a theoretical value from internal laboratory testing at 25 C, connected to a Sonoff gateway, triggered 50 times a day. Installation gap is under 20 mm with the door closed, and Sonoff says it is for indoor use only, with an operating range of -10 to 60 C. Zigbee2MQTT’s page lists the exposed values as contact, battery_low, tamper, battery and voltage, and says the device supports OTA firmware updates.

This is the one I would start with on a Zigbee network, because Sonoff itself names both ZHA and Zigbee2MQTT and Zigbee2MQTT has a device page for it.

I may earn a commission if you buy through these affiliate links. As an Amazon Associate I earn from qualifying purchases.

Search AmazonLink checked 2026-11-17 Search NeweggLink checked 2026-11-17

Shelly BLU Door/Window ZB (Bluetooth and Zigbee)

Shelly’s page describes Bluetooth 5 LE and Zigbee 3.0 connectivity on one sensor, “with support for simultaneous Zigbee + Bluetooth operation”, plus BTHome support, a reed switch, tilt-angle measurement, a light sensor and an encrypted mode. It uses an included CR2032 battery, and Shelly lists the battery life as 5 years with no test conditions on its documentation page. Bluetooth range is “up to 10 m / 33 ft indoors and 30 m / 100 ft outdoors”, which Shelly says depends on local conditions, and its listed ambient temperature range is -20 to 40 C. Pairing is by button presses: Shelly’s page says four quick presses put it into pairing mode and five quick presses activate Zigbee pairing. Zigbee2MQTT lists it as the Shelly SBDW-103C and exposes contact, handle_position, battery_low, battery, light_level and the dark and bright thresholds, with a note that Shelly devices should be updated over Wi-Fi or Bluetooth until they gain OTA over Zigbee.

Two cautions. The earlier Shelly BLU Door/Window is listed by Shelly as discontinued, with this ZB model as the recommended successor, so do not buy the old one. Shelly’s US store lists the ZB model, so it is sold in the US. Home Assistant’s Shelly page says Shelly BLU series devices are not supported by the Shelly integration and should use the BTHome integration, which covers the Bluetooth side; the Zigbee side goes through ZHA or Zigbee2MQTT.

Search AmazonLink checked 2026-11-17 Search NeweggLink checked 2026-11-17

Aeotec Door/Window Sensor 7 (Z-Wave)

Aeotec describes it as a Z-Wave Plus sensor with S2 security and SmartStart, magnetic detection only, a tamper switch, and two magnets in the box. It is IP20 and meant for dry indoor locations, with an operating range of -20 to 45 C. It does not act as a repeater. Aeotec’s battery life figure is 3 years assuming 5 open and 5 close events a day with wake-up reports disabled.

The details that bite: Aeotec’s spec page lists the battery by model number. The ZWA011-A, -B and -C use a 1/2 AA ER14250 3.6 V cell, and the -02 revisions use “CR14250 or CR2 3.0V”; Aeotec’s guide says the wrong battery will stop the sensor powering on, so check the model number printed on yours. The frequency is regional as well, 904-916 MHz for the US and 868.4-869.8 MHz for the EU, so match it to your adapter. Aeotec also sells a Pro version, which I did not read up on.

Search AmazonLink checked 2026-11-17 Search NeweggLink checked 2026-11-17

Aqara Door and Window Sensor P2 (Matter over Thread)

Aqara’s page says the P2 is Matter over Thread, uses a CR123A battery, and requires a Matter-compatible Thread border router. It lists Home Assistant Yellow among the 2-in-1 controller and border router devices it has tested. Aqara also says battery life depends on the border router and the Matter apps the sensor is connected to, and that an Aqara Hub M3 gives longer battery life in Aqara Home. The page lists tamper alarm, adjustable sensitivity and a programmable button among features coming in a future OTA update, and separately lists adjustable sensitivity and tamper alarm as Aqara Home app features with a Hub M3. I would not count on any of them in Home Assistant.

In Home Assistant it is a Matter device: Matter Server app, a border router (the OpenThread Border Router app on a ZBT-2 qualifies per Home Assistant’s Thread page), and a phone with Bluetooth to commission it.

Search AmazonLink checked 2026-11-17 Search NeweggLink checked 2026-11-17

Eve Door & Window (Matter over Thread)

Eve lists Thread as the wireless connection and a replaceable 1/2 AA ER14250 3.6 V battery, and says you need a hub with Matter controller and Thread border router functionality. Eve states there is no subscription, no registration and no Eve cloud. Some extra statistics in Eve’s own app require Apple Home, per Eve. In Home Assistant the path is the same as the Aqara P2: Matter Server app, Thread border router, phone commissioning. Eve does not publish a battery-life figure on the page I read.

Search AmazonLink checked 2026-11-17 Search NeweggLink checked 2026-11-17

Garage doors, and naming the sensor correctly

Home Assistant’s binary sensor page lists Door, Window, Garage door and Opening as separate device classes, each Open when on and Closed when off, with its own triggers such as “Garage door opened”. If a sensor lands as the wrong type you can change the class under Settings > Devices & services > Entities, then Settings and Show as. That is the software side of a garage sensor. The hardware side is the temperature range and indoor-only ratings above; none of the five pages I read describes a garage-door install.

What I would do

On a network that already has a Zigbee coordinator, I would buy the Sonoff. On a Z-Wave network, the Aeotec, after reading the model number on the box. If I were building around Thread and Matter, I would buy whichever of the Aqara P2 or Eve is easier to get, since both are Thread sensors that go in through the same Matter integration. The Shelly is the one to look at if you have Bluetooth reach and want a single sensor that speaks both Bluetooth and Zigbee. Whichever you choose, the sensor is only the trigger: the automations guide shows what to do when the door opens.

Frequently asked questions

Which protocol is best for a Home Assistant door sensor?
The one your Home Assistant machine already has a radio for. Zigbee needs a coordinator and either the ZHA integration or Zigbee2MQTT with an MQTT broker; Z-Wave needs a Z-Wave adapter plus the Z-Wave JS app and integration; Matter over Thread needs a Thread border router and the Matter Server app; Bluetooth needs a Bluetooth Low Energy adapter or an ESPHome Bluetooth proxy. Home Assistant’s documentation does not rank them, and I am not going to invent a ranking.
Does Home Assistant show a contact sensor as a door or a window?
Home Assistant’s binary sensor documentation lists door, window, garage door and opening as separate device classes, each reporting Open (on) or Closed (off). The integration that provides the sensor sets the class. If it shows up as the wrong type, for example an opening instead of a door, you can change it under Settings > Devices & services > Entities, select the sensor, open its settings and pick the type under Show as.
Can I use an Aqara door sensor with Home Assistant?
Yes, but check which Aqara sensor. Aqara’s page for the Door and Window Sensor P2 says it is Matter over Thread and requires a Matter-compatible Thread border router, so it goes in through Home Assistant’s Matter integration, not through Zigbee. Zigbee2MQTT lists the Door and window sensor P1 as the Aqara MCCGQ13LM on a CR123A battery; that is a Zigbee device.
How do I use a door sensor as a garage door sensor in Home Assistant?
Home Assistant has a Garage door device class for binary sensors, shown as Open or Closed, with its own door-opened and door-closed triggers. The hardware is the part to check: Sonoff lists the SNZB-04P as indoor only with an operating range of -10 to 60 C, and Aeotec rates its sensor IP20 for dry indoor locations at -20 to 45 C. None of the manufacturer pages I read describes a garage-door install, so confirm the range suits your garage before mounting.
Why does my battery door sensor show as unavailable?
Home Assistant’s ZHA documentation has a setting for exactly this: it marks a battery-powered device unavailable after 6 hours (21,600 seconds) with no activity, and it says to raise the value for sleepy sensors such as door sensors that only report when triggered. It is at Settings > Connectivity > Zigbee > Options. Zigbee2MQTT’s availability feature, which is off by default, expects battery-powered devices to check in every 25 hours.

Sources and corrections

Last updated
Methodology
See our methodology for research and review standards. It draws on 24 cited sources, listed below, each checked against the original page on 2026-11-17. I did not test any of these sensors for this page, and no measurement here is mine. On 2026-11-17 I read Home Assistant’s own integration documentation (ZHA, Z-Wave JS, Matter, Thread, Bluetooth, BTHome, MQTT, Shelly and the binary sensor building block), the Zigbee2MQTT getting-started, availability and device pages, ESPHome’s Bluetooth proxy page, and each manufacturer’s product, specification or user-guide page. Every battery figure is the manufacturer’s own, with the test conditions where the manufacturer gave them. sonoff.tech and shelly.com rate-limit automated fetches, so their pages were read in several passes. The Sonoff SNZB-04P product page, the older Shelly BLU Door/Window product page (listed as discontinued, with the ZB model as its recommended successor) and Shelly’s documentation page for the ZB model were all read live on 2026-11-17 and match this page; I use only specifications from them and no prices or stock. The ZB model’s own product page was rate-limited when I tried it, so its specifications here come from Shelly’s documentation page, and Shelly’s US store (us.shelly.com) lists the model. The choice of five sensors and the buying advice are my judgment from those documents.
Sources
Corrections
Spotted an error? Email a correction with the affected line and what you found. The draft includes this page’s address. Verified changes are recorded here. Contact details.

About the author

I am Lowell K. Wood IV. I research, write and maintain everything on TechFuelHQ from St. Louis County, Missouri.