Core: openzwave configuration are old due since python-openzwave flavour uses the embedded

[perosb]

python-openzwave is a wrapper around open-zwave.
python-openzwave haven't done any new releases lately since there hasn't been any changes to the wrapper.

However, configuration changes happen frequently as new devices are added and configured.

hass and hass.io should have a way to use more up to date configurations from https://github.com/OpenZWave/open-zwave repository.

There is a issue open with python-openzwave here https://github.com/OpenZWave/python-openzwave/issues/105

There are different solutions like having a custom installed flavour of python-openzwave which can use shared configs from /etc/openzwave
pip install python_openzwave --install-option="--flavor=git" etc.

@pvizeli might have more information how this can be done in hass.io

[tschmidty69]

I'll just copy my comment here for reference:

I get that the code itself hasn't changed but the git has configs that do need updating. HA has made a decision to not create dependencies on git repositories and only use packages that are released and available via pip for what seems to me a pretty valid reason. Using pip to install from git isn't the right way to do it since it would still leave users with different versions of the config depending on when they installed or updated HA. This would be unsupportable because it gives no way for us to ensure version X has X configs. We also have no way to update down the road since the version number doesn't change, so we would need to do something hacky like rerun the pip install every time for just this package. Even having the ability to use configs from /etc/openzwave like in the dev version is a lot less clean since we would need to do something to ensure those were updated and also breaks some of the philosophy of using virtualenvs to segregate things.

There are certainly ways this can be done, but it seems like the wrong approach to take to me.

[rwa]

I'm not necessarily advocating for this, but you can pip install from a specific commit in a github repo.

I'm not sure what the best way forward is. But it would certainly be very useful to have faster turnarounds with zwave support improvements.

[dshokouhi]

just an fyi but take a peak at their latest commit ;)

[simonk83]

Who's commit? HA, python-openzwave, or open-zwave :D

[perosb]

Updated configs was merged in https://github.com/home-assistant/home-assistant/pull/12057

A potential "fix" long term to update would be https://github.com/home-assistant/home-assistant/pull/12060 which pulls the configs from git.

[ryanm101]

Using pip to install from git isn't the right way to do it since it would still leave users with different versions of the config depending on when they installed or updated HA. This would be unsupportable because it gives no way for us to ensure version X has X configs.

Could we not "grab" a commit ID and do something like git checkout ID -> pip install ?
Then we have tied to specific version on our release

[balloobbot]

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates.

Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment :+1: