I believe this is a known issue but I can't see that anyone has documented a solution so far. If I can't use the bash shell in the container to edit my yaml files (see previous issue logged) and I can't SSH in, then how are users managing their HA files?

Clearly I'm missing something!

I don't know how to edit the readme file in github.

My suggestion for change to the readme file are:
"dbus-daemon" change this to "dbus"
"networkmanager" change this to "network-manager"

I am new to linux and installed ubuntu then tried to go through the installation instructions for hass.io
I needed to type "sudo apt-get install dbus" and "sudo apt-get install network-manager".
I think this change would help new users like me who get stuck, then have to google these steps.

Cheers
Kiwi

When trying to run the script nothing happens... When I execute journalctl -f it returns this:

Dec 26 14:11:18 hassio sudo[8792]: pam_unix(sudo:session): session closed for user root
Dec 26 14:11:19 hassio avahi-daemon[5226]: Joining mDNS multicast group on interface docker0.IPv6 with address fe80::42:2eff:fe7e:71c6.
Dec 26 14:11:19 hassio avahi-daemon[5226]: New relevant interface docker0.IPv6 for mDNS.
Dec 26 14:11:19 hassio avahi-daemon[5226]: Registering new address record for fe80::42:2eff:fe7e:71c6 on docker0.*.
Dec 26 14:14:34 hassio sudo[9032]:     root : TTY=pts/0 ; PWD=/root ; USER=root ; COMMAND=/bin/netstat -tulpn
Dec 26 14:14:34 hassio sudo[9032]: pam_unix(sudo:session): session opened for user root by hassio(uid=0)
Dec 26 14:14:34 hassio sudo[9032]: pam_unix(sudo:session): session closed for user root
Dec 26 14:17:01 hassio CRON[9054]: pam_unix(cron:session): session opened for user root by (uid=0)
Dec 26 14:17:01 hassio CRON[9055]: (root) CMD (   cd / && run-parts --report /etc/cron.hourly)
Dec 26 14:17:01 hassio CRON[9054]: pam_unix(cron:session): session closed for user root```

Trying to create a base image build with --base results in the build hanging forever. This is because of a missing check for the --base flag in the code.

I don't know if this is the right starting point.

Hi if have problems with installing new node red plugin. At first it works but after a curtain time its going into a error loop, i tried the stable and the beta version off hassio.

I also have a RPI whit hassio and there is no problem with that.

logfile below line

[cont-init.d] executing container initialization scripts...
[cont-init.d] 00-banner.sh: executing...

Hass.io Add-on: Node-RED v1.1.0

Flow-based programming for the Internet of Things

From: Community Hass.io Add-ons
By: Franck Nijhof [email protected]

[cont-init.d] 00-banner.sh: exited 0.
[cont-init.d] 01-log-level.sh: executing...
Log level is set to INFO
[cont-init.d] 01-log-level.sh: exited 0.
[cont-init.d] 02-updates.sh: executing...

INFO: You are running the latest version of this add-on
[cont-init.d] 02-updates.sh: exited 0.
[cont-init.d] 10-requirements.sh: executing...
[cont-init.d] 10-requirements.sh: exited 0.
[cont-init.d] 11-warning.sh: executing...
WARNING: No users configured and authentication has been disabled!
WARNING: This is not recommended!!!
[cont-init.d] 11-warning.sh: exited 0.
[cont-init.d] 20-config.sh: executing...
[cont-init.d] 20-config.sh: exited 0.
[cont-init.d] 80-system-packages.sh: executing...
[cont-init.d] 80-system-packages.sh: exited 0.
[cont-init.d] 81-npm-packages.sh: executing...
[cont-init.d] 81-npm-packages.sh: exited 0.
[cont-init.d] 82-user-scripts.sh: executing...
[cont-init.d] 82-user-scripts.sh: exited 0.
[cont-init.d] done.
[services.d] starting services
[services.d] done.

[email protected] start /opt
node $NODE_OPTIONS node_modules/node-red/red.js "--settings" "/etc/node-red/config.js"

Error loading settings file: /etc/node-red/config.js
TypeError: Cannot read property 'length' of undefined
at Object. (/etc/node-red/config.js:27:19)
at Module._compile (module.js:635:30)
at Object.Module._extensions..js (module.js:646:10)
at Module.load (module.js:554:32)
at tryModuleLoad (module.js:497:12)
at Function.Module._load (module.js:489:3)
at Module.require (module.js:579:17)
at require (internal/module.js:11:18)
at Object. (/opt/node_modules/node-red/red.js:115:20)
at Module._compile (module.js:635:30)

[email protected] start /opt
node $NODE_OPTIONS node_modules/node-red/red.js "--settings" "/etc/node-red/config.js"

Error loading settings file: /etc/node-red/config.js
TypeError: Cannot read property 'length' of undefined
at Object. (/etc/node-red/config.js:27:19)
at Module._compile (module.js:635:30)
at Object.Module._extensions..js (module.js:646:10)
at Module.load (module.js:554:32)
at tryModuleLoad (module.js:497:12)
at Function.Module._load (module.js:489:3)
at Module.require (module.js:579:17)
at require (internal/module.js:11:18)
at Object. (/opt/node_modules/node-red/red.js:115:20)

I'm on a TinkerBoard S. Installed TinkerOS latest version on eMMC. Update/Upgrade all. Docker is ready.

Even if avahi has been installed i get this error :
[Error] Please install avahi first
due to this test:
command -v avahi-daemon > /dev/null 2>&1 || { echo "[Error] Please install avahi first"; exit 1; }

Hello

I'm trying to use hassio, after the installation appears 404: Not Found.
Raspberry Pi3 32bit
http://10.0.1.4:8123
I installed using this command

sudo curl -sL https://raw.githubusercontent.com/home-assistant/hassio-build/master/install/hassio_install | sudo bash -s -m raspberrypi3

pi @ raspberrypi: ~ $ docker ps
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
763bb344cddf homeassistant / raspberrypi3-homeassistant "/bin/entry.sh pytho ..." 4 minutes ago Up 4 minutes homeassistant
0d72d13cb7df homeassistant / armhf-hassio-supervisor "python3 -m hassio" 30 minutes ago Up 5 minutes hassio_supervisor

docker logs 763bb344cddf

2018-11-24 02:24:37 ERROR (MainThread) [aiohttp.server] Error handling request
Traceback (most recent call last):
  File "/usr/local/lib/python3.6/site-packages/aiohttp/web_protocol.py", line 390, in start
    resp = await self._request_handler (request)
  File "/usr/local/lib/python3.6/site-packages/aiohttp/web_app.py", line 366, in _handle
    resp = await handler (request)
  File "/usr/local/lib/python3.6/site-packages/aiohttp/web_middlewares.py", line 106, in impl
    return await handler (request)
  File "/usr/local/lib/python3.6/site-packages/homeassistant/components/http/static.py", line 66, in staticresource_middleware
    return await handler (request)
  File "/usr/local/lib/python3.6/site-packages/homeassistant/components/http/real_ip.py", line 34, in real_ip_middleware
    return await handler (request)
  File "/usr/local/lib/python3.6/site-packages/homeassistant/components/http/ban.py", line 66, in ban_middleware
    return await handler (request)
  File "/usr/local/lib/python3.6/site-packages/homeassistant/components/http/auth.py", line 97, in auth_middleware
    return await handler (request)
  File "/usr/local/lib/python3.6/site-packages/homeassistant/components/http/real_ip.py", line 34, in real_ip_middleware
    return await handler (request)
  File "/usr/local/lib/python3.6/site-packages/homeassistant/components/http/ban.py", line 66, in ban_middleware
    return await handler (request)
  File "/usr/local/lib/python3.6/site-packages/homeassistant/components/http/auth.py", line 97, in auth_middleware
    return await handler (request)
  File "/usr/local/lib/python3.6/site-packages/homeassistant/components/http/view.py", line 113, in handle
    result = await result
  File "/usr/local/lib/python3.6/site-packages/homeassistant/components/http/ban.py", line 76, in handle_req
    resp = await func (view, request, * args, ** kwargs)
  File "/usr/local/lib/python3.6/site-packages/homeassistant/components/auth/init.py", line 258, in post
    hass, data, str (request [KEY_REAL_IP]))
  File "/usr/local/lib/python3.6/site-packages/homeassistant/components/auth/init.py", line 346, in _async_handle_refresh_token
    refresh_token = await hass.auth.async_get_refresh_token_by_token (token)
  File "/usr/local/lib/python3.6/site-packages/homeassistant/auth/init.py", line 330, in async_get_refresh_token_by_token
    return await self._store.async_get_refresh_token_by_token (token)
  File "/usr/local/lib/python3.6/site-packages/homeassistant/auth/auth_store.py", line 204, in async_get_refresh_token_by_token
    await self._async_load ()
  File "/usr/local/lib/python3.6/site-packages/homeassistant/auth/auth_store.py", line 247, in _async_load
    name = group_dict ['name'],
KeyError: 'name'

Could someone give a help?

Thank you very much

Hi,

I have installed as describe here hassio o Odroid HC2 (using machine odroid-xu), Everything went without error (I did not installed network-manager only). After some time I was able to connect to HA on port 8123 set up password and it seems working well but I have an error that hassio component can not be start check config. I have hassio: in my configuration.yaml.

2018-11-30 04:01:12 WARNING (MainThread) [homeassistant.setup] Setup of hassio is taking over 10 seconds. 2018-11-30 04:01:12 ERROR (MainThread) [homeassistant.components.hassio.handler] Timeout on /supervisor/ping request 2018-11-30 04:01:12 ERROR (MainThread) [homeassistant.components.hassio] Not connected with Hass.io 2018-11-30 04:01:12 INFO (MainThread) [homeassistant.setup] Setup of domain hassio took 10.0 seconds. 2018-11-30 04:01:12 ERROR (MainThread) [homeassistant.setup] Setup failed for hassio: Component failed to initialize. 2018-11-30 04:01:12 INFO (MainThread) [homeassistant.bootstrap] Home Assistant initialized in 13.93s

I am using Portrainer to control containers and I see both HA and Hassio are running.
But Hassio-supervisior has an errors as well:
[32m18-11-30 04:00:23 INFO (MainThread) [__main__] Initialize Hass.io setup�[0m �[32m18-11-30 04:00:23 INFO (MainThread) [__main__] Setup HassIO�[0m �[32m18-11-30 04:00:23 INFO (SyncWorker_0) [hassio.docker.supervisor] Attach to Supervisor homeassistant/armhf-hassio-supervisor with version 140�[0m �[32m18-11-30 04:00:23 INFO (MainThread) [hassio.utils.gdbus] Introspect org.freedesktop.systemd1 on /org/freedesktop/systemd1�[0m �[32m18-11-30 04:00:23 INFO (MainThread) [hassio.utils.gdbus] Connect to dbus: org.freedesktop.systemd1 - /org/freedesktop/systemd1�[0m �[32m18-11-30 04:00:23 INFO (MainThread) [hassio.utils.gdbus] Introspect org.freedesktop.hostname1 on /org/freedesktop/hostname1�[0m �[32m18-11-30 04:00:24 INFO (MainThread) [hassio.utils.gdbus] Connect to dbus: org.freedesktop.hostname1 - /org/freedesktop/hostname1�[0m �[32m18-11-30 04:00:24 INFO (MainThread) [hassio.utils.gdbus] Introspect de.pengutronix.rauc on /�[0m �[31m18-11-30 04:00:24 ERROR (MainThread) [hassio.utils.gdbus] DBus return error: b'Error: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name de.pengutronix.rauc was not provided by any .service files\n'�[0m �[33m18-11-30 04:00:24 WARNING (MainThread) [hassio.dbus.rauc] Can't connect to rauc�[0m �[32m18-11-30 04:00:24 INFO (MainThread) [hassio.host.info] Update local host information�[0m �[32m18-11-30 04:00:24 INFO (MainThread) [hassio.utils.gdbus] Call org.freedesktop.DBus.Properties.GetAll on /org/freedesktop/hostname1�[0m �[32m18-11-30 04:00:24 INFO (MainThread) [hassio.host.services] Update service information�[0m �[32m18-11-30 04:00:24 INFO (MainThread) [hassio.utils.gdbus] Call org.freedesktop.systemd1.Manager.ListUnits on /org/freedesktop/systemd1�[0m �[32m18-11-30 04:00:24 INFO (MainThread) [hassio.host.apparmor] Load AppArmor Profiles: {'hassio-supervisor'}�[0m �[32m18-11-30 04:00:24 INFO (MainThread) [hassio.host.services] Reload local service hassio-apparmor.service�[0m �[32m18-11-30 04:00:24 INFO (MainThread) [hassio.utils.gdbus] Call org.freedesktop.systemd1.Manager.ReloadOrRestartUnit on /org/freedesktop/systemd1�[0m �[32m18-11-30 04:00:24 INFO (SyncWorker_1) [hassio.docker.interface] Attach to image homeassistant/odroid-xu-homeassistant with version 0.82.1�[0m �[32m18-11-30 04:00:24 INFO (MainThread) [hassio.addons.git] Load add-on /data/addons/core repository�[0m �[32m18-11-30 04:00:24 INFO (MainThread) [hassio.addons.git] Load add-on /data/addons/git/a0d7b954 repository�[0m �[32m18-11-30 04:00:24 INFO (MainThread) [hassio.addons] Load add-ons: 47 all - 47 new - 0 remove�[0m �[32m18-11-30 04:00:25 INFO (MainThread) [hassio.updater] Fetch update data from https://s3.amazonaws.com/hassio-version/stable.json�[0m �[32m18-11-30 04:00:27 INFO (MainThread) [hassio.snapshots] Found 0 snapshot files�[0m �[32m18-11-30 04:00:27 INFO (MainThread) [hassio.discovery] Load 0 messages�[0m �[32m18-11-30 04:00:27 INFO (MainThread) [__main__] Run Hass.io�[0m �[32m18-11-30 04:00:27 INFO (MainThread) [hassio.misc.dns] Start DNS port forwarding for host add-ons�[0m �[32m18-11-30 04:00:27 INFO (MainThread) [hassio.core] Ignore Hass.io auto updates on dev channel�[0m �[32m18-11-30 04:00:27 INFO (MainThread) [hassio.api] Start API on 172.30.32.2�[0m �[32m18-11-30 04:00:27 INFO (MainThread) [hassio.addons] Startup initialize run 0 add-ons�[0m �[32m18-11-30 04:00:27 INFO (MainThread) [hassio.core] Hass.io reboot detected�[0m �[32m18-11-30 04:00:27 INFO (MainThread) [hassio.tasks] All core tasks are scheduled�[0m �[32m18-11-30 04:00:27 INFO (MainThread) [hassio.core] Hass.io is up and running�[0m �[33m18-11-30 04:00:42 WARNING (MainThread) [hassio.tasks] Watchdog found a problem with Home Assistant Docker!�[0m �[32m18-11-30 04:00:42 INFO (SyncWorker_5) [hassio.docker.interface] Clean homeassistant/odroid-xu-homeassistant Docker application�[0m �[32m18-11-30 04:00:44 INFO (SyncWorker_5) [hassio.docker.homeassistant] Start homeassistant homeassistant/odroid-xu-homeassistant with version 0.82.1�[0m �[33m18-11-30 04:12:23 WARNING (MainThread) [hassio.homeassistant] Don't wait anymore of Home Assistant startup!�[0m �[31m18-11-30 04:12:23 ERROR (MainThread) [hassio.tasks] Watchdog Home Assistant reanimation fails!�[0m

Help please?

hey,

i try to install hass.io on a rpi3b, not rpi3b+, with an aarch64 arch linux.
i run curl -sL https://raw.githubusercontent.com/home-assistant/hassio-build/master/install/hassio_install | sudo bash -s -- -m raspberrypi3-64 -d /home/alarm/share

With raspberrypi3 as -m i got an error with when the homeassistant container tries to start:

[FATAL tini (8)] exec /usr/bin/entry.sh failed: Exec format error

and get this error in the supervisor log:

18-03-25 09:46:40 INFO (MainThread) [hassio.homeassistant] No HomeAssistant docker homeassistant/raspberrypi3-64-homeassistant found.
18-03-25 09:46:40 INFO (MainThread) [hassio.homeassistant] Setup HomeAssistant landingpage
18-03-25 09:46:40 INFO (SyncWorker_0) [hassio.docker.interface] Pull image homeassistant/raspberrypi3-64-homeassistant tag landingpage.
18-03-25 09:46:43 ERROR (SyncWorker_0) [hassio.docker.interface] Can't install homeassistant/raspberrypi3-64-homeassistant:landingpage -> 404 Client Error: Not Found ("manifest for homeassistant/raspberrypi3-64-homeassistant:landingpage not found").

when I run this I get "cannot execute L" running raspbian on an RPi. any help I could get would be greatly appreciated

I started using hassio around 87.* During install I overrode the default source dir from /usr/share/hassio to /opt/hassio.
Several updates later, mostly on the beta branch, I was sitting on 89b2 and had experienced no issues with updates. I then received update notice for 89.0, after coming back online hass had lost my auth config, then I noticed no lovelace and finally I noticed the version had gone back to 87.1.
A bit of investigation and I realised that hass.io was now using the default source folder for loading of homeassistant and supervisor rather than the overriden one.

please excuse me if these are basic docker questions vs hassio questions.
I got this up and running very easily on my NUC. I'm used to managing my yaml files from a CLI within the filesystem of my RPI (typically I use Nano), but so far I see that none of my normal CLI commands (including nano) are available from the bash shell within the container.
(Note: I got to the bash shell with this command sudo docker exec -t -i homeassistant /bin/bash). Even the typical hassio CLI commands don't seem to be available.

Any suggestions?

hi, which is the correct way to install hassio on coreos (which is a stripped down os to run containers, no way to install addon packages there...)?
tried to build container based on stock hassio from https://github.com/home-assistant/hassio, and using this docker-compose.yml it complains about "18-08-24 09:57:39 CRITICAL (MainThread) [hassio.bootstrap] Can't find SUPERVISOR_SHARE in env!" even if build was successful:

version: '3'

services:
  hassio:
    container_name: hassio
    build:
      context: .
      args:
        BUILD_FROM: python:3.7-alpine3.8
    image: hassio/mine:amd64
    restart: always
    ports:
      - "8123:8123"
    network_mode: bridge

tried hassio_install, and it fails:

core@localhost ~ $ curl -sL https://raw.githubusercontent.com/home-assistant/hassio-build/master/install/hassio_install | bash -s
[Error] Please install avahi first

tried using builder, again errors:

core@localhost ~/t $ docker run --rm --privileged -v ~/.docker:/root/.docker homeassistant/amd64-builder --amd64
[INFO] Setup crosscompiling feature
[INFO] Starting docker.
[INFO] Waiting for docker to initialize...
[INFO] Docker was initialized
[INFO] Run addon build for: amd64
jq: error: Could not open file /config.json: No such file or directory
jq: error: Could not open file /config.json: No such file or directory
jq: error: Could not open file /config.json: No such file or directory

if i'm missing some parameters, please suggest me how to do, thanks in advance

Ciao a tutti,

Ho hass.io e utilizzo dei sonoff basic per controllare luci ed altro.
Quando va via la connessione internet oppure riavvio il mio router i sonoff con tasmota firmware cambiano il loro stato. Da spenti ad accesso ad esempio. Come posso risolvere questo problema?

Grazie

I have installed Hass.io based on the guide in this repository on a Raspberry Pi 3 B+ with Raspbian Stretch Lite (which has a fix IP and is accessible only via SSH) and Docker Community Edition (installed using the convenience scripts).

Now I have the problem that I can only access the Home Assistant UI via Chrome from the notebook which I have used to install Hass.io (over SSH) on the Pi. From other devices (like a Android mobile using Chrome) in the same network I can't access the UI.

Has anyone an idea to solve this problem?

Thank you!

I ran the installation instructions for the 'hassio_install' script and it suddenly restarted my docker deamon, thus also restarting my OctoPrint server, thereby aborting my ongoing 3d-print. It's not cool to just forcefully restart services on my system without asking.

Guess I'll throw away the wasted plastic and start again!

parsing output from docker --version fails on Fedora 29:

Output:

++ docker --version
++ grep -Po '\d{2}\.\d{2}\.\d'
+ DOCKER_VERSION=
$ docker --version 
Docker version 1.13.1, build accfe55-unsupported

Hi. I'm trying to use Folder Watcher to monitor the /backup folder, but when I add it to whitelist_external_dirs the config check reports not a directory @ data['whitelist_external_dirs'][0].
Issuing a docker inspect homeassistant I can see there are mounts for /config, /ssl and /share:

   "HostConfig": {
            "Binds": [
                "/usr/share/hassio/homeassistant:/config:rw",
                "/usr/share/hassio/ssl:/ssl:ro",
                "/usr/share/hassio/share:/share:rw"
            ]

...but /backup is missing, so no core components can access that folder. Is this by design? How can I monitor /backup folder then?

Here's my /etc/hassio.json:

{
    "supervisor": "homeassistant/armhf-hassio-supervisor",
    "homeassistant": "homeassistant/raspberrypi3-homeassistant",
    "data": "/usr/share/hassio"
}

and my /usr/share/hassio/updater.json which stands the current versions I'm running:

{
  "channel": "stable",
  "hassio": "140",
  "homeassistant": "0.82.1"
}

Thank you in advance.

19-01-25 16:58:35 ERROR (SyncWorker_13) [hassio.docker.interface] Can't install homeassistant/armv7l-homeassistant:landingpage -> 404 Client Error: Not Found ("pull access denied for homeassistant/armv7l-homeassistant, repository does not exist or may require 'docker login'").

ExecStop=-/usr/bin/docker stop hassio_supervisor

see this - ?
should b
ExecStop=/usr/bin/docker stop hassio_supervisor

Though this typo be small it causes any system to hang at shutdown/reboot for several minutes with a stop job until that finally times out.

According to the docs, the add-on config.json arch key is:

List of supported arch: armhf, aarch64, amd64, i386. Default all.

However with the changes made in 72986ef (specifically this section), the builder refuses to build any arch for an add-on that does not have the arch key in config.json with the message: [ERROR] $ARCH not supported for this add-on.

This differs from the old (and IMO correct) behavior of allowing builds of all archs when the arch key is missing.

I'm going to freely admit being a bit of a newb here. I have a tiny server running ubuntu 16.04 LTE (AMD Athlon P340, 4 GB mem), and I'd like to keep everything on it rather than add another Pi to the mix. I've tried rebuilding it multiple times and cannot get this running. It looks like the setup has changed in the last few days. Is there going to be a revision to the installation guide? I know you don't owe me anything, I'm just looking for some guidance on my best course of action, as I really like the ease of use of running hass.io vs standalone home assistant. Thanks in advance.

I'm trying to build a multi-architecture addon. Unfortunately, while every other architecture builds quickly, armhf builds take significantly longer. Currently my GitLab CI timeout is set at 2 hours, and my armhf builds are stuck running ./configure, so fairly early in the build process.

The addon source can be seen here, and the build script is here. The build logs and history are all public, so you can see how long other builds take and where this times out in the armhf build process.

It's interesting that this architecture takes significantly longer to build, and the fact that it is arm doesn't matter much since aarch64 builds seem to complete quickly.

I've tried building this both on GitLab's shared runners, and locally on my I7 laptop with 8 GB, just in case the runners were under-powered. Both places yield the same results.

Thanks!

hi!

After install hassio with command:

curl -sL https://raw.githubusercontent.com/home-assistant/hassio-build/master/install/hassio_install | bash -s -- -m raspberrypi3-64

I got the follow error. Please help to fix it. Thanks

Jun 26 11:43:41 raspberrypi hassio-supervisor[3180]: 18-06-26 04:43:41 INFO (SyncWorker_5) [hassio.docker.interface] Pull image homeassistant/qemu-armhf-homeassistant tag landingpage.
Jun 26 11:43:45 raspberrypi dockerd[487]: time="2018-06-26T11:43:45.174328912+07:00" level=error msg="Not continuing with pull after error: errors:\ndenied: requested access to the resource is denied\nunauthorized: authentication required\n"
Jun 26 11:43:45 raspberrypi dockerd[487]: time="2018-06-26T11:43:45.176456113+07:00" level=info msg="Ignoring extra error returned from registry: unauthorized: authentication required"
Jun 26 11:43:45 raspberrypi hassio-supervisor[3180]: 18-06-26 04:43:45 ERROR (SyncWorker_5) [hassio.docker.interface] Can't install homeassistant/qemu-armhf-homeassistant:landingpage -> 404 Client Error: Not Found ("pull access denied for homeassistant/qemu-armhf-homeassistant, repository does not exist or may require 'docker login'").
Jun 26 11:43:45 raspberrypi hassio-supervisor[3180]: 18-06-26 04:43:45 WARNING (MainThread) [hassio.homeassistant] Fails install landingpage, retry after 60sec

Right now, the aarch64 docker image of home assistant has no "landingpage" tag, so it can't be used as our HOMEASSISTANT_REPOSITORY for new hassos defconfigs.

eg.
https://github.com/rbray89/hassos/blob/0458041d3ecff82284d1def6887f0cac8f72e82b/buildroot-external/configs/odroidc2_defconfig#L86
https://hub.docker.com/r/homeassistant/aarch64-homeassistant/tags/

I have written an device_tracker based on arp-scan, which is very fast.
I would like to use this component with hass.io without the need to create an add-on and work via mqtt.
So is it possible to add arp-scan to next build?

hi there!

what're commands to test if install correctly?
did the installation script map port 8123 to host port yet?

Regards

When I run:
curl -sL https://raw.githubusercontent.com/home-assistant/hassio-build/master/install/hassio_install | bash -s -- -m raspberrypi3

I get error:
[Warning] No AppArmor support on Host.
[Warning] No NetworkManager support on Host.
[Info] Install supervisor docker
[Info] Install supervisor startup scripts
[Info] Run Hass.io
Failed to start hassio-supervisor.service: Unknown unit: hassio-supervisor.service
See system logs and 'systemctl status hassio-supervisor.service' for details.

systemctl status hassio-supervisor.service
Failed to get properties: No such interface ''

In system-connection\resin-sample, i using Notepad++ to put ssid & psk, but my RP3P can't join network!

Is there a way to have the supervisor tag addons and homeassistant with the appropriate nginx-proxy and letsencrypt tags? This would automate the issue of certs. Example environment entries on a manually configured home-assistant docker container.

• VIRTUAL_HOST=hass.${DOMAIN_NAME}
• VIRTUAL_PORT=80
• VIRTUAL_PROTO=http
• LETSENCRYPT_HOST=hass.${DOMAIN_NAME}
• LETSENCRYPT_EMAIL=${EMAIL_ADDRESS}

Those values make hass.${DOMAIN_NAME} available on port 443 which proxies you to port 80 on the hass container. The ssl certificates are auto generated.

Info links below.
https://github.com/jwilder/nginx-proxy
https://github.com/JrCs/docker-letsencrypt-nginx-proxy-companion

Hi, I am running

curl -sL https://raw.githubusercontent.com/home-assistant/hassio-build/master/install/hassio_install | bash -s -- -m raspberrypi3

on a raspberry pi 3 with latest Raspbian 9 lite and I get the following error

[Info] Install supervisor docker
Tag 123 not found in repository docker.io/homeassistant/armhf-hassio-supervisor

I am running under sudo su and all dependencies have been installed.
What could be going wrong?
Thanks!

Hi All,

I Run Debian 9 and installed via the Installer and works just PERFECT except for im really too stupid to reverse where the Docker image for Home Assistant is started so I can add the map device to my system??

Can anybody please help me to point in the right direction?

I was in the supervisor docker and trying to reverse the hassio.py but gave up - there must be an option to find the composer config or where the docker runtime is defined?

I installed hassio and homeassistant using the hassio_install script. It initially pulled the latest homeassistant image, which at the time was 0.75. There was a bug in 0.75 that prevented the hassio tab from loading, and therefore you couldn't upgrade homeassistant.

Re-running the install script will always pull the latest hassio image, but uses the pre-existing homeassistant image. I manually did a docker pull for the latest homeassistant image which resolved my issue.

Any reason why the hassio_install script doesn't force pull the latest version of the container?

Since upgrading to .69 when I reboot my HASS the automations do not auto deploy I have to go in and manually start them by pressing the refresh automations button. Also updating to 0.69.1 didn't help I've reached out on the forms and it seams I am not the only one with this issue.

Hi,
After my issue was close due to having portrainer I did clean install of archlinux docker and run the script as described:
I have installed as describe here hassio o Odroid HC2 (using machine odroid-xu), Everything went without error (I did not installed network-manager only). After some time I was able to connect to HA on port 8123 set up password and it seems working well but I have an error that hassio component can not be start check config.

Setup failed for hassio: Component failed to initialize. ‎9‎:‎37‎ ‎AM setup.py (ERROR) Not connected with Hass.io ‎9‎:‎37‎ ‎AM components/hassio/__init__.py (ERROR) Timeout on /supervisor/ping request ‎9‎:‎37‎ ‎AM components/hassio/handler.py (ERROR) Setup of hassio is taking over 10 seconds. ‎9‎:‎37‎ ‎AM util/async_.py (WARNING) Retrying in 18 minutes: Cannot connect to host aa015h6buqvih86i1.api.met.no:443 ssl:None [Try again] ‎9‎:‎37‎ ‎AM components/sensor/yr.py (ERROR) Database is about to upgrade. Schema version: None ‎9‎:‎37‎ ‎AM components/recorder/migration.py (WARNING)

So now I wat is the reason it is not working ?

After docker stats I can see both homeassistant and hassio_supervisor containers are running.

Please help.

Would be nice with a latest tag for the latest rpi3 docker version. This way you can have the docker auto-update by using a docker container like: https://github.com/v2tec/watchtower.

When I run the installer script
curl -sL https://raw.githubusercontent.com/home-assistant/hassio-build/master/install/hassio_install | bash -s
I get the following error

`root@homeassistant:/home/ha# curl -sL https://raw.githubusercontent.com/home-assistant/hassio-build/master/install/hassio_install | bash -s

