That is what I did and everything came back. I had to uninstall and secure install the garage door after the upgrade. I have noticed that the frontend is not updating the status of my zwave devices as quickly as it used too. I have a notification that texts me the status of certain things a minute and a half after they occur and the states are wrong.
And I did upgrade my github for anyone interested.
So just to make sure I’m on the same sheet of music.
Is the 0.4.9 version with the cover files added. 
Awesome, thanks for that!
Yes sir, should be…only need to change 0.4.3 to 0.4.9 in my instructions above.
Let me know if you have any issues.
And I had to remove and re-add the node
When I get to doing this I’ll let you know if I have to remove/readd as well
Thanks so much. I updated my fork, and also took the time to add this update for clearing user codes for schlage locks.
Just curious to see if that works!
Awesome. I get so much help from people between discord and the forum. This is my very small (very very very) niche to give back. Happy it helps people.
There are a couple things I would like to add but I can’t figure out where they are. Somewhere there is an update to thermostats to add something I forgot lmao…I gave up trying.
Edit: I think it is ThermostatSetpointClass
I removed my garage door from HA, changed my Dockerfile to reflect 0.4.9, deleted the pyozw.sqlite file, rebuilt the image and started the container, re-added the garage door and the only thing coming up is the sensors and the zwave.xxxx. The cover doesn’t show up. I even tried reverting everything back to 0.75.3. I guess I could just use my backup files and do a re-add under 0.75.3 but this is super frustrating. IDK what else I could be missing.
I did just check the logs and I’m getting this.
Secure CommandClass 0x66 - NOT SUPPORTED - 0x66 is BARRIER!
@pdobrien3 I have always used your repo and for kicks I did a pull just to ensure I had the latest updates. IDK what else to look for. Any ideas?
My config/dockerfile is below.
FROM homeassistant/home-assistant:latest
ENV LOCAL_OPENZWAVE=/usr/local/share/open-zwave
COPY /open-zwave $LOCAL_OPENZWAVE
RUN set -e && \
pip3 uninstall -y python_openzwave && \
pip3 install --upgrade cython==0.24.1 && \
pip3 install --no-cache-dir python_openzwave==0.4.9 --install-option="--flavor=dev"
<Node id="73" name="" location="" basic="4" generic="64" specific="7" type="Secure Barrier AddOn" listening="true" frequentListening="false" beaming="true" routing="true" max_baud_rate="40000" version="4" secured="true" query_stage="Complete">
<Manufacturer id="14f" name="Linear">
<Product type="4744" id="3030" name="GD00Z-4 Garage Door Opener Remote Controller" />
</Manufacturer>
It’s secure as well. There has to be something referencing something, somewhere.
EDIT and RESOLVED: Well, I sat here thinking… what else could I be missing. Then it hit me. I had an issue where another component had its version updated and for some reason, files got stored in my deps folder. I run HA on Docker so anything in deps really shouldn’t be there. Soon as I wiped it, rebuilt the image and container and refreshed the node, the cover came back!!! Hope this helps anyone else!
Awesome. Sorry for the late response. Happy it helped.
Been waiting for this! Looks like there isn’t an agreement on the method yet. Personally I don’t care about specs LOL. I want any method of deleting the user code
NP and thank goodness I got it working again!
I was able to get this done!! And I did not have to remove and readd, athought I did do a heal network, then heal the device, then a restart. And I was suprised to see that it came back.
Thanks Again for the help with this
Update: I tested this lock clear usercode PR and it worked great!
I’m thinking of getting one of these to replace my OpenGarage (keeps disconnecting from wifi as of late). Are these still a pain to setup or is it mostly plug and play now?
Depends on how much “pain” a couple of commands can be 
It’s very easy for virtual environment installs, slightly more difficult for docker/HassIO users.
Instead of hardcoding the python_openzwave version into your scripts/Dockerfiles you could do this to always install the version that HomeAssitant requires:
hassVer=`pip3 show homeassistant | grep Version | cut -f2 -d' '`
curl -LO "https://raw.githubusercontent.com/home-assistant/home-assistant/$hassVer/requirements_all.txt"
pip3 install --no-cache-dir --constraint requirements_all.txt python_openzwave --install-option="--flavor=ozwdev" --no-deps
The first line finds out what version of home assistant you have installed, that’s assuming you installed it with pip3.
The second line fetches the requirements file from git specific to the version of home assistant you have installed.
The third line installs python_openzwave, using the requirements file as a constraints file, meaning it will install the version specified in the requirements file.
For more info on pip constraints file check this. Note that the constraints file can be named anything you want and has the same/similar format as the requirements file.
No more hardcoding versions FTW!
I have what is probably an “obvious” question.
I get confused by the versions and the and the installs
For example, I get that open-zwave is on 1.4.xx and that 1.5.xx is the dev version on git hub, and that 1.6.xx is the future “new/current” version.
But how does that relate to 0.4.3 vs 0.4.9
I’m doing my own git repository with 1.4.xxx with a few files updated for this opener, but just confused how that ties into python_openzwave.
Thanks for clarifying
0.4.9 is the version of Python_OpenZwave, it’s a python wrapper for communicating with the openzwave stack.
Hey folks. Was wondering if I could get a hand. I’ve been using a version of the ozw library I built myself for a while now but as all things change during the last upgrade I tried the “flavor” method to catch up as I haven’t rebuilt the library in some time. And ran head long into the the following which flat out kills HASS and leaves me stuck. I’ve attempted to roll back to 0.4.8 with the same results. I may try to go back a little further. I’m afraid its an issue with openzwave itself (not to be confused with python-openzwave) which could complicate things. Any help is appreciated.
Sep 19 20:46:17 Hostname hass[5031]: 2018-09-19 20:46:17.949 Warning, Exception: Manager.cpp:2607 - 102 - ValueID passed to GetValueFloatPrecision is not a Decimal Value
Sep 19 20:46:17 Hostname hass[5031]: terminate called after throwing an instance of ‘OpenZWave::OZWException’
Sep 19 20:46:17 Hostname hass[5031]: what(): Manager.cpp:2607 - CannotConvertValueIDError (102) Msg: ValueID passed to GetValueFloatPrecision is not a Decimal Value
Sep 19 20:46:18 Hostname systemd[1]: [email protected]: Main process exited, code=killed, status=6/ABRT
Sep 19 20:46:18 Hostname systemd[1]: [email protected]: Failed with result ‘signal’.
Flavor Method
pip3 install --no-cache-dir python_openzwave==0.4.9 --install-option=“–flavor=ozwdev”
Homeassistant 0.78
Maybe try uninstalling openzwave, then start HA. it should see it’s missing and install the normal version.
If that works, then stop HA and install the dev flavor again
No joy. Did just as you suggested. It works fine with the default version 1.4.3142. Unfortunately as we know we need 1.5 to get cover support. I’ll keep digging but I’m open to suggestions.