fix boot loop caused by competing wifi_manager and cmd_wifi

It is now possible to set a default autoexec command to automatically
join wifi when wifi_manager is disabled. To test wifi stability without
wifi_manager, use the following commands:

nvs_set bypass_wm str -v "1"
nvs_set autoexec str -v "1"
nvs_set autoexec1 str -v "squeezelite -o I2S -b 500:2000 -d all=info -m
nvs_set autoexec2 str -v "join <ssid> <password>"
ESP32"
restart

Note that squeezelite occupies the "autoexec1" slot to avoid conflicts
with the wifi manager web configuration page when it is re-enabled. To
re-enable the wifi-manager, use the following commands:

nvs_set bypass_wm str -v "0"
restart

--
Additional change:  Credits page now has a button to enable the nvs
editor even in ota mode
This commit is contained in:
Sebastien
2019-11-01 09:49:51 -04:00
parent 2ed8b50fbe
commit 04b82e5bf6
4 changed files with 31 additions and 16 deletions

View File

@@ -543,14 +543,6 @@ char* wifi_manager_get_ap_list_json(){
static void event_handler(void* arg, esp_event_base_t event_base, int32_t event_id, void* event_data){
// if (event_base == WIFI_EVENT && event_id == WIFI_EVENT_STA_DISCONNECTED) {
// led_blink_pushed(LED_GREEN, 250, 250);
// esp_wifi_connect();
// xEventGroupClearBits(wifi_event_group, CONNECTED_BIT);
// } else if (event_base == IP_EVENT && event_id == IP_EVENT_STA_GOT_IP) {
// led_unpush(LED_GREEN);
// xEventGroupSetBits(wifi_event_group, CONNECTED_BIT);
// }
if(event_base== WIFI_EVENT){
switch(event_id) {