We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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 is not restored on stick which was used before in other z2m instance, even it was reflashed with JFlash.
Backup should be restored.
unclear
hasConfigured
instance_id
configuration.yaml
database.db
znpHasConfigured
The text was updated successfully, but these errors were encountered:
Here is function to erase all nvram items: https://github.com/jethome-ru/zigbee-herdsman/commit/b21bf0bf73d28e31a5b98e8ed6fe02153dba7b97
Sorry, something went wrong.
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
Would be nice to have a code that erases NVMEM as part of Z2M.
No branches or pull requests
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)
unclear
stick which was used on other z2m instance before.hasConfigured
is still true.Why this happend
Suggestion
instance_id
value which will be uniq for each z2m instance, for example 16-bit UUID.instance_id
toconfiguration.yaml
or todatabase.db
coordinator entry.instance_id
to coordinator NVMEM insideznpHasConfigured
or to the new nvitem.instance_id
is differentThe text was updated successfully, but these errors were encountered: