#installation-archived
1 messages Β· Page 52 of 1
Hopefully somebody can decode that lot and help you
yeh thx
le me try chatgpt first lol
lol
The logs you've provided show various normal informational messages and some errors. Notably, there's an error related to a missing Docker image for an SSH add-on, and a series of DNS errors indicating timeouts.
dns errors???
Yeah, there's some ongoing DNS related oddness with HAOS
No idea, but somebody else will know
alright back to chatgpt then lol
before i let u go whats the command to manually change the dnds to 8.8.8.8 and 8.8.4.4
using frotend is prefferd π
ha dns
thank you
________________#installation-archived message
for anyone to help will be much aprreciated π
Hello all - I had to disconnect my router etc at home, which meant my home assistant (on raspberry pi 4) was disconnected. I put it all back together - I get net work lights. And I still get messages from my home assistant - but I canβt access it. Not through the local address or app. What do I need to do? Thanks a lot for any help
Possibly the IP changed
I suspect it has. But surely the local address would still work no problem?
The DNS container might be corrupted. A try to fix it would be a downgrade to an older version, followed by an upgrade to the present one.
ha dns update --version 2022.04.1
When this command is completed, you can do the upgrade with
ha dns update --version 2023.06.2
It seems that some Python 3 process crashes hard:
Nov 30 18:51:33 homeassistant kernel: python3[3531]: segfault at 28 ip 00007fe6284dc8b0 sp 00007fe61caf3980 error 4 in libpython3.11.so.1.0[7fe62832a000+24d000] likely on CPU 3 (core 3, socket 0)
Nov 30 18:51:33 homeassistant kernel: Code: c7 38 02 00 00 e8 c0 01 00 00 48 89 d8 5b c3 66 66 2e 0f 1f 84 00 00 00 00 00 41 56 be 68 01 00 00 41 55 41 54 55 48 89 fd 53 <4c> 8b 6f 28 bf 01 00 00 00 e8 42 bb ff ff 49 89 c4 48 85 c0 0f 84
Nov 30 18:51:33 homeassistant kernel: audit: type=1701 audit(1701370293.989:501): auid=4294967295 uid=0 gid=0 ses=4294967295 subj=unconfined pid=2929 comm="python3" exe="/usr/local/bin/python3.11" sig=11 res=1
Nov 30 18:51:38 homeassistant systemd[1]: Created slice Slice /system/systemd-coredump.
There is also an isssue with the SSH add-on:
23-11-30 21:25:05 ERROR (SyncWorker_3) [supervisor.docker.manager] Image ghcr.io/hassio-addons/ssh/amd64:16.0.1 does not exist for addon_a0d7b954_ssh
23-11-30 21:25:06 INFO (MainThread) [supervisor.resolution.module] Create new suggestion execute_repair - addon / a0d7b954_ssh
23-11-30 21:25:06 INFO (MainThread) [supervisor.resolution.module] Create new issue missing_image - addon / a0d7b954_ssh
@frank gale I think I'd try to uninstall and install the SSH add-on again. But maybe there is more broken on your system. What hardware are you running on?
It's running on a mini pc but I tried it on a latte panda v1 too still didn't work all with fresh installations
Latte panda is a small board computer it's got 2gb of ram and a intel CPU unsure prbly intel atom
The other one I tried is a compulab pc4 with AMD CPU and 5gb ram
I also tried it on my main pc with a intel i5 32gb ram and a gtx 1080 ti
All is booting from a Kingston data travaler 128gb ssd
Correction usb
And for the SSH add-on it not just that add-on it's every add-on i try to install
I ruled out os bugs hardware usb stick but what I haven't done is my local internet as the other guy said could this python crash happen because at the first time the os boots it has to install other dependices so if it fails to connect to the internet because of the DNS then it would crash the python because the file cannot be found this is just my theory please correct me if I'm wrong
Feel free to ping me
@frank gale a segfault in Python (libpython3.11.so.1.0) points to a hard crash, caused by a buggy Python interpreter or broken hardware, or a CPU running too hot. I haven't seen a segfault with the latest Supervisor, so I would more guess that something is wrong with the hardware you are running on.
But I tried it on 3 different computers
1 of which is water cooled
Also to note that the docker application container engine takes 30 mins to start
Even then the waring message home assistant cli nnot starting entering emergency console comes up
And then the supervisor reports it's not ready with state setup
I have to type login in the emergency console
And banner on the setup error
To make it work
Maybe I should create another fresh install and directly put it into my main computer should I try that
Yeah hard to tell why/what did not work in your first attempts. The cli not starting on first start is not problematic per se, it could be that the system downloads things from the internet and waits until things are complete.
Should I try and boot it without connecting it to ethernet or WiFi
The thing I had ha before in 2022 then I stopped and then I started again in 2023 And the only that could have changed it software updates so I'm just going to downgrade core and supervisor down to 2022
I know the command for core
Could some one tell me how to downgrade supervisor please thankyou
Hello everyone! Is it possible to get SSH working with the latest HASS? I used the Pi4 image with HASS preinstalled.
I want to extend my sensor readings history to longer than 4 days with a database, but I can't do anything if I can't SSH into my Pi.
Not that you need SSH for that but yes. There's SSH addons available. I recommend the community one
Could you point me towards that please?
Hello I need some help with my installation. I install HA onto my synology NAS using Docker. I followed Crosstalk solutions install and I can't seem to launch the program. The homeassistant won't launch, I get connection refused. Any help?
What do the docker logs say?
Hi Impact, i'm pretty new to docker, how do I get those?
docker logs nameofcontainer
I'm not really familiar with synology. They might have (or limit you to) an option for that in the GUI
ok, let me check
In general it's best to follow the official docs rather than videos: https://www.home-assistant.io/installation/alternative/#synology-nas
thank you
@raven forge the network is in bridge on docker with an ip of 172.17.0.0/16 but my network is 192.168.x.x
I'd rather look at the data that made you come to that conclusion. It's normal for docker to use a different subnet though. This is unlikely to be related to your issue.
Well, thank you @raven forge you were right to follow the doc, it's up now, thanks again for your help
I just switched from HAOS to a docker install. I copied everything from the /config folder from my HAOS install over to my new docker install. One question I have is the backups option (settings -> system ->backups). Is this option supported in a docker install? If I choose "create backup" and select create, I simultaneously get a "unknown error" while it says "backup is currently being created" in the bottom right corner, though no backup is ever made
Since I'm on docker I obviously have other backup options, but I'm curious if this error is expected or if something went wrong with my installation
You can create backups with the docker installation method but you have to manually restore them. I'd say that errors for core functionality are not expected or normal and I don't get this on my docker installation either. Also see here: https://www.home-assistant.io/integrations/backup/
ok thank you. Guess I need to dig
Looks like it's running into an issue with ZHA, which I no longer use (I converted to zigbee2mqtt, so as far as HA knows I don't have any zigbee devices). I converted to zigbee2mqtt while I was still on HAOS also.
@hybrid bolt I converted your message into a file since it's above 15 lines :+1:
Open your Home Assistant instance and show your integrations
See if it's listed there and if you can can disable it.
I also found this: https://github.com/home-assistant/core/issues/103778
aha. brilliant. Same problem, and same root cause. I had a zha block left in my config.yaml. Removed, rebooted, and backup has started without errors.
Thanks!!
following this guide to get my docker setup set up, and i'm stuck here trying to set up node red to talk with mosquitto. https://sequr.be/blog/2022/09/home-assistant-container-part-5-node-red/
I get a warning when i run the docker command to create ther nodered user in mosquitto... Warning: File /mosquitto/config/mqttuser owner is not root. Future versions will refuse to load this file.To fix this, use chown root /mosquitto/config/mqttuser.Warning: File /mosquitto/config/mqttuser group is not root. Future versions will refuse to load this file.Password:
but if i just power through and set a password, it lets me without further complaint, but then as I go to add a server in node-red, it just says "connecting" and never actually connects. I haven't fully set up my system yet, so I can't really test if mqtt is working, but that warning from the docker exec command and node-red saying "connecting" make me think something isn't right
Error : coredns update failed
Literally every command I typed other than banner and login don't work it times out or fails
@wanton gulch I converted your message into a file since it's above 15 lines :+1:
You should use Docker Compose not docker run, and yes, you have to run the container as root
(your problem may be down to running rootless, or it may be that your user isn't in the docker group, but probably the first)
i deleted the containers & images and ran it after adding the docker group still with the same issue.
I will give it a go with compose
And ensure it runs as root
Not running it as root will cause countless problems
If you've got a rootless setup you may as well just give up now
No power outages but I sometimes remove the power cable from the pi (which is like a power cut as it does not have a shutdown button)
Also I have had this issue from very early on (the setup is quite young, a couple of weeks only)
How do I get ssh access to the host system? Is there any official docs on this? I found something that said to put an authorized_keys folder on a FAT32 formatted usb drive named CONFIG, but it does not seem to work.
You can shut the pi down using the OS though
If using HAOS there is an option for it
Ah I thought there was only rebooting
where would I find the shutdown button? Edit nvm found it
Cutting the power without shutting down the software properly might cause data corruption
"might" yes
does? 99.99% not unless you are doing something with the system right now
Which HA is constantly writing
ok guys I am very sorry i unplugged the usb cable
maybe it would be useful to have the shutdown button not hidden away in the developer section behind several clicks then
I can not get ssh access to work. I have a FAT32 usb drive named CONFIG with the correct public key in rsa_id file inside the authorized_keys folder in the root of the drive, the drive is detected when I plug it in, yet the config is not loaded when rebooting the system. Edit: got it to work via addon
So what I am actually getting is: failed to register layer: error creating overlay mount to /mnt/data/docker/overlay2/7b5c7bb8a409baf3e216e85943dbea28bb92ecd2b7cf0cb16cfc181be2d999ea/merged: too many levels of symbolic links
@faint dust moving /var/lib/docker did not solve the issue OO
@faint dust This solved the issue: https://gist.github.com/agners/c5ae781c828dbf76c4cc1e4588c034a5 as linked in https://github.com/home-assistant/supervisor/issues/4738. As docker does not have a mechanism for detecting or repairing corrupt image layers it seems to be very prone to power cuts, which I have ironically apparently been doing during a docker image pull (no idea how that happened). I suggest making the reboot & showdown buttons more prominent if the system is that prone to damage through power cuts.
Look you were right
The new Docker version shipped with OS 11.2 uses atomic writes for the layer metadata, so this shouldn't happen anymore as such. But yeah clean shutdown should always be preferred.
Especially since 3rdparty software like addons might also not like power cuts π’
The content of the configuration directory (outside of the container) is more important to backup. Backing up the container itself is not sufficient. (for the benefit of others like me who discovered HA architecture with pre-existing familiarity with the container concept)
Backing up the container image is largely pointless
I'm not really sure what docker container file is even referring to.
Oh this is about the backup archive for addons? Some addons store some of their data in the homeassistant path and hence it's in the homeassistant tar file.
Mine is the supervisord version installed. But every time there is a supervisor upgrade, I get this error after the upgrade: The system is unhealthy and there is no privilege escalation. At this time, it is good to restart the host. But this problem will occur every time I upgrade the supervisor. How to solve it once and for all
Switch to Home Assistant OS
What exactly does it say? Also check repairs π
Supervised is discouraged. If you want to be able to run addons and a OS or software of your choice I'd recommend proxmox VE and virtualizing HAOS and whatever else you want.
It will disappear after restarting the host.
Every time the supervisor is upgraded, it will appear.
That does not answer the question.
Wait a minute, I'll look for this error report
System is currently unhealthy because it does not have privileged access to the docker runtime. Use the link to learn more and how to fix this.
Do that π
Where did it link to?
Execute: systemctl restart docker
It will get better. But this error will appear every time the supervisor is upgraded. Is there any way to solve it once and for all.
So, had a power outage yesterday and when my stuff came back up, I'm no longer able to access Home Assistant externally via Reserve Proxy. Nabu works and accessing it directly with IP works but when I try with my CloudFlare Tunnel, it throws "400: Bad Request" on the site. Any ideas here?
Everything was working up until the outage
Can someone please help me. I changed something and keep getting an error 500 Internal Server Error Server got itself in trouble. I installed a new virtual machine and loading up a new vdi to start fresh and Im still getting the 500 error
Posted this last night, but wanted to try again:
following this guide to get my docker setup set up, and i'm stuck here trying to set up node red to talk with mosquitto. https://sequr.be/blog/2022/09/home-assistant-container-part-5-node-red/
I get a warning when i run the docker command to create ther nodered user in mosquitto... Warning: File /mosquitto/config/mqttuser owner is not root. Future versions will refuse to load this file.To fix this, use chown root /mosquitto/config/mqttuser.Warning: File /mosquitto/config/mqttuser group is not root. Future versions will refuse to load this file.Password:
but if i just power through and set a password, it lets me without further complaint, but then as I go to add a server in node-red, it just says "connecting" and never actually connects. I haven't fully set up my system yet, so I can't really test if mqtt is working, but that warning from the docker exec command and node-red saying "connecting" make me think something isn't right
You should change the owner of those files
to root? like the warning says.
I'm not
The official Mosquitto image runs as another user
Also, you can start Mosquitto and test it π
I'm still setting up the infrastructure and prelim stuff, Haven't used mqtt before, but wanted to use it this go-round
I just tested it and it will work fine if I execute this: docker restart hassio_superviosr
Also, absolutely loving this setup over haos @humble mirage , thank you
I can just backup the whole docker directories right?
zip up the top directory, and save that file somewhere?
okay
adding to todo list...
How can I find the user I need to chown the mqtt files to?
oh.
Easy to remember π
no kidding
okay, so then instead of chown root //path, I'll just chown 1883 //path, right?
sudo chown -R 1883 /my/path
Permisssion management with docker is a bit annoying hence why many recommend volumes and some run everything as root.
Awesome. thanks! I'm sure I'll hit all the snags. This is running way more smoothly though already. I kinda like the docker format over add-ons. I certainly feel more "in control" even if the controls are a little unfamillar
If node red breaks, I know where to go to fix it, instead of just trying to pull an old version for example
MQTT node in node red still reads connecting after restarting the docker container... any suggestions?
What address did you give it? Can you share your compose file as well?
I've tried both using the host name and the IP address
Yep, one sec
just noticed the timezones were off, need to fix that...
Can you connect MQTT Explorer to the broker?
Did you make the mistake of using localhost or 127.0.0.1 in Node Red?
mosquitto or the host's ip should both work with your configuration.
Host IP isn't working, haven't tried MQTT Explorer but I'll get and try that
right now the mqtt server is pointing at the local IP (192.168.1.150:1883)
but it wasn't working using the host machine name either
Also check the mosquitto logs. It listens to LAN only unless you configure it not to do that and IIRC logs that fact.
mqtt explorer: Connection refused not authorized
Whole bunch of new client connections from a 172.x address not authorized
Probably HA
Need to sort out the auth then π
Did you create any users?
(not in HA, in Mosquitto)
there's an actual valid connection from my homeassistant user on the expected 192.x address
Yea, one for homeassistant, and one for nodered
Looks like that
Starting in local only mode. Connections will only be possible from clients running on this machine.
Create a configuration file which defines a listener to allow remote access.
For more details see https://mosquitto.org/documentation/authentication-methods/
I don't see that, but let me do something other than catting the log
No need to cat, you can use docker compose logs -t mosquitto
Or add dozzle to your stack
My own conf is:
persistence true
persistence_location /mosquitto/data/
password_file /mosquitto/config/pwfile
allow_anonymous false
log_dest file /mosquitto/log/mosquitto.log
listener 1883
listener 8883
listener 9001
# Listen on port 1883 on all IPv4 interfaces
listener 1883
socket_domain ipv4
# save the in-memory database to disk
persistence true
persistence_location /mosquitto/data/
# Log to stderr and logfile
log_dest stderr
log_dest file /mosquitto/log/mosquitto.log
# Require authentication
allow_anonymous false
password_file /mosquitto/config/mqttuser
@raven forge my log is just full of those connection requests, I don't see literally anything else
ah I'm connected now
I had restarted my node-red container after changing permissions, but just now relaunched all of them after changing the timezone and it's connected. Thanks again!
I just installed an Unraid Home Assistant container and am encountering an issue.
-Z-wave will not let me install. I try "ws://localhost:3000" for the URL and receive "Failed to connect".
Is anyone familiar with configuring a container with a USB antenna that supports zigbee and z-wave?
Disregard: I switched to a VM on Unraid.
hello - been trying to do a standard install onto a RPi4 since yesterday, but it keeps failing. after flashing the image via my PC and putting the SD card into the RPi4, the device does not boot, nothing shows on the screen, no light turns on adjacent to the ethernet cable that is plugged into the RPi4, and the setup page (homeassistant:8123) does not load. any suggestions?
i know the RPI4 and the SD card and the ethernet cable and PS are are all fine since i was previously using them for a Pi-hole
How did you flash HAOS onto it? What was the name of the file you flashed?
i used the official RPI imager program on w11
and selected the HASS RPi4 version in there
home assistant OS 11.1 (RPi 4/400)
on one of my latter attemps i also formatted the SD card before reflashing HASS
anyone know if there are bugs with the latest os thats causing python3 to crash maybe a dns issue
i disabled my piholes right before attempting installation so i'm using standard upstream ISP DNS for the installation process
Check the logs to see what the error is
hello! I have an android phone (REDMI 8) with Debian 12 installed (I install Debian in the phone with Linux Deploy); when I access to Debian in phone with VNC works great! I can access to SSH and putty to... I tryed install Home Assitant Supervised but I have error when I try install Docker and have error to in "sudo dpkg -i os-agent_1.6.0_linux_aarch64.deb"
looked it up
i see i need to add it to the config file and then run install
will try
brb with logs
wait it says to add to the configuration.yaml file
mine is a config.txt
that's not the same thing right?
error when I do the command "docker version": "Cannot connect to the Docker daemon at unix:///var/run/docker.sock. Is the docker daemon running?"
HA supervised on a phone? Can't say I heard of that before. Probably not easy to find someone having experience with that.
Is the docker daemon running?
Is it?
I have runing debian12..with VNC server in the phone
But is the docker service running?
"root@localhost:~# sudo service docker start
Starting Docker: docker."
but when I put command: "docker version" the system says:
systemctl status docker.service
root@localhost:~# docker version
Client: Docker Engine - Community
Version: 24.0.7
API version: 1.43
Go version: go1.20.10
Git commit: afdd53b
Built: Thu Oct 26 09:08:15 2023
OS/Arch: linux/arm64
Context: default
Cannot connect to the Docker daemon at unix:///var/run/docker.sock. Is the docker daemon running?
To format your text as code, enter three backticks on the first line, press Enter for a new line, paste your code, press Enter again for another new line, and lastly three more backticks.
```yaml
example: here
```
Don't forget you can edit your post rather than repeatedly posting the same thing.
root@localhost:~# systemctl status docker.service
Running in chroot, ignoring command 'status'
root@localhost:~#
Try service status then or check the logs.
didnt mention before, solid red and green LED on the pi
the comand return: root@localhost:~# service status
status: unrecognized service
still not getting any install logs
can someone advise where they should be or how to enable them?
service docker status. Is there a good reason you use your phone as server? This is kinda painful as you're not getting the real debian experience.
root@localhost:~# service docker status
Docker is not running ... failed!
Check the logs: https://docs.docker.com/config/daemon/logs/
root@localhost:~# journalctl -xu docker.service
No journal files were found.
root@localhost:~# sudo systemctl start docker
Running in chroot, ignoring command 'start'
Is there a good reason you use your phone as server? This is kinda painful as you're not getting the real debian experience.
You might have to ask the developer or someone else: https://github.com/meefik/linuxdeploy/issues/1141
is any discord group of Linux Deploy ??
Doesn't look so
anyone know where i can get old versions to try the installation again with a different image?
still not able to find where the logs are
ah found it, going to try balena
Old versions of what?
HASS
the full hass os that would go on a pi4
but ill try a different imager first
We call that HAOS. You can grab all the files here: https://github.com/home-assistant/operating-system/releases
gotcha
haos
had a meeting but i tried this beforehand, https://www.home-assistant.io/installation/raspberrypi#writing-the-image-with-balena-etcher
that didn't seem to work either
i dont get why the ethernet light isn't even on, it doesn't seem t o be getting past the first part of boot i guess?
I haven't used a pi in forever. Not much of a fan
why?
i dont plan to have many containers, since i also have a server where i will do any heavier stuff
itll just be home assistant and pihole
(Pi4 + SSD on a powered USB hub isn't terrible though)
p4 seems plenty powerful for just haos, and i'm using an endurance sd card just in case to avoid issues longterm too
Here's a previous post/rant of mine about it: #general-archived message
Here's a little more I shared on another server when asked the same
I bought a pi 3 (2017) due to hype and curiosity and wanted to use it as server but ran into road blocks everywhere. Installing docker was a pain and a half and you needed third party blogs to even install compose. It was very very slow too. NPM/node for example took ages. I then tried to use it as a 3D print server. Its USB dropped out constantly ruining my prints.
Nothing I tried helped. I taped the USB plug's power pins, I even bought a shielded cable with one of those ferrite cores and other things I can't remember right now.
It works fine since I switched it to a SFF PC (that was cheaper). I can also wake it on LAN. Does that illuminate my grief?
i have specifically heard the rp3 isn't really enough for haos
but that rpi4 is fine
so that makes sense
Even if you only have few or no addons you should have a bit more than 1G of RAM. The pi4 is relatively slow but I guess one only notices after experiencing something faster.
like i said my install will be pretty lightweight so i'm not concerned. that being said, i doubt RAM is the reason it's not even booting
No. I'm just corroborating that pi3 is not a good choice for it.
gotcha, yeah agree, probably isn't
Is it rebooting and getting a different IP address?
What is shown on logs? (click the animated icon thing iirc)
hi @raven forge can you help me again..I think I can install de HAssSupervised in my phone..I folow this:
but now I have problem in this step:
tar c {post,pre}{inst,rm} md5sums control | gzip -c > control.tar.gz
I read this: Change the dependencies of a deb package (https://coderwall.com/p/hes3ha/change-the-dependencies-of-a-deb-package)
this steps are ok:
ar x homeassistant-supervised.deb
tar xJf control.tar.xz
sed -i 's/docker-ce/docker.io/' control
but the tar c {post,pre}{inst,rm} md5sums control | gzip -c > control.tar.gz guive me:
root@localhost:~/changed-deb# tar c {post,pre}{inst,rm} md5sums control | gzip -c > control.tar.gz
tar: prerm: Cannot stat: No such file or directory
tar: md5sums: Cannot stat: No such file or directory
tar: Exiting with failure status due to previous errors
I can only recommend using another device to run servers on so you can follow the docs and get something working that is officially supported. I also don't use supervised.
in the CLI version in the directory i see that create the files: "postinst", "postrm" and "preinst"
can you help in this comand: tar c {post,pre}{inst,rm} md5sums control | gzip -c > control.tar.gz I think I do anything wrong in {post,pre}{inst,rm}
if I put the name of files:
tar c postinst postrm preinst md5sums control | gzip -c > control.tar.gz
If docker does not work supervised will not work either. It's also meant for linux experts and masochists. There's no point. Save your time.
But this put docker work.. the "Change the dependencies of a deb package"
and I think that now I have docker work..
What does docker run hello-world say?
can you help me in the 4rt step:
You can change the dependencies of a deb package like this:
- Unpack deb: ar x golden-linux.deb (will create i.e. three files: debian-binary control.tar.gz data.tar.gz)
- Unpack control archive: tar xzf control.tar.gz (will create: postinst postrm preinst prerm md5sums control)
- Fix dependencies in control (use a text editor)
- Repack control.tar.gz: tar c {post,pre}{inst,rm} md5sums control | gzip -c > control.tar.gz
- Repack deb: ar rcs newpackage.deb debian-binary control.tar.gz data.tar.gz
root@localhost:~/changed-deb# docker run hello-world
docker: Cannot connect to the Docker daemon at unix:///var/run/docker.sock. Is the docker daemon running?.
See 'docker run --help'.
π¦
Like I said. No point continuing. You didn't aswer my question from earlier. Why not use something other than a phone?
I dont have.. but the phone run perfectly de Debian12..
Evidently not. Let me ask another way. Why not buy a cheap used (U)SFF PC?
ok..but I need to try this step..: tar c {post,pre}{inst,rm} md5sums control | gzip -c > control.tar.gz
root@localhost:~/changed-deb# tar c {post,pre}{inst,rm} md5sums control | gzip -c > control.tar.gz
tar: prerm: Cannot stat: No such file or directory
tar: md5sums: Cannot stat: No such file or directory
tar: Exiting with failure status due to previous errors
what I put in "prerm" and "md5sums"??
in the end. i've done.
anyone that can fix the problem with Tuya. white/yellow normal light color will work with the powerslider. when change to color the slider will change to backlight and dont have the solution to go under 5%
as the app also works with the page's for the setttings off the light
trying to figure out how to set up a backup script to automatically back up my docker configs and data... Is it as simple as 1) Stop home assistant, 2) cp source destination, 3) restart home assistant 4) zip up copied files ?
want to move my docker instance of HA over to a more beefier host , should i use the backup tarball or just copy over the container persistent volume ?
Do whatever you're comfortable with
hmm.. i have a certbot that uses --keep-until-expiring which is supposed to renew the cert if there is less than 30 days remaining, but its saying "Certificate not yet due for renewal"
never mind im an idiot π
Not After
Fri, 01 Mar 2024 09:57:55 GMT .. thats better
Elaborate
Hello, today i tried to move a VM to another device. Before was Qnap Visualisation Station now i moved it to Virtualbox. Much went okay, its also starting, but everything with oauth does not work and i also cannot reconfigure it because oauth fails... doesnt matter if google, alexa media or trakt.tv to tell some of them. IP Adress is the same, Mac Adress also... any advise?
You'll need to specify further on what "fails"
the initialisation fails of the repro. For alexa Media its telling that reauthentification is needed
and the rest like google or trakt are hanging in the initialisation.
so what i noticed is that this are all things which need the oauth
all other things which are integrated differentlly are running
Check your logs for more info on what might be going on
how can i import my VM from virtualbox to my other virtualbox that was started as sudo?
because when i start virtualbox as sudo the VM i have it does not appear
posted this yesterday, checking in again, any suggestions? still haven't made any headway
for the people helping me virtual box works amazing since this is working do you know what could be the issue
Hello, is rpi 5 OK for installation or should I consider something x64 ? I am mostly going to use it for zigbee and esphome and I do have a USB sonoff zigbee bridge
Mini pc
Pi5 isnβt supported yet and mini pcs price vs performance compared to SBCs like a pi is night and day
Well I did pre-order the pi5 at release and its gathering dust atm
N100 based mini pcs on Amazon are popular lately
I do have a very old AMD thinclient
Itβll prob still be better than a pi
and also an i5 optiplex
I will shove it in my meter cabinet and wanted to see if I can get away with something small
right now I have a PoE Switch and a router and a small netbook for pihole only
You can install haos bare metal too if you prefer
If I can fit all in one I prefer that
so router with pihole or some other dns sink and home automation basically
Oh you should definitely run proxmox
Eh
I wouldnβt combine firewall, router, and smart home all on one device
Itβs just bad form
Hmm
Iβd run a dedicated device for opnsense or something
And then however you want to run home assistant and other things
this is the thinclient that I am talking about
its passively cooled so in terms of noise its a better option also its "compact"
Fuck it has ps/2 ports lol
π
well it has displayport gbit ethernet and 2x usb 3.0 4xdusb2
but only 2 cores I belive
if it's over 1000 it is good enough for haos and better than a pi
damn am I going to have to buy more hardware now ?
I really dont want to use a SFF for this task
they are considered a better option than a pi
a real ssd not a microSD card
and much faster cpu
they keep adding more options to home assistant and esphome that require more processing power to get more out of them like openwakeword, piper, whisper, all the new stuff
right, but you will eventually
this is my first ever attempt on anything smart
and you'd have to migrate from the pi at that point
just got some tuya TRVs and sonoff screen
I am on a budget
yea
my boiler has 2 wires
so will use a smart relay for activating heating
have 2 extra temp/humidity sensors
Thinking putting one outside
how easy is migration to another hardware ?
the SFF is definetly overkill at this point
it has 5 gigabit ports for gods sake. I really want to make this a router
very easy
your mini pc is probably fine for haos for now
ok then let me see the hardware I have in there
it had a crappy pre-ssd flash thingy
I'll grab the SSD from the SFF for now and later I can grab a proper ssd for it
i swear my home is an e-wasteland
found another netbook
intel atom 2gb ram
Can anyone tell me how to reset my terminal screen in home assistant? I was trying to install hacs.
What do you mean with resetting the terminal screen?
Please use imgur or other image sharing web sites, and share the link here.
Image posting is blocked in most channels to discourage people from sharing text as images. Sharing text as images assumes that everybody sees the world as you do, which isn't the case. Some people are colour blind, or have visual impairment that means they can't make sense of an image of text.
I will load it on Imgur
I uploaded it on Imgur @placid sageub16
Impact, can you access the picture on Imgur?
Not unless you give me a link to it
Ok, are you on there for me to send the link?
Just paste it here so everyone can see it
Ok
I tried restarting
That was actually posted like 5 times but you get the point
No. I'm still waiting for that link to a picture that explains what your point is
You canβt see the pic posted above?
There is no link
I posted the actual pic, is it not showing?
Did you read the bot message?
Yes , I was trying to post a link and the pic posted. I guess it is blocked. If I can not post the link I will just figure it out.
You should be able to post links. Just no attached pictures.
Ok, still trying to create the link from photos on my phone
It shouldn't take 40 minutes to upload an image to imgur and copying a link to it for someone who can install HA.
Starting Network Time Synchronization. ..
Started Notify NFS peers of a restart.
Started Network Time Synchronization.
Reached target System Time Set.
TIME ] Timed out waiting for device /dev/virtio-ports/org.qemu.guest_agent.0.
[DEPEND] Dependency failed for QEMU Guest Agent
FAILED] Failed to start Wait Until Kernel Time Synchronized.
See 'systemctl status systemd-time-wait-sync.service' for details.
] Reached target System Time Synchronized.
] Started Discard unused blocks once a week.
] Reached target Timer Units.
Starting HassOS AppArmor ...
] Finished HassOS AppArmor
Starting Docker Application Container Engine ...
] Started libcontainer container 47b1bf9673f6f15416cce13d4f04bbbfc521ea43325ddb4e9522bd3cf75e2713.
] A start job is running for Docker Application Container Engine (2min 35s / no limit)
any know what happened here
and is there a fix for he erros in bold
this is running on winodws 10 virutal box
i am 100% sure there is nothing wrong with networking
You can run systemctl status qemu-guest but which file did you download for the VM?
Please show the VM's Detail page.
Also use a code block next time.
What is the file name?
haos_ova-11.1
i have this
this is a first boot accesed through ip and it says "An error occured while installing Home Assistant, check the logs below for more information."
.
Please run the command I shared (enter login first) and show the image I requested.
Please use imgur or other image sharing web sites, and share the link here.
Image posting is blocked in most channels to discourage people from sharing text as images. Sharing text as images assumes that everybody sees the world as you do, which isn't the case. Some people are colour blind, or have visual impairment that means they can't make sense of an image of text.
Type it correctly then π
The settings for the VM look correct. Although I'm not sure why you have a TPM. The guest agent thing isn't important. Virtualbox isn't qemu. I was just curious.
Can you run ha network info? or just network info in the ha > CLI.
will do
tpm must have been an acident
havent run the command yet but this came up
This the command output for ha network info
i can still access the web page
.
Seems like docker didn't start which checks out with your earlier message stating
A start job is running for Docker Application Container Engine (2min 35s / no limit)
You can enter login again and test systemctl status docker but it might be a better idea to grab a new vdi and try it again.
do you know what could have caused it in the first place
No. systemctl status docker or journalctl -u docker might give some hints.
Why not check the logs of the current issue first?
ill do that first then
just a back story but i switchted to windows10/virtual box becuase i had a issue on the HAOS image install python3 crashes hard and docker application container engine takes 30 minutes to load still it jumps into ermegeny console
Switch from what?
I'd have suggested putting proxmox VE rather than windows and virtualbox on it but if it fails on bare-metal it probably also fails in a VM. Easier to troubleshoot and restore though.
No
That looks okay though. A reboot might actually fix something. If not try running supervisor repair afterwards.
Why not check the logs of the current issue first?
ill do that first then
i did reboot it and then runned the command
π
That does not sound healthy. Might want to fix that first.
What something causes crashes?
was trying to make a server for a hardrive to make into a nas but thats unrelated
ran ha network info
That should not cause a crash though!? That can cause corruption and all kinds of other issues beside that it shouldn't happen at all.
Network info looks okay.
yup i can access the preparing HA page
Doing one thing at a time instead of doing everything a little bit might be a better approach
still says "An error occured while installing Home Assistant, check the logs below for more information."
anyone heard of quick assist
Very likely the crash corrupted something. Info like that is important. Might be fixable. Let it run for a little bit.
should i try a new ova file
If you want to to be safe that might be a good idea. I recommend frequent backups and snapshots. Also look into what caused the crash. If something is in the process of being written to and a cras happens that file can get corrupted. And since it was during setup...
ill let you know once i reisntall it
starting VM.....
qemu still failed to load on new VM it was too fast for me to a scrn but it was the same error as before
QEMU guest agent is for QEMU. Virtualbox ain't QEMU. That's fine.
You don't have to recreate the VM. Just power it off and attach a new VDI.
i know but just to make it completey fresh just in case
A start job is running for docker application container engine 3 min and increasing
started docker 4 mins
loading cli
supervisor starting
Error returned fro supervisor: system is not ready with state:setup
rcu INFO rcu_preempt detected stalls on cpus/tasks
On what hardware is this running?
im suspecting its hardware becuase it works really and i mean really fast on my main computer a gtx 1080 ti 32gb ram 10TB SSD storage and intel i5 12k
the pc thats not working with HA has a Processor AMD GX-420CA SOC with Radeon(tm) HD Graphics, 2000 Mhz, 4 Core(s), 4 Logical Processor(s)
and 6Gb ram
Oh wow. I wouldn't even run windows on this and you use it to virtualize with windows π¬
It's faster than a pi 4 though: https://www.cpubenchmark.net/compare/4297vs2121/BCM2711-vs-AMD-GX-420CA-SOC
just tried the normal Pi OS and it just shows 4 colors on the screen, normal setupo doesn't start though
so maybe thgat's why HAOS won't woirk either
is there something akin to bio on rpi4 to check?
bios*
if it works better than a pi it shouldnt be that bad right/
but surely this couldnt cause problems with docker
Yes and no. It likely causes those CPU stalls.
Virtualization is enabled yes?
and also what pc would you recommed that budget friendly
not sure if it even has it but ill check
later
(U)SFF or Mini PCs can be had for 50-100 depending on your currency.
I don't recommend windows and virtualbox for running HA(OS). Either HAOS bare metal or as VM via proxmox VE (my recommendation).
ill try proxmox ve
It should also work bare metal on the AMD box as well.
is any problem with VirtualBox..I try charge this VDI file: https://github.com/home-assistant/operating-system/releases/download/11.1/haos_ova-11.1.vdi.zip but Virtual Box dont have option to choose VDI files! I chose Linux - 64bts..
Did you extract it?
only show option to ISO files!
Go to the next step then. That's the boot media. The docs need updating.
You want this screen: https://i.imgur.com/2k3LHKa.png
!! ok..many thanks!! now work!!
Hi, all! I've been running HAOS in a VM for a couple years now, and I'm trying to understand if its worth it to migrate to Docker. I'm fairly inexperienced with Docker, but I have a few containers running (Caddy, ESPHome, PiHole, Portainer). The key is that this is my parents' server, and they aren't the most technically gifted, especially if it doesn't have a GUI. I love tinkering and don't mind learning and getting everything set up, I just want to make sure that when I move out, they don't have to deal with anything outside of the HA app.
Can anyone provide some insights?
Like, I don't quite understand the difference between Supervisor/Managed OS
Who's going to manage it?
Well I would be able to SSH in if something went wrong, but not necessarily everytime HA has an update
Like would I have to do a docker-compose down/up everytime they want to update HA?
Sure, just like you do today
Oh, well, if you used Docker you'd do that today
HAOS puts it in the UI
Basically, do you want "an appliance" (HAOS) that self-manages some parts, or do you want control (Container)?
Personally... for remotely supporting somebody I'd use Container (Docker) not HAOS
Basically, I want to be able to click update in the HA UI to update the HA version, but I don't need something to auto-update the Debian Host version
Okay, so the HA Docker isn't as simple as click update?
Docker you have to use SSH. Or write an automation to do it for you if you're brave.
I just hate not being able to share resources in a VM like docker does. I wouldn't mind writing a script to "docker-compose stop homeassistant; docker-compose up -d homeassistant" (or rebuild), then put a button in the HA GUI to run a script.
I just didn't know what the difference between a "Supervisor" and "Supervised OS" is
Well, it's pull then up -d
Supervised is a trap, don't even think about it
The two sane install options are HAOS and Container
Core is for Unix greybeards
Sorry, correction: "Supervisor" vs "Managed OS"
Supervised is for people who hate themselves
Supervisor is the thing that gives you add-ons
HAOS has the Supervisor, HAOS is not Supervised
HAOS has a managed OS (HAOS)
Okay, so I don't think I need Supervisor bc all of my add-ons have been migrated to Docker
But the lack of Managed OS is not a problem from Home Assistant's POV?
You can also run HAOS as a VM. I would never manage HA or anything else for someone though
HA doesn't care
Doesn't even know
That's what I'm currently doing. Just trying to go to a more power efficient/resource efficient route, and thought Docker would be the best way. I don't think managing it would be too difficult if I can get it setup and just run an update script
But maybe I'm just naive and don't know what kind of hole I'm digging myself into
Pffft, Docker FTW
Will your parent really read changelogs and update the system? What if an update fails?
Well, at least over SSH it's easy to revert an upgrade when running Container π
No, they probably won't. I guess I'd just SSH in every month or two and see if there's anything that needs updating and if there's any breaking changes.
Not sure about when updates fail. Haven't yet looked into how to revert upgrades/container backups
Docker makes that easy
Just change the tag in the compose file and run docker compose up -d
Bingo, done
Okay, I'll have to look into it. But you definitely helped put my mind at ease in moving to docker
Thank you so much!
is the zwave JS integration (Running in a docker inv) in HA just "Zwave" ? I can't find the Zwave JS one, but i found one that just says "Z-wave"
I have my zwave js ui server running in a container, but not sure what the next step is for zwave, and don't want to add a deprecated integration
<<salute gif>>
This is such a cleaner setup than what I had before. I'm glad I'm rebuilding
Hello is this the correct place to ask about my Nabu Casa account and how to transfer it to a new install of home assistant?
Trying to install using the raspberry pi 4 os image and get this in the logs. [supervisor.docker.interface] Can't install ghcr.io/home-assistant/raspberrypi4-64-homeassistant:2023.11.3: 500 Server Error for http+docker://localhost/v1.43/images/create?tag=2023.11.3&fromImage=ghcr.io%2Fhome-assistant%2Fraspberrypi4-64-homeassistant&platform=linux%2Farm64: Internal Server Error ("Get "https://ghcr.io/v2/": net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers)") [supervisor.homeassistant.core] Error on Home Assistant installation. Retry in 30sec
Any ideas.
I've tried two different devices to get HAOS running, a M900 ThinkCentre and a Intel NUC... I am following the guide exactly, no matter what I do... I get "no boot device" or "Start HTTPS Boot over IPV4"
Can anyone help
I even did the prompts in blue... on this page: https://www.home-assistant.io/installation/generic-x86-64#start-up-your-generic-x86-64
I booted into Ubuntu (try) restore the HAOS image... restart.... I have done this over and over 10 times trying to get it to work
How did you flash the boot media? UEFI boot is enabled yes? I'd recommend disabling network booting just so it doesnct even try.
So I did method, one which was to boot into ubuntu, and then to do the recovery partition, and then specify the image on a separate USB drive
And I donβt get any errors or anything like that, but thereβs just no boot medium every time I restart, even when I try to specify the boot with the provided commands
Did you disable secure boot?
Yes I did, and UEFI is enabled
Because this is happening on two separate devices I feel like Iβm doing something wrong though potentially in the command Iβm running in terminal?
The one to specify paths
Maybe. You can get the disk via lsblk -o+MODEL
In terminal? Inside Ubuntu?
Yep
If that doesn't work you can always virtualize and run HAOS as a VM if you're up for it
That command is a two line command but I can copy, edit and paste it as one yeah?
I get some result when I run it, but it not clear if its a good result or not
I had not been removing that \ so it could be the culprit
The \ is basically a new line escape.
Bah, I cant upload screenshots here I should show you the result.
Please use imgur or other image sharing web sites, and share the link here.
Image posting is blocked in most channels to discourage people from sharing text as images. Sharing text as images assumes that everybody sees the world as you do, which isn't the case. Some people are colour blind, or have visual impairment that means they can't make sense of an image of text.
Have to jump through hoops here π
It's OK to be EXT4 right? I am going to start over and wipe the drive again.
What exactly?
The NVMe that's in the NUC.
Not directly. There's many partions with different file systems.
BootCurrent: 0006
Timeout: 1 seconds
BootOrder: 0006,0007
Boot0006* UEFI: VendorCoProductCode 2.00, Partition 1 PciRoot(0x0)/Pci(0x14,0x0)/USB(0,0)/HD(1,MBR,0x19b79bde,0x800,0x3a97800)..BO
Boot0007* UEFI: VendorCoProductCode 2.00, Partition 1 PciRoot(0x0)/Pci(0x14,0x0)/USB(6,0)/HD(1,MBR,0x4575fb,0x800,0x3a97000)..BO
That's what -- verbose sends back
Please run lsblk -o+MODEL
@silent wolf I converted your message into a file since it's above 15 lines :+1:
Your NVME is not flashed correctly or at all
I just wiped it off, let me do it again, didnt think of that before running it. Sorry!
The drive in Disk Manager says its called nvme01n1p1
After flashing please show the output of lsblk -o+LABEL,FSTYPE,MODEL
That's the first partition of nvme0n1.
OK running the restore image now.
Here's how a trimmed output of that looks in a HAOS VM
# lsblk -o+LABEL,FSTYPE,MODEL
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS LABEL FSTYPE MODEL
sda 8:0 0 32G 0 disk QEMU HARDDISK
|-sda1 8:1 0 32M 0 part /mnt/boot hassos-boot vfat
|-sda2 8:2 0 24M 0 part squashfs
|-sda3 8:3 0 256M 0 part / squashfs
|-sda4 8:4 0 24M 0 part squashfs
|-sda5 8:5 0 256M 0 part squashfs
|-sda6 8:6 0 8M 0 part
|-sda7 8:7 0 96M 0 part /var/lib/systemd hassos-overlay ext4
`-sda8 8:8 0 31.3G 0 part /var/log/journal hassos-data ext4
Restore image? The docs suggest balena
Method 1 was to use the Restore Disk Image workflow in Ubuntu
So that's what I had been following
METHOD 1: INSTALLING HAOS VIA UBUNTU BOOTING FROM A USB FLASH DRIVE
You're right. I apologize
All good, that was my next plan anyway but idk if I could do that via booting Ubuntu or not and I am trying real hard to not have to remove this drive and connect it to my home system
@silent wolf I converted your message into a file since it's above 15 lines :+1:
I'd simply suggest dd: <#general-archived message>
But restore image should work too
Nope. It should look similar to what I shared above.
So then restore image is def not working
So can I do the other method from within Ubtunu on a USB drive?
How do I even like download DD, I only see a link to its wiki
Damn this is so hard lol, I see your file but discord converted it.
Its not all one command, right?
I see backticks in it ```
I was trying to edit it in text editor
Much to my lamentation: #installation-archived message
No it's not just one command. The backticks were part of the markup to make it look nice but the bot kept them in.
Within terminal or another console?
I'm not sure what you mean.
I mean where do I run all these commands, terminal?
I am all set, thanks man!
Trying to start the Raspberry pi version and continually get a DNS error.[supervisor.store.git] Can't clone https://github.com/esphome/home-assistant-addon repository: Cmd('git') failed due to: exit code(128) cmdline: git clone -v --recursive --depth=1 --shallow-submodules -- https://github.com/esphome/home-assistant-addon /data/addons/git/5c53de3b stderr: 'Cloning into '/data/addons/git/5c53de3b'... fatal: unable to access 'https://github.com/esphome/home-assistant-addon/': Could not resolve host: github.com
Is there a trick to this. I can reach it using my pc without issue
Nabu serves up ha in https, but my default install uses http (unless I'm just missing something), how do I serve it up locally with https?
You don't. Why do you want to?
This sounds like a DNS issue. Is your router annoucing a DNS server in your network? Can you ping github.com from the SSH/Web terminal add-on? If no, can you check the DNS logs (Settings > System > Logs then choose DNS on the top right)?
A next step then would be to set a DNS server explicitliy using
ha dns options --servers dns://8.8.8.8
If you don't want to bother with SSL, you could look at accessing it via Tailscale, which is a mesh VPN, highly recommended. I wouldn't serve it over the general Internet without SSL though.
Hi..I instal in a VM Debian12 and install HAss Supervised; I do a backup .. after this because the system is a bit slow; I isntall a new VM a put on this the Hassi OS - I try to restore the backup from Hass Supervised - and now I have this error:
in the version of Hass Supervised I have supervisor mode version 2023.11.7 (dev3002) and in the Hassi OS the supervisor version is 2023.11.6
I cant restore backup because this..
what can I do?
You could have rolled back Supervised to not use the dev release
Hey guys, I've had a quick search but maybe I'm not looking for the right terms. I have a TrueNas Scale install of Home Assistant. It's a container install working pretty well. But I'm looking to expand and use more features. I've been trying to learn up on the history section and why my install doesn't have it. Seems like it's not setup with the defaults on TrueNAS, so was going to see if I can get it working. My logic would tell me that I need to also run a database container like MariaDB and then setup HA to connect to it. Anyone know of a good docker install guide that includes recorder that I can learn from?
how can I do this?
I try but I cant downgrade from 2023.11.7(version from HassSupervised) to 2023.11.6(version that I have in HassOS)
You never shared the error though
I put the comand ha supervisor options --channel stable but the supervisor continues with 2023.11.7.dev3002
I restart the system but the version of supervisor dont change to 2023.11.6
I put the camand to try force install version 2023.11.6:
ha supervisor upgrade --version 2022.11.6
but return the error:
Prossessing.... Done
Error: No supervisor update available - 2023.11.7.dev3002
You never shared the error showing why you couldn't restore your backup
images of text ... 
and in HassiOS I cant update supervisor to 2023.11.7.dev3002
Then you have to wait for somebody else who can help you, assuming help is possible
Why on earth were you running a dev release though?
I stopped using nightly builds on my production system because of supervisors auto-updates. I recommend doing the same.
See, that was your opportunity to switch to container
It was, but then I just fixed the issue in like 5 minutes
So, I successfully made the change from Micro SD on my Rpi4b to a USB 3.0 NVME drive, AND did a full restore from a backup. It was surprisingly smooth. HOWEVER. I lost all my DB history... I still have the Micro SD drive with ostensibly has the old history on it. Is there something I missed? Should it have worked or is my history lost forever?
you can just drag and drop the file while HA is off
Hi all, I'm running ha in docker on a RPI4 and it works great. What's a good procedure when updating to a new version? Do I need to shut down the docker container gracefully or can I just docker rm -f it and then start a new container with a different version?
Ideally you use docker compose and just have to run docker compose pull && docker compose up -d. It handles everything for you.
Otherwise yeah, stop the container, remove it, pull the new image, recreate.
It's a single container so compose feel like overkill. I have a bash script to start it.
Most of my containers have their own compose file. I'm not sure what is supposed to be overkill about it.
See here for how it can look like: https://www.home-assistant.io/installation/raspberrypi#docker-compose
The only downside is that it makes it easy to back up and migrate your container configs
This is by design, we currently don't allow downgrades for Supervisor. This should resolve itself once a newer Supervisor (2023.12.x) comes out.
to start, get off the dev channel
Yeah. I do switch between beta and dev quite often on my test instances. But when moving to dev -> beta that Supervisor stays stuck a bit. Usually no big deal, resolves itself after a couple of days or weeks latest.
If really necessary, one can revert it using a couple of docker commands manually from the OS shell. But I'd have to try out what actually works
@dreamy ibex YMMV. I can script in my sleep and I won't be going near YAML unless I have to. There's more than one way to do it.
okay π€·
@humble mirage tar -czf backup.tgz config is simple enough for me. How does compose help with backup and migration?
Anyway, I'm getting a warning in the logs about sqllite not shutting down properly when I start a new container. That's kind of why I was asking
2023-12-04 20:20:40.949 WARNING (Recorder) [homeassistant.components.recorder.util] The system could not validate that the sqlite3 database at //config/home-assistant_v2.db was shutdown cleanly
How are you stopping the container?
docker stop
@Tinkerer tar -czf backup.tgz config
That should be fine. There's a 10s timeout after which it kills IIRC. Maybe it takes longer to stop?
People and compose files and here I am with my systemd unit files
@rustic shadow I converted your message into a file since it's above 15 lines :+1:
I want to run home assistant in docker, so Iβve created 3 instances for testing. Raspberry Pi 4 (2 GB RAM), Synology DS 920+ VMM and Synology NAS docker version. For the most part, the pi and the VMM all function the same, but the docker version has issues with integrations; like my printer with IPP saying API canβt connect, or LIFX finds my bulbs, but gives me a completely blank error message that I just need to click βokβ on and thatβs it. I donβt experience the same issues the OS counterpart, but do with the docker versions. Ideally I would love to have docker versions, but I want to know what Iβm missing here since docker is supposed to be platform agnostic and I donβt need to install other packages / drivers unless I want to specify volumes or devices into it.
version: '3'
services:
home_assistant:
container_name: home_assistant
image: "ghcr.io/home-assistant/home-assistant:stable"
volumes:
- /volume1/docker/home_assistant:/config
- /etc/localtime:/etc/localtime:ro
- /run/dbus:/run/dbus:ro
restart: unless-stopped
privileged: true
network_mode: host
I am soo confused⦠why did you give it read only to dbus when you gave it read / write with privileged and host networking mode
I think I was following the original guide on home assistant
docker run -d \
--name homeassistant \
--privileged \
--restart=unless-stopped \
-e TZ=MY_TIME_ZONE \
-v /PATH_TO_YOUR_CONFIG:/config \
-v /run/dbus:/run/dbus:ro \
--network=host \
ghcr.io/home-assistant/home-assistant:stable
Ah itβs the way they do Bluetooth, thatβs new π
Docker should work the same way as the haos vm
Logs?
I dont think Iβll be using Bluetooth, so I might as well remove dbus, but still weird that mine doesnβt want to work the same was as the OS VMβ¦ could it be a Synology DSM thing?
Possibly, get ha logs when you have the issue
Iβm running home assistant inside podman inside a Linux userpace under a user who does not exist
Like docker but a wee bit more isolated with root being a non root subguid
Not going full on rootless until the rootless network performance issues get worked out to near root performance
Here's my logs, I've tried to set up a lifx device at 192.168.0.26 and 192.168.0.8, neither of which show up in the logs, unless I'm looking at the wrong ones
Trying to get a smaller amount of logs.. in paste bin
And before broken IPv6 /matter
No firewall?
I dont have anything exposed to the internet, so no firewall (at least none that I set up)
These devices work successfully on HA OS though
What's also interesting is that I tried to add my apple tv to HA as well, but it doesnt actually turn the TV on to give me authentication codes; just spins on the "Confirm adding Apple TV" state, also confirmed working on HA OS VMM
Here's the apple tv one, if it may help
I've also tried to delete my entire config folder and create a brand new instance of home assistant, all with the same error (removed the dbus)
I just learned that supervised version can be install on docker...
Is there any easy way for me to migrate from container version to supervised?
I just learned that supervised version can be install on docker...
that doesn't make sense
You shouldn't migrate to Supervised. Nobody should
Could you elaborate?
I am not using HAOS I'm using the HA container version... and would like to benefit from auto backup to clouds, supported by supervised version
and it still doesn't make sense to install Supervised "in" docker
sounds like you're describing a specific addon
Hi, I'm trying to move my Home Assistant from a computer to another, so I created and downloaded a backup but I can't figure out how to import it on the new instance. Help ? Thanks
No version of HA natively supports backing up to any cloud
yes I am... This one; https://github.com/sabeechen/hassio-google-drive-backup
and it relies on supervised api
if you want access to addons, rather than handling backups like that yourself, you should migrate to HAOS
It's not cloud, it's a tar file
Just because HAOS uses docker containers doesn't mean you can install them yourself and have them working without HAOS
That wasn't a reply to you. Are you using a container installation?
I'd like to insist on my first question... How would I go about migrating from container version (within portainer) to supervised version?
I am currently watching a tutorial video on how to install supervised version on docker...
but it is for first time setup... since I have installed the container version... I was wondering how would go about from there...
Make a backup, download it, install HAOS, use its restore function
Please link it
is sharing tube videos allowed?
If not you can put the blame on me I guess π€·
The Jedi role (blue) is given to our community members who have proven themselves knowledgable and worthy of helping others. Please do not request to be assigned this role. It must be earned.
Sorry. It's installed at /home/homeassistant/.homeassistant
so, yes, I guess
And the answer is that you untar the backup into your config directory. HA cannot do the restore for you
I wouldn't call that "in docker" but yes that works. Most of us don't really recommend supervised though
at all
I wish it would completely go away and folks would stop talking about it and making videos about it
I mean... I really do want automated cloud back ups though π¦
then use HA OS
I can't ... for reasons
Why not? What hardware are you using?
Are we talking about Supervised?
It's not about the hardware..(well it is... ) @raven forge we have already talked about it in #general-archived few hours back...
I'm sorry I talk to many people about roughly the same things and my short term memory is not very good
Guys please don't start mocking again... I'm just trying to figure out the best setup, for my priorities with in my obligations...
Above from that
Yeah I just checked. I'd recommend installing the "addons" yourself. If you install supervised you "enslave" yourself to the supervisor: https://github.com/home-assistant/architecture/blob/master/adr/0014-home-assistant-supervised.md
Unfortunate for me this add on doesn't work on the container version...
If you guys /gals know any alternative add on for automated drive back up integration pls do let me know
The video guide will also not result in a healthy Supervised install. Only Debian 12 is supported, not RPi OS
So not only do you get little support from us here (I don't use it, for example), you also have to manage the system as how supervisor wants it and can't even use it for what you want without making it unhealthy. See link above. There's not really any benefit. You will make the system unsupported in a hurry and you might also run into mean or snarky comments. Not from me but still.
I'd recommend either using the integrated backups (perhaps with a automation) and then use rclone to sync it off-site or do the backups with something like restic.
Which add-on you want does not work as a container?
This oneo
There's an issue thread where the author says that it currently relies on the supervised api
I did dig into the automations for back up a bit... but then I hit a brick wall... That's where that video came in, while looking for solutions.
There's an example here: https://www.home-assistant.io/integrations/backup/#example-backing-up-every-night-at-300-am
The problem with just backing up the /config directory with restic or whatever is that the database isn't locked during that time so it is safer to let HA make the backup and transfer those.
There is also Linux software to connect a Google Drive to the host system
Hey thank you so much for sharing the link, I haven't delved much into YAML yet but perhaps the solution lies there... Would I even be able to do my own cloud backups, If I were ever able to write the code for it, using YAML ?
You can use rclone which can communicate with all kinds of things: https://rclone.org/overview/
restic can talk to rclone as well: https://restic.readthedocs.io/en/stable/030_preparing_a_new_repo.html#other-services-via-rclone
If you have enough space you can simply only use encrypted rclone to safe a bit of complexity.
Anyone in this group run Home Assistant as a docker container on unRaid?
Alright, the devices are there but all switches are greyed out π€
I am asking this question, because i am trying to get HACS working with the container version. I got the container all working, but needs HACS so i can get my Reolink camera working....
you can just follow the HACS installation instructions
When it's put on to words like this it almost sounds like everything is already possible with what I have installed.
I just have to look into the right places but that's the biggest problem of all... How can a newbie know what to look for...
Thanks to kind and patient people like you... we learn. No wonder they made you a Jedi.
Indeed. On the topic of HACS. there's also this: https://jcwillox.github.io/hass-auto-backup/
I'm using that
Here's another crazy stupid question... Is there any possibility to run a virtual box type of software and run HAOS on it... On Rasbian OS
waivering from some performance etc?
I'm not sure you can on a pi. Qemu should work on them but I'm not sure if HAOS' OVA works with that and I wouldn't expect the performance to be great.
I run all my services (besides my firewall and print server) in VMs/CTs and can recommend proxmox VE if you get a "normal" PC in the future.
I just remembered that some folks use pimox (based on proxmox VE) to virtualize things so it's definitely possible: : https://github.com/pimox/pimox7
Sounds like pain though.
I'm now thinking if it would be possible to have two instances of HA on the same network... one being thecontainer version of HA on a pi 7/24 ... And a HAOS on virtual box on my main pc, up whenever I'm working on it.
Would they terribly conflict or just get along just as well?
That very much depends on the devices and your configuration. Having multiple automations that toggle something might prove unhealthy, for example.
Yeah I guess I would have to stop the other service when one is up...
Generally having a development VM is quite nice and practical. I do this for HAOS as I don't use it myself. I start it up, check some commands or whatever I think I can help with and when I'm done I restore my snapshot.
Well I don't know what I'm even babbling about anymore mate... I couldn't even get my rasbian boot from my SSD yet... it's way too slow and throws errors etc...I suspect power being low but I have a 3amp 5v adapter which in theory should be enough...
And while that setup is like that I'm here dreaming about setting up multiple instances and shit.. I'm slowly getting coldfeet from all this linux and HA thing... may be I should just return the pi and stick with my existing automations... I dunno... I'm a bit depressed... Whole bite is more than I can chew and only a handful of people to talk to..
There's plenty of people doing stuff like this on the selfhosted,homelab or just homeassistant subreddits. I'm sure there's other communities as well you'll feel at home at.
Thanks again for the directions... You keep being you tho: rmvp
About the power issue. We tend to recommend powered USB hubs when using USB storage. Using the official power supply is also recommended. It's about more than just peak amps.
You might also find this interesting: https://pip.raspberrypi.com/categories/685-whitepapers-app-notes/documents/RP-003610-WP/Making-a-more-resilient-file-system.pdf
Also see here: https://www.home-assistant.io/faq/usb_boot/
I believe there was a white paper about properly powering pis too but I can't find it at the moment. rasperry brownout or rasperry under voltage might find it.
Yet again great resources. .. ALL I wanna do is to create a resilient pi (and file system)... That's why I went with SSD setup etc.
Before I ordered anything I calculated a total of 2 point some ampers for all the peak powers of pi, SSD (SSD peak is surprisingly only 0.4 ) and the fan on the case... Won't matter in a week though cause I already ordered a sata to usb3 with external power adapter... So I'll know then if it was power or any of my boot configurations or perhaps it's the converter itself..
If everything fails, I may just end up trying to boot the SSD with HAOS installed anyways... I shall see
The version of Docker Container in the unRaid appstore does not have the app store for me to add HACS. I am brand new to HA... so im learning as i go.
You have to run the command in the HACS installation instructions from the command line
I did try that.. and it says its installing, but when i restart the HA container. I don't see the app store or HACS on the left side, so im not sure if there is more i need to do that isn't listed in the HACS install.
Have you restarted HA and added the HACS integration in
https://my.home-assistant.io/redirect/integrations/
?
I did restart it multiple times, but not sure by adding the HACS integration in
Basically keep following the docs on their website. The script is just one part of the process.
Hmm i didn't see anything else in the guide.... ill google on HACS integration to see if i can find more i guess. I have been reading up on it and it seems the unRaid docker container version is CORE... if that helps
You might want to see if you canβt make a docker macvlan
Have you cleared the browser's cache?
And you need to actually add it
If HomeKit is also broken, sounds like the host is mucking with the multicasts in some way
I hate containers on these NAS devices. There is probably some kind of firewall most users do not know about or know how to configure
lol, i didn;t realize you had to add it.. i thought searching for it was trying to add it..
Thank you i managed to finally add HACS, i will continue reading on what i need from here. Thank you all for the help
How do I make sure docker compose is running automatically on system reboot?
As long as your containers are set to 'restart: unless-stopped' or similar, they start on their own
Awesome, thank you. I have one set to always, but otherwise good!
I'm still not sure how to get to things like portainer if I'm not home... On-network, it all works fine, I'm not using SSL and serving up via http, but if I access off network via nabu, it serves up using SSL, and https, and my Lovelace links don't work anymore
I just get the following error:
Unable to load iframes that load websites over http:// if Home Assistant is served over https://
I'm using the home assistant app though, maybe there's a setting in there
So then can I run everything USING ssl locally so that I can get to those items outside the network? What's normal SOP for that, if you're off network, assume you can't get to the deeper backend?
If they're locally hosted sites, you'd need to use a remote proxy like NGINX and expose it externally
That will handle SSL for you
Ahh, okay. So I couldn't get to it even if I was self-signing or something anyway. I dunno why, I thought for some reason that nabu was tunneling in somehow and serving up as a "local" instance that'd let me get to them
It is not a vpn or general proxy
Okay, struggling with probably a very basic thing... but I'm trying to create a group of most-used switches and a script, but my entity ID for one of my switches is the name of the switch, rather than what it controls (see screen cap) and if I try to rename just the switch (to switch.livingRoomLights) I get an "Invalid entity ID" error
eh, i can't upload a screen cap
switch.in_wall_toggle_switch_500s vs something like switch.LivingRoomLights
Am I missing something super simple? I thought I'd renamed the switch after adding it in via zwave, but I must have just renamed the device instead of the entity
Entities can't have uppercase letters
jesus
thank you.
any harm in having the various zwave elements (ping, node status, firmware, etc) having the assigned name, and the switch entity having a logical name?
entity ID*
Doesn't matter
Hello. Can I have both:
Use external nginx server running on same network (on proxmox). I would prefer this over HA nginx addon
Remove ssl_certificate for local non encrypted access.
Yes
Just found my mistake in nginx config π
I am running the downloaded image of the current on the current HA (OS Version: Home Assistant OS 11.2, Home Assistant Core: 2023.11.3) in a VMware VM. Can I install snmp service to monitor HA and sub containers with my monitoring system (PRTG)?
Short answer, no
Long answer, if there's an SNMP #add-ons-archived that provides that, yes
Was this directed at my question or something else?
yes, it was directed at you
it's a file system, just access the file system, pull the file, move it over to your new system
backup/restore should have done that, if it didn't, there's most likely an issue w/ your db.
Hmm. Whatβs the file look like? I see my configuration.yaml has a db_url with Maria-db in the URL. I guess it was set to use the addon?
oh you're using mariadb? Then it's significantly harder to pull this over.
you'll need to spool up your system, install phpmyadmin, export the database and import it into your new system
Ah. Spool up?
Can a Mac system read an HAOS formatted drive?
turn on old system, install phpmyadmin, export database from phpmyadmin to a file. Import file into new system using phpmyadmin.
No, you literally need to turn it on to get mariadb database
Right. Itβs.. kind of hard to physically access the new system. I will try putting the old SD card back in but I flashed my Pi to do USB booting
How much data is it?
A year
does it really matter that much? Just use the default database and build from now
Yeah. Might not be worth it. I was going to compare the attic seasonal temps post install of new attic venting but that would be the only important history
I'd like to restore a backup to new (identical) hardware (HA Blue/Hardkernal odroid N2). Any suggestion on how best to do this? HA OS backup/restore/reboot?
can you dual boot a pi4? Like have both an SD card install and a USB drive install?
π€·ββοΈ
Or I can maybe find and copy the database storage file from Maria without booting the old HAOS. Itβs a .sock file I think
That's pretty much it
Thanks
Guys, I screwd up my HA VM and now it's not getting an IP.
I'm running it on a Fedora Server with Cockpit (so... libvirt?).
Can anyone help diagnose my problem?
I need help troubleshooting network related configs for:
- Hypervisor
- Virtual NICs
- VNET
- Bridge
- VM
hello, I have instaled like this:
is this:
is it safe? or my network is exposed??
My odroid N2 console has pages of the following error: fe.dai-link-0: ASoC: no backend DAIs enabled for fe.dai-link-0. Not sure when this started since I don't often look at the console, but certainly in the last few weeks. I am guessing it is caused by some upgrade since it has not been there for the last couple of years until recently. Thoughts appreciated.
is it safe? or my network is exposed??
hi i have updated Home Assistant Operating System Update 11.2
i now have problems with supervisor it won't start
Dec 05 18:43:53 homeassistant hassio_supervisor[536]: [18:43:53] INFO: Supervisor restart after closing
Dec 05 18:43:55 homeassistant hassio_supervisor[536]: Error relocating /usr/lib/libstdc++.so.6: unct_cacheIT_E: symbol not found
Dec 05 18:43:55 homeassistant systemd[1]: Started Process Core Dump (PID 7670/UID 0).
Dec 05 18:43:56 homeassistant systemd-coredump[7671]: Process 7665 (python3) of user 0 dumped core.
Dec 05 18:43:56 homeassistant systemd[1]: systemd-coredump@333-7670-0.service: Deactivated successfully.
Dec 05 18:44:54 homeassistant kernel: audit: type=1334 audit(1701801867.899:2487): prog-id=1031 op=UNLOAD
it tries to reinstall supervisor docker image after several times
i have an rpi 4 with hassio installed
any help ?
Log showing that?
@torpid dagger Please use a code share site to share code or logs, for example:
- https://dpaste.org/ (select YAML for the language, and consider picking a longer expiry)
- http://pastie.org/ (select YAML for the language)
- https://paste.debian.net/ (you guessed it, select YAML as the language)
Please don't use Pastebin, since it can randomly add spaces to the main view. Please also don't share text as images since it makes it harder for people to help you. Remember that others may have colour blindness, impaired vision, etc.
fatal: unable to exec run: Exec format error

Never seen that before, not with HAOS
hey guys, i just updated my HA core from 2023.02 following the instructions from https://www.home-assistant.io/common-tasks/core/#update - it seems it somewhat updated itself to 2023.07, but for some reason nothing is available now: https://i.imgur.com/Ng2Dpoe.png
Sounds like wrong architecture
any idea how to fix this? i think after some 10 minutes it should detect my devices, wont it?
But an update shouldn't cause that... right?
ha os is basic install on my rpi right? what if i downgrade docker image of hassio_supervisor
docker ps
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
dd77deab8a7f ghcr.io/home-assistant/aarch64-hassio-supervisor:latest "/init" 14 minutes ago Up 14 minutes hassio_supervisor
7218e0cf2cab ghcr.io/home-assistant/aarch64-hassio-observer:2023.06.0 "/usr/bin/observer" 5 months ago Up 14 minutes 0.0.0.0:4357->80/tcp, :::4357->80/tcp hassio_observer
@torpid dagger To format your text as code, enter three backticks on the first line, press Enter for a new line, paste your code, press Enter again for another new line, and lastly three more backticks.
```yaml
example: here
```
Don't forget you can edit your post rather than repeatedly posting the same thing.
I would try a ha su repair
I know there was talk of eliminating 32-bit support
Error response from daemon: Container ebe2e5482afc16fa6e2ec5ca92b79da1803ea18a8d6930b5fe7120dd0913fa1d is not running```
Yeah, but that's some way off I suspect
otherwise, I got nothin'
Dec 05 19:12:57 homeassistant dockerd[539]: time="2023-12-05T19:12:57.797443590Z" level=error msg="Error setting up exec command in container hassio_cli: Container ebe2e5482afc16fa6e2ec5ca92b79da1803ea18a8d6930b5fe7120dd0913fa1d is not running"```
besides, the docker ps output above clearly says aarch64
I would just reinstall and restore from backup
it will take less time than trying to debug this issue, I suspect
HA OS. reflash, restore backup
trying to reinstall bits and pieces of it isn't going to end well
there could be lots of things wrong
ok this is a way to go for but before i would like to try old hassio_supervisor is there a way to it back to version before update
if the hassio_cli container doesn't start, then no ha commands will work, though
you'd have to use raw docker commands
do you know the raw command?
I read it from the bottom on the phone so I missed what the information was used for. I'd do docker inspect ebe2e5482 first to get some information about that container. Maybe you can just start it or figure out the image.
You can then grab the right image from here: https://github.com/orgs/home-assistant/packages?repo_name=supervisor
I don't know the run arguments the system uses though.
Seems to be this: https://github.com/home-assistant/operating-system/blob/1211b24c7f1d59b84eb7033fd737d62d199646c6/buildroot-external/rootfs-overlay/usr/sbin/hassos-supervisor#L88
s6-rc: info: service s6rc-oneshot-runner: starting
s6-rc: info: service s6rc-oneshot-runner successfully started
s6-rc: info: service fix-attrs: starting
s6-rc: info: service fix-attrs successfully started
s6-rc: info: service legacy-cont-init: starting
s6-rc: info: service legacy-cont-init successfully started
s6-rc: info: service legacy-services: starting
s6-rc: info: service legacy-services successfully started````
That's the CLI.
@raven forge does Fix Supervisor image corruption detection (#2953) mean update is corrupted?
That's just a commit message but perhaps. I don't know.
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
dd77deab8a7f ghcr.io/home-assistant/aarch64-hassio-supervisor:latest "/init" 43 minutes ago Up 42 minutes hassio_supervisor
7218e0cf2cab ghcr.io/home-assistant/aarch64-hassio-observer:2023.06.0 "/usr/bin/observer" 5 months ago Up 43 minutes 0.0.0.0:4357->80/tcp, :::4357->80/tcp hassio_observer````
should i pull hassio-supervisor?
I told you what you can do above. I had to read a bit of context first. hassio_supervisor is running. You can check the docker status of hassio_cli. Your output above is limited.
The CLI seems to be started here: https://github.com/home-assistant/supervisor/blob/c2d4be33042e6cd98412fd48e1639e7b0c605ec4/supervisor/docker/cli.py#L35
but that's not that useful and I kinda changed my stand point on debugging HAOS like this a bit. I feel like it sours people to HA more than when they're told to re-flash and restore.
hassio_cli is not running. I have started Home Assistant Operating System Update from 11.1 to 11.2 via webinterface after an hour it didn't come up. After that i have reseted my pi with the problem that supervisor is not running correct
ok i go with reflash
If you want to we can go further but I can't guarantee success.
ok tell me howto
I'd check docker ps -a | grep -i cli and see if it is just stopped. If yes you can try to start it.
You can also check docker logs --since 24h hassio_cli
1c6dc59d8470 ghcr.io/home-assistant/aarch64-hassio-cli:2023.10.0 "/init" 16 minutes ago Exited (111) 13 minutes ago youthful_khorana
ebe2e5482afc ghcr.io/home-assistant/aarch64-hassio-cli:2023.10.0 "/init" 3 weeks ago Exited (255) 2 hours ago hassio_cli
# ````
Okay check the logs first, then try docker start hassio_cli
I'd still like to see the logs (if it even logs anything) but sure.
# docker ps
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
dd77deab8a7f ghcr.io/home-assistant/aarch64-hassio-supervisor:latest "/init" 59 minutes ago Up 59 minutes hassio_supervisor
ebe2e5482afc ghcr.io/home-assistant/aarch64-hassio-cli:2023.10.0 "/init" 3 weeks ago Up 48 seconds hassio_cli
7218e0cf2cab ghcr.io/home-assistant/aarch64-hassio-observer:2023.06.0 "/usr/bin/observer" 5 months ago Up 59 minutes 0.0.0.0:4357->80/tcp, :::4357->80/tcp hassio_observer
# ha su repair
Post "http://supervisor/supervisor/repair": dial tcp 172.30.32.2:80: connect: no route to host
Is that the full output? There's a lot of things that are not up. That ip usually belongs to hassio_dns IIRC.
yes because of supervisor i guess
Have you tried a reboot already?
Hmm okay, try docker ps -a | grep -Ei '(hassio|core)*'
I don't think I've seen this before.
#
The * is important. I missed the ' at the end though
# ```
Sorry, has to look something like docker ps --filter status=exited | grep -Ei "(hassio|core)*". I always forget the different regex rules for different things.
I got my HAOS up now though so I can test the commands first.
need to paste it on webpage sorry
but limited pastin chat
i guess my problem is with latest supervisor image
is it possible to stop and reinstall image
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
1c6dc59d8470 ghcr.io/home-assistant/aarch64-hassio-cli:2023.10.0 "/init" 31 minutes ago Exited (111) 28 minutes ago youthful_khorana
a3992eafce38 ghcr.io/home-assistant/raspberrypi4-64-homeassistant:2023.11.3 "/init" 11 days ago Exited (0) 2 hours ago homeassistant
0241bbbf5c89 homeassistant/aarch64-addon-nginx_proxy:3.5.0 "/init" 3 weeks ago Exited (255) 2 hours ago 0.0.0.0:443->443/tcp, :::443->443/tcp addon_core_nginx_proxy
4ca5ec75afa6 ghcr.io/home-assistant/aarch64-hassio-multicast:2023.06.2 "/init" 3 weeks ago Exited (255) 2 hours ago hassio_multicast
d2f86b6ad74b ghcr.io/home-assistant/aarch64-hassio-audio:2023.10.0 "/init" 3 weeks ago Exited (255) 2 hours ago hassio_audio
847bd12a71f5 ghcr.io/home-assistant/aarch64-hassio-dns:2023.06.2 "/init" 3 weeks ago Exited (255) 2 hours ago hassio_dns
# ```
Try docker start hassio_dns, then ha supervisor repair again.
In theory yes but you have to figure out all the arguments that are being used and that's not that trivial. At least not for me as a non-python programmer.
hassio_dns
# ha supervisor repair
Post "http://supervisor/supervisor/repair": dial tcp 172.30.32.2:80: connect: no route to host
#```
docker logs hassio_dns
@torpid dagger I converted your message into a file since it's above 15 lines :+1:
Hmm. You can try something like this to get the container ip adresses.
for container in $(docker ps --format '{{ .ID }}'); do docker inspect $container --format='{{.Name}}: "{{range .NetworkSettings.Networks}}{{.IPAddress}}{{end}}"'; done
/hassio_dns: "172.30.32.3"
/hassio_cli: "172.30.32.5"
/hassio_observer: "172.30.32.6"```
supervisor has 232.2 right now but cli tries to repair 32.2
howto to tell cli to repair supervisor 232.2
π€·
Maybe try another reboot.
You also have to create the container and I can't tell you the args for it.
what about stop and start
docker stop hassio_supervisor and then docker start hassio_supervisor
Sure you can try that.
it is taking sometime stopping?
hassio_supervisor
# docker ps
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
847bd12a71f5 ghcr.io/home-assistant/aarch64-hassio-dns:2023.06.2 "/init" 3 weeks ago Up 14 minutes hassio_dns
ebe2e5482afc ghcr.io/home-assistant/aarch64-hassio-cli:2023.10.0 "/init" 3 weeks ago Up 28 minutes hassio_cli
7218e0cf2cab ghcr.io/home-assistant/aarch64-hassio-observer:2023.06.0 "/usr/bin/observer" 5 months ago Up About an hour 0.0.0.0:4357->80/tcp, :::4357->80/tcp hassio_observer
# docker start hassio_supervisor
Error response from daemon: No such container: hassio_supervisor
Error: failed to start containers: hassio_supervisor
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
1c6dc59d8470 ghcr.io/home-assistant/aarch64-hassio-cli:2023.10.0 "/init" 47 minutes ago Exited (111) 45 minutes ago youthful_khorana
a3992eafce38 ghcr.io/home-assistant/raspberrypi4-64-homeassistant:2023.11.3 "/init" 11 days ago Exited (0) 2 hours ago homeassistant
0241bbbf5c89 homeassistant/aarch64-addon-nginx_proxy:3.5.0 "/init" 3 weeks ago Exited (255) 2 hours ago 0.0.0.0:443->443/tcp, :::443->443/tcp addon_core_nginx_proxy
4ca5ec75afa6 ghcr.io/home-assistant/aarch64-hassio-multicast:2023.06.2 "/init" 3 weeks ago Exited (255) 2 hours ago hassio_multicast
d2f86b6ad74b ghcr.io/home-assistant/aarch64-hassio-audio:2023.10.0 "/init" 3 weeks ago Exited (255) 2 hours ago hassio_audio
#```
after stopping supervisor image is gone
is this maybe my problem that it was not correct deleted