Four Aeotec product boxes on a light surface: Z-Stick 10 Pro, Z-Stick 7, Z-Pi 7 and TriSensor 8

Z-Wave in Home Assistant: Set Up Aeotec Z-Stick 10 Pro, TriSensor 8 & Z-Pi 7

This article is for anyone already running Home Assistant who wants to extend their network with Z-Wave devices – whether via USB stick or GPIO module. Want to bring sensors, switches, and actuators into Home Assistant reliably and without cloud lock-in? Z-Wave has been one of the most robust options for years: an encrypted mesh radio network, a huge device ecosystem built on the open Z-Wave Alliance standard, and control that runs entirely locally on your Raspberry Pi – no manufacturer cloud or app lock-in required. In this article we test four Z-Wave components from Aeotec: the USB controller Z-Stick 10 Pro (Z-Wave and Zigbee in one stick), the simpler Z-Stick 7, the GPIO controller Z-Pi 7 for anyone who doesn’t want to (or can’t) give up a USB port, and the 3-in-1 sensor TriSensor 8 for pairing. We’ll show you step by step how to get the Z-Stick 10 Pro running, set up Z-Wave JS in Home Assistant, and pair your first sensor – plus a look at the GPIO alternative for purists.

Last updated on July 4, 2026.

What is Z-Wave?

Z-Wave is a radio standard for smart home devices developed in 2001 that operates at 868 MHz in Europe and forms a self-healing mesh network – every mains-powered device relays the signal to its neighbors, significantly extending range. Unlike many cloud-based systems, control in Home Assistant via Z-Wave JS runs entirely locally, with no manufacturer account required. A Z-Wave network always needs a controller (USB stick or GPIO module) as its hub. Which devices are specifically compatible with Z-Wave JS can be looked up in the official Z-Wave JS device database.

The short version
  • A simple USB stick (Z-Stick 10 Pro or Z-Stick 7) is enough as a controller – if you don’t want to give up a USB port, use the GPIO module Z-Pi 7 instead.
  • Home Assistant uses the official “Z-Wave JS” app, not the phased-out “Z-Wave JS UI”.
  • With automatic setup, a single wizard installs the app and the integration together – with manual setup, you’ll need to add the integration separately afterward.
  • Once the controller is running, sensors like the TriSensor 8 pair within minutes and are immediately usable in automations – even alongside devices from other systems like Homematic IP.

The Z-Stick 10 Pro, Z-Stick 7, Z-Pi 7, and TriSensor 8 were kindly provided to us free of charge by Aeotec.

Z-Wave vs. Zigbee: The Key Differences

Z-Wave and Zigbee are the two most established radio standards for mesh-based smart home devices – Home Assistant supports both natively, and the Z-Stick 10 Pro in this test even covers both at once. Before we get into setup, here’s a quick rundown of the key differences so you can judge where the two standards diverge.

FeatureZ-WaveZigbee
Frequency band868 MHz (EU, sub-GHz)2.4 GHz (uniform worldwide)
InterferenceLow – the frequency band is barely used by other devicesShares the band with Wi-Fi and Bluetooth, making it potentially more interference-prone
Range per hop (indoor)approx. 30–100 m, good wall penetration thanks to sub-GHzapprox. 10–20 m
Max. hops in mesh4 (Z-Wave Plus/classic)practically unlimited
Data rateup to 100 kbit/sup to 250 kbit/s
Long Range variantZ-Wave LR: star topology instead of mesh, up to 4,000 nodes, several kilometers of range at high transmit powerno direct equivalent, still relies on classic mesh
Device interoperabilityStrictly, centrally certified – Z-Wave devices from different brands are, by specification, generally compatibleOpen standard with many profiles – cross-brand compatibility depends on implementation
Region setting requiredYes – EU, US, and AU use different frequenciesNo – 2.4 GHz is identical worldwide
Home Assistant integrationZ-Wave JSZHA (native) or Zigbee2MQTT
Device ecosystemSmaller, but consistent (Aeotec, Fibaro, Danfoss, Qubino …)Larger and cheaper (Philips Hue, IKEA, Aqara, Sonoff …)

When to Use Z-Wave, When to Use Zigbee?

