Devices not found

[thenudeavenger]

Hey, using this app I can login successfully but then it says "devices not found" when I tell it to fetch a key.

When I try to connect to my watch it hangs on the "Sending random to watch" bit

Using a fossil HR gen 6

[dakhnod]

Try registering your watch with your fossil account through the app before fetching the key thenudeavenger ***@***.***> schrieb am Sa., 22. Juli 2023, 18:36:

…

Hey, using this app I can login successfully but then it says "devices not found" when I tell it to fetch a key. When I try to connect to my watch it hangs on the "Sending random to watch" bit — Reply to this email directly, view it on GitHub <#3>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AGHOUF4FMCJZMVMNVN7VHQLXRP6RPANCNFSM6AAAAAA2T5Y7OQ> . You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>

[thenudeavenger]

Ah still no luck. Dan Mercuri

________________________________ From: Daniel Dakhno ***@***.***> Sent: Saturday, July 22, 2023 1:49:00 PM To: dakhnod/WatchAuthenticator ***@***.***> Cc: thenudeavenger ***@***.***>; Author ***@***.***> Subject: Re: [dakhnod/WatchAuthenticator] Devices not found (Issue #3) Try registering your watch with your fossil account through the app before fetching the key thenudeavenger ***@***.***> schrieb am Sa., 22. Juli 2023, 18:36:

Hey, using this app I can login successfully but then it says "devices not found" when I tell it to fetch a key. When I try to connect to my watch it hangs on the "Sending random to watch" bit — Reply to this email directly, view it on GitHub <#3>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AGHOUF4FMCJZMVMNVN7VHQLXRP6RPANCNFSM6AAAAAA2T5Y7OQ> . You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>

— Reply to this email directly, view it on GitHub<#3 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/BBOFAPM4Y7HYZ32KGCDZPNLXRQHAZANCNFSM6AAAAAA2T5Y7OQ>. You are receiving this because you authored the thread.Message ID: ***@***.***>

[thenudeavenger]

I'm also getting the response code is not 200:403 error

[dakhnod]

okay, then try fetching the key via bluetooth a few times. It usually takes a few attempts but eventually works.

[thenudeavenger]

By scanning for the device? Dan Mercuri

________________________________ From: Daniel Dakhno ***@***.***> Sent: Saturday, July 22, 2023 1:49:00 PM To: dakhnod/WatchAuthenticator ***@***.***> Cc: thenudeavenger ***@***.***>; Author ***@***.***> Subject: Re: [dakhnod/WatchAuthenticator] Devices not found (Issue #3) Try registering your watch with your fossil account through the app before fetching the key thenudeavenger ***@***.***> schrieb am Sa., 22. Juli 2023, 18:36:

Hey, using this app I can login successfully but then it says "devices not found" when I tell it to fetch a key. When I try to connect to my watch it hangs on the "Sending random to watch" bit — Reply to this email directly, view it on GitHub <#3>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AGHOUF4FMCJZMVMNVN7VHQLXRP6RPANCNFSM6AAAAAA2T5Y7OQ> . You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>

— Reply to this email directly, view it on GitHub<#3 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/BBOFAPM4Y7HYZ32KGCDZPNLXRQHAZANCNFSM6AAAAAA2T5Y7OQ>. You are receiving this because you authored the thread.Message ID: ***@***.***>

[dakhnod]

yep, and by then clicking on the device once its found