You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
yea on second thought, I agree with you @TyIsI that we should just simply require the format and clients are responsible for the conversion. If this becomes an issue for some readers or something in the future we can re-open this.
Currently membercard keys are stored simply as string in the following case sensitive format:
04:02:63:ea:0f:0f:0f
While this is fine if scanning from many devices, others provide the value as an int or different hex formats.
We should fix this to accept and parse different hex type formats. ie 0x040263ea0f0f0f
The text was updated successfully, but these errors were encountered: