Firmware 4.0.x sleep mode kills join status

[szumbrunn]

Hello,

Just today I've discovered that the join status (AT+JSTA) is disconnected in OTAA configuration after applying sleep mode in firmware 4.0.x.
I've used the following commands as specified in the AT Command manual:

AT+AK=<keyhere>
AT+APPEUI=<appeuihere>
AT+RX2DR=0
AT+JOIN=1
+JoinAccepted
AT+WDCT // I assume further that this would put the current status into EEPROM?
AT+PS=0,1
AT+SLEEP
+PS=1,1

The funny thing is, that with AT+PS=0,1 and the following AT+SLEEP if we wake up the USI module the join status is gone:

AT+JSTA
0

This is really bad since we would like to put the device into sleep asap after transmitting data. And we cannot afford to send a join before every data transmission.

Btw. there is the current workaround of setting a timeout for the sleep mode as it could be done before by using AT+PS=0,1,0,5000. This will put the device into sleep without loosing the current join state.

Could you please provide a fixed update soon?

[rony-vargas]

I have this same question, It should be retained, I am believe this module has EEPROM when looking to the integrated MCU, but not sure if is enough to save all configuration AND the Join State, or is too small for all that.
@szumbrunn thanks for the workaround, I will try that.
Looks like this is my nightmare with many LoRaWAN modules, not losing their Join Status after reset.