@AlvaroFitbit I was able to fix it that time after losing hours of sleep and gaining at least 300 gray hairs. Since then, it has decided that it wants to act up at least twice a week now. It is starting to get very tiresome to have to re-pair it all the time. I can't tell if it's something with the app software or the firmware in the tracker itself. When the tracker loses the capability to sync, the bluetooth menu under settings on my iPhone shows that it is connected.
For me to be able to successfully reconnect it, i have to first go into settings > bluetooth and forget device, then go to settings > about > clear user data on my tracker and wait for it to reboot. Simply rebooting the tracker does not affect anything. After I've lost all the data that it had been collecting, then it will reconnect 5 out of 7 times. As a programmer myself, it seems that there is a problem with the tracker not automatically syncing on whatever the sync schedule is and once it collects a certain amount of data in its buffer, it becomes unable to transmit that buffer or connect to any device at all until that buffer is cleared and the tracker resets its bluetooth connection list. Hopefully this insight will help the programmers at Fitbit to figure out a patch to correct this long term. My concern with that though is that since the Charge 3 is an older device and the money comes from selling new devices, not fixing bugs on older devices, that any continued changes and corrections to the programming for the Charge 3 will stop and that device will be marked as obsolete. My belief, and I'm sure that I share it with at least the other people who have commented on this thread, is that I wouldn't mind upgrading my tracker, but based off of the performance and headaches that have come about as the Charge 3 moves further down the new and shiny list makes me wonder if I don't just need to upgrade to a device that isn't a Fitbit. Scanning all the various posts on this board and the cookie cutter responses from tech support that we know don't help doesn't install a great deal of trust that the company supports or cares that thousands of people are having the exact same problem with the same tracker and it doesn't take a giant leap of faith for one to assume that Fitbit just doesn't care about the issue because it is an older tracker. It has also been said that the latest firmware for the Charge3 was supposed to activate the SpO2% sensor that has been dormant inside the sensor package of the Charge3. Despite that activation code being present in either 1 or 2 firmware versions ago (can't remember exactly) and the software change necessary to read and interpret that data being added to the Fitbit program the same 1 or 2 releases ago, I have yet to see any change in what has been being displayed for the sleep data.
