You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This is a documentation issue for users like me that use esphome devices off-internet and away from the machine that is used to compile and link the yaml. I had some difficulty figuring out:
a) where the build files for a device are located on the computer that you are using for compiling/linking, and
b) which file and file type the OTA update button on the web server v2 page requires to perform the update.
For reference, the firmware.bin file is the one that is required (not firmware.elf, firmware.map, or firmware-factory.bin) and it is stored in
/config/.esphome/build//.pioenvs/
Now, perhaps this location is a result of using a manual esphome install on the machine that is used to compile, if so please let me know. It is quite hard to find the .bin . If there is documentation on the above please point me to it.
FWIW, I really appreciate being able to update the device from the .local web page, as there are a lot of kilometers between the compiling machine and the esp device.
The text was updated successfully, but these errors were encountered:
This is a documentation issue for users like me that use esphome devices off-internet and away from the machine that is used to compile and link the yaml. I had some difficulty figuring out:
For reference, the firmware.bin file is the one that is required (not firmware.elf, firmware.map, or firmware-factory.bin) and it is stored in
/config/.esphome/build//.pioenvs/
Now, perhaps this location is a result of using a manual esphome install on the machine that is used to compile, if so please let me know. It is quite hard to find the .bin . If there is documentation on the above please point me to it.
FWIW, I really appreciate being able to update the device from the .local web page, as there are a lot of kilometers between the compiling machine and the esp device.
The text was updated successfully, but these errors were encountered: