I have AIO install before decemberso i basically just have to change homeassistant to hass. my only fear is z wave as 89% of my setup is based on it … don’t wanna break it 
anyway i am actually at 78 / 405 for python 3.6 so i still have time
welll didn’t work for me 
No module named vent.main; ‘vent’ is a package and cannot be directly executed
Sorry I must have typoed it, it shoudl be venv not vent
python3.6 -m venv /srv/homeassistant
Note : just fixed it in the original.
1 Like
fuck and i took my backup now to fiy trhis again let me try again after backup has successfully been written on sd card
I should be online for a while unless someone walks in and actually wants me to work on something at work. I’ll try and watch for any messages in case you run into any other problems. But please make sure you have a good backup before moving forward…
don’t u wory my raspi makes backups each sunday… so freeeeshhhhhhHhh and yes… BE ONLINE MATE!!!
$ sudo apt-get install build-essential tk-dev libncurses5-dev libncursesw5-dev libreadline6-dev libdb5.3-dev libgdbm-dev libsqlite3-dev libssl-dev libbz2-dev libexpat1-dev liblzma-dev zlib1g-dev
this is necesary to build paython 3.6. can u add those to the first post?
Done thanks
YOu might want to mention that the config path changed with python-openzwave mine looks like:
/srv/hass/hass_venv/lib/python3.6/site-packages/python_openzwave/ozw_config
after upgrading hass it install python-openzwave again … so i let it run and will see what happens
I sucessfuly upgraded… everything works now! COOL and 1000 thanks!
1 Like
I have been trying to follow this thread as it sounds like this might be a mandatory upgrade at some point. I also have AIO installed prior to Dec 2016. Can you tell me how accurate are the steps above to do this upgrade? It does seem a little involved and following this thread it seemed like there have been some challenges along the way. Do you feel everything is accurately depicted in the instructions above? Also, how difficult do you feel it was to get through this upgrade? Really fearful of impacting a perfectly running system. Thx
it is like described above … with the new config path for zwave i posted earlier. it takes justa bit time but works fine . take care of the “-” in the post … those are wrong and must be “–” then i face zwave plus issues where network key was disabled by default after upgrading. i added it again but my devices won’t react … investigating on this
After re-reading this a few times and I might be confusing myself but are you including the “openzwave” upgrade because you are still using the separate openzwave program? With openzwave now integrated with HA I thought that wouldn’t be needed? When I went to 0.47.1 I removed my config_path since it now defaults to the correct path that it was installed with. Is that piece needed as part of the upgrade to 3.6? Just trying to understand all of the steps above - thx
join the chat … it is easier there
I do IT for living and have some familiarity with linux. I only say that to level set that my level of frustration with this might be different than yours. Of me, it wasn’t that bad, I was nerve racking at points where I had my fingers crossed. This is not “required” right now, and I expect that when it is required, the HA devs will give some more concrete explanation of how to do it. The good thing is, this is creating a new virtual environment so you technically don’t have to delete the old one. You can just name your new one something different and change the startup scripts to run the new name instead of the old name. Also do a good backup first, and if you aren’t sure of that back, do another one on another sd card or something.
1 Like
actually those are --'s Mac notes apparently converted them to one line when I typed them in as I was doing it. Sorry
It seems to depend on whether you had openzwave installed before going to 47 or not. I had it installed so it used the path I had for my old openzwave config. I would like to get it back to the standard HA one, but haven’t gotten an answer to my question in another post about where it should be…
Sorry I would have joined however we had a power outage here just at that time and I am finally able to get back to this after having to fix my HA setup/with Alexa.
Thanks for the additional information. I applaud you for going forward with the upgrade however I have a feeling I will wait and hopefully as you say the HA Devs will come up with something to make it less frightening. I have enough knowledge to be dangerous but I also know my limitations when unsure. Have you noticed any difference since you have upgraded?
To be honest I don’t feel any performance increasing or more stability for the moment I’m struggling with my zwave plus devices and wondering if I reset my network to start from scratch in zwave if I can’t get it work
No difference. But I really didn’t expect any. There was an issue with the myq app not working under 3.4 that pushed me over the edge. So I went ahead and upgraded to the version the dev was using. Good news is myq works for me again. Bad news apparently appdaemon still requires 3.5 so I had to setup another virtual environment for appdaemon and install 3.5 into it. LOL Now I have python 2.7, 3.4, 3.5 and 3.6 all running happily together. I just setup a virtual machine using whichever one I want and it works just right.
1 Like