Timezone list in config portal missing? about esp_wifimanager

[khoih-prog]

Thanks for your interest in the library.

I've just tested the unmodified ConfigOnDoubleReset example and have no issue with NTP and Timezone at all

Starting ConfigOnDoubleReset with DoubleResetDetect using LittleFS on ESP8266_NODEMCU_ESP12E
ESP_WiFiManager v1.7.8
ESP_DoubleResetDetector v1.2.1
[WM] RFC925 Hostname = ConfigOnDoubleReset
[WM] Set CORS Header to :  Your Access-Control-Allow-Origin
ESP Self-Stored: SSID = HueNet1, Pass = password
[WM] * Add SSID =  HueNet1 , PW =  password
Got ESP Self-Stored Credentials. Timeout 120s for Config Portal
[WM] LoadWiFiCfgFile 
[WM] OK
[WM] stationIP = 192.168.2.186 , gatewayIP = 192.168.2.1
[WM] netMask = 255.255.255.0
[WM] dns1IP = 192.168.2.1 , dns2IP = 8.8.8.8
Got stored Credentials. Timeout 120s for Config Portal
[WM] Current TZ_Name = America/Toronto , TZ =  EST5EDT,M3.2.0,M11.1.0
LittleFS Flag read = 0xD0D04321
No doubleResetDetected
Saving config file...
Saving config file OK
[WM] * Add SSID =  HueNet1 , PW =  password
[WM] * Add SSID =  HueNet2 , PW =  password
ConnectMultiWiFi in setup
[WM] ConnectMultiWiFi with :
[WM] * Flash-stored Router_SSID =  HueNet1 , Router_Pass =  password
[WM] * Add SSID =  HueNet1 , PW =  password
[WM] * Additional SSID =  HueNet1 , PW =  password
[WM] * Additional SSID =  HueNet2 , PW =  password
[WM] Connecting MultiWifi...
[WM] WiFi connected after time:  1
[WM] SSID: HueNet1 ,RSSI= -46
[WM] Channel: 2 ,IP address: 192.168.2.132
After waiting 4.46 secs more in setup(), connection result is connected. Local IP: 192.168.2.132
[WM] freeing allocated params!
Local Date/Time: Mon Dec  6 16:44:23 2021
Stop doubleResetDetecting
Saving config file...
Saving config file OK
Local Date/Time: Mon Dec  6 16:45:23 2021

I suggest you start over, using Arduino IDE to verify it's working OK to retrieve the TZ automatically. If OK, then moving forward gradually to see where / when it's broken.

I don't like and won't add the option to modify the TZ manually, as I don't see the reason to use TZ if you can't access NTP to get the correct time.

Be sure to check that you haven't modified the example's code and you can access the NTP server.

Also have a look at previous TZ-related issues to see anything can be applied in your case.

I'm closing the issue now, unless you can prove this is the bug of this library.

Good Luck