12-21-2019 22:44
12-21-2019 22:44
So I have a weird issue. I just got a Versa 2. I should have read the specs to see what was needed to sync with it, but I didn't. My bad. First I tried my phone. It initially connected, but then it told me my android was too old. (5.1 on Moto E 2nd gen.) So I downloaded the pc app. (6 mo old Windows 10 Dell Inspiron computer.) Versa 2 was in the list of devices, and it synced just fine. I got through the initial setup, and then it said it needed to update and would take a while. Ok. I happened to step away for a while, and let it do its thing. When I came back, my computer had put itself to sleep. I woke it up and it said the update failed. *Sigh* I assumed my computer falling asleep had interrupted the update and tried again. But my computer wouldn't sync with my watch at all. And it's still not syncing to anything.
I tried turning it off and on a number of times. Bluetooth says my watch is connected. The app though won't connect. It says the watch is set up but needs to update. The watch disagrees. It says I need to download the app and set it up. It seems to think nothing ever happened. I tried creating a new login to go through set up from scratch. The watch still won't sync. I tried to connect it to my phone but I had deleted the app from my phone and my phone keeps freezing when I try to redownload it. I tried it on another phone, (also old running android 6.0.1), just to see if it will connect. It doesn't and complains the phone is too old.
I went to Fitbit chat, they told me that I can't set it up with the PC. When I pointed out that it started to just fine they said the watch was showing that it was never set up, but it had been stuck syncing with my computer. they said my computer went through all the setup screens only *thinking* that it was connected. I googled the issue, and the problem with PC set up seems to be that the Versa 2 isn't in the device list. Well, mine was and is. The app still says I have a Versa 2 that just isn't connected. It seems to me that it's much more likely an interrupted update bricked the watch rather than it connected by accident, but wasn't REALLY connected, faked setup, and now has finally realized it shouldn't connect.
From what I can tell, my options sans any miracles you guys can inform me of are: Convince tech support there really is a problem and get the watch replaced; root my phone putting it at risk so I can update to Android 9, then find out the watch still isn't working and get it replaced; or just return it to Amazon and try to find somewhere that isn't out of Versa 2s this close to Christmas.
I should mention that I have a sleep disorder and am really wanting this watch to try and help my sleep. Amazon oversold and took an extra couple weeks getting it to me, and then when I'm setting it up, this happened. Basically, *whimper* Help? (And sorry for the long post.)
12-21-2019 23:36
12-21-2019 23:36
Well, now it just decided to sync to the computer for a minute. It started updating, asked to sign up for wifi, and then lost the connection again. I'll keep trying. Maybe I can get it to work after all...
12-22-2019 01:39
12-22-2019 01:39
I'm so sorry. It turns out I had forgotten to update my bluetooth driver in my computer. I'm an idiot.