See #3960 for more details of the problem and the solution. I only implemented what was proposed in this ticket, as it solves my problem, which was the same as in this ticket. Credits for the code going to @etrinh ;-)
This also is a more consistence behaviour compared to esp8266, where it also is possible to restart the wifiserver immediately on the same port.
* Change check for CONFIG_BT_ENABLE to really be a check for CONFIG_BLUEDROID_ENABLED
Which is really what should have been tested. This allows use of
the Arduino layer with the newer Nimble stack for those that don't want
to use Bluedroid.
In support of https://github.com/meshtastic/Meshtastic-device/issues/266
* Change check for CONFIG_BT_ENABLE to really be a check for CONFIG_BLUEDROID_ENABLED
Which is really what should have been tested. This allows use of
the Arduino layer with the newer Nimble stack for those that don't want
to use Bluedroid.
In support of https://github.com/meshtastic/Meshtastic-device/issues/266
* wifi prov changes
* merge fixes
Co-authored-by: geeksville <kevinh@geeksville.com>
* Added ESP32-Wrover-Kit with distinct build.board
* Fixed broken values
* Update boards.txt
Co-authored-by: Me No Dev <me-no-dev@users.noreply.github.com>
* Added UM FeatherS2 and UM ProS2 boards to boards.txt
Updated the name of TinyPICO to UM TinyPICO in boards.txt
* Added VID/PID/Product names for TinyPICO, ProS2 & FeatherS2
Setup variant folders for each board
* Removed unneeded stuff from FeatherS2 & ProS2 menu options
* Added Serial CDC output default for FeatherS2 and ProS2
* Removed unneeded stuff from FeatherS2 & ProS2 menu options
* Rebase from upstream and fixed Serial Output settings for FeatherS2 and ProS2
Co-authored-by: Seon Rozenblum <seonr@3sprockets.com>