Z-Wave plays to its strengths in larger homes with lots of walls, where better sub-GHz penetration and lower interference tip the scales – and where guaranteed cross-brand interoperability matters to you. Zigbee pays off if you want access to a larger, generally cheaper device selection, or if you already have Zigbee devices in use (e.g., from Philips Hue or IKEA). With the Z-Stick 10 Pro, you don’t have to commit either way: it covers both networks in parallel over a single USB stick.

Aeotec Z-Wave Test Kit at a Glance

We ran this setup with these four Aeotec components – a controller of your choice (USB stick or GPIO module) plus a sample sensor to pair.

DeviceModelTypeFunctionManufacturer page
Z-Stick 10 Pro*ZWA060 (EU: ZWA060-C, US: ZWA060-A)USB stickDual controller Z-Wave + Zigbee, 800 seriesManufacturer page
Z-Stick 7*ZWA010USB stickZ-Wave controller, 700 seriesManufacturer page
Z-Pi 7*ZWA025GPIO HATZ-Wave controller directly on the Raspberry PiManufacturer page
TriSensor 8*ZWA045Battery sensorMotion, light, temperature (3-in-1)Manufacturer page
Links marked with * are affiliate links, which makes them advertising. If you buy through one, I earn a commission at no extra cost to you. As an Amazon Associate I earn from qualifying purchases. Learn more
Aeotec Z-Stick 7, Z-Stick 10 Pro, and Raspberry Pi
Aeotec Z-Pi 7, Z-Stick 7, and Z-Stick 10 Pro

Z-Wave Controllers Compared

With the Z-Stick 10 Pro, Z-Stick 7, and Z-Pi 7, Aeotec offers three different ways to connect Z-Wave to your Raspberry Pi. For most people, a USB stick is the easiest way in; if you don’t want to give up a USB port, go with the GPIO module Z-Pi 7. Aeotec has since discontinued the Z-Stick 7 and Z-Pi 7, so any you find in shops is leftover stock.

ControllerConnectionProtocolsSeriesNotable feature
Z-Stick 10 ProUSBZ-Wave + Zigbee800Two radio chips in one stick, Long Range capable, plug & play
Z-Stick 7USBZ-Wave700Simplest setup, plug & play
Z-Pi 7GPIO (Pi 3/4/5)Z-Wave700No USB port used, but conflicts with Bluetooth (UART), manual setup
  • Z-Stick 10 Pro (800 series): The most current chipset in this test, including the latest-generation S2 security and support for Z-Wave Long Range – on top of classic mesh operation, it can also be used in a star topology with significantly greater range. The only controller in this test with a second, independent Zigbee radio chip. The most expensive, but also the most future-proof controller.
  • Z-Stick 7 (700 series): The previous chipset generation, Z-Wave only, no Long Range. Setup works almost identically to the Z-Stick 10 Pro – just without the port selection between two radio chips. An option if you only need Z-Wave and can still find one.
  • Z-Pi 7 (700 series, GPIO): Technically on par with the Z-Stick 7, but doesn’t use a USB port – in exchange, it has a UART/Bluetooth conflict and isn’t automatically detected by Home Assistant (details in the “For Pi purists” section further below). That makes it the controller with the most setup effort in this test.

For our main walkthrough in this article, we use the Z-Stick 10 Pro: the most current 800 series, Long Range capable, and with its extra Zigbee radio chip also interesting for anyone who wants to cover both worlds down the line. If you only need Z-Wave and can still get hold of a Z-Stick 7, it works just as well – setup runs almost identically. Further below, we also show what to watch out for with the Z-Pi 7 as a GPIO alternative.

Requirements

  • A running Home Assistant instance – ideally on a Raspberry Pi, as described in our Home Assistant installation guide
  • For the USB sticks (Z-Stick 10 Pro / Z-Stick 7): a free USB port on the Raspberry Pi
  • For the Z-Pi 7: access to the microSD card or boot drive of Home Assistant OS to edit config.txt
  • For the TriSensor 8: a CR123A battery (included)

Which Z-Wave Integration / App?

There are two apps/integrations for Z-Wave: “Z-Wave JS” and “Z-Wave JS UI”. I use the “Z-Wave JS” integration.

Choosing the right Home Assistant Z-Wave integration
The Z-Wave JS app

