aircoookie / esp8266minimalhttpupdater

Simple tool to reflash binary software to the ESP8266 over-the-air.

This is a simple tool to reflash/upload new binary software to the ESP8266 micro-controller over-the-air.

Often it can be cumbersome to compile code with lots of dependencies just to use it. Therefore, some projects (including my WiFi-LED solution WLED) provide ready to flash binaries. You just need to compile and flash this sketch in the Arduino IDE, the only dependency is the ESP8266 Arduino Core.

Usage:

1. Manually compile and upload the updater.ino sketch to your ESP board via the Arduino IDE. Wait until sketch is fully flashed.

2. Disconnect your ESP8266 from power, wait a second and reconnect it. This is neccessary due to a reset issue after uploading via the IDE.

3. Use a WiFi-enabled device to connect to the board's WiFi Access Point "UpdateMe". The password is "updater1".

4. In your browser, type "192.168.4.1" in the address bar. This is the module's IP.

5. You should now see a welcome screen and be able to upload your binary file.

esp8266minimalhttpupdater's Issues

No welcome screen

l have flashed the sketch to five different nodemcu's including Lolin and Amiga brands. All of them
open a WiFi Access Point "UpdateMe" which accepts the password "updrater1". However, When
"192.168.4.1" is entered into my Chrome browser, "This site can’t be reached" is displayed. Waiting as much as an hour still produces no welcome screen.

My browser "Version 78.0.3904.70 (Official Build) (64-bit)" and router Asus RT AC3200 work very well.
Google search has produced no applicable response to "ESP8266 Minimal HTTP Updater no welcome screen". Is there a better search term?

Any help greatly appreciated.

Cannot use GZ files

Not really an issue - but the docs don't specifically mention it.

You cannot use a zipped BIN. Took a few rounds of "UPLOAD FAILED" before I realized this.

Otherwise - this was a savior for a "too large" BIN that would not allow a normal "minimal" bin to be flashed. Thanks!

EspBuddy now handles Wled & Feature request

Hi
I'm the developper of EspBuddy, a sort of SwissArmyKnife intended to make build/upload, as well as various usefull command, available, in a simple, easy-to-use command line tool.

I've just added some support (currenly only in the develop branch) for your EXCELLENT Wled firmware , among already supported EspEasy, Tasmota & Espurna firmwares

It currently support the following commands for Wled:

'upload'		=> "Build and/or Upload current repo version to Device(s)",
'build'			=> "Build firmware for the selected device",
'backup'		=> "Download and archive settings from the remote device",
'monitor'		=> "Monitor device connected to the serial port",
'send'			=> "Send commands to device",
'status'		=> "Show Device's Information",
'version'		=> "Show remote device version",
'reboot'		=> "Reboot Device(s)",
'ping'			=> "Ping Device(s)",
'repo_version'	        => "Parse the current repository (REPO) version. REPO is a supported repository (espurna, espeasy, tasmota or wled)",
'repo_pull'		=> "Git Pull the local repository (REPO). REPO is a supported repository (espurna, espeasy, tasmota or wled)",

Give it a try 😃

---

One of the MAIN (and now popular) reason that I've created this tool, was the ability to easily update remote ESPs, even when they need a "2steps" upload (needed for 1M devices: first OTA upload an intermediate firmaware, then OTA upload the final firmware)

This work like a charm for Tasmota, EspEasy and Espurna!

I could also implement this for Wled (thus making Wled users life easier when updating 1M devices), BUT, counter to theses other firmwares, there is a small issue with your minimal minimal Esp8266HTTPUpdater.
---> it revert itself to another fixed IP, in a Wifi AccessPoint mode.
This makes it really boring (many steps) to use, and near impossible to script.

SO:

Would you mind (as others great ESP firmware makers do) to simply update your Minimal firmware to:

• read the saved setting (IP address, Mask, Gateway, Wifi AP, Wifi password)
• connect the ESP using THESES settings

This would:

• certainly not make the minimal firmware that bigger
• make life really easier for any Wled user that need to perform this "2Step" upload
• Finally allow me to implement it in EspBuddy, so that it's even easier for people able/daring to use EspBuddy. Or anyone wanting to automate "2Steps" uploads

Anyway , congratulations for your AMAZING firmware! 🍻