You could make the code platformio compatible by using forward declared functions.

The new_install_improv_wait_time option is only necessary if a new installation takes a long time to come online (ie it's expanding the file system). It's not necessary for this example.

Docs: https://esphome.github.io/esp-web-tools/#manifest

Sorry for the flood of issues 😅

Could you rename this repository to improv-wifi-example or something like that? It would help people with discovering this repository (I also plan on linking it on the docs for both Improv and ESP Web Tools).

Currently it's set to go to google.com. If you set that to to http://<local IP>, users will be redirected to the built-in webserver.

Due to the way the web components work that are used by ESP Web Tools and the Improv SDK, it's not compatible to have both active on the same website.

To see it for yourself: open ESP Web Tools, hit cancel, then open Improv. An error will be logged about mwc-ripple already being defined.

The solution is to just use ESP Web Tools. It offers all features of Improv Serial.

thanks for the info, i will give it a try

https://ldijkman.github.io/async-esp-fs-webserver/

ok maybe can get it to work

aybe can get it to work

Hello, great example.

I've been testing this, and i ran into an issue.

When using your provided binary file, everything works fine.

However, when i try to build from your source and run that the Wifi Connection always times out - and i can't figure out why.

I've tried everything i can think of - what do i have to do to get the wifi connection stage to complete?

I'd even be fine with skipping that stage altogether tbh - as i don't need it for my application.

When esptool.py merges binaries, it will set some bits for the target device. ESP Web Tools does not do that. For compatibility with most chips, it's suggested to use esptool.py command to merge binaries: https://docs.espressif.com/projects/esptool/en/latest/esp32/esptool/basic-commands.html#merge-binaries-for-flashing-merge-bin