Overpriced in MHO. SMLight's configurator is half the price, twice the distance, and can be used on ethernet. This device will need windows to properly configure and update. Linux will work, just what you get is it. I did not encounter the bug mentioned in other reviews.

BJ Murray's excellent post above is extremely helpful, especially in concisely giving the steps to install and configure the device. However, some of the jargon isn't quite consistent with the Home Assistant guidance. In particular, the Home Assistant site refers to the "Z-Wave JS UI" and not the Zwavejs2Mqtt. However, it later remarks: "Zwavejs2Mqtt was renamed Z-Wave JS UI in September 2022. They are synonymous with no difference between their capabilities." Except for this minor blip, Murray's concise instructions appear to match those on the Home Assistant site, although the latter are more detailed (and hence long-winded and harder to follow).

I bought the dual-antenna z-station. Many reviewers seem to not know what they are getting. So here's how this works and what it's for:This is used to connect local IoT devices, directly through the antenna to some controller software, instead of using proprietary "hubs" for each manufacturer's device. How this works is when you plug this in to your server, it will give you 2 new TTY ports like TTY1 & TTY2. TTY1 is for Zwave protocol only. TTY2 is for Zigbee protocol, BlueTooth LE and wifi protocols.This device is ideal for a dedicated "server" for home automation, most likely running several docker containers, rather than installing the manufacturer's software "drivers" on your local computer (although this is possible , not recommended).Most setups will be something like this: On a server (probably linux) running docker, you will have something like the following:- homeassistant- zwavejs2mqtt- zigbee2mqtt- mqttbrokerHomeAssistant is one of Many possible "Interfaces" to control your devices. OpenHab, etc. are other optionsZWaveJS2MQTT is the DRIVER SOFTWARE for your device. Do not install the z-way z-wave-server. Use this instead. It is a docker container, running a "server" that has all the stuff you need installed already to use the z-station with your home auto software and includes a more powerful option for configuration of antenna, updates etc... through this gui rather than your home auto software (which only has a subset of features avaiable most likely).NOTE: this container / software uses TTY1 port / antennaNOTE: you dont have to use the MQTT portion of this server. Just uncheck "Enable MQTT Gateway" in Gui settings after container is up and running.Zigbee2MQTT is the zigbee protocol software, and has it's own GUI config interface as well. This will also allow your home auto software to detect and import your zigbee devices and configs and allow you to control them without the 3rd party hubs or software.NOTE: this container uses the TTY2 and 2nd antenna of the device.NOTE: you dont have to use the MQTT on this either.MQTTbroker is some container (probably eclipse-mosquitto) that runs an optional MQTT broker server that allows home auto software to talk to devices through MQTT messages - allowing the MQTT broker to operate independently of Home Auto software - so if you restart your software or update it the other containers keep on working together on their own, unaffected by the reboot of the home auto container. etc.The easy way to do all this is in docker-compose.yml file.If none of this makes sense to you, do not buy this device, until it does!READ THE DOCS FOR EACH DOCKER IMAGE/CONTAINER mentioned above and they give you the default example configs for your docker setup.Try this order: in docker 1) set up zwavejs2mqtt container & make sure your logs show adapter working, no errors etc. 2) set up zigbee2mqtt container & make sure your logs show adapter working, no errors, etc. 3) set up MQTT container, optionally, and make sure containers 1&2 are set up rightly to connect to this container for MQTT messaging. If not using MQTT skip this step. 4) set up your home automation software container (ex: home assistant). Config to talk to prior installed containers. check logs for errors. You should be set up to now connect/ add /use your various devices in your home auto software.HTH

It is a nicely built device, and it does work as advertisedI bought it mainly for use with Z-Wave JS, not with Z-Wave.Me's proprietary Z-Way software. The device DOES work with Z-Wave JS - but with some very important caveats!1. You can't do firmware updates to the Z-Wave controller in ZWave JS like you can with other controllers it supports. You will have to get into the terminal and update it. It can't be done from Z-Wave JS or the Z-Wave JS UI.2. You cannot use ZWave JS' NVM backup/restore capability with the Z-Station controller. So if the Z-Station dies and you need to replace it, you will not be able to just restore the NVM backup created in ZWave JS. You would have to factory reset and re-pair every device. That is a really big deal to me, and a deal breaker for using Z-Station with Zwave JS.

Now my Aquara zigbee motion sensor switches on Aeotec Z-Wave wall switch.Initially, I ordered the device to solve the latency problem for a distant sensors. Before I placed 2 sensors in my yard, Aeotec Z-Stick 5 satisfied me. I connected them but they weren't working stable. The replacement to Z-Station made my system work again. The cable even allowed me to put it on the wall, keeping my Pi on the table, where it lives since the first day. I'm glad with the extended transmission distance and stability!

Nice and useful! My home automation started with Z-Wave and then I added RS485 roller shutter and Zigbee window sensor.My Rapsberry Pi already had 3 ports occupied. It's great Z-Station is using only one USB slot for both Z-Wave and Zigbee. I added the rule to prevent closing the curtains if the window is opened. Works fine.By the way, I had to update the firmware to make the Zigbee2MQTT work. While doing it I found many other firmware options. Even with a Thread one enabling Matter support. I think I will try it.

I seldom write any reviews; however, I had great expectations when I ordered this product, only to find the documentation less than adequate. I attempted to follow the directions however when reaching out to their Technical Support only to learn that the product was shipped with a bug in their code, which they sent a response 2 days after I requested assistance. Even after correcting the configuration file, I was unable to connect to this device. The web page required a username and password, which was never provided when requested. Even as I attempted to search their own resources, nothing. I would steer clear of this device until the address tech support and address their bug issues. Saddly, I am giving up on this product only to return it. Maybe they will address documentation and bugs!