ESPHome cannot do reconfiguration

I have a ESP12E device which I flashed with 1y.o. esphome, worked alright, almost, so I upgraded it:
“git checkout” the latest stable esphome, rebuild, reflash, HA picked it up, works as before.

2 days later a notification popped up asking to reconfigure ESPHOME intergration. The api/key from yaml is not accepted. The original device is still available in the HA, the fw version is the one I flashed so HA has no problem with, and the device responds to the commands.

What is that new reconfiguration request about?

Also, is there a dashboard on ESPHOME to see the fw version and other status info? Port 6052 does not respond, adding /dash or /dashboard opens a blank page. (Sorry if it is a stupid question, I mostly use Tasmota :slight_smile: )

So you neither use the addon, nor the container, nor the pip package?
You seem to be on shaky grounds, her :wink:

Actually I am not even sure what ~/.local/bin/esphome run nebula.yaml does. It is all so screwed/

So why do you it, rather than throwing a plain container, which provides a webui?

version: '2.1'
services:
    esphome:
        container_name: esphome
        volumes:
            - ./cache:/cache
            - ./config:/config
            - /etc/localtime:/etc/localtime:ro
        restart: unless-stopped
        image: esphome/esphome:stable
        #image: esphome/esphome:beta
        network_mode: host
        ports:
          - 6052

Well, the config came from GitHub - kireque/esphome_nebula_light and never bothered changing it :slight_smile: The proposed “plain container” looks bizarre though, absolutely no clue what it is going to do on my machine, install docker, run a container? imho it is too hard for something which should be fairly simple like tasmota :-/

Erf, you really seem to only have a vague idea of what you’re doing, do you :slight_smile:
Nevermind, then.

but do you know what is that new reconfiguration request about?