How did I end up on a release candidate channel. Just offered HAOS 18.0RC1. I don't know if I changed it anywhere. If this is a home assistant error on the dev side, it's a big big issue. Huge issue.
Usually it means, at some point, you clicked the option to join the Beta Channel in the expansion menu of the Updates Settings. If you don't want to be offered beta releases and RC's, you can click "Leave beta channel".
If you didn't want to run it, why did you do the update?
Look, let's not make this about "the user did it". I thought it was a regular OS update and never have a problem with it, and so I clicked install, and then noticed. I posted here in case it's a system-wide problem and needs intervention. Please don't shoot the messenger.
Same here. Not on the Beta channel for sure.
Noticed in time and skipped it. This must be some sort of mistake on the HA dev end.
Do they monitor here?
The RC version 18.0.rc1 has been promoted to stable by accident. The release has been pulled, 17.3 is the stable version.
If you are on 18.0.rc1, you can downgrade with the command ha os update --version 17.3
I'd recommend to create and download a backup (and the encryption key) - just in case.
3 Likes
That doesn't work for me.
I tried with ha os update -- version 17.3 and ha os update -- version "17.3" but everytime the system reboots it always says OS Version is 18rc1
How can I fix this?
It's:
ha os update --version 17.3
not:
ha os update -- version 17.3
If you were on 17.3 before updating to 18.rc1, you can also try this:
ha os boot-slot other
This should boot the other slot with the previous os.
@Baxxy13 you are very right ... it was a typo; I did ha os update --version 17.3 and It didn't worked out.
Thanks for ha os boot-slot other. I will try this now.
ha os boot-slot other doesn`t work either.
Any other ideas?
Now, version 18.1 is released and I can't upgrade this, too.
Any suggestions?
UPDATE: after many tries I succeeded with other browser on desktop PC (I am used to use firefox. Now it worked out with MS edge).