Installing Home Assistant Supervised using Debian 12

pollinolas · August 15, 2020, 11:58pm

thank you very much, it worked for me

DavidFW1960 · August 16, 2020, 12:31am

I have no idea why this would be. I have used this for 2 years and always update via the supervisor button (or ssh if I am jumping the gun)

finity · August 16, 2020, 3:06am

Me neither. I thought it was strange too but every time I tried to update from within HA it never completed. But if I updated using Portainer it always worked. Until this time…

DavidFW1960 · August 16, 2020, 4:36am

So how are you doing that with Portainer? Are you sure you are talking about a supervised install?
A few months ago, for some inexplicable reason, one of the images/containers was removed. The audio one or one of those types… had constant errors in the logs about it. Or it might have been there with the wrong tag for the image and supervisor couldn’t start it. I eventually pulled the correct tagged image manually in Portainer, restarted supervisor and it was happy again. So certainly glitches are possible.

kanga_who · August 16, 2020, 4:57am

I’ve updated the guide with this info after testing as part of a fresh install, I’m getting no warnings or errors in HA. Thank you for the info @mjoshd.

finity · August 16, 2020, 2:00pm

start here:

ex1

Then you will see:

ex2

change the version at the end to what you want to update/downgrade to.

Then click:

ex3

Really?

But yes, I’m talking about a Supervised install:

poudenes · August 16, 2020, 2:45pm

I tried it on my RPi4 with Debian Buser Lite. Didn’t work. Still get the info my installation is unsupported

ghstudio · August 16, 2020, 6:28pm

did you read the information on that note? It’s normal…the note just is a warning that you are responsible for some of your own system support…there is another thread on this…many are seeing this note for the first time…but nothing has really changed.

kanga_who · August 16, 2020, 11:24pm

They have updated the installation script to include this now.

# Detect wrong docker logger config
if [ ! -f "$DOCKER_DAEMON_CONFIG" ]; then
  # Write default configuration
  info "Creating default docker deamon configuration $DOCKER_DAEMON_CONFIG"
  cat > "$DOCKER_DAEMON_CONFIG" <<- EOF
    {
        "log-driver": "journald",
        "storage-driver": "overlay2"
    }

finity · August 17, 2020, 2:12pm

Any idea how that change affects other docker containers?

I assume that it would be fine for everything else as well but I still like knowing what changes are being made systemwide that might affect other things.

poudenes · August 17, 2020, 6:13pm

Tried this, still get the message “You are running an unsupported installation."
I edit the daemon.json file outside the docker, so on root command line.
That is correct?

mjoshd · August 17, 2020, 10:01pm

If you follow the link and read the document it describes several conditions, all of which must be met, in order for the unsupported message to go away.

DavidFW1960 · August 17, 2020, 10:03pm

When you run

Docker info

From the command line hat does it tell you for the storage driver?
If it doesn’t show the right driver you did it wrong… You would do it on the Host OS where you installed docker.

@finity it hasn’t seemed to affect my other docker stuff.

poudenes · August 18, 2020, 7:41am

Did everything ok. Bit have same note…not supported…

Storage Driver: overlay2
Logging Driver: journald

see output docker info

Client:
 Debug Mode: false

Server:
 Containers: 12
  Running: 11
  Paused: 0
  Stopped: 1
 Images: 17
 Server Version: 19.03.12
 Storage Driver: overlay2
  Backing Filesystem: extfs
  Supports d_type: true
  Native Overlay Diff: true
 Logging Driver: journald
 Cgroup Driver: cgroupfs
 Plugins:
  Volume: local
  Network: bridge host ipvlan macvlan null overlay
  Log: awslogs fluentd gcplogs gelf journald json-file local logentries splunk syslog
 Swarm: inactive
 Runtimes: runc
 Default Runtime: runc
 Init Binary: docker-init
 containerd version: 7ad184331fa3e55e52b890ea95e65ba581ae3429
 runc version: dc9208a3303feef5b3839f4323d9beb36df0a9dd
 init version: fec3683
 Security Options:
  seccomp
   Profile: default
 Kernel Version: 5.4.51-v7l+
 Operating System: Raspbian GNU/Linux 10 (buster)
 OSType: linux
 Architecture: armv7l
 CPUs: 4
 Total Memory: 3.738GiB
 Name: <MY DOMAINNAME HERE>
 ID: 3BGR:4IET:KKOD:2VHF:G5ND:UEU4:5YI6:NA7J:VU6P:7WI6:276L:ZCRV
 Docker Root Dir: /var/lib/docker
 Debug Mode: false
 Registry: https://index.docker.io/v1/
 Labels:
 Experimental: false
 Insecure Registries:
  127.0.0.0/8
 Live Restore Enabled: false

WARNING: No memory limit support
WARNING: No swap limit support
WARNING: No kernel memory limit support
WARNING: No kernel memory TCP limit support
WARNING: No oom kill disable support
WARNING: No cpu cfs quota support
WARNING: No cpu cfs period support

DavidFW1960 · August 18, 2020, 8:08am

What does it say in the supervisor log?

tteck · August 18, 2020, 9:01am

Operating System: Raspbian GNU/Linux 10 (buster) - Not supported

EDIT: If your Operating System is anything other than Debian GNU/Linux 10 (buster), it is Not Supported in a supervised installation

poudenes · August 18, 2020, 9:25am

This is only thing I see in supervisor log:

20-08-18 06:38:42 CRITICAL (MainThread) [supervisor.core] System running in a unsupported environment!

Also there is a 0.114.2 update but this update is not showing anymore in supervisor as well

DavidFW1960 · August 18, 2020, 11:59am

Well that’s odd… mine is complaining about some other docker containers but no red text… Even when I had red text I had the update button. Did you try the reload option on that panel?

poudenes · August 18, 2020, 12:11pm

Yes I tried that also. Reboot RPi also didn’t work.
Maybe I have to do a fresh install with a supported OS

poudenes · August 18, 2020, 2:41pm

sudo journalctl CONTAINER_NAME=addon_a0d7b954_zwave2mqtt

Aug 18 12:29:32 MY.HOSTNAME.HIDE fd60504e0ab3[622]: 2020-08-18T10:29:32.902Z z2m:Zwave zwave node 96: changed: 50-1-256:Exporting:false -> false
Aug 18 12:29:35 MY.HOSTNAME.HIDE fd60504e0ab3[622]: 2020-08-18T10:29:35.840Z z2m:Zwave zwave node 79: changed: 50-1-0:Electric - kWh:4.58 -> 4.58
Aug 18 12:29:35 MY.HOSTNAME.HIDE fd60504e0ab3[622]: 2020-08-18T10:29:35.841Z z2m:Zwave zwave node 79: changed: 50-1-256:Exporting:false -> false
Aug 18 12:29:36 MY.HOSTNAME.HIDE fd60504e0ab3[622]: 2020-08-18T10:29:36.644Z z2m:Zwave zwave node 79: changed: 50-1-2:Electric - W:0 -> 0
Aug 18 12:29:36 MY.HOSTNAME.HIDE fd60504e0ab3[622]: 2020-08-18T10:29:36.646Z z2m:Zwave zwave node 79: changed: 50-1-256:Exporting:false -> false
Aug 18 12:29:37 MY.HOSTNAME.HIDE fd60504e0ab3[622]: 2020-08-18T10:29:37.638Z z2m:Zwave zwave node 79: changed: 50-1-4:Electric - V:234.23 -> 234.49

sudo journalctl CONTAINER_NAME=homeassistant

-- Logs begin at Tue 2020-08-18 12:25:07 CEST, end at Tue 2020-08-18 16:37:36 CEST. --
-- No entries --

sudo journalctl CONTAINER_NAME=hassio_supervisor

-- Logs begin at Tue 2020-08-18 12:25:07 CEST, end at Tue 2020-08-18 16:37:40 CEST. --
-- No entries --

sudo journalctl CONTAINER_NAME=hassio_dns 
Aug 18 12:26:36 MY.HOSTNAME.HIDE e4515dd6a321[622]: [INFO] 172.30.32.1:52784 - 25817 "AAAA IN feeds.livep2000.nl. udp 36 false 512" NOERROR qr,aa,rd,ra 128 0.000327809s
Aug 18 12:26:36 MY.HOSTNAME.HIDE e4515dd6a321[622]: [INFO] 172.30.32.1:52784 - 24910 "A IN feeds.livep2000.nl. udp 36 false 512" NOERROR qr,aa,rd,ra 70 0.0004879s
Aug 18 12:26:36 MY.HOSTNAME.HIDE e4515dd6a321[622]: [INFO] 172.30.32.1:52919 - 314 "A IN feeds.livep2000.nl. udp 36 false 512" NOERROR qr,aa,rd,ra 70 0.000206145s
Aug 18 12:26:36 MY.HOSTNAME.HIDE e4515dd6a321[622]: [INFO] 172.30.32.1:52919 - 1277 "AAAA IN feeds.livep2000.nl. udp 36 false 512" NOERROR qr,aa,rd,ra 128 0.000179794s
Aug 18 12:26:37 MY.HOSTNAME.HIDE e4515dd6a321[622]: [INFO] 172.30.32.1:38918 - 45370 "A IN feeds.livep2000.nl. udp 36 false 512" NOERROR qr,aa,rd,ra 70 0.000192737s
Aug 18 12:26:37 MY.HOSTNAME.HIDE e4515dd6a321[622]: [INFO] 172.30.32.1:38918 - 46184 "AAAA IN feeds.livep2000.nl. udp 36 false 512" NOERROR qr,aa,rd,ra 128 0.000208108s
Aug 18 12:26:37 MY.HOSTNAME.HIDE e4515dd6a321[622]: [INFO] 172.30.32.1:58558 - 12141 "A IN feeds.livep2000.nl. udp 36 false 512" NOERROR qr,aa,rd,ra 70 0.000399383s
Aug 18 12:26:37 MY.HOSTNAME.HIDE e4515dd6a321[622]: [INFO] 172.30.32.1:58558 - 14179 "AAAA IN feeds.livep2000.nl. udp 36 false 512" NOERROR qr,aa,rd,ra 128 0.000834375s
Aug 18 12:27:02 MY.HOSTNAME.HIDE e4515dd6a321[622]: [INFO] 172.30.32.1:33352 - 41398 "A IN feeds.livep2000.nl. udp 36 false 512" NOERROR qr,rd,ra 70 0.012455234s
Aug 18 12:27:02 MY.HOSTNAME.HIDE e4515dd6a321[622]: [INFO] 172.30.32.1:33352 - 43639 "AAAA IN feeds.livep2000.nl. udp 36 false 512" NOERROR qr,rd,ra 128 0.018759128s
Aug 18 12:27:06 MY.HOSTNAME.HIDE e4515dd6a321[622]: [INFO] 172.30.32.1:47109 - 26751 "AAAA IN feeds.livep2000.nl. udp 36 false 512" NOERROR qr,aa,rd,ra 128 0.000166145s

So homeassistent and hassio_supervisor are both not using it. But other do…
I don’t understand it… haha