Sense connects to WIFI but not the CLI

[rlhilton59]

I have a Sense (1) and have previously been able to build and install a clockface but I recently made a small change and tried to install the change.  The CLI is unable to find the Sense in order to install.  I have set "Enable" in the bridge settings menu.  It then says "connecting" and "retrying" multiple times but then gives up.  Meanwhile, I try to "connect device" but it says there is no device to connect to.  It will connect to my phone, and it will connect to the simulator (device and phone).

The WiFi on the Sense is set up and shows a connection while doing all this.  My router also shows the Sense is connected.

Is there anyone out there that can offer help?

[alayan2]

Were you able to make any progress? I'm looking into purchasing a fitbit that allows 3rd party apps for development. I read somewhere that Sense 1 was possibly going to disable third party apps but haven't read that anywhere officially. I want to purchase a fitbit but not sure which of the SDK compatible models to go for. 

[Guy_]

Hi @rlhilton59 - the account for CLI and watch need to be the same and set-up as a developer, just in case.

As an alternative you can create a GAM project to upload the built clock and install it on a watch via private link, though you can only run it.

@alayan2 - the Sense 2 and Versa 4 aren't supported in the Fitbit OS Simulator which makes debugging very hard.

The Sense 1 and Versa 3 share 1 SDK and Versa 2 another and are probably your best choices and have features later watches don't have.

Access denial to 3rd party stuff applies only to EEA users, see here

[rlhilton59]

I have made no progress.  My request for help was made in July and I got no response until yesterday.  I think support for 3rd party apps is diminishing.  I would stay away from Fitbit if your goal is to write 3rd party apps.  It has been great in the past, but I don't see a future for it.