@armor that is a good idea, however I've programmed it so whenever the device is in listening mode, it restarts and does not load any of the large memory buffers, therefore reducing the free memory down to as low as it could go. See here. This has worked well for us and we've not had problems with softAP since. The problem lies in normal operation after a long amount of time on weak wifi. I know it is happening on weak wifi because there are these [hal.wlan] TRACE: connect cancel scattered around the logs before it goes offline.
@UMD we don't use any softap include statements. From the docs, it states there is a default page;
When a browser requests the default page (
http://192.168.0.1/) the system internally redirects this to/indexso that it can be handled by the application.
This index is pre-written, although it can be redirected to a custom page like you may have done. But I'm not sure this default page can be disabled?