@penright: Make sure you’re doing it from inside the virtual environment, are you running hassbian or from the AIO?
hassbian
No, I was not.
Before I go back and update the start of the hassbian cheetsheet,
How does this look …
I know you said AIO, but lets try it on hassbian. 
Edit: +2 This is what I going to try this time.
hassctl stop
hassctl update-hass
sudo su -s /bin/bash homeassistant
source /srv/homeassistant//bin/activate
cd /srv/homeassistant/src/python-openzwave
make install
exit
hassctl start
Stay tune for results.
For the AIO installed version it’s:
sudo su -s /bin/bash homeassistant
source /srv/homeassistant/homeassistant_venv/bin/activate
cd /srv/homeassistant/src/python-openzwave
make install
I had tried that and it was still not preserving the rename and the node. I then used OZWCP to rename the node and that seems to have persisted it. I can now restart HASS and the Linear GDO is persisted.
Now I need to try removing my Zooz multi sensor and re-adding it with OZWCP because it’s reporting as unknown right now.
Is the Linear GDO supposed to show up as an unknown device? I know the Zooz has a config entry so it shouldn’t show up as unknown, so I’m gonna try to fix that. But the Linear still shows up as unknown, but it works.
I just rename it in the xml files to ‘Garage Door’ 
but yes it shows up like that initially.
Ran through the steps and this is my output …
https://hastebin.com/eraniserox.coffeescript
Need to give it more time, but for now I heading home.
So I took a snippet of the homeassistant log incase I can not get to it in the morning
https://hastebin.com/fotozewafu.sql
Update:
Hass came up, but not the garage door.
Here is the current log: https://hastebin.com/hanohavuvo.sql
As you can see zwave is working from node 6, but node 12 (garage door) is back to getting the class 66 error.
2017-08-08 12:46:58.101 Info, Node006, Received SensorMultiLevel report from node 6, instance 1, Temperature: value=72.5F
2017-08-08 12:46:58.101 Detail, Node006, Refreshed Value: old value=72.5, new value=72.5, type=decimal
2017-08-08 12:46:58.101 Detail, Node006, Changes to this value are not verified
2017-08-08 12:46:58.101 Detail, Node006, Notification: ValueChanged
2017-08-08 12:52:24.750 Detail, Node012, Received: 0x01, 0x08, 0x00, 0x04, 0x00, 0x0c, 0x02, 0x98, 0x40, 0x25
2017-08-08 12:52:24.750 Info, Node012, Received SecurityCmd_NonceGet from node 12
2017-08-08 12:52:24.750 Info, NONCES: 0x5d, 0x49, 0x54, 0x17, 0x6d, 0xef, 0x95, 0x43
2017-08-08 12:52:24.750 Info, NONCES: 0xc4, 0xb2, 0x1f, 0xaf, 0x62, 0xc6, 0xf1, 0xea
2017-08-08 12:52:24.751 Info, NONCES: 0xdc, 0x34, 0xcb, 0x8c, 0x4c, 0xe7, 0xe8, 0xdf
2017-08-08 12:52:24.751 Info, NONCES: 0x80, 0x93, 0x29, 0x46, 0xdd, 0x7e, 0x76, 0xd9
2017-08-08 12:52:24.751 Info, NONCES: 0x7f, 0x4a, 0x2e, 0xaf, 0xba, 0x23, 0x9a, 0x7e
2017-08-08 12:52:24.751 Info, NONCES: 0xd6, 0xb9, 0x2d, 0x38, 0x7f, 0x1f, 0x23, 0x5c
2017-08-08 12:52:24.751 Info, NONCES: 0x53, 0xee, 0xe8, 0x9f, 0xd6, 0xd1, 0x7e, 0x55
2017-08-08 12:52:24.751 Info, NONCES: 0x65, 0xa8, 0x9b, 0x42, 0x26, 0x12, 0x1b, 0xa5
2017-08-08 12:52:24.751 Info, Node012, Sending (Send) message (Callback ID=0x01, Expected Reply=0x00) - Nonce_Report - 0x01, 0x11, 0x00, 0x13, 0x0c, 0x0a, 0x98, 0x80, 0x5d, 0x49, 0x54, 0x17, 0x6d, 0xef, 0x95, 0x43, 0x05, 0x01, 0xe4:
2017-08-08 12:52:24.760 Detail, Received: 0x01, 0x04, 0x01, 0x13, 0x01, 0xe8
2017-08-08 12:52:24.760 Detail, ZW_SEND_DATA delivered to Z-Wave stack
2017-08-08 12:52:24.776 Detail, Received: 0x01, 0x07, 0x00, 0x13, 0x01, 0x00, 0x00, 0x02, 0xe8
2017-08-08 12:52:24.776 Detail, ZW_SEND_DATA Request with callback ID 0x01 received (expected 0x01)
2017-08-08 12:52:24.794 Detail, Node012, Received: 0x01, 0x1d, 0x00, 0x04, 0x00, 0x0c, 0x17, 0x98, 0x81, 0xf8, 0xb6, 0x53, 0x98, 0x20, 0xb3, 0x0f, 0x7c, 0x58, 0x97, 0xe6, 0x04, 0x5d, 0x5f, 0x72, 0x69, 0x84, 0xf0, 0x85, 0x79, 0xe9, 0xd4
2017-08-08 12:52:24.794 Info, Raw: 0x98, 0x81, 0xf8, 0xb6, 0x53, 0x98, 0x20, 0xb3, 0x0f, 0x7c, 0x58, 0x97, 0xe6, 0x04, 0x5d, 0x5f, 0x72, 0x69, 0x84, 0xf0, 0x85, 0x79, 0xe9, 0xd4
2017-08-08 12:52:24.794 Detail, Node012, Decrypted Packet: 0x00, 0x66, 0x03, 0xff
2017-08-08 12:52:24.794 Detail,
2017-08-08 12:52:24.794 Info, Node012, ApplicationCommandHandler - Unhandled Command Class 0x66
The garage door zwave has not worked since upgrading to 50.2.
Also every time I shut it down to try and restart SSH fails to connect.
I have to go back to an image I saved with 48.1 before I loaded 50.2. When I do all works again.
Check your venv location:
49. homeassistant@hassbian:/home/pi $ source /srv/homeassistant/homeassistant_venv/bin/activate
50. bash: /srv/homeassistant/homeassistant_venv/bin/activate: No such file or directoryWas that in the first log?
The second one did not show it.
Sorry, have to ask, check it how?
Yes, it was in the first log. You need to track down where bin/activate lives. In my case it is: /srv/homeassistant/bin/activate
What is the bin active? What am I looking for?
Since it was not in the other logs, would that mean it is ok?
Just to be clear I had all working with 48.1, it is only trying to go to 50.2.
I may just restore me 48.1 and wait till the next release. The only thing in this release for me was the barrier fix.
Example:
sudo su -s /bin/bash homeassistant
source /srv/homeassistant//bin/activate
cd /srv/homeassistant/src/python-openzwave
make install
I am only making guesses here as you’re running Hasbian and I’ve done my install via the AIO script.
@gentoosu I would assume is running hasbian like you are.
We have a winner !!!
Here is a complet log of my expericane. There were some errors, but if it passes perreview then we have a hassbian cheetsheet. 
https://hastebin.com/savisatuso.lua
@gentoosu I am sooooo sorry, I was not following, I thought it was something to do with booting.
You both get brownie points.
Ah the permission denied errors, that’s just because the directory needs to be chowned to homeassistant.
Command:
chown -R homeassistant:homeassistant /srv/homeassistant/lib/python3.4/site-packages/openzwave-0.4.0.35-py3.4.egg
should fix it up for the future.
So I have a brand new RPi I’ve been wrestling with. I have figured out how to do it via AIO, Hassbian as well as HASSIO.
What I have not figured out is how to get this to work. I’ve tried all the scripts in all different fresh installs. I just can’t figure it out. I don’t know C/C++ so that doesn’t help.
Do we have some fresh up to date instructions on a fresh install of either AIO or Hassbian? Either is fine for me.
I have no other devices right now besides some window sensors. I have that all good in a yaml with HA. Just need to figure out the garage door opener. That’s supposed to be my first automation item!
You might want to look 2 posts up from yours
I tried it. It didn’t work
Patch for those running docker images. Adding these lines:
> RUN pip3 uninstall -y python-openzwave && \
> pip3 install 'python_openzwave==0.4.0.31' --install-option="--flavor=ozwdev"
> RUN mv /usr/local/lib/python3.6/site-packages/python_openzwave/ozw_config/options.xml /usr/local/lib/python3.6/site-packages/python_openzwave/ozw_config/options.xml.orig
> RUN ln -s /config/options.xml /usr/local/lib/python3.6/site-packages/python_openzwave/ozw_config/options.xml
before the copy source line and the docker image will install the dev version of ozw and work with the opener.
Just need to make sure that the 0.4.0.31 matches what ever is in requirements_all.txt for python-openzwave.
how would one go about installing the docker images vs AIO etc
If you have read through this thread you will know it hasn’t been easy for anyone. You will also note that people have posted what they did and indications of what failed. “It didn’t work” isn’t a complete response.
I read every single post. I have tried every single script with every single variation of reply.
Closest I got was Hassbian using post 125, but I cannot get OZWCP to compile
There are plenty of posts that claim “oh do this and this script and it works” and maybe it did when they wrote the script, but now it just doesn’t.