Details: in attempting to delete a duplicate discovered ESP device, I uninstalled + reinstalled the ESPHome addon several times. At this point, the addon seems to install just fine (see logs below), but it does not start anymore. When clicking the start button, nothing happens.
@nickrout Good to understand that this is where the log ends, but the fact remains that the Addon does not start up. The dashboard does not come up; and when clicking the ESPHome icon in the sidebar, it says the addon is not started.
FYI: I am running HA Supervised as a VM (Debian-based) on ProxMox.
The annoying thing is that it has worked for a few times on this setup, but after a few reinstalls of the addon it no longer does. Looks like there must be some corruption with the container or container mgmt.
What does docker tell you? Does it say the container is running? Can you enter the container? Did you wait for the container to start before trying to enter the ui?
I am afraid I a bit too noob to know how I can see from within Home Assistant how to talk to Docker.
I do have installed SSH and can get to the initial terminal screen.
Thank you! Now it’s working for me - but unfortunatelly when I updated one of my device to the new version of ESPHome which is contain only 4 dallas DS18B20 sensors - it’s not working : “Scratch pad config register invalid!” - yesterday everything was fine till upgrade the ESPHome.
I had the same problem. If I connected to home assistant via the nebu casa web page I could install and run esp home no problem. But nothing seemed to work doing it via the homeassitant.local URL.