The supervisor is saying there is an upgrade available to 3.13 when I’m currently running 4.8.
Is this a mistake/bug ? Ideas ?
1 Like
Doing a quick search, the update to 4.8 seems to have broken allot of people’s installs.
Hence the rollback, I guess.
I think it’s mainly an issue with raspberry pi’s. I might be wrong. I had a few issues. Mainly with temp increase. That is resolved now with the roll back to HassOS 3.13
After upgrade to 4.8 RPI4 and 4.9 the system will no longer boot. Not visible on the network. Just the end. Many users have this problem. reinstallation from an older backup will help. 
Seems like a very odd thing to do when 4.9 has just been released, 3.13 is a long way to roll back…, I’m on a Pi3B+ with no issues…
4.8 update break my install (RPI 3B+). I solved the problem with a rollback:
- Connect Screen + Keyboard
- CLI login (root / no password)
- ha > login
- os upgrade --version 3.13
- docker pull homeassistant/armv7-hassio-supervisor:latest
- reboot
1 Like
I have a Pi3B+ too, and I have no problems.
Should I upgrade, or will that message disappear with the next upgrade?
All of a sudden my Supervisor went down today giving me the
Unable to load the panel source: /api/hassio/app/entrypoint.js. error.
And I am running on a rpi3b so wonder if it’s related because last time there was an OS update after restarting I got this error again. But I haven’t updated today. Unless the HassOS update installs itself? Is that even possible?
And unfortunately the only way to fix that supervisor issue so far is to cut the power completely
I made the rollback to 3.13 and now my 3b+ can’t keep it alive more than 1 hour. I need to hard reboot to return to have a 15min or 45min system.
Anyone else with something like this?
The Pi keep the power on only HA shuts down, I can’t … Wait…
I made a scan and my pi is on my network but the static IP config simply resets itself, is on another ip.
The stranger thing is when I reset the rpi returns to my “static IP” for certain time and then lose it and re-assign the IP automatically.
Is hardwired!
FWIW, My upgrade on RPi4 first to 4.8, then to 4.9 today, worked flawlessly. I appreciate the team’s efforts.
My understanding was 3.13 was the stable version everything from that to 4.8 was a Dev version
The final official from 3.13 to 4.8 was the official non dev jump and now a new to fix the boot issues with pie. 4.9
1 Like
Make a reservation in your DHCP server.
I already made it before.
It’s very odd.
Like if the Mac address changes temporary.
I have the same situation with the following system, I’ll come back in a week.
➜ ~ ha info
arch: armv7
channel: stable
docker: 19.03.8
hassos: "4.8"
homeassistant: 0.110.4
hostname: hassio
logging: info
machine: raspberrypi3
supervisor: "227"
supported_arch:
- armv7
- armhf
timezone: Europe/London
Thanks! This solve my problem.
One important thing, you have to be patience between steps haha
1 Like
One quick comment:
Today 4.10 update is out. I upgraded via GUI and it works fine.
I have my HA running OK on 227. Did you notice any issue using 228? If not, my suggestion is keep your installlation as is.
1 Like