Reset Token - Counter synchronization with counter value 0 is not working

[JoLo33]

Hey there,

in the general documentation is described that a reset token is a counter synchronization token with counter 0 and this token should be accepted all time.
When I try to use a reset token on a device with a counter 100 I get an old token feedback. I tried it with the c code implementation and also with the python scripts.

I used the example device key and starting code (123456789)
I generated a counter sync token with counter 100 - 397832788
I generated a counter sync token with counter 0 - 123456788

I used the python code and the device simulator like this:

device_simulator.enter_token('397832788')
device_simulator.print_status()

device_simulator.enter_token('123456788')
device_simulator.print_status()

And the output is:

TOKEN_VALID | Value: 999
UNKNOWN_COMMAND
Device:

Expiration Date: 2022-08-24 15:47:20.823061
Current count: 100
PAYG Enabled: True
Active: True

OLD_TOKEN
Device:

Expiration Date: 2022-08-24 15:47:20.823061
Current count: 100
PAYG Enabled: True
Active: True

Regards
Jonas

[benmod]

There is an issue in the documentation, it should read a sync token with counter of 1 and not 0, counter of 0 is not supported.

[JoLo33]

Does it mean that the reset token function in general should be not supported? Or is a counter synchronization token with counter 1 the one which should be accepted all time as described in the documentation?

[benmod]

The counter sync with 1 is the one that should be accepted.

…

On Thu, Oct 20, 2022, 16:19 JoLo33 ***@***.***> wrote: Does it mean that the reset token function in general should be not supported? Or is a counter synchronization token with counter 1 the one which should be accepted all time as described in the documentation? — Reply to this email directly, view it on GitHub <#9 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ABUSSJISXDPNUBELBA6ULN3WEFIHHANCNFSM57OIMXCQ> . You are receiving this because you commented.Message ID: ***@***.***>