UZB/RaZberry Firmwares - Update

[LibraSun]

We're clearly thinking along the same lines here lol.

[PerH]

looking at the compatibility matrix, it seems like differences are in options I don't use in my file, did you try to change line 1 to version: "3.7"?

regarding networks:
I have several dockers, and Openluup/InfluxDB/Grafana/etc is all communicating inside this network.
The "networks:" part needs to define this network for each docker-compose file in order to tie them together, so it will show an error if you do docker-compose down on one docker while other dockers are connected. and thats OK.

Edit: you could skip the "networks:" definitions all together, but then you would have to open ports for intercommunication as well to the host. I found that to be over complicating when you can have internal communication.

Wrt. timezone sync:
I haven't done timezone in z-way, as it hasn't been nessecary as i'm using openLuup for control an logging, but i've added the sync lines like I did in the openluup compose file below.

I just tested the code below, and it worked on my testbench.

version: "3.7"
services:
  Z-Way:
    container_name: Z-Way #or what you want to call it
    restart: always
    image: perhu/z-way-server-3-1-3:latest
    networks:
      HAnett:  #or whatever you internal docker network is called
        ipv4_address: 192.168.0.2  #this volume gets this IP in the internal network
    ports:
      - "8083:8083" #UI port
    volumes: 
      - type: bind    #timezone sync
        source: /etc/localtime
        target: /etc/localtime
      - type: volume
        source: Z-Way-zddx #Device info storage (i think)
        target: /opt/z-way-server/config/zddx
      - type: volume
        source: Z-Way-storage #application settings
        target: /opt/z-way-server/automation/storage
    devices:
      - "/dev/serial/by-id/usb-0658_0200-if00:/dev/serial/by-id/usb-0658_0200-if00" #your device here
    environment:
      - ZWAY_VERSION=3.1.3
    logging:
        driver: "json-file"
        options:
            max-file: "5"
            max-size: 10m
networks: #I set up a network for the dockers to communicate, with static IPs
    HAnett:
        name: HAnett
        driver: bridge
        ipam:
            config:
                - subnet: 192.168.0.0/16 #subnet of choice
                  gateway: 192.168.0.254 #gateway ip (this can be used to reach ser2net devices on host)
volumes:
  Z-Way-zddx:
    name: Z-Way-zddx
  Z-Way-storage:
    name: Z-Way-storage

EDIT: added the "logging:" settings in the code above. I've done this to all my dockers, as logs were stored without limit and ended up filling my HD!

[SweetGenius]

@perh Thanks for the all the help ! A couple more questions if you don’t mind: PoltoS mentioned the volume should be zddx instead of zddl. I assume that is in the docker file but does that change anything in the compose file?
Im confused with the volumes: sections, With the run command that I used that had data created in the storage folder was:
sudo docker run --restart=always -p 8083:8083 --device=/dev/ttyACM0 --name="zway" -v /volume1/docker/zway/zddl:/opt/z-way-server/config/zddl -v /volume1/docker/zway/storage:/opt/z-way-server/automation/storage perhu/z-way-server-3-1-3:latest
Can you explain how to put these paths in the compose file because when I try i do not get any thing in the directories? So obviously i still don't understand the compose file.

[PerH]

ah, it should be zddx, yes. I've corrected that in my own dockerfile and docker-compose, but haven't fixed it on the forums. sorry.
The change is both in the dockerfile and compose file. replace "zddl" with "zddx".

The docker-compose file uses docker volumes instead of binds. docker has its own system for persistent storage, volumes, that is stored in /var/lib/docker/volumes.
In your run command you use binds to host folders, which can also work if you declare it like this:

    volumes: 
      - type: bind   
        source: /volume1/docker/zway/zddx
        target: /opt/z-way-server/config/zddx

like i did in the above file with the time zone folder.

I ended up using the docker way instead as that was recommended in the docker documentation, but as long as you keep strict control of the folders you bind to, that will work too.

[PerH]

did anyone test the updated docker-compose on synology? I'm curious to if that was all it took to make it work there.

[SweetGenius]

@perh I did try your docker-compose and it does run just like the run command. So I think that part is good but the image still has some issues. I installed zway on a rpi again to see how it works. The remote access error was there until a reboot and then went away. That is without touching the config of remote access. Setting the time zone set and then prompted for a reboot and all was well. I think there is some permission issues or something else because this does not happen on the docker image. On all the other docker images I use (MSR, Homeassistant, Homebridge) i shut the container down, update the image, action clear and the container would update and not lose any settings. I did a action clear on this image and it was like a brand new image. No settings were saved. Sorry to say It Idont think it is totally working. I sure appreciate your help and expertise.

[PerH]