Z-Wave JS UI (formerly Zwavejs2Mqtt) was built because the lean Z-Wave JS backend long lacked its own UI and MQTT connectivity. That UI functionality has since been merged directly into the interface (the Z-Wave panel under Settings → Connectivity → Z-Wave). The developers write: “The Z-Wave JS UI app is being phased out, as its feature-rich UI is now included in the Z-Wave JS app.” There’s an official migration script to move existing Z-Wave JS UI networks to the new app without re-pairing.

Step 1: Connect the Z-Stick 10 Pro and Set Up Z-Wave JS

I ran this setup on my Home Assistant OS (HAOS) test system, a VM running on Proxmox – that way I can test much more freely without affecting my production setup or devices. In this article, I’m covering exclusively the use of Z-Wave via the Z-Wave integration via the “Z-Wave JS” app in Home Assistant. We’ve already covered using and setting up Zigbee in our Zigbee2MQTT tutorial.

Practical tip: According to Home Assistant’s own troubleshooting documentation, most reported problems (devices won’t pair, sensor readings are off, control is delayed) are caused by radio interference right at the USB port. A short USB 2.0 extension cable between the Raspberry Pi and the Z-Stick fixes this in most cases.
Practical tip: Besides regular Home Assistant backups, you should always save your Z-Wave network’s security keys somewhere else too. Once the app starts for the first time (they’re generated automatically), you can view them under Settings → Apps → Z-Wave JS → Configuration – if you already had a Z-Wave network and are migrating it, you can also enter existing keys there.

Automatic Setup of the Z-Wave Stick

Since a few Home Assistant versions ago, initial setup of a Z-Wave controller runs through a single guided dialog – just plug in the adapter and follow the Z-Wave integration’s setup wizard, done. A manual installation is also possible, see below:

  1. Plug the Z-Stick into a free USB port on the Raspberry Pi (see the note about using a USB extension cable above)
  2. Open Settings → Devices & Services and add the “Z-Wave” integration there.
Installing the Home Assistant Z-Wave integration
Adding the Z-Wave integration
Home Assistant Z-Wave integration setup screenshot
Choosing the setup method
  1. The Z-Stick 10 Pro reports as two serial ports (one chip for Z-Wave, one for Zigbee) – in the selection dialog, choose the Z-Wave port (labeled “if01”). With a Z-Stick 7, only one device is shown.
Home Assistant Z-Wave integration setup screenshot
Selecting the Z-Wave stick
  1. Assign an area and finish with Finish. Home Assistant then interviews the entire Z-Wave network (with a freshly paired controller and no legacy devices, this goes quickly).
Home Assistant Z-Wave integration setup screenshot
Assigning the Z-Wave stick to a room
  1. Check the radio region: under Settings → Apps → Z-Wave JS → Configuration → Radio Frequency Region, Home Assistant usually sets the region automatically based on the location configured in Home Assistant. If needed, switch it manually to “Europe” or “Europe (Long Range)”. Long Range support is available on the Z-Stick 10 Pro; on the Z-Stick 7, choose “Europe” without Long Range.
Z-Wave Home Assistant setup screenshot
Setting the Z-Wave region

Now you can dive right in via the Z-Wave integration or the Z-Wave JS app (installed automatically alongside it) and start pairing devices – further below we’ll show that using the TriSensor 8 as an example, including a matching automation.

Manual Setup of the Z-Wave Stick

In some cases, depending among other things on your Home Assistant version, the Z-Wave stick may not be detected automatically – for me, for example, because my Home Assistant OS test system runs as a VM on Proxmox and the stick is passed through to the VM via USB passthrough. Running directly on a Raspberry Pi, this normally isn’t an issue, but for completeness I’ll show the manual path here too.

Only for Virtualized Home Assistant: USB Passthrough in Proxmox

If your Home Assistant OS runs as a VM (e.g., on Proxmox), the stick first needs to be passed through to the VM before Home Assistant can even see it. In Proxmox, open Hardware → Add → USB Device for the relevant VM, select “Use USB Port”, and choose the Z-Stick 10 Pro in there – it reports as “CP2105 Dual USB to UART Bridge Controller” (the chipset used to address both radio modules on the stick). Confirm with Add.

Proxmox USB passthrough dialog
USB passthrough in Proxmox: assigning the Z-Stick 10 Pro to the VM via “Use USB Port”

Manually Installing the Z-Wave JS App

