@HeyImAlex Yeah, I have no problems with that, that’s what I have been doing for years. The thing is that I have spent time amounting to two working days on it, and I still can’t get it to work. But if your setup works and mine doesn’t, there has to be something different we have done, and I assume it’s that you are running US locale. I can’t do that, I have stuff that is depending on using Norwegian keyboard and language (custom Python scripts and commands), and that will take so much more time for me to change then if I just go Docker.
And as long as the 2022.6.7 version works, and it stops working by upgrading to any later versions and starts working agan when I downgrade to 2022.6.7 again, it’s not a wrong encoding in anything in my .Storage, it is a breaking change done in programming that just won’t work with core, Norwegian locale and special characters in files in .Storage. Not even when I change to Python 3.10 and make the venv in there, making sure that it’s a 3.10 environment. So given the choice between going US on the Pi with all the changes that demands, and going Docker on Hass, I have to go Docker.
As an experiment, if you want to test, you could try to change your locale to Norwegian. If that actually works for you, I’m stumped.
Dude, every single HA install method uses Core under the hood. They just come with a pre-chewed execution environment.
And why exactly do you need NO locale with your scripts ? Locale has nothing to do with utf8 encoding. Norwegian characters won’t just suddenly break just because you’re not on NO locale. That’s exactly what Unicode solves. Your error seems related to an invalid utf8 encoding byte sequence in one of your files. Maybe the new version does stricter error checking on invalid sequences, while previous versions ignored it. Maybe it’s as simple as one of your files being ISO encoded rather than UTF8. That would be a 10 second fix.
If you think Docker will fix this, then sure, go ahead…
OK, I see that I wasn’t clear higher up. I thought I was, but no. I said:
As for where that happens, it’s on the second start of Hass after adding any one or more integration, built in or custom.
That’s before I even copy over my own stuff. So a totally clean installation, nothing added except for the info in my first startup, and it will reboot and reboot without any problems. I can reboot until the cows come home, as they say in Texas. But if I add one single integration, no matter what it is, it will refuse to start up next time with that UTF-8 error. I have not tried to install from scratch with everything US locale.
Edit: And I know Docker will fix it because I have already tried. No errors at all, even when copying over my info and rebooting a bunch of times.
OK, well then use Docker if it works for you. But it shows that the problem is somewhere in your OS config or with the dependencies you installed. Because inside that Docker container runs HA Core too.
Finally got it working with Core, I think. I had to create the venv with US locale, then I could go to Norwegian without having the error messages. At least I think that’s what did it, of course there are updates and upgrades to both Rasbian and other packages constantly, so maybe it was an upgrade in one or more of the packages that did it. At least it seems like I’m up and running now. And I did it under Python 3.9.2, which came with the installation of Rasbian. With Python 3.10 there were other dependencies that I could not find out, because some integrations didn’t work. So I guess I have to do another install when Hass stops working with Python 3.9, probably in two weeks…
