Refactor the saveIdentity method #1221
Open
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.
This change will allow uses to use these two new commands:
regen key
Auto mode generates a new identity avoiding collisions with neighbors and reserved hashes (00, FF).
regen keyResponse: OK - new ID: A3 (reboot to apply)
regen key XX
Vanity mode generates a new identity with a specific hash prefix (2 hex characters).
Response: OK - new ID: A3 (reboot to apply)
If the target hash collides with a neighbor:
Response: WARNING: collision! new ID: A3 (reboot to apply)
The purpose of this is to reduce those annoying collisions that happen in the app and also to resolve times where repeaters with the same hash end up repeating a message that was intended for another repeater thus increasing airtime.