help menu

Join us on the Community Forums!

  • Community Guidelines

    The Fitbit Community is a gathering place for real people who wish to exchange ideas, solutions, tips, techniques, and insight about the Fitbit products and services they love. By joining our Community, you agree to uphold these guidelines, so please take a moment to look them over.

  • Learn the Basics

    Check out our Frequently Asked Questions page for information on Community features, and tips to make the most of your time here.

  • Join the Community!

    Join an existing conversation, or start a new thread to ask your question. Creating your account is completely free, and takes about a minute.

Not finding your answer on the Community Forums?

Cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Show  only  | Search instead for 
Did you mean: 

connection Error 1006 on watch when connecting to server (Dev bridge)

‎03-20-2018 16:29

‎03-20-2018 16:29

Hi 

I can't seem to be able to connect fitbit studio with my watch. It says connecting to server and afterwards displays Connection error 1006.  I'm not sure how to fix this.

I was also wondering if I could install my clockfaces that I made in Fitbit studio without publishing them?

 

Thanks in advance.

 

Kind regards 

 

Radu

Best Answer
20 REPLIES 20

‎07-13-2019 18:20

In response to fit2kel

‎07-13-2019 18:20

Old post but maybe worth posting what was worked out...

In addition to the Dev bridge connect error 1006, I experienced the Coach app update issue many others have seen. I suspected the 2 are related so checkout as below:
I deleted the existing Coach app and tried installing the new version with failure results.
I am a SW dev in real life and figure on testing the Fitbit waters so I enabled the developer bridge and tried to connect my Ionic to the Fitbit dev server but that failed with error 1006.
I utilize an enterprise type gateway solution in my lab/home network but none of the logs showed blocked or limited traffic from my Ionic so I ran a sniffer and analyzed the traffic. I see failures due to missed replies from the Fitbit servers in both the app install and dev server connection attempts.
In a first 'shotgun' attempt, I bypassed all traffic from my Ionic through the gateway.
The failures to connect Ionic to the dev server no longer happen. Then I successfully performed an install of the Coach app. The Fitbit app popped up an error after the Coach install, but it was installed. Subsequent syncs produce no errors.
Based on these results, I suspect the success some people have experienced by using wifi hotspot connections with a cellphone is because that's not being filtered through a home router or other firewall. These have been known to cause issues in other applications and the manufacturers aren't typically forthcoming with info regarding their 'protection' algorithms.
I don't really have the time to research what was interfering with the connects to Fitbit in my environment but I did note there was a disparity in the destination IP Address requested/resolved to Fitbit and the IP Address shown in the actual connect session for my Ionic's IP Address.

Best Answer
0 Votes