Create new bundle/release with latest configs

[perosb]

Hi,

is it possible to create a new tagged release with the latest configs?
Even though it is possible to build using flavor=git, it's more convenient to have a specific version as a dependency.

Maybe this is something that could be automated just bumping the patch version with latest configs? What are your thoughts?

br

[skeptizzle]

I'm looking forward to new configs as well.. I have a Fibaro Co2 sensor and a Philio Motion sensor that are currently unsupported by Home-assistant..

[bibi21000]

Hi
You can use the embed_shared favor and put your conf in /etc/openzwave. This is the first place where the lib looks for config files :
https://github.com/OpenZWave/python-openzwave/blob/master/src-lib/libopenzwave/libopenzwave.pyx#L606

[rogersmj]

People on hass.io can't use the workaround to obtain new configs, I don't think, because of the way the docker container is setup (?). It's not possible to get to those files. We really need a new patch release that includes the latest configs.

[rogersmj]

Hi @bibi21000 , not having more frequent releases of python-openzwave is becoming an increasing problem in the Home Assistant community. Would you consider doing a patch release with the new configs, or can you allow someone else to take a larger role in the project and issue those releases?

[dshokouhi]

Hello, I think another release would be great for the home assistant community. There are so many install flavors that a release from here would be the best way to get it out to everyone. The community would greatly appreciate all recent fixes as well :)

[bibi21000]

@rogersmj :
What is the problem with the workaround ?

[DubhAd]

The issue is that because of the way Hass.io works (Docker containers) people can't just apply the workaround themselves - they don't have access.

[rogersmj]

@bibi21000 Yep, exactly what @DubhAd said. Hass.io is becoming the preferred method to install HA because it's so relatively hassle-free and doesn't require you to muck around with server administration -- makes it more like an appliance, which is opening up HA to a lot more people. The downside is that anything that requires hacky workarounds -- modifying source/library files -- can't really be done on Hass.io. So we really need a new release of python-openzwave to incorporate all the latest device configs from openzwave's master branch to truly solve this.

[bibi21000]

Almost everything can be done with docker ;) I use to test python-openzwave installation :)
Which flavor is used for Hass.io ? Or does it use the make way to install python-openzwave ?
Do you have a link to the Dockerfile ?
Maybe devs can use git ou git_shared flavors: it will download the last openzwave release and build it for python-openzwave (https://github.com/OpenZWave/python-openzwave/blob/master/Makefile#L769)
It's also possible to use the shared flavor, but in this case devs must download openzwave and build it in the docker build process.
It's also possible to use docker's volume to let users updating configuration files
By the way, if you don't have access (by ssh or other method) to copy configuration files, I can't see how you can update the python-openzwave egg !

[bibi21000]

For the shared flavor, look at https://github.com/OpenZWave/docker-openzwave/blob/master/Dockerfile

[perosb]

I assume Hass downloads the package as a runtime dependency IF the user has enabled zwave. If the official package doesn't look for "shared" config files at all a custom package must be built like you say. That would be installed for all users then regardless if they want zwave or not.

Maybe it's possible to make "shared" default? If they exist in /etc otherwise fallback to bundled.

[rogersmj]

I don't know the intricacies of how Hass.io is setup. However before I came here and filed an issue I asked, explicitly, if such files as python-openzwave could be accessed/edited from the access level Hass.io provides via the SSH add-on, and was told unequivocally that they cannot. Which philosophically makes sense because such access would defeat the purpose of Hass.io, which is to hide all the dependency management and system administration and make it as bulletproof as possible.

[bibi21000]

@perosb : if it's impossible to add a simple --install-option="--flavor=git" to the install process of python-openzwave, I can't see how it should be possible to download/config/build openzwave before using the shared flavor
@rogersmj : you can also access of a docker image using bash
Can you provide a link on how the zwave package is download/build/installed ?