AliExpress for Home Assistant: Finding Devices That Actually Work

I run 72 Zigbee devices through Home Assistant, almost all of them bought on AliExpress and almost all of them cheap. This guide is the reasoning behind those choices — what to check on any "smart" listing before assuming it will integrate, which sensor people waste money on first, and the handful of automations that turned out to be worth building.

None of it is theoretical. Every device mentioned is on our roundup, running in this house.

Check the protocol first

Before anything else, look for Zigbee 3.0, Matter, or Wi-Fi with a documented local API stated explicitly in the listing title or specs. Zigbee devices talk to a hub over a low-power mesh network and generally don't need internet access to keep working once paired — this is why they show up so often in Home Assistant setups specifically, ours included. Matter is newer and increasingly well-supported. Plain Wi-Fi devices can work too, but only if the manufacturer actually exposes local control rather than routing everything through their own cloud.

Spotting a cloud-locked device

The warning sign is a listing that only mentions a proprietary app name — "works with [Brand] App" — with no protocol named anywhere in the title, images, or specs. That's usually a device that depends on the manufacturer's own servers to function at all, which means it either won't integrate with Home Assistant cleanly or will require a workaround with no guarantee it keeps working after a firmware update. A listing that's genuinely Home Assistant-friendly usually says so, or at minimum names the actual radio protocol rather than just the app.

What reviews actually tell you

Reviews that specifically name Home Assistant, Zigbee2MQTT, or ZHA are a real positive signal — a reviewer wouldn't invent that level of detail, so it's a genuine data point about compatibility. Generic praise for "the app is easy to use" tells you nothing about local integration and shouldn't be read as confirmation either way; plenty of cloud-locked devices have perfectly pleasant apps.

Categories that tend to work well

Zigbee sensors — smoke detectors, motion sensors, door/window contacts, temperature/humidity — are consistently among the safer categories, since the protocol itself doesn't allow much room for a vendor to lock things down the way a Wi-Fi app-based device can. Smart plugs and lighting are a mixed bag: Zigbee versions tend to integrate cleanly, while Wi-Fi versions vary a lot by brand. When in doubt, a Zigbee listing beats a Wi-Fi one for Home Assistant purposes, all else being equal.

Motion vs presence — the expensive mistake

This is the one I'd warn a beginner about before anything else, because almost everyone buys the wrong one first and then concludes that automated lighting doesn't work.

A PIR motion sensor detects movement — a change in infrared across its field. Sit still at a desk, or lie still in a bath, and once its timeout expires the sensor reports an empty room and the lights go out. That isn't a fault; it's what the sensor measures. A mmWave presence sensor uses 24GHz radar to detect that a body is there, moving or not, and holds the room occupied while you sit perfectly still.

The rule: PIR wherever movement is a safe assumption, mmWave wherever people sit still. I use PIR in the bathrooms — nobody stands motionless in a bathroom — and mmWave in the office and on the porch, where the entire point is detecting someone who isn't moving. PIR is also cheaper and lasts far longer on a battery, so it isn't simply the worse product; it's the wrong product in roughly a third of the places people fit it.

One practical caveat on mmWave: it reads through thin partitions and will cheerfully detect someone in the next room if you aim it carelessly. Tune sensitivity and range once, at install, rather than trusting the defaults to suit your room.

Five automations worth copying

Cheap sensors are only worth owning if something acts on them. These are the ones in my own setup that have earned their place — each a few dollars of hardware doing a job worth considerably more.

1. Rain closes the blinds — gated on presence

When a rain sensor reports sustained rain, Home Assistant closes all the blinds. The important part isn't the trigger, it's the gate: the automation is blocked while the presence sensor on the upstairs porch says someone is out there, because closing a blind on a second-floor porch with a person standing on it locks them outside in the rain. That gate is the difference between an automation you trust and one you switch off after it embarrasses you once. Anything that acts on the physical world needs the same question asked of it — what happens if this fires at the wrong moment?

2. Two rain sensors, not one

Both the blinds and the irrigation depend on knowing whether it's raining, so I run two rain sensors from different sellers into the same logic. A sensor that dies doesn't announce itself — it silently stops reporting rain, and you find out during the first real downpour. Under ten dollars each, redundancy is cheaper than one wet floor. This matters more here than elsewhere: one of my two listings has since vanished from AliExpress entirely, so buying the second at the time turned out to be the only chance I got.

3. Irrigation that skips the rain

A Zigbee water valve runs the drip irrigation on a schedule, and the same rain sensor tells it to skip the cycle. A mechanical timer can't do this — it waters the garden mid-downpour and empties the tank. It's the clearest illustration of why a valve that can be told something beats a timer that can only count.

4. Laundry notifications from a power threshold

The washing machine and the dryer each sit on a power-monitoring plug. When the draw falls below a threshold and stays there, Home Assistant decides the cycle has finished and sends a notification. No appliance integration, no smart washing machine required — just wattage and a little patience. It also happens to prove the plug's metering is responsive, because an automation like this cannot work on readings that lag or jump around.

5. Outdoor lights on lux, never on sunset

Most people trigger outside lights on sunset time. That works until the first heavily overcast afternoon, when the garden is dark at four and the lights are still waiting for a clock — then the seasons shift and it's wrong in the other direction. An illuminance sensor outdoors reports actual brightness, so lights come on at a light level rather than a timestamp. The same reading gates the night lighting so it physically cannot fire during the day, which is the failure that makes people abandon automated lighting altogether.

And one nobody plans for

I keep a water leak sensor under every sink — five of them. For a long time they did nothing whatsoever. Then the small under-sink hot water unit — the one we use for drinks and washing up — began leaking, and the sensor beneath it caught it: we were notified while it was still a leak rather than after it had become a flood. That's the whole argument for the category. They're the cheapest insurance in the house, and they're supposed to be boring.

Start with the coordinator

Building from scratch, spend your attention here rather than on sensors. Individual devices are commodities and largely interchangeable; the coordinator decides whether a large mesh stays stable or starts dropping devices and demanding re-pairs at midnight.

Mine holds 72 devices without complaint. Get one with an external antenna, pre-flashed for ZHA or Zigbee2MQTT so Home Assistant recognises it on plug-in, and run it on a USB extension cable away from the machine — USB 3.0 ports emit interference right in the 2.4GHz band Zigbee uses, and "my mesh is flaky" is very often a dongle pushed straight into a server. Everything else on this page pairs to that one device. Get it right once and the rest of the category becomes cheap.

Frequently asked questions