Open nickolas1969 opened 3 years ago
Snagged this in the logs as well, previous log errors scrolled it passed me.
Please, share the above information when looking for help or support in, e.g., GitHub, forums or the Discord chat.
Just attempted the ESPHome stable 1.15.3 with my old ESPHome directory (3 devices) and it loads fine, the devices are accessible. (Tag Reader and 2 KMC Flashed wall plugs)
I am seeing the same. Thought it was a problem at my end after I was playing with Docker settings yesterday. Running supervised Raspbian GNU/Linux 10 (buster) Rpi4 4GB.
Removed esphome_version: dev
from the config to roll back to 1.15.3.
temporary solution https://github.com/esphome/issues/issues/1702#issuecomment-749720677
Same here running an Odroid C2 with hassos 5.10
This same on RPi4 with Home Assistant Operating System 5.10 and HA 2021.1.1
Duplicate of https://github.com/esphome/issues/issues/1716
Duplicate of #1716
This is #1716 :)
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
Still persist.
RPi 3b+ hassio os 6.1, esphome 1.19.4. Same problem, freezes on compilation. I can only restore the system by manually restarting the RPi. I tried reinstalling hassio, using yaml from devices that were already working and had no luck.
Operating environment/Installation (Hass.io/Docker/pip/etc.):
RPi 4 8GB running Hass.io image, and recently updated to current (as of yesterday)
Supervisor version 2020.12.7 Home Assistant OS 5.9
ESP (ESP32/ESP8266, Board/Sonoff):
No issues with my ESP8266 modules, this is just with the add-on in HA.
ESPHome version (latest production, beta, dev branch)
ESPHome-Dev current version as of today. 15ef4d2f_esphome-dev
Affected component:
Description of problem:
The ESPHome-dev version is no longer building itself under Hass.io on RPi 8GB 64-bit image.
Problem-relevant YAML-configuration entries:
Logs (if applicable):
Additional information and things you've tried:
Tried uninstalling the Add-On, deleting the ESPHome directory, then re-installing fresh. The logs above are the result.