update python-openzwave to 4.1.3#12057
Conversation
|
just an FYI but looks like we may be able to get a new |
|
@dshokouhi saw that too. Great if so. Though is says it won't update for |
|
Yeah, I saw that as well, and it would sort of work in that we could add something like a button in the front end zwave config to implement the update function. But as you say it won't work for shared and it also doesn't address how we handle upgrades. |
|
According to the docs it defaults to shared, but only if there’s a precompliled OZW library available. On a normal HASS install there shouldn’t be any (my guess??) so it should revert to embed thus the update function should work |
|
I did an other PR here #12060 which includes a service that invokes the update method. edit: I can see that it downloads the file and updates the edit: It might require a restart of HASS to use the updates...? |
|
FYI |
|
I don;t see any reason not to merge this, a lot of users have been looking for updated conifigs for quite a while. Thanks for adding this. |
|
This has been mistitled as 4.1.3 where it should be 0.4.3, isnt it? Just pointing it out because I read about it on the latest release changelog, but saw a different version being installed on the logs |
|
Yes. You are correct. |
Description:
update python_openzwave to latest version.
Checklist:
If the code communicates with devices, web services, or third-party tools:
toxrun successfully. Your PR cannot be merged unless tests passREQUIREMENTSvariable ([example][ex-requir]).requirements_all.txtby runningscript/gen_requirements_all.py.