Home Assistant Z-Wave Network Viewer (using Docker)

Configuration Z-Wave
144

just to be sure, you are not using HTTPs, right?
in addition, can you try this:
docker exec -ti ha-zwave-network wget http://192.168.0.70:8123
what is the response?

145

Hi Bar,

No, i do not use a SSL certificate. I tried the command you gave me and this is the result

docker exec -ti ha-zwave-network wget http://192.168.0.70:8123
Connecting to 192.168.0.70:8123 (192.168.0.70:8123)
saving to 'index.html'
index.html           100% |********************************|  3327  0:00:00 ETA
'index.html' saved
146

Sorry, Iā€™ve been buried at work lately and havenā€™t been watching the forums. This is odd, for some reason the versions of openssl-dev and libssl donā€™t align. Itā€™s getting 1.1.1g of the dev libraries but only 1.1.1g of libssl.

Supposedly the fix is to switch to libressl-dev, but when I do that it builds but doesā€™t work over an SSL connection. Iā€™m going to do some more digging and see if I can get to the bottom of the incompatible versions. Worst case, Iā€™ll see if I can pin both packages to the same version to fix this.

147

A new version of the add-on is up that should fix the build issue. It should automatically show up as an upgrade to version 0.4.

1 Like
148

Thanks for the fix. It is working well now.
Happy New Year

149

Hi,

Any clue about the issue with the docker container I mentioned above? I pulled the latest image but still having the same issue

Thanks

150

I am still unable to get this working on a pi4 hassos 64bit. Iā€™m installing the 0.4 version and have tried removing and re-adding the repo. This is what I see in the supervisor logs:. It sits at starting build.

21-01-03 13:30:11 INFO (MainThread) [supervisor.store] Loading add-ons from store: 72 all - 0 new - 1 remove
21-01-03 13:30:19 INFO (MainThread) [supervisor.store.git] Cloning add-on https://github.com/sjthespian/addon-zwave-network-viewer repository
21-01-03 13:30:20 INFO (MainThread) [supervisor.store] Loading add-ons from store: 73 all - 1 new - 0 remove
21-01-03 13:30:29 INFO (SyncWorker_1) [supervisor.docker.addon] Starting build for 76287f4b/aarch64-addon-zwavenetworkviewer:0.4

151

That output is normal, but it should eventually come back with a message saying that the image was built. This is what I see on my RPi4:

21-01-01 03:45:04 INFO (SyncWorker_0) [supervisor.docker.addon] Starting build for 76287f4b/armv7-addon-zwavenetworkviewer:0.4
21-01-01 03:49:01 INFO (SyncWorker_0) [supervisor.docker.addon] Build 76287f4b/armv7-addon-zwavenetworkviewer:0.4 done
21-01-01 03:49:01 INFO (MainThread) [supervisor.addons] Add-on '76287f4b_zwavenetworkviewer' successfully installed
21-01-01 03:50:36 INFO (SyncWorker_1) [supervisor.docker.addon] Starting Docker add-on 76287f4b/armv7-addon-zwavenetworkviewer with version 0.4
152

Yeah Iā€™m not sure whatā€™s happening but it fails to do anything after days of leaving it sit. Itā€™s weird. Havenā€™t had much time to dig in.

153

If you have ssh enabled on your HA server, you can try building the container yourself to see if itā€™s something specific to your system. You should be able to ssh in, cd to /addons, git clone the repo there, and then run: docker build . in the zwave-network-viewer directory. You might not have /addons by default, I think I may have had to disable protection mode in the SSH & Web Terminal addon to get that to show up.

154

So this was actually my fault. Iā€™m running opnsense with suricata and it was dropping the traffic. Once excluded, it built immediately.

155

Thanks for this. Got it working on my new configuration. Any chance you can add support for Docker secrets so I donā€™t have to add the token in the docker compose file?