Python upgrade

DavidFW1960 · June 9, 2019, 12:13am

That will most likely be this week as Buster is set for release within days.

dhaker · June 9, 2019, 1:47am

I got mine working on a PI Raspbian All In One Installer Hassbian with the following script.

home-assistant/hassbian-scripts/blob/dev/docs/suites/python.md

_Scripts used in the Hassbian image._

***

[HOME](/hassbian-scripts/) | [**SUITES**](/hassbian-scripts/suites) | [HASSBIAN-CONFIG (CLI)](/hassbian-scripts/cli) | [CONTRIBUTE](/hassbian-scripts/contribute)

***

# Python

~~This script will upgrade Python and Home Assistant to the latest stable version.\
It will also create a new virtual environment to be used for Home Assistant.\
_This upgrade takes long time to finish, on an Raspberry Pi 3
this takes about 1 hour._~~

To upgrade python have a look here https://www.home-assistant.io/blog/2019/07/19/piwheels/#option-1



## Additional info

This file has been truncated. show original

flamingm0e · June 9, 2019, 4:07am

Sure it will. You just have to do it differently. Use SSH commands to the host to run, or bind mount the binary files needed to run VLC directly.

You sure about that? I use postgresql and it works just fine. Hassio uses the same home assistant docker image and it will communicate with MySQL just peachy.

hp1 · June 9, 2019, 4:00pm

I have to upgrade Python 3.5.3 to the latest version. I’m using Hassbian so I tried :
“sudo hassbian-config upgrade python”
But I got this message: “suite python doesn’t exist”
Can you help me? (I’m a beginner)
Thanks

kbahey · June 9, 2019, 6:06pm

This is the first time I use Docker, and the above two components did not work with my exact same configuration that worked for over a year with venv.

Since Raspbian Buster is around the corner, I will not bother with Docker anymore, and just upgrade to Buster and get a newer Python version that way.

kbahey · June 9, 2019, 6:07pm

Thanks. That is the easiest upgrade path. Please post here when it is out.

flamingm0e · June 10, 2019, 11:55am

Like I said. You have to think the docker way, and stop trying to force the old methods on it.

firstof9 · June 10, 2019, 5:24pm

Whipped up a bash script if anyone wants to give it a whirl

github.com

firstof9/raspberry_python_updater/blob/master/python_update.sh

#!/bin/bash

path=
version=
shortversion=

function pause(){
   read -p "$*"
}

