Using the developer bridge with Sense 2

[tristan_roddis]

I'm trying to develop a clockface for my brand new Sense 2, but the web-based Fitbit Studio doesn't seem to work (presumably due to the lack of wifi mentioned halfway down this getting started page).

So I switched to the CLI: I connected it directly to my computer (Linux, Ubuntu 18) using the USB charging cable, and enabled Developer Bridge. However, the device doesn't show up after running "npx fitbit" then "connect device".

What am I doing wrong?

[Guy_ · Accepted solution]

Hi @tristan_roddis - developers can't create clock faces as no SDK has been issued. In addition the Sense 2 doesn't support developer apps.

It is therefore normal that you can't connect your watch with developer bridge as there is no support for it.

[Gondwana]

The SDK for Sense 2 will be released soon (no date given).

[Guy_]

@Gondwana- We expected the SDK to appear at or before watch release but it didn't happen and the watches have been out over 3 months already! 

So, "Soon" without a date, means it's not working but might one day.

As this is a significant OS change and there is no roadmap of what will be released, what the SDK will contain is purely speculation and may be missing many features. It is probably better to wait and see.

[SomethingChoco]

Hi there, 

am I understanding this correctly, that any face i am developing in with the fitbit studio - with the simulator - even if I were to publish it, it would not be available for my Sense 2?

I would assume that somehow there is a way to create new faces for the Sense 2 because there are non-by-Fitbit faces available in the gallary. How is this possible, if I cannot select Sense 2 in the Fitbit Studio?

[Guy_]

Hi @SomethingChoco  - you are correct you cannot develop clocks for a Sense 2 or Versa 4, even for yourself. And Apps are not supported, only Fitbit system functions.

The non Fitbit clock faces in the Gallery were put there by Fitbit. They may or may not work but can't be fixed if they don't.

Best solution, get a refund on your Sense 2 or Versa 4, and get the prior model with which you can have fun deveioplng for and enjoy the features not found on the later models.

[SomethingChoco]

wow, that is disappointing. I have read that additional functions are still being released, so I am not sure, if this is also something that might be there in the future.
I have tried to install one of the none-fitbit-faces and it actually crashed my watch.. I had to reset it because it was restarting again and again...
(it did have a tag that said something about "not optimized" or something - but I thought it might work anyway...)

In addition to this - I do feel the Sense 2 hast a lot less functionality than the Sense.. So I think I will actually follow your advice and switch to a Sense...

[Gondwana]

There's a bit more to it than Guy_ mentioned.

Fitbit has stated that an SDK for Sense 2 is coming. A date hasn't been specified.

[SarahBass]

That is such good news!! I am excited for that release. 

[Guy_]

---

@Gondwana wrote:

Fitbit has stated that an SDK for Sense 2 is coming. A date hasn't been specified.

---

@Gondwana- Christmas is coming and a date has been specified!

It is nearly 6 months since the announcement went public, see Sense 2 announcement  2022-08-23  and already by then the SDK must have been fully operational since a long time in order to build the software.

Given this delay it is probable it may not be coming at all, despite what has been stated.

And as there will be no Apps possibility, developers are already severely discouraged.and may not bother with these watches and wait for the next models, if there are any..

It's great to dangle a fruit, but if it's not already available by now it becomes of little interest. See also SDKs preparation Developers may not be able to support older watches.

---

[Dopovo]

---

@Gondwana wrote:

There's a bit more to it than Guy_ mentioned.

Fitbit has stated that an SDK for Sense 2 is coming. A date hasn't been specified.

---

I've never read anywhere such statement, on the contrary the moderators, such as @LizzyFitbit , are continuosuly reiterating that Sense2/Versa4 do not support apps and to vote for the relevant suggestion that, despite the many votes, is still not being considered. @Gondwana Can you please share the source thanks?

In any case, as @Guy_  is saying, I honestly don't understand why Fitbit shouldn't speak more openly about such plan, if existing, to avoid 1) that developers abandon the platform 2) users return or change brand looking for a smartwatch and not just a fitness watch.

[Gondwana]

There are two issues here. Fitbit has stated that there will be a SDK for the new devices, but they haven't stated whether it will allow development of clockfaces only or non-clockface apps as well.

The clearest statement that the SDK is coming is on the Fitbit dev Discord. Unfortunately, this forum blocks links to Discord, so you'll have to search for it yourself. It's in the 'fitbit' channel on Oct 17 by JonFitbit.

There's a brief official comment on this board here.

[Guy_]

@Gondwana  - to answer the first issue, it is almost certain that's there will be no apps support, why?:

Currently there are no "apps" only system functions provided by Fitbit and listed as apps for the Sense 2/Versa 4.

Although Fitbit ported some developer clock faces no developer apps have been ported. They presumably only work in the system environment that only Fitbit has access to.

As regards an SDK release date, it might be quicker to have a baby! We can only wait to see which is actually quicker 

[Guy_]

---

@Guy_ wrote:

As regards an SDK release date, it might be quicker to have a baby! We can only wait to see which is actually quicker 

---

 As Fitbit likes giving names to things, may be if we just thought up a cute name it might speed things along, something like Phantom or OSprey?

[cyberprodigy]

I upgraded to Versa 4 and can confirm that Versa 4 no longer works and it is not possible to obtain a connection from Versa 4 in https://studio.fitbit.com/ . FitBit studio can establish a connection with the phone but in the device list it shows "No device found". Trying to use my old Versa 2 and it shows up properly.

Additionally if following the tutorial on the web page https://www.youtube.com/watch?v=WkCKycDUgmU&t=436s&ab_channel=FitbitDevelopers then it says that on the device it should show "Connected to server" when enabling developer mode. For Versa 2 it works as expected, but for Versa 4 it shows unclear message ""Charger connected" "USB debugging: ON". Not sure what it means but looks like it is not connecting to the server any more.

  

If I connect devive via USB and run "adb devices", then only my phone shows up. Are there any Fitbit SDK tools I don't know of that lists the connected devices?

[Gondwana]

It will be possible to use Versa 4 with the CLI when the SDK for that device is released.

[cmengler]

@cyberprodigy If you want to be adventurous in the meantime -- you can use this approach to sideload your apps onto your Versa 4 -- this repo gives a brief rundown of the steps -- https://github.com/cmengler/fitbit-app-versa4

I've used it to install my own apps and the original Spotify HR app onto my Versa 4 -- all working great!