In Home Assistant, continue under Settings → Apps. Click “Install app” to open the app store and search for “z-wa”. Here you’ll also immediately see the distinction described earlier in this article: under “Official apps” you’ll find Z-Wave JS – the app we’re installing – while under “Home Assistant Community Apps” you’ll find the older, phased-out Z-Wave JS UI.

App store search results showing Z-Wave JS and Z-Wave JS UI
App store search results: the official Z-Wave JS app on top, the community app Z-Wave JS UI below

On the Z-Wave JS info page, a click on Install is all it takes.

Installing the Z-Wave JS app
Installing the Z-Wave JS app

After installation, start the app via Start. I also enable “Start on boot”, “Watchdog” (automatic restart on crash), and “Show in sidebar” – after that, a new “Z-Wave” entry appears in the menu on the left.

Z-Wave menu item appears in the sidebar after starting the app
After starting the app, “Z-Wave” appears as its own menu item in the sidebar

Manually Determining the Serial Device Path

Because the stick wasn’t detected automatically, Home Assistant doesn’t yet know the right serial port – you’ll have to find it manually. Go to Settings → System → Hardware and switch to the “System Hardware” tab, then search for “tty”.

Home Assistant hardware overview showing two serial devices from the CP2105 chip
The Z-Stick 10 Pro reports as two serial devices – one CP2105 chip with two ports

Because the Z-Stick 10 Pro addresses two radio modules (Z-Wave and Zigbee) through the same CP2105 chip, you’ll see two nearly identical entries here – ttyUSB0 and ttyUSB1. The difference is the interface suffix at the end of the path:

  • …usb-Silicon_Labs_CP2105_Dual_USB_to_UART_Bridge_Controller_…-if00-port0 → Zigbee
  • …usb-Silicon_Labs_CP2105_Dual_USB_to_UART_Bridge_Controller_…-if01-port0 → Z-Wave
Practical tip: It’s best to copy the full path directly from the hardware overview rather than typing it out – the serial number in the path is device-specific and easy to mistype.

Watch out!
On some revisions of the Z-Stick 10 Pro, the Z-Wave chip may be on “if00” instead of “if01”. If one path doesn’t work, just try the other of the two serial devices.

Entering the Device Path in the Z-Wave JS Configuration

Back in the Z-Wave JS app: in the Configuration tab, use the three-dot menu at the top right to choose “Edit in YAML” – here you can also see that rf_region was already correctly set to “Europe” automatically for me.

Editing the Z-Wave JS configuration as YAML
The three-dot menu lets you edit the configuration directly as YAML

In the YAML editor, set the device value to the path you determined earlier, ending in -if01-port0 (the Z-Wave port), and save. The app generates the security keys (s0_legacy_key, s2_access_control_key, etc.) automatically on first start, so you don’t need to edit them. If you still have an old network_key from a previous install, it gets migrated to s0_legacy_key. I simply added this line:

device: /dev/serial/by-id/usb-Silicon_Labs_CP2105_Dual_USB_to_UART_Bridge_Controller_0160A613-if01-port0
Z-Wave JS YAML configuration with the device path entered
The Z-Wave port (suffix “-if01-port0”) is entered manually as the device path (security keys redacted for privacy)

After saving, start the app via Start or Restart. Startup can take a few seconds; if you entered the wrong device, the app won’t start, and the log file will show a corresponding message.

The Z-Wave JS app running
The Z-Wave JS app is running – time to check the connection in the Control Panel

Click “Open Web UI” to reach the Z-Wave JS Control Panel. If the controller shows up there as Node 001 with manufacturer “Aeotec Ltd.”, product “Z-Stick 10 Pro”, and product code “ZWA060”, the manual setup was successful.

Z-Stick 10 Pro shown as Node 001 in the Control Panel
Successfully connected: the Z-Stick 10 Pro appears as Node 001 in the Control Panel

Adding the Z-Wave Integration in Home Assistant

At this point, the Z-Wave JS app is running and the stick is visible in the Control Panel – but not a single device shows up in Home Assistant itself yet. The reason: the app and Control Panel only manage the Z-Wave network at the protocol level. For Home Assistant to turn that into actual devices and entities, it also needs the Z-Wave integration, which connects to the running app.

  1. In Home Assistant, go to Settings → Devices & Services, click Add Integration at the bottom right, and search for “z-wave”. In the results, pick the top entry “Z-Wave” (not “Z-Wave.Me” or any of the other manufacturer entries below it).
