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

Backup restore does not work on "unclear" stick, even after reflashing it with JFlash #4960

Closed
hacker-cb opened this issue Nov 12, 2020 · 4 comments
Labels
problem Something isn't working stale Stale issues

Comments

@hacker-cb
Copy link
Contributor

hacker-cb commented Nov 12, 2020

What happened

Backup is not restored on stick which was used before in other z2m instance, even it was reflashed with JFlash.

What did you expect to happen

Backup should be restored.

How to reproduce it (minimal and precise)

  • Take new unclear stick which was used on other z2m instance before.
  • Flash it with JFlash
  • Stop z2m
  • Extract old stick
  • Insert new one
  • Start z2m
  • Backup will not be restored because hasConfigured is still true.

Why this happend

  • JFlash does not erase NVMEM items.

Suggestion

  • Add instance_id value which will be uniq for each z2m instance, for example 16-bit UUID.
  • Save instance_id to configuration.yaml or to database.db coordinator entry.
  • Save instance_id to coordinator NVMEM inside znpHasConfigured or to the new nvitem.
  • Erase NVMEM if instance_id is different
@hacker-cb hacker-cb added the problem Something isn't working label Nov 12, 2020
@hacker-cb
Copy link
Contributor Author

@github-actions
Copy link
Contributor

This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 7 days

@github-actions github-actions bot added the stale Stale issues label Dec 13, 2020
@dmak
Copy link

dmak commented Dec 13, 2020

Would be nice to have a code that erases NVMEM as part of Z2M.

@github-actions
Copy link
Contributor

This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 7 days

@github-actions github-actions bot added the stale Stale issues label Jan 13, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
problem Something isn't working stale Stale issues
Projects
None yet
Development

No branches or pull requests

2 participants