bingobob
(Bingobob)
August 5, 2017, 12:29pm
1
Hi all,
flawless upgrades up to this point but I now can’t get past 0.49.0
When I upgrade like this…
sudo pip3 install --upgrade homeassistant
nothing works in 0.50.0
the logs fill up with this sort of thing.
ImportError: No module named ‘phue’
ImportError: No module named ‘speedtest’
ImportError: No module named ‘xmltodict’
etc
I go back to 0.49 to fix.
Pi3 if it matters
Be really grateful for any help, not sure what to do, stuck at 0.49.0 for now.
bb
PtP
(Mike)
August 5, 2017, 12:43pm
2
You are running hass as root?
bingobob
(Bingobob)
August 5, 2017, 12:59pm
3
as user pi by the looks…
pi@custard-pi:~/.homeassistant$ ps aux | grep hass
pi 665 13.3 5.0 223800 47660 ? Ssl 13:54 0:28 /usr/bin/python3 /usr/local/bin/hass
gpbenton
(Graham)
August 6, 2017, 5:11am
4
Most people run HA in a virtualenv. If you did, then sudo is not appropriate and you should just switch to the virtual environment and run the command without sudo.
If not, I think you need to describe your installation method, because otherwise we will be playing a game of 20 questions for a while.
bingobob
(Bingobob)
August 6, 2017, 6:15am
5
sounds like i might be best to blow out the existing install and reinstall in a virtualenv.
eek
maybe its the same error. I solved this by setting permissions to the new deps folder.
The deps folder has changed location to virtual environment.
Its located in: path/to/venv/lib/python3.6/site-packages
But where is my “path/to/venv”??. I installed HA with AIO installer.
Pls help
bingobob
(Bingobob)
August 6, 2017, 7:15am
7
gawd - i’ve blown out my existing install and using the virtualenv method…
like here…
now two problems…
starting it at reboot
i can’t even find the .homeassistant folder to add back my config
don’t really understand how to enter/exit the virtual env to config stuff.
double eeek.
bingobob
(Bingobob)
August 6, 2017, 7:51am
8
sorted the autostart by following this…
Newer Linux distributions are trending towards using systemd for managing daemons. Typically, systems based on Fedora, ArchLinux, or Debian (8 or later) use systemd. This includes Ubuntu releases including and after 15.04, CentOS, and Red Hat. If...
Reading time: 7 mins 🕑
Likes: 33 ❤
gpbenton
(Graham)
August 6, 2017, 9:35am
9
Assuming you have set up the directories the same
$ source /srv/homeassistant/bin/activate
will start the virtual environment, and
$ desactivate
will exit from it.
You only have to do this when using pip (or starting HA manually). Editing the config file you can do without the virtual environment.
Tinkerer
(aka DubhAd on GitHub)
August 6, 2017, 11:02am
10
That’ll be in /home/homeassistant
(or possibly /srv/homeassistant
, I’ve never used the manual install, but the All In One)
bingobob
(Bingobob)
August 8, 2017, 7:06am
11
Thanks Tinks,
Works a treat. Appreciate the extra explanation.
I’m on 0.50.2 now in a virtual environment and things seem to be going fine.
bb