Ok. Just checked my installation, and i have removed the remote access app completely, and according to @PoltoS, the error message would stay there if you don't set that app up. It is the one that appears twice when you go into "Settings", right? Did it go away just by rebooting on the non-docker install?

Timezone:
My timezone is working correctly now, as it is defined to Europe/Oslo in the image. that can be overridden by this in docker-compose:

    environment:
      - ZWAY_VERSION=3.1.3
      - TZ=Europe/Oslo

(adding that last line with your timezone)
I thought that changing it in the Z-way UI would do the same, but mabye not?

persistent storage:
How did you do the folders? Did you use the docker-compose as-is, or change to binds to your /folder1/ folders?
I don't have a synology, it might be an issue with binds on that?
you should perhaps go over to volumes in that case, you can still access the volume the same way as a bind folder by going to /var/lib/docker/volumes/*volume name*/_data.

Are you using docker-compose up -d and docker-compose down to start and stop/remove the container?

Definately no expert on dockers yet, but its an interesting thing to learn.

[SweetGenius]

On the non-Docker install it just went away. On your docker image, no remote access is installed at first and there is the error. If I install it and make it not active it warns that is not active. If make it active it keeps prompting to make it active... I am using your compose file with the exception of taking out the network stuff and adding my time zone in the environment settings. The time zone will show up after fiddling with it but if you try to change it to something different than what is set in the compose file it errors. Is the update supposed to work? If so, I need to put back in some network settings as it does not work the way it is.

[SweetGenius]

One other note on the network, All the other docker containers i use, I do not specify an IP. You access each container by the Synology IP:Port. So, this might be different but I do not know for sure. Just giving you information.

[PerH]

Ok. Sounds like some other folder of z-way needs to be persistent too, which holds info on the plugins.. I'll ask @PoltoS.
Not sure about the timezone update, i'll have to try that later. Usually its not nessecary to change after you set it in docker compose though.

The reason for the static IP's is to use the internal docker network for all communication between the dockers. I only expose the web UI ports of the applications, as all communication between the docker applications goes internally on the docker network. I.e. InfluxDB, which has no web UI (that i use), have no exposed ports, and it sends and recieves everything on the docker network.
This also exposes less ports on the host, which may be better security-wise?

[RHCPNG]

Hi @sofakng,

How is the development of the docker going? Is it production ready yet? I would like to use it in the coming months (migrate Vera to Zway), but would like it to be kind of stable, because I don't want additional uncertainties with the migration if possible.

Would it be possible to add socat to the docker? I would like to share my dongle over my network.

[PerH]

You could see if mine works for you?

Works great here, there is an updated docker-compose in the description on dockerhub.

[RHCPNG]

@perh Ok, that's great! I will try it as soon as possible, but it could take some time though. Thnx!

[akbooer]

Any developments here recently?

I’m keen to try this on a Synology to support my only two remaining Zwave devices – power meter readers.

[akbooer]

@perh

Hi there. I've installed your 3-2-11 version and can't access it through port 8083. Wondering if I can get any guidance on this?

Here's the log from within Docker:

perhu-z-way-server-3-2-11
date,stream,content
2022-10-07 15:53:46,stdout,
2022-10-07 15:42:03,stdout,Error: 'debug-port' number is out of range. Skipping it.
2022-10-07 15:42:03,stdout,Using default configuration file config.xml
2022-10-07 15:42:03,stdout,Module modzwave.so loaded
2022-10-07 15:42:03,stdout,Module modzbw.so loaded
2022-10-07 15:42:03,stdout,Module modws.so loaded
2022-10-07 15:42:03,stdout,Module modsockets.so loaded
2022-10-07 15:42:03,stdout,Module modskininstaller.so loaded
2022-10-07 15:42:03,stdout,Module modnotification2ext.so loaded
2022-10-07 15:42:03,stdout,Failed to load module modmqtt.so: libmosquitto.so.1: cannot open shared object file: No such file or directory
2022-10-07 15:42:03,stdout,Module modinstaller.so loaded
2022-10-07 15:42:03,stdout,Module modiconinstaller.so loaded
2022-10-07 15:42:02,stdout,Module modhttp.so loaded
2022-10-07 15:42:02,stdout,Module modhomekit.so loaded
2022-10-07 15:42:01,stdout,Module modenocean.so loaded
2022-10-07 15:42:01,stdout,Module moddhs.so loaded
2022-10-07 15:42:01,stdout,Module modcrypto.so loaded
2022-10-07 15:42:01,stdout,Looking for modules in ./modules
2022-10-07 15:42:01,stdout,Z-Way version v3.2.1 from 2021-09-15 19:34:27 +0300 (build 6c1821fe5c4b95bd8c5e109843b31a4127ad69ca)

[akbooer]

Oooh, I now get to the local smarthome web page.

I switched to "host" for the network mode.

Not sure whether the Zwave stuff actually works...

[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.