Z-Wave Future....

[akbooer]

...apparently not:

12:34   Cannot start Z-Wave binding: Error: Invalid port
12:34   Cannot instantiate module: HomeKitGate: Error: Failed to announce DNS record

Not sure how to fix this? Clearly need to map to the UZB somehow?

Also keen to learn more about the HomeHitGate...

[PerH]

Are you using my docker-compose? Don't know anything about synology, but I always use the /dev/serial/by-ID... designation, as it doesn't shift addresses.. But you can have a simpler address internally (the one after the ":" ).

Host works, but you should be able to just forward 8083 as well? if something else also uses it on the host, you can change it on the outside (before the ":")..

I think the log looks fine, don't know anything about homekitgate though..

Mabye you can post your docker-compose?

[akbooer]

Thanks, I've got this a step further by running the docker in privileged mode which allows mapping of the /dev directory, so that it does now find the UZB. This is running under Synology DSM v6, which is not the latest, but I understand that under version 7 it doesn't allow mapping of device ports at all. (This is a bit of a downer for people trying to use a UPS, AFAIK, which was the next thing I was wanting to add.)

I'm not using docker-compose at all, just the native Synology Docker UI and/or editing the config.json directly.

Anyway, one step more along the way. Next is to try add a Zwave device. The only reason I'm doing this is to move my two final Zwave devices (power meter readers) off of Vera , because I can find no equivalent devices which use WiFi.

Thanks again for the response.

[akbooer]

Now seeing:

sh: 1: ip: not found

I think this happens when trying to include a device, which eventually fails with timeout.

[PerH]

That one is OK, it's related to the UI in some way, and not the stick..

Very strange that you have contact to the stick, but can't include? that part usually works flawlessly, I don't use the expert panel for that though, as the other UI has a naming wizard for the units..

[akbooer]

OK, I’ll try again!

[akbooer]

@PerH
...still not working, just timing out on any include.

Are there any other parameters in the config that need changing? I see an id parameter – is that relevant? Or maybe not using the right frequency band (I am in the UK) ?

How is the licence key handled in the stick? I recall having to buy a licence separately??

[PerH]

Ok, so what firmware do you have? You've used this stick before?

The firmware stuff is a bit of a mess, look at this thread..

As I discovered; There is a Bridge firmware for using the stick without z-way, and a regular one for Z-Way. Mabye you have the bridge one?

Don't think you have area troubles, EU is part of the most common firmware..

[RHCPNG]

@PerH Does your docker image support Socat? And, if so, is the configuration persistent after a container update?

[PerH]

Its been a while since i've used this now, I've moved to Z-WaveJS..
Socat - so you have a remote connection to your z-stick? Should work fine with this contatiner, just set it up in the docker-compose file.
That said, I would ask on the z-way forum, you may find a more current z-way version in a newer container..

All settings should be persistent if volumes are set up correctly.

[RHCPNG]

@PerH said in Docker container for Z-Way:

Its been a while since i've used this now, I've moved to Z-WaveJS..
Socat - so you have a remote connection to your z-stick? Should work fine with this contatiner, just set it up in the docker-compose file.
That said, I would ask on the z-way forum, you may find a more current z-way version in a newer container..

All settings should be persistent if volumes are set up correctly.

I don't have a remote connection yet, I'm preparing for the migration from Vera to Z-way. I wanted to nuke the Vera and use it as a central hub for my Z-way stick.

From what I've read, Socat will not work in combination with docker. The Ser2net/ Socat solution is giving me a headache with the preparation alone. It is difficult with docker, so it seems, unless you create a docker specifically with Socat in it. But creating docker images is not a skill I possess (yet).

Unlike others in this thread, I'm a fan of docker containers. (Easier to maintain, troubleshoot and keep up-to-date). But Socat is a show stopper for now.

I think I'll ditch the Vera Edge and Z-way docker. I'm looking at using a Raspberry Pi with USB/IP (can't easily install this on the Vera) now instead of Ser2net/Socat and running the Z-way addon for HA.