ozwdev is the flavor that works with the GDZ00-4
1 Like
I’m still getting this error trying to install flavoe ozwdev
Command “/usr/bin/python3 -u -c “import setuptools, tokenize;file=’/tmp/pip-build-c3hnntkk/PyDispatcher/setup.py’;f=getattr(tokenize, ‘open’, open)(file);code=f.read().replace(’\r\n’, ‘\n’);f.close();exec(compile(code, file, ‘exec’))” install --record /tmp/pip-j86iun7t-record/install-record.txt --single-version-externally-managed --compile --flavor=dev --user --prefix=” failed with error code 1 in /tmp/pip-build-c3hnntkk/PyDispatcher/
Try a pip install pydispatcher
heres a “dumb” question, do I need to do any of this as the my home assistant user account? I’m running in a python vm
You execute all these commands from inside your python venv.
I’ll post a script to be used to make this a bit easier for everyone once I get home.
1 Like
Here’s a script to run the install:
#!/bin/bash
if [ "$(id -u)" != "0" ]; then
echo "This script must be run with sudo. Use \"sudo ${0} ${*}\"" 1>&2
exit 1
fi
echo "Changing to user homeassistant"
sudo -H -u homeassistant /bin/bash <<EOF
echo "Activating virtual environment"
source /srv/homeassistant/homeassistant_venv/bin/activate
# install cython if not already installed
pip3 install --upgrade cython==0.24.1
# remove previously install python_openzwave
pip3 uninstall -y python_openzwave
# install ozwdev flavor of python_openzwave
pip3 install --no-cache-dir 'python_openzwave==0.4.3' --install-option="--flavor=ozwdev"
echo "Deactivating virtual environment"
deactivate
EOF
exit 0
1 Like
I wanted to take the time to thank you for the steps. I was definitely doing it wrong. Main issue was I never ran this from the VM as Home assistant. Once I did that, it all worked great. I have not added my garage door opener yet, but will take care of that tonight. I’ll report back if I have any issues, but I suspect I will not. 
Make sure you are using the “Add Secure Node” button and have a network key setup 
Good deal, thanks for that. I do have a key setup, but did not think about this being a secure node.
Any entry device requires it.
Let us know how it goes.
1 Like
OK, I added it, I have 5 sensors, but not sure how to actually open it. haha. I’m sure it’s easy, this is the first device of this kind I have added, so I’m sure its just me. But if you have a quick, duh, do this bit of info, I’ll take it.
This is what I am seeing. I did not have
cover:
zwave
in my configuration.yaml, so I removed and readded secure. It seems to add, but what else do I need to do?
I’m running 67.1 and have updated the zwave component as instructed above.
I’ve read much of the comments above, but many of the comments seem to be outdated.
Thanks
What does the first line of your ozw_log.txt say?
018-04-28 17:18:06.527 Always, OpenZwave Version 1.4.2926 Starting Up
Any you didn’t have Home Assistant running while running the commands right?
I dont believe so, but I can run them again.
Hmm, that might have been it. I swore I had it stopped, but when running the install I got a message about .43 being unintstalled, then .44 was installed. So, I’m going to remove and readd. Do I need to do anything special for the Cover to appear for me to be able to open or close the door?
Thanks again
So, no difference, Here is one “weird” thing though. When I upodated to 0.4.4, I went back and the garage door nodes seemed to be named properly, they did not have the word unknown in them. I still did not have any way that I could see to open or close the door, so I removed and did a secure add, it added, and now everything says unknow again just like in the picture above.
I’ve scanned through most of these posts. I need to do anything other than run the few commands(the script you provided), right?
Is this what I should see as the first line?
018-04-28 19:52:58.100 Always, OpenZwave Version 1.4.2926 Starting Up
If not, what should I see.
I will say that I had one minor difference
My vm path was different from
/srv/homeassistant/homeassistant_venv/bin/activate
$ sudo su -s /bin/bash homeassistant
$ cd /srv/homeassistant
$ source bin/activate
I did that instead? Would that cause any issues? I dont think so, but maybe otherthigns expect a different path?
My version shows up as 1.5.2717.
Did you get any errors while it was compiling?
Check for similarly named: libopenzwave.cpython-35m.so the numbers could be diffrent.
Example location: /srv/homeassistant/homeassistant_venv/lib/python3.5/site-packages/libopenzwave.cpython-35m.so
You can remove this file and re-run the commands to make sure it gets recompiled.