Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Are TTN credentials lost when going off battery? #73

Closed
ffries opened this issue Apr 10, 2023 · 4 comments
Closed

Are TTN credentials lost when going off battery? #73

ffries opened this issue Apr 10, 2023 · 4 comments

Comments

@ffries
Copy link

ffries commented Apr 10, 2023

Dear Disk91,

But what happens if battery goes off completely to 0%? All all TTN credentials lost and reverted to stock firmware? This is not a problem for Helium as credentials are hard-coded. But this is surely a problem for TTN. Is there a workaround other than clearing eprom? Do we need to recompile firmware?

All this is not very clear in a documentation, please make a clarification for newbies like me.

Kind regards,
Ffries

@disk91
Copy link
Owner

disk91 commented Apr 10, 2023

No they are not, credentials are stored in NVM and LoRa-E5 EEPROM

@ffries ffries changed the title Are credentials lost when going off battery? Are TTN credentials lost when going off battery? Apr 12, 2023
@ffries
Copy link
Author

ffries commented Apr 12, 2023

Dear Disk91,

I understand what is going on. I am using a wio kit from seeed. I cleared credentials and uploaded the latest firmware. After rebooting, I need to click on 5 button and then choose European setup. Buttons 1, 2 and 3 do now allow me to change app and dev credentials. Therefore settings are back to Helium. After configuring TTN with credentials, I can connect. However when rebooting credentials are lost and back to Helium.

How to solve this issue? Should I recompile the firmware (I am using Linux, not Windows).

It would be nice to have a custom screen displaying dev-ui and app-ui.

Kind regards,
FFries

@disk91
Copy link
Owner

disk91 commented May 29, 2024

Hello, sorry to answer so late, I missed your response.
You can follow the guide in documentation to unlock your device and definitly remove the seeed factory configuration.

@disk91
Copy link
Owner

disk91 commented May 29, 2024

see: #34

@disk91 disk91 closed this as completed Jun 9, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants