I had my phone (w/serial terminal) and Teensy setup in my microwave and the ESP couldn't find my specified AP. After 20 seconds it defaulted to Soft AP mode.
Is there a way this .begin() behavior could be altered - perhaps with .begin() parameter(s) so it could just return on WiFi failure and allow me to try again later on the preferred AP and not go into the Soft AP mode? (and a non-broadcasting AP)
Ideally I might like to use this at two+ places where the AP is known but different - or in between where I don't need to have WiFi access until one is in range?
I haven't tested what happens when it starts with the preferred AP and then is it lost. Nor have I looked at the code to see if there was an existing way around - but that would be hacking your library work without a defined interface. Maybe it is defined and I just recognize I don't like Soft AP and periodically check for my preferred AP? But lesser timeout would need to be programmed as well as a awy to shutdown Soft AP and restart finding a known AP.
I had my phone (w/serial terminal) and Teensy setup in my microwave and the ESP couldn't find my specified AP. After 20 seconds it defaulted to Soft AP mode.
Is there a way this .begin() behavior could be altered - perhaps with .begin() parameter(s) so it could just return on WiFi failure and allow me to try again later on the preferred AP and not go into the Soft AP mode? (and a non-broadcasting AP)
Ideally I might like to use this at two+ places where the AP is known but different - or in between where I don't need to have WiFi access until one is in range?
I haven't tested what happens when it starts with the preferred AP and then is it lost. Nor have I looked at the code to see if there was an existing way around - but that would be hacking your library work without a defined interface. Maybe it is defined and I just recognize I don't like Soft AP and periodically check for my preferred AP? But lesser timeout would need to be programmed as well as a awy to shutdown Soft AP and restart finding a known AP.