OpenZwave on another networked device

Configuration Z-Wave
1

The advent of moving to this implementation of z-wave is just what I have been waiting for! (I think) Would it be possible to run openzwave on another device (Say a 1st gen RPi) and have it connect to the MQTT server running on a machine over the network? The location of my actual computing equipment is in a sheetmetal shed that is detached from my house, so I stole a RPi 3 from another project to run HA on. If it works that way I could move the HA instance to an ESXi box and have the zwave instance running dedicated on a device in the house where reception is less of a problem.

2 Likes
2

Yes, you can.

3

I was just talking to a friend, it’d be really nice if we could install a base image on a pi, and then deploy OZW and Deconz to it and keep ingress security.

4

I have it working like that.
The dongle sits on a raspberry PI 2 in the main area of home.
on the raspberry a zwave and a zigbee dongle (zigbee2mqtt ).

For zwave no need to setup anything extra since it sends mqtt messages
For zigbee ser2net is installed.

I have just a small problem but it is not related , I think, to the remote config

5

No Ingress that lets Home Assistant act like it’s all the same system right?

6

Almost. Please check another ingoing topic

7

I tried to get the docker image running as mentioned in the github readme on an rpi2, but all I get is:

[s6-init] making user provided files available at /var/run/s6/etc...exited 0.
[s6-init] ensuring user provided files have correct perms...exited 0.
[fix-attrs.d] applying ownership & permissions fixes...
[fix-attrs.d] ozw-logs: applying...
[fix-attrs.d] ozw-logs: exited 0.
[fix-attrs.d] done.
[cont-init.d] executing container initialization scripts...
[cont-init.d] ozw-logs: executing...
[cont-init.d] ozw-logs: exited 267.
[cont-init.d] done.
[services.d] starting services
[ozwdaemon]: Exited with Status Code 256
[services.d] done.
[ozwdaemon]: Exited with Status Code 256
[ozwdaemon]: Exited with Status Code 256
[ozwdaemon]: Exited with Status Code 256
[ozwdaemon]: Exited with Status Code 256
[ozwdaemon]: Exited with Status Code 256
[ozwdaemon]: Exited with Status Code 256
[ozwdaemon]: Exited with Status Code 256
[ozwdaemon]: Exited with Status Code 256
[ozwdaemon]: Exited with Status Code 256
[ozwdaemon]: Exited with Status Code 256
[ozwdaemon]: Exited with Status Code 256
[ozwdaemon]: Exited with Status Code 256
[ozwdaemon]: Exited with Status Code 256
[ozwdaemon]: Exited with Status Code 256
[ozwdaemon]: Exited with Status Code 256
[ozwdaemon]: Exited with Status Code 256
[ozwdaemon]: Exited with Status Code 256
[ozwdaemon]: Exited with Status Code 256
[ozwdaemon]: Exited with Status Code 256
[ozwdaemon]: Exited with Status Code 256
[ozwdaemon]: Exited with Status Code 256
[ozwdaemon]: Exited with Status Code 256
[ozwdaemon]: Exited with Status Code 256
[cont-finish.d] executing container finish scripts...
[cont-finish.d] done.
[s6-finish] waiting for services.
[s6-finish] sending all processes the TERM signal.
[s6-finish] sending all processes the KILL signal and exiting.

Any tips from your setup? (I have rasberry pi os lite installed)

8

I have also tried this with the same error “Exited with Status Code 256”.
How can we solve this?

9

The github fails to mention a couple of required environment variables: MQTT_USERNAME and MQTT_PASSWORD

10

Also, take a look at Problems when ozwdaemon is on a different machine

11

I see the environment variables in the README:

https://github.com/OpenZWave/qt-openzwave#enviroment-variables

1 Like