Searching for z-wave in Home Assistant integrations
When searching for “z-wave”, pick the top result “Z-Wave”
  1. In the “Set up Z-Wave” dialog, choose Recommended installation. Since the Z-Wave JS app is already running, Home Assistant detects it automatically and connects to it internally – no manual WebSocket URL needed.
Recommended installation option in the Z-Wave setup dialog
“Recommended installation” connects automatically to the already-running Z-Wave JS app
  1. Home Assistant now briefly interviews the existing Z-Wave network and then shows “Name and assign” – all nodes already paired in the Control Panel show up here, in our case the Z-Stick 10 Pro (ZWA060). Names and areas from pairing are carried over directly. Finish with Finish.
Already-paired devices are automatically taken over with name and area
Already-paired devices are taken over automatically, including name and area

After that, the Z-Wave integration is ready to use and shows all devices with their entities – from here you can pair further devices as usual, for example the TriSensor 8 in the next step.

Z-Stick 10 Pro now available as a device in Home Assistant
Done: the Z-Stick 10 Pro is now available as a device in Home Assistant
Practical tip: If a “Z-Wave” card already exists under Devices & Services but stays empty or isn’t connected, you don’t need to add a second integration. Instead, use the three-dot menu on the existing card and choose Reconfigure → Reconfigure the current adapter.

Step 2: Pairing the TriSensor 8

Pairing new devices works easiest directly through the Z-Wave JS Control Panel (reachable via “Open Web UI” in the Z-Wave JS app). There, the Nodes Manager opens a multi-step wizard for inclusion.

  1. Click the infinity icon at the bottom right of the Control Panel to open the Nodes Manager. In the “Action” tab, Inclusion (“Add a new device to the network”) is already pre-selected – confirm with Next.
Opening the Nodes Manager and selecting Inclusion
Opening the Nodes Manager and selecting “Inclusion”
  1. In the “Name and Location” tab, you can assign the device a descriptive name and a location right away, which is automatically applied once pairing completes – in our case, “Kitchen Motion Sensor” in “Kitchen”.
Name and location assigned during pairing
Name and room are assigned right at pairing time
  1. In the “Inclusion Mode” tab, you set the security level. Default (S2 if supported by the device, otherwise S0 only if necessary) is the right choice for most devices – including the TriSensor 8. Alternatively, “Scan QR Code” (for SmartStart-capable devices), “S0 encryption”, and “No encryption” are also available.
Inclusion mode options: Default, Scan QR Code, S0 encryption, No encryption
“Default” automatically applies the highest security level the device supports
  1. In the “Security Classes” tab, you decide which S2 security classes the device is allowed to use. For a sensor like the TriSensor 8, S2 Authenticated and S2 Unauthenticated (both pre-selected) are enough – “S2 Access Control” is more aimed at door locks and garage doors. I deselected “S0 Legacy”: wherever possible, S2 – ideally S2 Authenticated – should always be used.
S2 Authenticated and S2 Unauthenticated are enough for sensors like the TriSensor 8
S2 Authenticated and S2 Unauthenticated are enough for sensors like the TriSensor 8
  1. Now actually put the TriSensor 8 into pairing mode (press the internal pairing button three times in quick succession). The sensor confirms with a brief blink; shortly after, the “DSK Validation” tab asks for the first 5 digits of the DSK PIN, which is usually printed on the packaging or the device itself. On the TriSensor 8, it’s on the inside of the housing lid.
Entering the first 5 digits of the DSK PIN
The first 5 digits of the DSK PIN (printed on the packaging/device) confirm secure pairing
  1. Within a few seconds, the TriSensor 8 appears as a new node in the Control Panel’s node table – in our case, Node 002, with manufacturer “Aeotec Ltd.”, product “TriSensor 8”, product code “ZWA045”, the assigned name and location, and two green security checkmarks. The corresponding entities for motion, illuminance, and temperature also show up in Home Assistant shortly after, and the sensor is ready to use.
TriSensor 8 successfully paired as Node 002 with full battery and security enabled
Successfully paired: the TriSensor 8 shows up as Node 002 with a full battery and security enabled

What Entities Does the TriSensor 8 Provide?