download_python()
{
    if [ ! -f "Python-$version.tgz" ] then
        wget https://www.python.org/ftp/python/$version/Python-$version.tgz
        status=$?

        if [ "$status" -gt 0 ]; then
            echo "Error downloading file."
            exit 1
        fi

This file has been truncated. show original

It installs to /usr/local/opt so it won’t bother an official python3.7 install once one’s available.
I’ve tried to incorporate suggestions to have it reinstall the python modules for you as well.

kbahey · June 10, 2019, 10:35pm

Totally disagree: users should have a choice. If I wanted easy, I would use Hassio. I wanted “familiar” and “reliable”, and therefore chose a plain vanilla Raspbian install with venv.

“Old” does not necessarily mean “bad” or “obsolete”. It can also mean “mature”, “well tested”, and “trustworthy”. The .deb way of installing things has been proven for ~ 25 years and is used by millions of professional servers.

The venv way is on the web site as a way to install HA, and it worked fine for over a year.

Once Buster is released, this issue goes away, and no need to fight with Docker to get what I had working before and broke down, to work again.

kadfils · June 11, 2019, 11:29am

I ran into the same problem and have fixed by upgrading the home assistant and hassbian-scripts as follow:

sudo hassbian-config upgrade hassbian => to upgrade Home Assistant first
sudo hassbian-config upgrade hassbian-script => to upgrade hassbian-scripts

Regards
Kadfils

hp1 · June 12, 2019, 12:07am

Thank you very much for your help, but it still does not work. (?)
I have managed to install Python 3.7.3 successfully, but in the Home Assistant version 3.5.2 still appears. Do you know why? There must be a way to correct this. My problem is that I am a beginner and there are many things that I do not know. I do not know what to do. I have made several attempts following the advice of people in the forum, but I can not solve the problem.

Regards

ConcordGE · June 12, 2019, 10:09am

In a separate post from @bosbourne he listed a successful method of upgrading Python to 3.7.3 with Hass in situ. It has worked for a number of users.

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
wget -O /tmp/Python-3.7.3.tar.xz https://www.python.org/ftp/python/3.7.3/Python-3.7.3.tar.xz
cd /tmp
tar xf Python-3.7.3.tar.xz
cd Python-3.7.3
./configure
sudo make altinstall
sudo apt -y autoremove
cd
rm -r /tmp/Python-3.7.3
rm /tmp/Python-3.7.3.tar.xz
sudo systemctl stop [email protected]
sudo mv /srv/homeassistant /srv/homeassistant_old
sudo mkdir /srv/homeassistant
sudo chown homeassistant:homeassistant -R /srv/homeassistant
cd /srv/homeassistant
/usr/local/bin/python3.7 -m venv .
source bin/activate
pip install wheel homeassistant

20a. ** Note I chose to run hass first time to see all the installation messages.**

20b. sudo systemctl start [email protected]

bastienh · June 12, 2019, 5:15pm

works well for me, thank you very much !

hp1 · June 12, 2019, 10:46pm

Thank you very much. After the upgrading Python to 3.7.3 my Home Assistant won’t start!

"$ sudo systemctl status [email protected]
? [email protected] - Home Assistant for homeassistant
Loaded: loaded (/etc/systemd/system/[email protected]; enabled; vendor preset: enabled)
Active: failed (Result: exit-code) since Thu 2019-06-13 00:08:52 CEST; 10min ago
Process: 540 ExecStart=/srv/homeassistant/bin/hass (code=exited, status=1/FAILURE)
Main PID: 540 (code=exited, status=1/FAILURE)

jun 13 00:08:51 hassbian systemd[1]: Started Home Assistant for homeassistant.
jun 13 00:08:52 hassbian hass[540]: Traceback (most recent call last):
jun 13 00:08:52 hassbian hass[540]: File “/srv/homeassistant/bin/hass”, line 6, in
jun 13 00:08:52 hassbian hass[540]: from homeassistant.main import main
jun 13 00:08:52 hassbian hass[540]: ModuleNotFoundError: No module named ‘homeassistant’
jun 13 00:08:52 hassbian systemd[1]: [email protected]: Main process exited, code=exited, status=1/FAILURE
jun 13 00:08:52 hassbian systemd[1]: [email protected]: Unit entered failed state.
jun 13 00:08:52 hassbian systemd[1]: [email protected]: Failed with result ‘exit-code’."

Do you know what is happening?. What to do to correct the error?

ConcordGE · June 12, 2019, 11:43pm

Are you starting HS from a service daemon. If so where is the path pointing to. Once you have rebooted your Pi type

sudo systemctl status [email protected]

Paste the output here.

hp1 · June 13, 2019, 11:01am

You know, I did a new installation of Python 3.7.3 following the 20 steps you sendt to me. After the 19. step when its finished, I got this error:

Could not install packages due to an EnvironmentError: [Errno 13] Adgang nægtet:
‘/srv/homeassistant/lib/python3.7/site-packages/wheel’
Consider using the --user option or check the permissions.

What to do? It is work if I use --user? (pip install wheel --user).

ConcordGE · June 13, 2019, 11:14am

Yes pip is telling you what to do here.

hp1 · June 13, 2019, 12:03pm

After the install (pip install wheel --user) I started the home assistant service ( $ sudo systemctl start [email protected]). The Home Assistant it’s NOT starting! You can se it in the log:

pi@hassbian:~ $ tail -30 /var/log/syslog
Jun 13 13:00:01 hassbian CRON[22947]: (pi) CMD (~/duckdns/duck.sh >/dev/null 2>&1)
Jun 13 13:00:01 hassbian CRON[22948]: (pi) CMD (/home/pi/certbot/certbot-auto renew --quiet )
Jun 13 13:01:56 hassbian CRON[22938]: (CRON) info (No MTA installed, discarding output)
Jun 13 13:05:01 hassbian CRON[23280]: (pi) CMD (~/duckdns/duck.sh >/dev/null 2>&1)
Jun 13 13:10:01 hassbian CRON[23338]: (pi) CMD (~/duckdns/duck.sh >/dev/null 2>&1)
Jun 13 13:15:01 hassbian CRON[23400]: (pi) CMD (~/duckdns/duck.sh >/dev/null 2>&1)
Jun 13 13:17:01 hassbian CRON[23439]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly)
Jun 13 13:20:01 hassbian CRON[23508]: (pi) CMD (~/duckdns/duck.sh >/dev/null 2>&1)
Jun 13 13:25:01 hassbian CRON[23602]: (pi) CMD (~/duckdns/duck.sh >/dev/null 2>&1)
Jun 13 13:28:11 hassbian systemd[1]: Started Home Assistant for homeassistant.
Jun 13 13:28:11 hassbian systemd[23673]: [email protected]: Failed at step EXEC spawning /srv/h omeassistant/bin/hass: No such file or directory
Jun 13 13:28:11 hassbian systemd[1]: [email protected]: Main process exited, code=exited, statu s=203/EXEC
Jun 13 13:28:11 hassbian systemd[1]: [email protected]: Unit entered failed state.
Jun 13 13:28:11 hassbian systemd[1]: [email protected]: Failed with result ‘exit-code’.
Jun 13 13:30:01 hassbian CRON[23732]: (pi) CMD (~/duckdns/duck.sh >/dev/null 2>&1)
Jun 13 13:35:01 hassbian CRON[24006]: (pi) CMD (~/duckdns/duck.sh >/dev/null 2>&1)
Jun 13 13:40:01 hassbian CRON[24124]: (pi) CMD (~/duckdns/duck.sh >/dev/null 2>&1)
Jun 13 13:41:14 hassbian smbd[24216]: [2019/06/13 13:41:14.478663, 0] …/source3/smbd/ipc.c:843(reply_trans)
Jun 13 13:41:14 hassbian smbd[24216]: reply_trans: invalid trans parameters
Jun 13 13:45:01 hassbian CRON[24360]: (pi) CMD (~/duckdns/duck.sh >/dev/null 2>&1)
Jun 13 13:46:06 hassbian systemd[1]: Started Home Assistant for homeassistant.
Jun 13 13:46:06 hassbian systemd[24396]: [email protected]: Failed at step EXEC spawning /srv/h omeassistant/bin/hass: No such file or directory
Jun 13 13:46:06 hassbian systemd[1]: [email protected]: Main process exited, code=exited, statu s=203/EXEC
Jun 13 13:46:06 hassbian systemd[1]: [email protected]: Unit entered failed state.
Jun 13 13:46:06 hassbian systemd[1]: [email protected]: Failed with result ‘exit-code’.
Jun 13 13:50:01 hassbian CRON[24459]: (pi) CMD (~/duckdns/duck.sh >/dev/null 2>&1)
Jun 13 13:50:43 hassbian smbd[24468]: [2019/06/13 13:50:43.014959, 0] …/source3/smbd/ipc.c:843(reply_trans)
Jun 13 13:50:43 hassbian smbd[24468]: reply_trans: invalid trans parameters
Jun 13 13:53:01 hassbian smbd[24504]: [2019/06/13 13:53:01.990606, 0] …/source3/smbd/ipc.c:843(reply_trans)
Jun 13 13:53:01 hassbian smbd[24504]: reply_trans: invalid trans parameters

hp1 · June 13, 2019, 12:10pm

An other thing. Whe finished wheel install, this text appears:

The script wheel is installed in ‘/home/homeassistant/.local/bin’ which is not on PATH.
Consider adding this directory to PATH or, if you prefer to suppress this warning, use --no-warn-script-location.
Successfully installed wheel-0.33.4

Does it mean something important?

hp1 · June 13, 2019, 12:36pm

The log file its saying that “srv/homeassistant/bin/hass” NOT EXIST!:

Jun 13 13:28:11 hassbian systemd[23673]: [email protected]: Failed at step EXEC spawning /srv/h omeassistant/bin/hass: No such file or directory