QT5 Wrapper for OpenZWave
Find a file
2020-01-22 17:07:39 +08:00
.github/workflows Cleanups and Github Actions (#24) 2020-01-22 14:58:48 +08:00
Docker use binary resource files instead 2020-01-06 14:45:41 +08:00
docs Polling Commands and Network Key Support (#21) 2020-01-21 23:50:01 +08:00
qt-openzwave Polling Commands and Network Key Support (#21) 2020-01-21 23:50:01 +08:00
qt-openzwavedatabase use binary resource files instead 2020-01-06 14:45:41 +08:00
qt-ozwdaemon Really fix the crash path creation 2020-01-22 17:07:39 +08:00
qt-simpleclient
tools Fix Crash when values that have been deleted (#17) 2020-01-17 16:16:08 +08:00
.dockerignore use binary resource files instead 2020-01-06 14:45:41 +08:00
.gitignore
.qmake.conf
LICENSE
makeosxbundle.sh
qt-openzwave.pri
qt-openzwave.pro
README.md Update README.md 2020-01-21 23:51:13 +08:00
setenv.sh
updaterpath.sh

qt-openzwave

This is a QT Wrapper for OpenZWave and contains ozwdaemon - a service that allows you to remotely manage a Z-Wave Network via ozw-admin or connect to a MQTT Broker.

Home Assistant MQTT Client Adapter

A Docker Container to connect to the new Z-Wave Integration for Home Assistant - python-openzwave-mqtt

Running:

Start a container with the following command line:

docker run -it --security-opt seccomp=unconfined --device=/dev/ttyUSB0 -v /tmp/ozw:/opt/ozw/config -e MQTT_SERVER="10.100.200.102" -e USBPATH=/dev/ttyUSB0 openzwave/ozwdaemon:latest

  • replace MQTT_SERVER with the IP address of the MQTT Server
  • replace all /dev/ttyUSB0 entries with the path to your USB Stick.
  • OpenZWave Config Files are copied on startup to the host directory specified by /tmp/ozw - You should replace it with a directory that is persistent.

the --security-opt seccomp=unconfined is needed to generate meaningfull backtraces, otherwise it will be difficult for us to debug.

Please see docs/MQTT.md for complete instructions, including settting up Network Keys etc

QT Wrapper Interface

Documentation is in progress. See the qt-simpleclient for a basic example.