This is almost certainly irrelevant, but I'll recount it because it matches your description (brief periods of 'Connected' before dropping back to 'Connecting').
After weeks of pain, I discovered that my aging router was occasionally assigning the same IP to the watch and some other device on my network. Needless to say, when it did this, neither device could maintain a reliable connection. Occasional restarts of various devices would make the problem go away for a while because DHCP would usually reassign IPs which were unique.
My interim solution was to reserve IPs for the problematic devices (rather than relying on DHCP). My definitive solution was a new router. These changes totally fixed it for me.
As I said at the start, this is probably irrelevant for others because it's highly unlikely that your router is as dodgy as mine was. However, it might be worth a quick check to verify that your network IPs are all unique. You could even assign reserved IPs for your watch, companion device and development box if desperate.
Peter McLennan
Gondwana Software
Gold Fitbit Product Experts share support knowledge on the forums and advocate for the betterment of Fitbit products and services. Learn more
Best Answer
Fitbit Developers oversee the SDK and API forums. We're here to answer questions about Fitbit developer tools, assist with projects, and make sure your voice is heard by the development team.
