Supervisor November beta issue impacting users on Home Assistant beta/dev channels

Installation
64

Spent several hours earlier today trying to make it work with USB method with no result (re-formatted it several times, made sure I used Linux line endings and ANSI encoding - to no avail). Only direct keyboard and TV attached seem to have worked.

One thing I am still left confused about - since I joined a beta channel a few months ago (after another major issue with ZWave), I was under a strong impression that I still had the last say in what gets updated. I am 99% sure I rejected any and all updates over the last 2 weeks as I simply was way too busy with work stuff. If I was NOT a part of a beta channel, would this issue still have occurred? I was hoping I finally got everything up and running in a stable way and this one was certainly not what I expected…

65

Supervisor auto updates by default. You can turn that off if you want, see the thread in my post right above yours. But it’s on by default, the ability to turn auto updates for it off is a recent addition.

No. Stable channel wasn’t affected.

66

ok i might sound stupid for asking this it is asking for login and password when i use login command . is this HA login ID and passwordScreenshot 2022-11-22 at 6.35.44 PM

67

You appear to be doing this from the terminal in the VSCode addon. That won’t work, that terminal does not have docker access. Please follow the directions here to get access to a terminal which does have docker access to run this fix.

68

Just fixed it with monitor and keyboard attached to pi, no problem, just don´t forget to login first

69

what user ID and password do you use with this

70

There’s no username and password required for any of this. If you’re seeing a username and password prompt then you mustve done something wrong or be in the wrong place. Please follow the directions at the top.

1 Like
71

ok finally managed to get terminal access. but it was a lot of pain. I know some beta versions may get bugs but i think HA guys need to figure out an easier way to iron out a bug and not let a user specially who are beginners go through all this hassle. anyways opted myself out from beta tester. Although paul acknowledged the problem the solution should have been easier. lesson learnt: "Get the right Terminal integration into HA :stuck_out_tongue:

72

+1 - the observer was really unhelpful with this unfortunately; it feels like this should be where it shines!

image
image1284×2778 74.9 KB

1 Like
73

Thanks much,This worked great for me, I didn’t have a full backup so I used the script. All Fixed!!!

74

I used the curl command, it extracts and works fine but I stil can’t update the system. Add ons are not starting. The system is still a mess automations run poorly. And I did’nt install any beta, just 2022.11.0.
This is really frustrating…

75

That is the beta

76

Maybe this shows how big a problem not labeling the version number with a “b”? Another user bit but this.

1 Like
77

Disabled protection mode and the script worked a treat - many thanks.

78

I tried all 3 ways, I can’t upload any backup, I can’t install SSH & Web Terminal Add-on, at least I tried to connect a monitor into my raspberry but It doesn’t work. Do you know if with 2022.12.0 version it is possible to fix it?

79

I used the curl command, it extracts and works fine but nothing has changed.

update_available: true
version: 2022.11.0
version_latest: 2022.11.2

what else can i do?

arch: amd64
channel: stable
docker: 20.10.14
hassos: “8.5”
homeassistant: 2022.11.2
machine: qemux86-64
operating_system: Home Assistant OS 8.5
state: startup
supervisor: 2022.11.0
supported: true
supported_arch:

  • amd64
  • i386
80

Can you share the output you see from the curl command?

81

curl comand
curl comand758×425 10.6 KB

82

Who can tell about the consequences of executing this command instead of curl

docker exec -it hassio_supervisor /bin/bash
# pip3 install --upgrade dbus-fast
# exit
docker restart hassio_supervisor
83

The actual issue that occurred which broke the release of supervisor in the post at the top was due to the version of dbus-fast bundled with it. That was the fix we were using initially to get systems out of it (updating dbus-fast inside the container). The curl command is much more generic, it simply forces supervisor to the latest stable version. So it could be used in the future as well in case of issues

Although fyi you should use ha supervisor restart instead of docker restart hassio_supervisor since the latter doesn’t always cleanly stop the container and can create new issues. When I was working on that fix sometimes the docker restart would work and sometimes it caused a new problem and the host service remade the container. Which put me back where I started. ha supervisor restart always worked