06-21-2018 17:21
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post

06-21-2018 17:21
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post
- Who Voted for this post?
I am stepping thru creating my first new Clockface per the "Getting Started" SDK guide.
- I am able to view the new clockface thru the Versa Simulator just fine
On the watch, though, when I go into Options->DeveloperBridge, and try to connect to Fitbit Studio, I always get a connection error.
- I see a message "Connecting to Server"
- I see a message "Reconnecting"
- These 2 messages cycle over and over for a while
- This always ends, though, in "Connection error 1006"
When looking at the watch thru Versa->About, I do see an IP address on the watch
I have tried many steps to fix this
- I reset the Wifi connection in the Fitbit App on the phone (Nexus 5X)
- I rebooted the watch and the phone several times
I have tried toggling the following Fitbit Phone App settings
- Always Connected
- Keep-Alive Widget
- All-Day Sync
- Developer Menu->Developer Bridge
All without luck
I am stuck. I don't know what else to try. I cannot run the new clockface on my Versa watch from Fitbit Studio. I tried following a similar Forum message on this same "1006 Error" topic, but it did not help
Thanks . . . Leigh Potter
06-22-2018 02:33
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post

06-22-2018 02:33
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post
- Who Voted for this post?
I'm having the same issue.
Phone can connect, but the Fit bit Versa continually fails.
I've tried using the Android hotspot and work WiFi, tried restarting the watch, nothing has worked
firmware is 32.32.10.15
06-22-2018 05:34
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post

06-22-2018 05:34
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post
- Who Voted for this post?
Same problem here, got my Versa a few days ago and it connected successfully the first times but today it keeps getting error 1006 when trying to bring up the dev bridge.
I've dumped the network activity from the watch and after it connects to Wifi it makes a DNS query for 032-v3-client.fitbit.com and makes an HTTPS request to 169.55.193.23, after that it closes the HTTPS connection, disconnects Wifi and restarts the cycle for 4-5 times before showing the error 1006 message.
In other words the network works fine and the problem seems to be with the fitbit server.
06-22-2018 20:09
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post

06-22-2018 20:09
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post
I didn't change anything . . . but this seems to work fine today

06-22-2018 20:32
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post

06-22-2018 20:32
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post
Just checked mysef and it connected straight away .
The server must have been having some issues 🙃

04-26-2019 11:01 - edited 04-26-2019 11:12
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post

04-26-2019 11:01 - edited 04-26-2019 11:12
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post
Nearly the same problem, my laptop can connect, but my Fitbit Versa SE just can't be found
Version is 32.33.1.30

06-07-2020 14:23
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post

SunsetRunner
06-07-2020 14:23
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post
- Who Voted for this post?
yeh I got. the same problem, my phone can connect but my versa 2 does the exact same thing
08-09-2020 08:44
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post

08-09-2020 08:44
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post
- Who Voted for this post?
Sad but true. You would think they would want us developers making cool apps for it so they could sell more watches. But they can't seem to keep their developer server up (Connection error 1006), so we give up on writing apps.
