Running docker puts the config on a disk on your real machine, as well inside the docker container. It will therefore be preserved if docker is crashed/not running.
If your docker command line is not mapping the config to a real life directory you are not following the instructions.
Thanks, this just saved my bacon! I did the same thing, created a stub, accidentally pasted the full config over the OTA password. I was actually on the way to trying a dissembler when I saw your post. Sure enough, my OTA password was there! Iâm now putting it in my secrets file so that I donât accidentally overwrite it in the future.
Thank you, this worked for me. I donât have to open my plug up again 
Sorry to resurrect this after a few months. Iâm getting the dreaded âESP requests password, but no password given!â
My HA corrupted at the end of last year and iâve had to rebuild some esphome configs that didnât make it into the backups. When I wrote them the first time I didnât set an ota password, but iâm wondering if home assistant had created one internally?
same problem here! wondering if youâve solved it in the meantime?
Is this during an OTA update?
Yeah, thatâs correct. Iâve got four plugs (which I canât seem to open, possibly bonded). Iâve never used an ota password because I didnât realise it was a thing.
And why do you need to update them? Presumably they work.
They do work, but I want to adjust the configuration including update_interval and tweak the hlw8012 sensor config.
edit: in addition, iâm struggling to connect to the fallback AP. Even though i know the password, and can see the SSID being broadcast. it seems to disconnect immediately. Appears to be the same as âCannot connect to captive portal / fallback hotspotâ, sadly no solution there if weâre unable to flash OTA.
I guess your only solution is a serial connect.
If you read the above posts you will see they want to do this without having to open the case the device resides in. In my case, the ESP device is on a pole 8 feet above the ground and is not easily flash the firmware using a USB cable. The request or question in the OP was how to do using WiFi.
So you forgot your ota password?
I donât even use an OTA password. But where I live my next-door neighbor is out of my WiFi range.
There is also
web_server:
port: 80
⊠where you can upload new firmware.
how do you get the ota key out of the bin file
What command are you running? Please stop posting pictures of text.
I just run the command you gave but with my fileâs directory path
Ok, so iâve just retrieved my OTA password from the .bin file.
First of all I want to say that I know anything about the stuff I use, Iâm just a stubborn with access to Google (Neither am I a native English speaker, so sorry for any typo or grammatical error)
So first of all itâs downloading Cutter (I downloaded for Linux, so I havenât tried Mac or Windowsâs alternatives, but i guess theyâd work the same way)
Then you open your .bin file, youâll see something like this:
Then you go to âStringsâ which is the second option in the bottom menu
In there youâll look for wifi in the Quick filter
Then youâre going to right click on the second-to-last option and select Show in>Hexdump:
Youâll see something like this:
)Live safer! Thank you!
Just recovered the OTA password from a .bin file for a NOUS A1T that I had updated to ESPHome. Copied a bit too much from another .yaml file.
I just did this by mistake as well to a Merkury light bulb. The API key appears to be correct, just not the OTA one. I have the UF2 file that I had used originally, is there a way to use that?
