I think ozw-admin is a critical part of the new qt-openzwave infrastructure since it allows access to information and configuration that's not yet exposed through services of the ozw integration in HA.
I wanted to start a conversation about this comment
Right now, the Versions of ozwdaemon and ozw-admin are tightly coupled (as a lot of development work is going on right now on the Network aspects of the code). Suggest you run the allinone docker image of ozwdaemon and use VNC to use ozw-admin till such a time that the work has stabilized a bit
Right now, the only way to get a working qt-openzwave <-> ozw-admin session is to run the latest version of both. With this zwave addon, build hashes are locked down and it's very difficult to determine which version of ozw-admin is compatible with the qt-openzwave version running in the addon.
I see a few options:
1) Mirror the qt-openzwave/allinone docker image, include ozw-admin and a VNC daemon, and expose a VNC port from the addon.
2) Document (and link to) the specific ozw-admin build that is compatible with the current version of the zwave addon.
3) Update the zwave integration to support the missing services that ozw-admin provides.
I think that 2 is probably the best way forward for now.
I think ozw-admin is a critical part of the new qt-openzwave infrastructure since it allows access to information and configuration that's not yet exposed through services of the
ozw
integration in HA.I wanted to start a conversation about this comment
Right now, the only way to get a working qt-openzwave <-> ozw-admin session is to run the latest version of both. With this zwave addon, build hashes are locked down and it's very difficult to determine which version of ozw-admin is compatible with the qt-openzwave version running in the addon.
I see a few options:
1) Mirror the qt-openzwave/allinone docker image, include ozw-admin and a VNC daemon, and expose a VNC port from the addon. 2) Document (and link to) the specific ozw-admin build that is compatible with the current version of the zwave addon. 3) Update the zwave integration to support the missing services that ozw-admin provides.
I think that 2 is probably the best way forward for now.