Connection to Mobile Hotspot OK - to LTE Router not OK

[ArminPP]

Hello Martin, I use a Wemos D1 pro (Clone?) with your fabolous software, but I have an Issue to connect to a LTE WiFi Router. I always get error messages at the serial console:

reconnect
state: 2 -> 0 (0)
scandone
state: 0 -> 2 (b0)
state: 2 -> 3 (0)
state: 3 -> 5 (10)
add 0
aid 9
cnt 
state: 5 -> 2 (ea0)
rm 0
disconnect from ssid _WLAN_, reason 14

(.. and so on ..)

On the other hand I tried the Wemos on a hot spot with my mobile phone, and it worked perfect.

connected with OnePlus 6, channel 10
dhcp client start...
connect to ssid OnePlus 6, bssid c6:dd:3f:2a:54:f9, channel 10
ip:192.168.43.28,mask:255.255.255.0,gw:192.168.43.140
ip:192.168.43.28,mask:255.255.255.0,gw:192.168.43.140,dns:192.168.43.140
add 1
aid 1
station: 34:de:1a:5f:82:50 join, AID = 1
station: 34:de:1a:5f:82:50 join, AID = 1
LmacRxBlk:1

I am not familiar with the error codes from a WiFI Network, but I figured out "reason 14" from above says "REASON_MIC_FAILURE", but I could not find any explanation what this means...

The LTE Wifi credentials are:

SSID: _WLAN_
PW: includes (+!]@  characters

If I check the settings via serial console with "show", the credentials are stored correct in the ESP. I also use "set ssid %5FWLAN%5F" instead of "set ssid _WLAN_" and also %-Notation for the Password - but I doesn't work.

Thanks in advance for some tips, Greetings from rainy Austria :-)

[ArminPP]

Small Update: I was able to connect to a 2nd LTE/ADSL WiFi Router with different credentials, and it worked fine:

SSID: only characters from A..Z and '-'
PW:   only characters from A..Z and a..z

So I belive, the Wemos is working, but there is an issue with one WiFi Router, but I don't know what?

[ArminPP]

Last update ;-)

Yesterday I tried the same Wemos from the 1st post on the same WiFi - without changes to the Wemos. And it worked! I do not know what happened. The only thing was that there was a power failure at the location where the WiFi router is located! So the router was restarted when I arrived at the site to make the test...

So I think this problem can be closed :-)