Upgrade to 0.24 not reflected in ui

Configuration
1

I ran the command from 0.23.1
pip3 install --upgrade homeassistant

Results:
Collecting homeassistant
Using cached homeassistant-0.24.0-py2.py3-none-any.whl
Collecting sqlalchemy==1.0.14 (from homeassistant)
Collecting pip>=7.0.0 (from homeassistant)
Using cached pip-8.1.2-py2.py3-none-any.whl
Collecting voluptuous==0.8.9 (from homeassistant)
Collecting jinja2>=2.8 (from homeassistant)
Using cached Jinja2-2.8-py2.py3-none-any.whl
Collecting pyyaml<4,>=3.11 (from homeassistant)
Collecting pytz>=2016.4 (from homeassistant)
Using cached pytz-2016.6.1-py2.py3-none-any.whl
Collecting requests<3,>=2 (from homeassistant)
Using cached requests-2.10.0-py2.py3-none-any.whl
Collecting setuptools>=0.6b1 (from voluptuous==0.8.9->homeassistant)
Using cached setuptools-24.0.3-py2.py3-none-any.whl
Collecting MarkupSafe (from jinja2>=2.8->homeassistant)
Installing collected packages: sqlalchemy, pip, setuptools, voluptuous, MarkupSafe, jinja2, pyyaml, pytz, requests, homeassistant
Successfully installed MarkupSafe-0.23 homeassistant-0.24.0 jinja2-2.8 pip-8.1.1 pytz-2014.10 pyyaml-3.11 requests-2.9.1 setuptools-20.7.0 sqlalchemy-1.0.14 voluptuous-0.8.9

However, when I run hass it still shows 0.23.1.

2

Did you stopped hass before the pip3 upgrade?

3

yup. i did.

4

That’s weird, I didn’t had any issue when upgrading. Did you used sudo before in any step when installing? Also, where do you check HA version when running?

5

What is the output from hass --version ?

6

Are you using the All In One Installer, and if so, did you activate your virtual environment before upgrading?

7

I ran the update as the local user.
I only use sudo to launch hass.

8

williamp0044@Set:~$ /srv/hass/bin/hass --version
0.23.1

9

Not using the all in one.
But this helped to solve the issue.

I originally did a fresh install on ubuntu. Following the instructions on https://home-assistant.io/getting-started/installation-virtualenv/
But over time switched from using the ‘hass’ user to using the local user to run homeassistant. When I upgraded, i thought it would be fine to upgrade under the local user but it wasnt. Upgrades still have to be done in the virtualenv even if i’m not using the ‘hass’ account.