Can we revisit the move to qt-openzwave?

[petro]

@finity

What if people don’t use the add-on? as in the people who aren’t running a supervised flavor of HA and don’t have access to the add-on?

You just answer no to the first question when installing the integration. Which is something like “Use Zwave JS addon”

@finity

I haven’t really heard about any progress to make a stand-alone (non-add-on) version (in docker or whatever) of the server that doesn’t also include the ui & mqtt that zwavejs2mqtt already offers.

It already exists:

GitHub - zwave-js/zwave-js-server

@finity

At that point we have competing UI’s? or will non-supervised HA users not be able to use the built-in UI because we don’t use the add-on?

If you use ZwaveJS2MQTT, both interfaces will work.

EDIT: Take a look at the overview and the flow charts I made. Maybe it’ll help you understand better:

Zwave & Home Assistant Overview

Introduction Currently, there are 3 different ways to integrate a ZWave network . This is a broad overview of each method. Zwave JS Addon & Zwave JS Integration (Websockets) ZWave JS UI & Zwave JS Integration (Websockets) ZWave JS UI & MQTT Integration (MQTT) Note: The legacy Zwave 1.4 and OpenZwave (Beta) integrations no longer exist and are not covered in this overview. Glossary Addon - Click on the link for a description. Integration - Click on the link for a description. Zwave JS …