#hassle_io

1 messages · Page 1 of 1 (latest)

latent raptor
#

discord has rendered the container names oddly: they are all hassio__

hexed delta
#

I think you accidentally installed home assistant supervised instead of home assistant container

latent raptor
#

i found a port in the observer container's info, which reports:

Home Assistant observer

Supervisor: Connected
Supported: Unsupported
Healthy: Healthy

hexed delta
#

it seems you came across some old guide for installing home assistant supervised

#

the requirements for supervised have changed

latent raptor
#

ah dear... do you know i can remove it? fairly sure I installed it from Mac Terminal, headless obvs; but i can't locate anything beyond the Docker containers in Portainer which keep coming back

hexed delta
latent raptor
#

I mean I could flash the card and start again, I'm just weary of reading and writing more than I can help

#

I need to run HACS, is the thing

hexed delta
#

hacs does not require os or supervised

#

if you wanted home assistant addons that would require os or supervised

latent raptor
#

Home Assistant is necessary in my set up for ESP Home... that's an add on, right?

hexed delta
latent raptor
#

hmm.. Idk if you're familiar, but I bought a Dudanov ESP to control my heat pumps, which are MIdea-like,.. all his instruction is based around HA so that's why I've been fixated on it. would prefer to run Homebridge tho tbh

hexed delta
#

it sounds like most of what you want to do can be done with addons in HA OS

#

the only thing is homebridge, why not use the built in homekit connector

latent raptor
#

some, but not the most "important" thing: HKSV, which I had working on Homebridge like a dream, notifications on my Apple TV with motion and everything, but thought I'd give HA a shot as I do from time to time and discovered there's no equivalent

#

⬆️ camera.ui isn't for HA yet

hexed delta
#

oh ok

#

I can try to walk you through removing hassio

latent raptor
#

that would be awesome, please – thanks heaps

#

like i said i know how to remove the containers but they keep coming back

hexed delta
#

did you stop both the services?

latent raptor
#

i wonder if that's an order of operations thing and it's doing them one by one, and by the time they've removed the offending one, there's time for it to repopulate and recreate the others

#

they are running but can pause. there's 5 btw

#

6

#

k paused

hexed delta
#

first you have to stop the supervisor

latent raptor
#

should i do that now, from paused?

#

sorry I promise to not be dense

hexed delta
# 
systemctl disable hassio-supervisor.service
systemctl disable hassio-apparmor.service
systemctl stop hassio-supervisor.service
systemctl stop hassio-apparmor.service
docker stop hassio_supervisor
#

those commands in that order should stop the supervisor which is the thing responsible for ensuring all the other containers are alive

latent raptor
#

arghhh it's like night of the living dead, they're back. here's the commands:

pi@raspberrypi:~ $ systemctl disable hassio-supervisor.service
==== AUTHENTICATING FOR org.freedesktop.systemd1.manage-unit-files ===
Authentication is required to manage system service or unit files.
Authenticating as: ,,, (pi)
Password:
==== AUTHENTICATION COMPLETE ===
Removed /etc/systemd/system/multi-user.target.wants/hassio-supervisor.service.
==== AUTHENTICATING FOR org.freedesktop.systemd1.reload-daemon ===
Authentication is required to reload the systemd state.
Authenticating as: ,,, (pi)
Password:
==== AUTHENTICATION COMPLETE ===
pi@raspberrypi:~ $ systemctl disable hassio-apparmor.service
==== AUTHENTICATING FOR org.freedesktop.systemd1.manage-unit-files ===
Authentication is required to manage system service or unit files.
Authenticating as: ,,, (pi)
Password:
==== AUTHENTICATION COMPLETE ===
Removed /etc/systemd/system/multi-user.target.wants/hassio-apparmor.service.
==== AUTHENTICATING FOR org.freedesktop.systemd1.reload-daemon ===
Authentication is required to reload the systemd state.
Authenticating as: ,,, (pi)
Password:
==== AUTHENTICATION COMPLETE ===
pi@raspberrypi:~ $ systemctl stop hassio-supervisor.service
==== AUTHENTICATING FOR org.freedesktop.systemd1.manage-units ===
Authentication is required to stop 'hassio-supervisor.service'.
Authenticating as: ,,, (pi)
Password:
==== AUTHENTICATION COMPLETE ===
pi@raspberrypi:~ $ systemctl stop hassio-apparmor.service
==== AUTHENTICATING FOR org.freedesktop.systemd1.manage-units ===
Authentication is required to stop 'hassio-apparmor.service'.
Authenticating as: ,,, (pi)
Password:
==== AUTHENTICATION COMPLETE ===
pi@raspberrypi:~ $ docker stop hassio_supervisor
hassio_supervisor
pi@raspberrypi:~ $

#

they're back and running again, except supervisor which is stopped

#

listen, I appreciate your help. I'm just gonna flash the card again and start over. cheers tho, for real.

#

if you could please link me to the instructions I should follow once I'm re-installing, that'd help this from happening again?

hexed delta
#

sorry... I didn't get notified

# 
docker run -d \
  --name homeassistant \
  --privileged \
  --restart=unless-stopped \
  -e TZ=MY_TIME_ZONE \
  -v /PATH_TO_YOUR_CONFIG:/config \
  --network=host \
  ghcr.io/home-assistant/home-assistant:stable