Nope. Still working here.
If you pr so convinced put it down. Tell us how to do it.
OK, so we are now in 0.116.4 and I still do not see yet system metrics bars being visible in Safari… Shouldn’t it be fixed in 0.116.2? I cleared cache, reloaded… still the same. Work perfectly fine in other browsers… Anyone else still facing this?
So many misunderstandings in that post.
A newbie/Linux novice should just do a HA OS installation. That will be up and running in 15 minutes.
I along with many other people have zero interest in node red… never have and never will use it and I have a complex system.
So you have problems installing a Python upgrade then as someone else commented you’re complaining about your skill level being inappropriate for this install type and you’d be better off using HA OS.
Or you could do a HA supervised install which yes uses docker and is considered advanced but really would solve all your issues if you have the skills. BTW using docker would most likely make every single thing you want to do far easier.
4 Likes
Thanks for this. Is venv to docker migration a ‘thing’ or better to build up from scratch? I’m sure I can bring over some basics like yaml but integrations, nest, certs? If yes, any guides before I embark searching the forums?
You can just copy the config in as-is including the .storage folder for the integrations.
I’ve never done that as I have pretty much ran either HA OS and then switched to Supervised on Debian a few years ago. (So I always used snapshots when I switched installs a few times) It should be pretty straightforward.
Yes the change from venv to docker is 5 minute job.
Turn off whatever method you use to turn the venv on with (probably systemctl).
Use the documented docker command pointng /config to wherever you had your venv config, probably /home/homeassistant/.homeassistant
1 Like
There are a couple of “gotchas” to consider, which caught me out when I switched to a Docker installation recently:
- If you have any references to your config folder path in your configuration files (e.g. in shell_commands, etc.) these need changing to /config
- If you use MariaDB and the connection string in your recorder config starts with mysql+pymysql:// it needs changing to just mysql:// as the Docker container doesn’t include the pymysql package.
But, apart from those, I agree that it’s a painless switch.
1 Like
Just upgraded to 0.116.4 (actually a start from scratch installation as I also upgraded python).
Only issue I ran into was the breaking change for a custom card of mine which seems to be fixed by the following:
Also upgraded Python version to 3.8 for use with venv.
If anyone is using Ubuntu bionic 18.04.x, you may be able to install Python to 3.8.0 directly from the Ubuntu distribution (at least for amd64).
$ sudo apt install python3.8
$ sudo apt install python3.8-venv
$ sudo apt install python3.8-dev
Just for the record:
I’m pretty sure there is some easy way to install additional python packages for home-assistant OS. Hmm… looking into it, the only easy way looks to be creating a do-noting custom component, with the needed requirement specified in its manifest, and forcing it to load… Not really ideal.
If one needs to install additional non-python OS packages for the main Home Assistant under the Home Assistant OS, that would require a shell within the “homeassistant” container. It is not particularly easy to access that. If one has access to the host-os shell, one can use docker exec. Otherwise portainer can let you access it. Lastly, one can use the unofficial shh plugin with protected mode disabled in order to use docker exec.
Accessing the host OS shell is harder. The developer SSH documentation is one way to do it. There is a really tricky one to do it via the unofficial ssh plugin via ns_enter, but I will not be documenting how to do it. Lastly, I believe the easiest way to access it is via attaching a keyboard and monitor to the single-board computer.
Multiply the attributes value by an int. If it’s a string it will repeat itself. E.g false when multiplied by 2 will be falsefalse. Or you can do {{ blah is string }} and it’ll return true
Right. (actually I didn’t know about the multiplying a string by an int thing. That is interesting, so thanks for that.)
That’s the kind of faffing around I was referring to, tho.
Before it was easy since everything was a string. Now you have to use the editor to test every attribute to see which data type it is before you can know it’s valid to use in a certain method.
Attributes have always been the Wild Wild West since day one. Only states have always been strings.
I really have an issue with the Python update roadmap. Most users like me will run Home Assistant on a RaspberryPi. Raspbian (I know it has been renamed, but this is not the point) comes with Python3, latest release (buster) with Python3.7. Why do we now need to move to 3.8 if 3.7 is still good until 2023-06-27? Until then, a new Raspbian (with a newer Python3) will be released, and this can also bump Python to the next version.
Pushing people through these short, unnecessary update cycles will clearly have an impact on the acceptance - this should run “out of the box” (with a little bit of installation) and not become an exercise to install the latest of the latest versions in parallel to the OS.
To be fair, most users who are still using a pi, or new users who start with a pi are mostly using the recommended install method of full Home-Assistant which manages all of that and the user never needs to touch, or even know about, the Python installation.
Installing just core and managing the entire system (including Python) is an “advanced” install method that likely will never be a “works out of the box” experience simply because the user has to manage the backend himself, which is constantly changing.
For an experience that works out of the box, they should be using full Home-Assistant which manages the OS and all dependencies automatically.
Yeah but I thought that the system always converted them to strings when used in automation triggers, conditions, etc.
Why else would there be the need to make the change? 
That I do not know. I don’t use conditions outside template condition
You missed the point: the “easy” path is locking the Raspberry to Home Assistant. Most packages to run something else are missing.
If I wanted a locked down box, I go for Hue or any other commercial solution. Home Assistant allowed the full versatility of the Raspbian. Now I have to install Python with every minor version update again instead of using the maintained OS version. What’s the point? Stay another year on 3.7 (which is fully supported!) gives more stability and easier maintenance.
AD was in the release notes - You’ll want to read them but basially comment out config.yaml and then re setup through the integration.
.116 I am getting the same - Dropping out of order packet 6000 times in 30 minutes of clock time and time stamp overflow detected.