After pairing, Home Assistant automatically creates all of the TriSensor 8’s entities. On the device page, four of them are enabled and directly usable by default:

  • Motion (Motion detection) – binary sensor, “detected” / “clear”
  • Illuminance – light level in lux
  • Temperature (Air temperature) – in °C
  • Battery – charge level in %
The TriSensor 8's three sensor entities on the device page: temperature, illuminance, and motion
The TriSensor 8’s three sensor entities on the device page: temperature, illuminance, and motion

Home Assistant also lists well over 30 additional entities that are disabled by default (diagnostic and configuration values like firmware status or link quality) – but for everyday use, the four above are entirely sufficient.

Step 3: Building an Automation – TriSensor 8 Triggers a Homematic Light

Once the TriSensor 8 exists as a completely normal Home Assistant device with its own entities, it no longer matters which radio protocol it’s connected through – it can be used in automations just like any other device. As a practical example, we’ll build an automation that automatically turns on a kitchen light on motion – controlled via a Homematic IP switch actuator paired with our CCU3. To connect Homematic IP to Home Assistant through the Access Point 2, see our Homematic IP guide. The Z-Wave sensor and the Homematic actuator don’t need to know about each other – Home Assistant, as the shared hub, handles the mediation.

  1. In Home Assistant, go to Settings → Automations & Scenes and start a blank automation via Create Automation → Create new automation.
Starting with a blank automation
Starting with a blank automation
  1. As the trigger (“When”), choose the TriSensor 8’s motion entity (in our case, “Kitchen Motion Sensor – Motion detection”) and react to the “detected” state.
  2. Optionally add a condition (“And if”) that only proceeds if the kitchen light is still off – this prevents unnecessary switching commands if the light is already on.
  3. As the action (“Then”), trigger the Homematic actuator – in our case via the Homematic(IP) Local for OpenCCU integration (despite the name, it works with the CCU3 too), which sets the on-time of the kitchen light switch.
Finished automation: Z-Wave sensor as trigger, Homematic actuator as action
The finished “Kitchen light on motion” automation: Z-Wave sensor as the trigger, Homematic actuator as the action
Practical tip: This is exactly the charm of using Home Assistant as your hub – sensors and actuators from completely different radio ecosystems (here, Z-Wave and Homematic IP) can be combined in the same automation. For the automation itself, it no longer matters whether Z-Wave JS, ZHA, or Homematic(IP) Local is handling communication behind the scenes.

More Automation Ideas with the TriSensor 8

With illuminance and temperature as additional entities, you can easily extend the motion automation above, and a few other automations are worth considering independently:

  • Light only when dark: Extend the condition from Step 3 with “illuminance below, say, 10 lux” – that way the automation no longer turns on unnecessary lights during the day despite motion.
  • Overtemperature warning: Use the temperature entity as a trigger (e.g., above 28°C) and send a notification or trigger a fan/ventilation automation.
  • Vacation presence simulation: If no motion is detected for an extended period, switch lights randomly on a schedule – the motion entity acts as an exclusion criterion here, so the simulation doesn’t kick in while someone is actually home.
  • Ventilation reminder: Combine temperature and illuminance readings from multiple rooms in a statistics card on your dashboard to track temperature trends over the day.

For Pi Purists: Z-Pi 7 Instead of a USB Stick

If you don’t want to give up a USB port for the Z-Wave controller, you can use the Z-Pi 7 instead – it plugs directly onto the Raspberry Pi’s 40-pin GPIO header (compatible with Pi 3, 4, and 5) and doesn’t use a USB port at all. The catch: the Z-Pi 7 uses the same serial port (/dev/ttyAMA0) as the Raspberry Pi’s built-in Bluetooth module. Without adjusting config.txt – disabling Bluetooth and enabling UART – Home Assistant won’t find the controller.

  1. Plug the Z-Pi board onto the Raspberry Pi, making sure to align the pins correctly – the included manual provides very good guidance here.
Aeotec Z-Pi 7 on the Raspberry Pi
Aeotec Z-Pi 7 on the Raspberry Pi
  1. Enable UART and disable Bluetooth: put the SD card into a computer and edit Home Assistant OS’s config.txt. Add the appropriate line for your Pi generation (dtoverlay=disable-bt for Pi 3/4, or dtoverlay=disable-bt-pi5 on the Pi 5, each together with enable_uart=1).
