I’ve recently installed home assistant using the all in one installer and I absolutely love it, I might have got a bit carried away and ordered all the zwave stuff I could find… problem is my most recent purchase fggc-001 the fibaro swipe isn’t supported in the version of openzwave I have installed but checking github config files it is in the latest.
How can I update the openzwave installed from the all in one installer?
I don’t think you can just update the openzwave installed. I think you have to clean it off and recompile. I’m sure someone will let you know. I would image though the AIO script is grabbing a specific build, you might have to assemble home assistant manually. Just save the configs
Hi I was looking for this as well, you have probably found out how to do this but I couldn’t find it on the site.
So this method works for me.
Log into your pi through SSH and put in the following commands.
- sudo su -s /bin/bash homeassistant
- source /srv/homeassistant/homeassistant_venv/bin/activate
- cd /srv/homeassistant/src/python-openzwave/
- git pull
- make build
- make install
If you deployed Home Assistant via the AiO installer prior to December 2016, replace sudo su -s /bin/bash homeassistant with sudo su -s /bin/bash hass and source /srv/homeassistant/homeassistant_venv/bin/activate with source /srv/hass/hass_venv/bin/activate
Good luck!
Edit:
One thing I forgot to mention, you also need to change your config_path in your configuration.yaml for me I had to update:
/srv/homeassistant/homeassistant_venv/lib/python3.4/site-packages/libopenzwave-0.3.1-py3.4-linux-armv7l.egg/config
to: /srv/homeassistant/homeassistant_venv/lib/python3.4/site-packages/libopenzwave-0.3.2-py3.4-linux-armv7l.egg/config
Also if you use the openzwave-control-panel you need to make sure this uses the new version as well. The config directory in /srv/homeassistant/src/open-zwave-control-panel is a symbolic link to the config_path. So if you update open-zwave you need to delete the symbolic link and create a new one. I did it like this:
cd /srv/homeassistant/src/open-zwave-control-panel
sudo rm config
sudo ln -s /srv/homeassistant/homeassistant_venv/lib/python3.4/site-packages/libopenzwave-0.3.2-py3.4-linux-armv7l.egg/config config
For anyone trying to do the upgrade, remember that if you are using Z+ you need to set your network key in the ./config/options.xml, just copy it from the old options.xml and restart
I ran through these steps but I am unsure if it is actually updating OpenZWave or only the Python layer for it? Before and after compiling it shows me the same version of 1.4.2497.
I am trying to get the OZW package to upgrade to 1.5 so that I can use some of the newly supported devices, is this possible or is this a limitation of using Python-OpenZWave in between the two systems?
Well Python open-zwave is going through some (nice) changes lately and apparently removing the Python3 branch is one of them. I get the same error now, while I didn’t get this error when I updated yesterday.
I believe the options are to either reinstall python open-zwave from scratch or wait until the next release of Home Assistant since I thought they will be using or including the Python Open-Zwave package in that release.
Thanks for your quick reply. I decided to ignore the error for now and just continue but then stumbled upon the issue of Pilight not working anymore (I have this issue: https://forum.pilight.org/Thread-Pilight-stopped-working-after-updating-RPi3)
So decided to abort everything and go back to my backup image of version 0.43.1.
I really wanted to upgrade to 0.44 because I just bought a rf door/window sensor and like to try the new Pilight Binary Sensor component.
Guess I’ll have to wait
Couldn’t you just run the Pilight Binary Sensor in /custom_components/binary_sensor/? I couldn’t wait for the Weather Underground and Octoprint updates so I’m running them in custom.
I saw all the issues with updating OZW so I figured I’d just sit this release out and wait.
Also if you use the openzwave-control-panel you need to make sure this uses the new version as well. The config directory in /srv/homeassistant/src/open-zwave-control-panel is a symbolic link to the config_path. So if you update open-zwave you need to delete the symbolic link and create a new one. I did it like this:
cd /srv/homeassistant/src/open-zwave-control-panel
sudo rm config
sudo ln -s /srv/homeassistant/homeassistant_venv/lib/python3.4/site-packages/libopenzwave-0.3.2-py3.4-linux-armv7l.egg/config config
As an added precaution when doing this, I recommend backing up that open-zwave-control-panel config directory with
cp -r config/ config-bak/
And then checking the version number of the libopenzwave by typing:
ls /srv/homeassistant/lib/python3.4/libopenzwave
Then hit tab to autocomplete. Use the directory it spits out in these commands:
cd /srv/homeassistant/src/open-zwave-control-panel
sudo rm config
sudo ln -s /srv/homeassistant/homeassistant_venv/lib/python3.4/site-packages/libopenzwave-0.3.2-py3.4-linux-armv7l.egg/config config
let me explain why I’m trying to do this and maybe I’m going about it wrong… A developer updated the Open Z-Wave Library today with a template for the ZSE33 and I wanted to get the device working correctly on my pi.
I thought it would be good to update the whole dir but even when I try to just copy a few files I get access denied. Do I need Root? if so how do I get that access?