Issue pairing Baro 9 with Pixel 7
-
I have the exact same problem with my Pixel 7a. Connecting as a normal bluetooth device works fine but within the app I don’t get the question for PIN and no PIN is showing up on the watch. And yes, I’ve removed the watch from the list of bluetooth devices before I tried to connect from the app.
-
@SvenG did you remove the connection from the watch too?
-
@SvenG said in Issue pairing Baro 9 with Pixel 7:
And yes, I’ve removed the watch from the list of bluetooth devices before I tried to connect from the app.
And did you reboot your phone after this removing from BT list?
Sometimes it is removed but still putting mess somewhere -
@Johann
@Alex-Machado
@SvenG
did you manage to connect your watch with the phone by now?
I’ve had the same issue with my up to date Pixel 4a 5G.
what helped was to clear cache and storage of SA. after that connecting worked flawlessly like alwaysliving sideways
-
I had to pair (bluetooth) the watch with the mobile first.
After, the app was able to detect my watch.
Thanks for your help. -
@Johann
strange this is exactly the way it never worked and afaik shouldn’t work -
-
F freeheeler referenced this topic on
-
@Łukasz-Szmigiel Yes I did
-
@Mff73 Yes I reboot my phone and removed the bluetooth connection in the phone. Even did booth soft and hard reset of the watch, nothing helped.
-
I have not managed to get them paired.
I was chatting with Suunto support earlier today and they are both aware of the problem and monitoring this thread. They seemed very informed on the issue and said Engineering is also aware and working on a fix with haste.
I got a good sense they’re working it, from the chat.
-
@AlexMmm Good to hear that they are aware of the problem and work on it. I spoke with the chat a week ago and then they seemed to never heard of the problem. It is however frustrating that it doesn’t work.
-
@SvenG have you checked this?
-
@isazi That suggestion actually worked. Thank you.
-
@SvenG a proper solution is also being tested by the app developers, apparently something changed with a recent Pixel update.
