I recently bought the Z-Wave antenna from Nabu Casa (Home Assistant) in order to use Long Range sensors to automate my mailbox, which is too far from my setup to use more common protocols like Zigbee, Matter, or Wi-Fi.
So, I added 3 sensors: a Zooz ZSE18 motion sensor and 2 ZSE41 contact sensors, all advertised as Long Range compatible sensors by the well-known home automation retailer Domadoo.
The problem is that when installing these sensors in Home Assistant via Z-Wave JS, I’m never given the option to choose between a mesh or a long-range installation. All three sensors are automatically integrated as mesh…
So I contacted Domadoo, who explained they had reached out to Zooz, and Zooz replied that the sensors need to be updated to version 2.20 (while the most recent OTA version offered by Z-Wave JS is only 2.10).
I went ahead and downloaded the updates from the Zooz website, unpaired the sensors, re-paired them, but still — no option to choose between LR or mesh…
Has anyone else run into the same problem? Does anyone know where this issue might come from?
For context, I’m based in Europe and my sensors are the EU versions.
Hi there! As long as the ZSE41 sensors have been updated to 2.20, and confirmed that you are running the Z-Wave JS UI integration, then you can follow our inclusion instructions here.
For the ZSE18, ZWLR has not been implemented for the EU frequency at this time, so this would need to be included as a mesh device. Devices that are currently available in Long Range in EU frequency will still need a complete SDK update due to a shift in the EU frequency specifically for Z-Wave Long Range.
We will be updating our EU devices to support the long range protocol in Europe, but it will take time due to the required SDK update for the frequency shift.
This update will be done via OTA; we will reach out with the new firmware as soon as it is available.
Please let us know if you have any questions in the meantime.
I’m experiencing exactly the same issue. I purchased a ZSE41 800 EU sensor which Amazon claims supports Long range in the description despite the packaging or instructions making no reference it when it arrived. It came with firmware 2.10.
I completed a firmware update to 2.30 and followed the instructions linked above (How to Add Your ZSE41 Open | Close XS Sensor to Home Assistant - Zooz Support Center) after first excluding the device and completing a full resetting. After scanning the QR code the Add Device screen appears but I only see the options to name and set an area, the choose network type sections doesn’t appear, and it joins the the z-wave mesh not LR.
My setup is as follows
Home Assistant: 2026.2
Z-Wave JS 15.21.0
Z-Wave JS UI 11.12.0
Sensors: FW: v2.30
Nabu Casa ZWA-2: FW: 1.2
Living in the Europe
For complete transparency this is my first z-wave device I’ve wanted to use for LR. Any pointers would be appreciated.
Hello - I’m not sure if helpful, but here’s a short vid on adding Zwave LR via JS UI.
With the device not powered (pull the battery) I’ve had success scanning the QR code directly into the smart start provisioning list first. Then edit that smart start entry for LR and activate it. Lastly, power on the device and let it auto-add.
One important thing about taking a physical device that was not manufactured for Z-Wave Long Range, then updating and including it via Z-Wave Long Range is that the QR code is not a ZWLR QR code. This is not an issue for Hubitat, but is an issue for Z-Wave JS (Home Assistant, HomeSeer, Jeedom, and others). In order to include a device that is now ZWLR compatible by firmware update, you need to enter the full DSK manually, you cannot scan the QR code.
While using the Z-Wave JS UI, you can add the DSK code to the provisioning list and select LR. The ZSE41 will then be included as an LR device. See screenshots below:
Thanks @Sara , that was exactly the issue. Entering the DSK rather than using the original QR code when provisioning did the trick, as you described it then allowed me to change the protocol before enabling inclusion mode on my adaptor.