HAOS config.txt screenshot
config.txt with the necessary entries
  1. Since the Z-Pi 7 isn’t a USB device, the automatic “Recommended installation” dialog won’t appear. Instead, set it up manually via Settings → Devices & Services → Add Integration → “Z-Wave” and enter the serial path /dev/ttyAMA0 (see the manual installation section).
  2. From here, setup continues exactly like the USB path.

Practical Tips

Set the Region/Frequency Correctly

Home Assistant usually sets the radio region automatically based on your configured location – manually adjusting it usually isn’t necessary. If you do need to set the region manually (e.g., because you’re using Long Range devices), you’ll find the option under Settings → Apps → Z-Wave JS → Configuration → Radio Frequency Region.

Two Ports on the Z-Stick 10 Pro

Don’t be surprised if two serial devices show up during setup – one is for Z-Wave, one for Zigbee. For the Z-Wave JS integration, you need the Z-Wave port.

No Cloud Requirement

Unlike Homematic IP with an Access Point, whose Home Assistant integration goes through eQ-3’s cloud servers, Z-Wave JS runs entirely locally in Home Assistant – no Aeotec account is required for operation.

USB Detection Can Be Finicky

If the stick isn’t detected automatically: first check the hardware (a cable with data lines, not just power), then add it manually via Settings → Devices & Services → Add Integration → “Z-Wave”. If the problem persists, the USB extension cable mentioned above to reduce interference usually helps, according to the official troubleshooting docs.

Do I need a cloud account or manufacturer account for Z-Wave in Home Assistant?

No. Z-Wave JS in Home Assistant runs entirely locally; no Aeotec or Z-Wave Alliance account is required for operation.

What’s the difference between the Z-Pi 7 and the Z-Stick 7?

The Z-Pi 7 plugs directly onto the Raspberry Pi’s GPIO header and doesn’t use a USB port, but requires manual UART configuration including disabling Bluetooth. The Z-Stick 7 is a regular USB stick with simpler plug-and-play setup.

Can the Z-Stick 10 Pro control Z-Wave and Zigbee at the same time?

Yes, the stick contains two separate radio chips, each with its own serial port – one for Z-Wave (Z-Wave JS) and one for Zigbee (ZHA or Zigbee2MQTT).

How long does the battery last in the TriSensor 8?

With the included CR123A battery, Aeotec states a runtime of around 1.5 years, depending on how often it’s triggered.

The hardware from this test

The controller and the sensor at a glance. Prices come live from your local Amazon store; stale prices are not shown at all.

Ad
Aeotec Z-Stick 10 Pro
Aeotec Z-Stick 10 Pro
$67.64
Price before sales tax, as of 2026-11-21, 17:35 — prices may have changed since.
Ad
Aeotec Z-Stick 7 | Z-Wave Plus V2 | ZWA010 | 700 Series
Aeotec Z-Stick 7 | Z-Wave Plus V2 | ZWA010 | 700 Series
$52.89
Price before sales tax, as of 2026-11-21, 20:20 — prices may have changed since.
Ad
Aeotec Z-Wave Bridge Controller for Raspberry Pi
Aeotec Z-Wave Bridge Controller for Raspberry Pi
$95.99
Only a few left in stock
Price before sales tax, as of 2026-11-21, 19:20 — prices may have changed since.
Ad
Aeotec TriSensor 8 (Z-Wave Motion, Temperature and Light Sensor)
Check the current price at the merchant.

Conclusion

As Z-Wave newcomers, getting started was initially a bit more complex than expected for us – not because of the hardware itself, but because it’s not obvious at first glance that the Z-Wave JS app and the Z-Wave integration in Home Assistant are two separate building blocks that only together make up a complete setup (see “Adding the Z-Wave Integration in Home Assistant” above). Once you understand how they work together, though, setup runs just as smoothly as with other smart home systems: our automation with the TriSensor 8 as a Z-Wave sensor and a Homematic IP actuator as the action shows that Z-Wave fits in seamlessly alongside existing systems, without either one slowing the other down.

The hardware also makes a good impression in person: the TriSensor 8 is pleasantly small and unobtrusive, and thanks to the included adhesive strip, it can be mounted reliably almost anywhere without drilling.

Similar Posts