Ensure users are compatible between v1 and v2 #625
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
RC522 UIDs were broken in v1 - they sometimes missed '0's. This was fixed in abd0e66 and 20e4dcb, but that means a user database from v1 will not be entirely compatible after upgrading to v2, so some users could get locked out.
To solve this we calculate both the new (correct) format and the old (broken) format. If the new format UID doesn't exist in the database we do a check for the old format as well, and continue with that if it exists. This allows a seamless upgrade to v2.