[Info] Install supervisor docker
invalid reference format`

is there a log what is created I am having difficulty finding any useful information

thanks

At Debian 9.4 hassio_install keeps showing '[Error] Please install avahi first'. Seems that packet already included. After removing line number 19 from the script all went fine.
Happy days.

It appears hassio is running as a root user. See more details here:

https://community.home-assistant.io/t/what-user-does-the-hass-io-container-run-under/45803/5?u=60ft

I am experimenting with the command_line feature of HA.
I have the HASSIO-docker installed in a Debian Proxmox VM.

I have written a script that works on debian but not inside the HASSIO-docker.
The culprit is "grep": I'm using the grep -oP option to filter data between two characters: - and .
I'm filtering out the characters of a string eg "-1234.5678/><" to the string "1234"

When I run the script inside the HASSIO-docker I get the warning: grep: unrecognized option: P

Is there any way to install a full version of grep inside the Docker?

clean install on ubuntu 16.04

using the curl -sL https://raw.githubusercontent.com/home-assistant/hassio-build/master/install/hassio_install | bash -s command:

It does not complete the install. It appears to install and start the container but the container just crashes and restarts in a loop. The usr/share/hassio/home-assistant folder is missing everything but apparmor folder.

When running the builder instruction from here under MacOS, I get the following error:

error creating aufs mount to /var/lib/docker/aufs/mnt/ab197f71211cb833b324b17e75c0ba2e0a7f7b2599410238980a9e2b5aa27c9d-init: invalid argument

The solution I found was in this issue: go to Docker-for-mac preferences > Daemon > Advanced, and add in the "storage-driver": "aufs" key

{
    ... might have other keys already,
    "storage-driver" : "aufs"
}

@gabrielaraujof commented on Jan 29, 2018, 5:15 PM UTC:

I'm trying to install home-assistant via hassio on my OrangePi PC board running the armbian OS. Everything seems to be installed fine, but when I try to start hassio I got an error:

gabriel@orangepipc:~$ hassio-start
18-01-29 17:13:30 INFO (SyncWorker_4) [hassio.docker.interface] Pull image homeassistant/armhf-homeassistant tag landingpage.
18-01-29 17:13:32 ERROR (SyncWorker_4) [hassio.docker.interface] Can't install homeassistant/armhf-homeassistant:landingpage -> 404 Client Error: Not Found ("manifest for homeassistant/armhf-homeassistant:landingpage not found").
18-01-29 17:13:32 WARNING (MainThread) [hassio.homeassistant] Fails install landingpage, retry after 60sec
18-01-29 17:14:32 INFO (SyncWorker_9) [hassio.docker.interface] Pull image homeassistant/armhf-homeassistant tag landingpage.
18-01-29 17:14:34 ERROR (SyncWorker_9) [hassio.docker.interface] Can't install homeassistant/armhf-homeassistant:landingpage -> 404 Client Error: Not Found ("manifest for homeassistant/armhf-homeassistant:landingpage not found").
18-01-29 17:14:34 WARNING (MainThread) [hassio.homeassistant] Fails install landingpage, retry after 60sec

I checked and the landing page tag doesn't exist, indeed. I'm not sure how to fix it.
Anyone can help me?

This issue was moved by @pvizeli from home-assistant/supervisor/issues/335.

Yesterday, I successfully deployed Hassio on my Odroid XU-4 running Ubuntu LTS 16.04 but after reinstalling it today the hassio_supervisor contained is now failing to start.

I run the following command to deploy hassio on my Odroid's Docker CE:

curl -sL https://raw.githubusercontent.com/home-assistant/hassio-build/master/install/hassio_install | bash -s -- -m raspberrypi3

The hassio_supervisor container fails with the following error:

Traceback (most recent call last):,
OverflowError: Python int too large to convert to C long,
"main", mod_spec),
File "/usr/local/lib/python3.7/runpy.py", line 193, in _run_module_as_main,
File "/usr/local/lib/python3.7/runpy.py", line 85, in _run_code,
exec(code, run_globals),
File "/usr/local/lib/python3.7/site-packages/hassio/main.py", line 24, in ,
attempt_use_uvloop(),
File "/usr/local/lib/python3.7/site-packages/hassio/main.py", line 15, in attempt_use_uvloop,
import uvloop,
from .loop import Loop as __BaseLoop # NOQA,
File "/usr/local/lib/python3.7/site-packages/uvloop/init.py", line 7, in ,
File "uvloop/includes/stdlib.pxi", line 128, in init uvloop.loop

All the necessary packages and requirements seem to be in place.

Any tips about how to troubleshoot this error?

hi , When I started supervisor in docker, hassio could not start it and pulled out a tag whose name was none

18-11-30 23:37:30 INFO (MainThread) [hassio.misc.dns] Start DNS port forwarding for host add-ons


18-11-30 23:37:30 INFO (MainThread) [hassio.supervisor] Update Supervisor to version None


18-11-30 23:37:30 INFO (SyncWorker_3) [hassio.docker.interface] Pull image homeassistant/armhf-hassio-supervisor tag None.


18-11-30 23:37:44 ERROR (SyncWorker_3) [hassio.docker.interface] Can't install homeassistant/armhf-hassio-supervisor:None -> 404 Client Error: Not Found ("manifest for homeassistant/armhf-hassio-supervisor:None not found").


18-11-30 23:37:44 ERROR (MainThread) [hassio.supervisor] Update of Hass.io fails!


18-11-30 23:37:44 INFO (MainThread) [hassio.api] Start API on 172.30.32.2


18-11-30 23:37:44 INFO (MainThread) [hassio.addons] Startup initialize run 0 add-ons


18-11-30 23:37:44 INFO (MainThread) [hassio.addons] Startup system run 0 add-ons


18-11-30 23:37:44 INFO (MainThread) [hassio.addons] Startup services run 0 add-ons


18-11-30 23:37:48 INFO (SyncWorker_0) [hassio.docker.homeassistant] Start homeassistant homeassistant/raspberrypi3-64-homeassistant with version 0.83.1


18-11-30 23:37:58 ERROR (MainThread) [hassio.homeassistant] Home Assistant has crashed!


18-11-30 23:37:58 INFO (MainThread) [hassio.addons] Startup application run 0 add-ons


18-11-30 23:37:58 INFO (MainThread) [hassio.tasks] All core tasks are scheduled


18-11-30 23:37:58 INFO (MainThread) [hassio.core] Hass.io is up and running

I'm attempting to use GitLab's internal registry. Authentication is successful, and a push should work. I have the following image set in config.json:

"image": "registry.gitlab.com/ndarilek/hassio-mycroft/{arch}",

What I see in my logs:

[INFO] Start upload registry.gitlab.com/ndarilek:2
[WARN] Upload fail!

Looks like the script is ignoring everything after the second /.

This registry and image should be publically accessible, so I don't think there's a conceptual reason that it shouldn't work. The builder should probably just not drop everything after the second /.

Thanks.

Device : Orange pi zero (arm H2)
OS : Armbian Debian Stretch

I use this script and got no error after installation

$ curl -sL https://raw.githubusercontent.com/home-assistant/hassio-build/master/install/hassio_install | bash -s -- -m armhf

When I try to connect to 192.168.1.12:8123 there is nothing.

In the container logs there is errors :

19-02-23 00:16:48 ERROR (MainThread) [hassio.utils.gdbus] DBus return error: b'Error: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name de.pengutronix.rauc was not provided by any .service files\n'

19-02-23 00:16:48 WARNING (MainThread) [hassio.dbus.rauc] Can't connect to rauc

19-02-23 00:17:54 ERROR (SyncWorker_2) [hassio.docker.interface] Can't install homeassistant/armhf-homeassistant:landingpage -> 404 Client Error: Not Found ("manifest for homeassistant/armhf-homeassistant:landingpage not found").

19-02-23 00:17:54 WARNING (MainThread) [hassio.homeassistant] Fails install landingpage, retry after 30sec

I'm now trying to push my Hassio addon image to Docker Hub. I have the following in build.json:

"image": "nolan/hassio-mycroft-{arch}",

I'm using GitLab to build my image. Before I begin, I run:

docker login -u $DOCKER_HUB_USERNAME -p $DOCKER_HUB_PASSWORD

The build logs show:

$ docker login -u $DOCKER_HUB_USERNAME -p $DOCKER_HUB_PASSWORD
WARNING! Using --password via the CLI is insecure. Use --password-stdin.
WARNING! Your password will be stored unencrypted in /root/.docker/config.json.
Configure a credential helper to remove this warning. See
https://docs.docker.com/engine/reference/commandline/login/#credentials-store

Login Succeeded
$ docker run --rm --privileged -v /root/.docker:/root/.docker -v $CI_PROJECT_DIR:/data homeassistant/amd64-builder --armhf -t /data/mycroft

$DOCKER_HUB_USERNAME is set to nolan.

The image successfully builds, then I get:

Successfully tagged nolan/hassio-mycroft-armhf:2
[INFO] Finish build for nolan/hassio-mycroft-armhf:2
[INFO] Start upload nolan/hassio-mycroft-armhf:2
[WARN] Upload fail!
[INFO] Start upload nolan/hassio-mycroft-armhf:latest
[WARN] Upload fail!
[INFO] Clean crosscompiling feature

It would be nice to know why the upload fails. I see its output is redirected to /dev/null. Any particular reason for this?

If I fix this and want to test my fix, how do I build my own hassio-builder image to test things out?

Thanks.