Extended configuration mode and bug-fix

[BogyS]

Hello,

I started adapting the library for a project that has the following requirements:

• setting credentials if they do not exist
• once the network is set, do not start the AP at startup in case it cannot connect to the network For example, in case of a power failure, the router will start more difficult and the application will be stuck in AP mode
  • option to restore the default values (from the web page or button)

I also modified:

• the names of the defines so that there is a lower risk of being equal to defines from other libraries
• defines with values 0/1 that can be added in platformio,ini with build_flags
• option to completely remove serial port calls

Kind regards, Bogdan

[cotestatnt]

Hi, thank you for your valuable contribution! If you feel like it, also take a look at this variant of the library that uses ESPAsyncWebServer as base webserver. From the tests I have carried out on some of my projects I have noticed that the performance of the library in question is better than the one included with the core.

https://github.com/cotestatnt/async-esp-fs-webserver

[BogyS]

Hi, thank you for your valuable contribution! If you feel like it, also take a look at this variant of the library that uses ESPAsyncWebServer as base webserver. From the tests I have carried out on some of my projects I have noticed that the performance of the library in question is better than the one included with the core.

https://github.com/cotestatnt/async-esp-fs-webserver

Thanks for the suggestion, I've seen that library, but I think this one is more suitable for my project. The device I work on measures the energy to monitor a pump over time. The web server part is only used for initial configuration and some troubleshooting - in the local network. I think, it will never be the case to have more clients connected simultaneously. However, the project includes several libraries and need ota, so I have to reduce the size as much as possible - even on Esp32

I still have some changes that I would like to make, maybe you can help me :) Please let me know how you prefer to communicate for these.

Thank you, Bogdan

[cotestatnt]

Good morning @BogyS For next changes it's the same for me: you can open an issue or if you already have some working code, make a pull request as you have already done.

As for your project, keep in mind that you can use a partition scheme that reserves more space for the firmware (for example, I recently developed a project with a firmware of almost 1.6Mbytes and I selected "Huge app").

For firmware updates, consider that you can also do it from the browser without adding other libraries. In the "async" library for example, I integrated this functionality directly into the /setup page. As soon as I have some time I'll do it in this library too