Versa Lite continually losing BT overnight; won't sync. Now my phone can't even find it.

[cm20192]

For the past week, my Versa Lite would randomly disconnect from BT, especially overnight. I would wake up in the morning after syncing the night before and the time on my VL would be way off which messed up my alarms. I spent each morning following all the troubleshooting steps: restarting the VL, turning on/off the BT, restarting my iPhone, forgetting my BT connection, and resetting up my device. Yesterday I did a factory reset on my VL and updated my iPhone. That seemed to work, I had no issues all of yesterday. But I wake up late this morning to the same issue. After completing the trouble shooting steps my phone can't even find the VL during set up, despite restarting both and going through the troubleshooting steps. This Versa Lite was a Mother's Day gift last year, so I don't understand why it would be malfunctioning like this.

[JohnnyRow]

But it sounds to me that you are making the assumption your problem is caused by losing bluetooth connection.  Myself, I would not necessarily jump to that conclusion.  I would simply say your time is wrong, without adding that diagnosis.  If loss of bluetooth necessarily leads to wrong time, then it could not keep time whenever you are away from the phone.

[meragrin · Accepted solution]

Something was updated last week and caused things to break.  Last Friday I noticed mine change watch faces.  Didn't really think much of it since I actually preferred the watch face.  Couple of days later, I noticed it wasn't syncing and the time was way off.  Now the only way I can get it to sync is to remove the watch and add it back.  A lot of times it includes some combination of restarts, powering off, and/or factory resets.  I KNOW the firmware is the issue since none of my devices can see the watch to pair with it.  The watch is not even announcing its presence most of the time.  I don't know if it was strictly a firmware update and issue or maybe if an update to the phone application is contributing.  My bet is it is just the firmware since it is both iPhone and Android affected.