Open jmlich opened 6 months ago
The Gadgetbridge is able to connect to Amazfit NEO without troubles. I tried to compare the pairing mechanism in gadgetbridge and amazfish. So far I can see the only difference, gadget bridge is using bytes 3-19 and amazfish bytes 3-17:
The value "\x10\x83\b" for characteristics corresponds to this condition
value[0] == RESPONSE &&
(value[1] & 0x0f) == AUTH_SEND_ENCRYPTED_AUTH_NUMBER &&
value[2] == 0x08
doesn't seems to be handled in gadgetbridge either.
Are you able to pair other Amazfit watches on that version of Amazfish? or only the NEO is the one with the problem? Because it seems that the erroneously fetched data issue may also correspond to a problem of using the miband2 service for the Neo.
I don't have any other Amazfit device to test.
There are many differences from my previous try:
I am trying to pair with Amazfit NEO. The device is connected to zepp application and I am getting token with
The
0xcaa04207ff084f260d8513a5d75d8dcf
(including 0x) was entered into dialog.I can see authfailed message in daemon's log:
Whole log follows:
It looks like the "\x10\x83\b" is the unexpected data. Maybe also @kirbylife can take a look.