@d-alvrzx I strongly support this request. I see, that restoring some of the data may cause trouble, if restore is executed multiple time w/o a save in between. Like the packet counters. But that is less cumbersome than loosing all data. See also my notes here to retrieve individual elements: https://forum.pycom.io/topic/5922/an-alternative-to-nvram_save-restore-using-the-sd-card/6?

Hi Drop an email to sales@pycom.io with the details :)

@jcaron Just to clarify something from our use case: In our experience using the same frame counter is not a problem with our private instance of a TTN server. How we do it now is that we restore from nvram and save it immediately after. This is so we don't need to think about it again. I understand ADR will not work for us here, but it is still a lot easier and spares us from some logic with exception handling and still keeping the session and avoiding a new join. We also do not need to receive responses. We are basically using it as a makeshift abp connection, as our setup and back-end does not support abp. Having a function that restores the session without erasing it would actually be quite nice for our case. This, as far as I understand it from TTN, does also work for the public TTN network, but I have not confirmed this. Is there some way of getting all connection details down in a file so we could save it to an SD card instead? This would actually allow us to quite efficiently create devises and manage the things for our system.

@jcaron Thanks. Just to note this method works also for both a software reset AND powercycle.

I know this is an old post but for me this is still an issue. Any may of learning more about the specifics would be very much appreciated e.g what does pycom.nvs_get(key) return? Should I see somthing in the REPL? Example: >>> lora.nvram_save() >>> l= pycom.nvs_get('lora') >>> print(l) None Am I going about this in completely the wrong way?

@dbrgn The library may also have a local cache, which would be used for reading, and could compare values against the cache before actually writing to flash. There could also be some way to write only a few bytes rather than full sectors like a filesystem would do, not sure if that's actually possible with the flash interface used.

@jcaron The issue has been worked out and it works quite well now! Thanks a lot!