Ok so I ran the pip3 install --upgrade homeassistant and here’s the initial output
Exception:
Traceback (most recent call last):
File “/usr/lib/python3.5/shutil.py”, line 544, in move
os.rename(src, real_dst)
PermissionError: [Errno 13] Permission denied: ‘/srv/homeassistant/lib/python3.5/site-packages/certifi-2018.8.24.dist-info/DESCRIPTION.rst’ -> ‘/tmp/pip-xj7yxoru-uninstall/srv/homeassistant/lib/python3.5/site-packages/certifi-2018.8.24.dist-info/DESCRIPTION.rst’
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File “/srv/homeassistant/lib/python3.5/site-packages/pip/basecommand.py”, line 215, in main
File “/srv/homeassistant/lib/python3.5/site-packages/pip/commands/install.py”, line 360, in run
File “/srv/homeassistant/lib/python3.5/site-packages/pip/req/req_set.py”, line 778, in install
File “/srv/homeassistant/lib/python3.5/site-packages/pip/req/req_install.py”, line 754, in uninstall
File “/srv/homeassistant/lib/python3.5/site-packages/pip/req/req_uninstall.py”, line 115, in remove
File “/srv/homeassistant/lib/python3.5/site-packages/pip/utils/init.py”, line 267, in renames
File “/usr/lib/python3.5/shutil.py”, line 559, in move
os.unlink(src)
PermissionError: [Errno 13] Permission denied: ‘/srv/homeassistant/lib/python3.5/site-packages/certifi-2018.8.24.dist-info/DESCRIPTION.rst’
Rebooted the Raspberry Pi to allow Home Assistant finish the installation process.
0.82.1 is now installed. I was prompted to create a Name, UserID and Password which I did. It then requested my to Login and I supplied the UserId and Password I just created.I am now able to access the UI both inside and outside my LAN but have a persistent message displayed in the centre of the UI
“Login attempt or request with invalid authentication from 192.xxx.x.xx” which is my LAN address for the Raspberry Pi. I also get the same message displaying my web IP address when i attempt to login remotely.
My HADashboard will not display it’s icons displaying the message “entity not found etc,etc”. Clearly something needs to be changed in the appdaemon configuration to resolve this.
I’m wondering if anyone could shed some light on this.