← Directory

ozwdaemon

Container for running the OpenZWave MQTT Adapter (for Home Assistant via the new Z-Wave Integration) You will need a running MQTT instance and a z-wave…

  • Home Automation
  • Network Services
  • Tools & Utilities
Container for running the OpenZWave MQTT Adapter (for Home Assistant via the new Z-Wave Integration) You will need a running MQTT instance and a z-wave controller in order to use this container. For more information see: https://github.com/OpenZWave/qt-openzwave https://www.home-assistant.io/integrations/ozw/ Or visit the Unraid forum support thread for more configuration/info

Platform availability

Available on 1 of 9 platforms

  • Unraid
  • TrueNAS (not listed)
  • Umbrel (not listed)
  • ZimaOS (not listed)
  • Proxmox (not listed)
  • Helm (not listed)
  • Mac (not listed)
  • Windows (not listed)
  • Linux (not listed)

Health score?A 0-100 score computed nightly from four factors: maintained (40%: recent commits and steady activity), popular (25%: GitHub stars, log scale), easy to install (20%: platforms, install notes, setup guides, Docker image) and light to run (15%: minimum RAM, ARM support). When the source code has been checked, a fifth factor, security check (20%: automated scan for committed secrets, unsafe desktop-app settings, known-vulnerable dependencies and project hygiene; any serious finding caps it at 20), is added. Factors without data are left out and the rest are rescaled.

17/100 Low

Maintained
0last commit 2172 days ago
Popular
41105 GitHub stars
Easy to install
201 install platform, Docker image
Light to run
No data

Based on 3 of 4 factors.

Availability: platform listings confirmed today, links checked 17 days ago

GitHub stars
105
Open issues
60
Last commit
2020-11-03
License
LGPL-3.0
Activity
stale

Checked 9 days ago - source: GitHub (OpenZWave/qt-openzwave)

Resources & Compatibility

ARM (e.g. Raspberry Pi) is supported.

Checked 17 days ago - source: Docker Hub image tags and published docs

First-install notes

No first-install notes yet.

Alternatives

No alternatives collected yet.

Common questions

Where should I put persistent storage for ozwdaemon?

ozwdaemon uses /opt/ozw/config as the default location for cache files, device config files, logs, and crashdumps. Mount a persistent bind mount or named volume at that path.

How do I connect the container to my MQTT broker and Z-Wave USB controller?

Set MQTT_SERVER, optional MQTT_PORT, MQTT_USERNAME, and MQTT_PASSWORD for the broker. Set USB_PATH to the container pathname of the mapped serial device, and it must match the device mapped into the container.

Do I need to disable seccomp?

Use --security-opt seccomp=unconfined if you want meaningful backtraces and crashdump files. Without it, debugging ozwdaemon crashes can be difficult.

Why might the ozwdaemon container stop unexpectedly?

The service shuts down under certain error conditions, such as being unable to connect to the MQTT broker. Set a restart policy, and use MQTT_CONNECT_TIMEOUT if you need more time for the broker to become available.

How do I connect ozw-admin to a remote ozwdaemon?

Use the Remote OZWDaemon section of the Open dialog and specify the container host IP address and port 1983. The default ozw-admin port is 1983.

Answers sourced from ca.unraid.net, github.com

Community

Collected 16 days ago - public community threads