Z-Station support

There is a new device from z-wave.me called z-station. Info can eb found at Z-Station.

Is this supported out-of-the box using the z-wave plugin?

They claim it works with openHAB. :smiley: My understanding is that Zwave defines a standard for the serial protocol between the computer and a USB dongle. And it comes with Zway for which OH does have a Zway add-on and they claim it works with zwave2mqtt and zigbee2mqtt which a lot of OH users are using too.

I’ve not kept up with the state of the Zwave binding. My understanding is it now supports Zwave controller based on SI Labs SDK 7 controllers partially but not Zwave 8 controllers yet. This appears to be a 7 controller so it should work with some limitations (see the add-on docs for details).

For Zigbee, support for the controller depends on the chipset of the controller. Other Silicon Labs chips are supported but EFR32MG21P is not in the list of supported coordinators. So it might be that zigbee2mqtt is the only way to get the Zigbee to work, but it also might just work with an “Ember” chipset configuration.

Over all, I think it would be relatively low risk to get this device and integrate it with OH. The Zwave will mostly work out of the box minus some extended Zwave 7 level stuff. The Zigbee will either work or you have a third party option.

It looks like a nice device. I hope someone comes back and reports their experiences.

I just bought one and I’ll share my experiences.

3 Likes

I successfully migrated from Aeotec zWave Gen5+ to Z-Station, but I’m only using the zWave part. The docker image from this site does not work on my Openhab server (CentOS Stream release 8)

Therefore I use this image:

podman pull youdownwithjpd/docker-zway
podman container create -it --device=/dev/ttyUSB0 -p 8083:8083 docker-zway
-> started container

Browsed to http://ip_server:8083

  • added Z-Station Controller to network
  • stopped the container (as there are issues when controller is active in OpenHAB)

In Openhab:

  • created new zWave thing for Controller
  • added all new zWave nodes as things (are the same as the old ones with a different deviceId)
  • changed the deviceId of all my zWave items (I have file based item definitions)
  • disabled Z-Station thing

Then I did a reset of the Aeotec Z-Stick Gen5+

  • start container again
  • browsed to http://ip_server:8083
  • removed the failed node which has represented the Aeotec Z-Stick
  • stopped the container again

In Openhab:

  • enable Z-Station thing again

Finally I had to wake-up the only battery powered device.

1 Like

Yes, you cannot have more than one service accessing a physical device at the same time. If Zway is using the controller, OH cannot, and vice versa.

If you don’t need the Aeotec controller still active when you add the Z-Station, you can delete the Aeotec Thing and when you create the Z-Station Thing give it the same UID and all your links will work unchanged as your Things will all have the same UID as they had before.

It’s not clear to me but I think it only needs to be active for the first step where you add Z-Station to the networking using ZWay, correct?

Correct. This way the new device gets the full network map from the old device.

According to z-wave.me support, there is an updated docker version available.
I have not yet tested it, but here is the link to the github repo:
GitHub - msazanov/docker-z-way: Docker file for Z-Way under Ubuntu x64

The new provided Z-Way docker version is working fine.
I also updated the zigbee firmware and was now able to setup Zigbee with zigbee2mqtt (also in docker). Zigbee is not working with the binding and the ember chipset configuration.

Just to note that if this is a very new device, it possibly has a very new version of EZSP (the protocol used by the binding to talk to the coordinator). The binding is currently one version behind - I think this version was released a couple of months back and there is a PR to update it to the latest…

Anyway, if you’re keen to get this working (I’m not sure?) then getting a log to see what’s going on will help. It’s possibly as simple as versions :slight_smile:

1 Like

I guess this should answer your question.

2024-05-25 09:59:23.552 [ERROR] [zigbee.dongle.ember.ZigBeeDongleEzsp] - EZSP Dongle: NCP 
requires unsupported version of EZSP (NCP = V13, supported = V4-V12)

Thanks. So this is as I thought - the communications with the coordinator is working, but the EZSP version is the very latest, and while that was added to the zigbee library that OH uses back in January, it’s not been merged into the binding as yet.

I’ll see if I can get this merged shortly.

1 Like

How has this been for you? I’m in the same situation and thinking of moving to this device. Has it worked reliably and the range is as good or better?

The range is better compared with the Aeotec and the device is rock solid. Beside of that the administration GUI (z-way) offers all required functions. And finally it supports also OpenThread.

1 Like