Allows you to use your ZWave devices using ozwdaemon, a service that allows you to remotely manage a Z-Wave Network via ozw-admin or connect to a MQTT Broker.
Have a look: https://github.com/OpenZWave/qt-openzwave
Just type:
# Create new container image
docker build . -t openzwave2mqtt
# Run the docker image
docker run --privileged -ti --rm -e TZ=Europe/Amsterdam -v /dev/ttyUSB0:/dev/ttyUSB0 -v $(pwd)/config:/config -e MQTT_SERVER="10.100.200.102" -e MQTT_USER=ozw -e MQTT_PASS="pass" openzwave2mqtt
create-release.sh
Given the docker image with name openzwave2mqtt
:
docker run --privileged --name openzwave -e TZ=Europe/Amsterdam -v /dev/ttyUSB0:/dev/ttyUSB0 -v $(pwd)/config:/config -e MQTT_SERVER="127.0.0.1" -e MQTT_USER=ozw -e MQTT_PASS="pass" -d jriguera/openzwave2mqtt
Variables, they can be updated at any time re-defining env variables (all except NETWORK_KEY
).
TZ
Timezone, defaults to Europe/Amsterdam.NETWORK_KEY
By default is generated automatically and stored inNETWORK_KEY.txt
file. Changing requires repairing of all devices!!. So is not possible to change it once it was generated via env var, you will need to delete the previous files.DEVICE
Controller device, by default is/dev/ttyUSB0
.LOG_LEVEL
default toinfo
.MQTT_SERVER
MQTT server, defaults to127.0.0.1
.MQTT_USER
MQTT username auth.MQTT_PASS
MQTT Password.MQTT_PORT
MQTT Port, default is1883
.
Jose Riguera <jriguera@gmail.com>