Closed wutr closed 5 years ago
Exactly the same issue, Hass.io on Raspberry Pi Zero W.
I've just noticed that edge has a esphomeyaml_version
configuration option. I'm going to try out older versions to see if any of those work in the meantime.
Same with Raspberry Pi 1 B. I think problem can be lack of resources. Both devices has 512 MB RAM.
Tested on home assistant 0.84.6 and 0.85.
Add-on log:
[s6-init] making user provided files available at /var/run/s6/etc...exited 0.
[s6-init] ensuring user provided files have correct perms...exited 0.
[fix-attrs.d] applying ownership & permissions fixes...
[fix-attrs.d] done.
[cont-init.d] executing container initialization scripts...
[cont-init.d] 00-banner.sh: executing...
[cont-init.d] 00-banner.sh: exited 267.
[cont-finish.d] executing container finish scripts...
[cont-finish.d] 99-message.sh: executing...
s6-maximumtime: warning: child process crashed
[cont-finish.d] 99-message.sh: exited 111.
[cont-finish.d] done.
[s6-finish] syncing disks.
[s6-finish] sending all processes the TERM signal.
Syslog:
19-01-10 12:51:37 INFO (SyncWorker_1) [hassio.docker.interface] Tag image homeassistant/raspberrypi-homeassistant with version 0.85.0 as latest
19-01-10 12:51:38 INFO (SyncWorker_1) [hassio.docker.interface] Stop homeassistant/raspberrypi-homeassistant Docker application
19-01-10 12:52:12 INFO (SyncWorker_1) [hassio.docker.interface] Clean homeassistant/raspberrypi-homeassistant Docker application
19-01-10 12:52:14 INFO (SyncWorker_1) [hassio.docker.interface] Cleanup Docker images: ['homeassistant/raspberrypi-homeassistant:0.84.6']
19-01-10 12:53:33 INFO (SyncWorker_0) [hassio.docker.homeassistant] Start homeassistant homeassistant/raspberrypi-homeassistant with version 0.85.0
19-01-10 12:56:25 INFO (MainThread) [hassio.homeassistant] Detect a running Home Assistant instance
19-01-10 12:56:25 INFO (MainThread) [hassio.homeassistant] Successful run Home Assistant 0.85.0
19-01-10 13:06:20 INFO (MainThread) [hassio.addons.addon] Create Home Assistant add-on data folder /data/addons/data/7bce6681_esphomeyaml
19-01-10 13:06:20 INFO (SyncWorker_1) [hassio.docker.interface] Pull image ottowinter/esphomeyaml-hassio-armhf tag 1.10.0.
19-01-10 13:08:51 INFO (MainThread) [hassio.homeassistant] Updated Home Assistant API token
19-01-10 13:22:14 INFO (SyncWorker_1) [hassio.docker.interface] Tag image ottowinter/esphomeyaml-hassio-armhf with version 1.10.0 as latest
19-01-10 13:28:23 INFO (SyncWorker_1) [hassio.docker.addon] Start Docker add-on ottowinter/esphomeyaml-hassio-armhf with version 1.10.0
i have the same problem when install esphome 1.12 on Hass.io - Raspberry Pi Zero W. I don't think RPZ W lack resources because my install on Hassio - Orange pi zero worked well. Anyone sold it?
Closing as won't fix - esphome does not work with the resources of the tiny rpi zero
Operating environment (Hass.io/Docker/pip/etc.): Hass.io on Raspberry Pi Zero W
Affected component: https://esphomelib.com/esphomeyaml/guides/getting_started_hassio.html
Description of problem: After successfully adding the repository to the Hass.io add-on store I have installed esphomeyaml v1.9.3 which took a while but as far as I'm aware it was successful. When clicking "start" however, it appears the add-on is starting, and the "open web-ui" link appears. There is no webserver running though and a connection can't be made. When leaving the add-on page and returning to it, the add-on is in the "stopped" state and clicking on "start" doesn't actually do anything from then on.
Additional information: