Can only push data to API while the Fitbit app is logged in developer's account

[Coolbit2019]

I am developing a simple Fitbit clockface for a research project on occupants' feedbacks on the thermal environment. All the data collected from the watch (questionnaire feedbacks, HR, steps, etc.) should be pushed to an external API. However, I found the data can only be pushed to the API when the Fitbit app is logged in my developer's account. 

While I logged in the Fitbit app using another account, the 'status' and 'settings' of the clockface from ‘running’ and ‘included’ become ‘unavailable’. So, I am wondering if this is because of the clock face is still a private developer version? Or are there any special settings I need to take care of when coding for pushing data to the external API?

[nenazarian]

Hi, Just checking if the Fitbit team has an answer to this? Thanks 

[nenazarian]

@Gordon-C do you happen to have any feedback on this? We're quite stuck and would appreciate any feedback. 

[Gondwana]

I suspect that this thread may be in the wrong forum. I think the focus of this forum is Fitbit's web API, whereas this thread may be about a third-party web API which is to be accessed via the Fitbit SDK. It may get more relevant consideration if moved to the Fitbit SDK forum.

[Coolbit2019]

I am developing a simple Fitbit clockface for a research project where people can give feedback using their watch. All the data collected from the watch (questionnaire feedbacks, HR, steps, etc.) should be pushed to an external API that I developed at the backend of my website server. However, I found the data can only be pushed to the API when the Fitbit app is logged in my developer's account. 

While I logged in the Fitbit app using another account, the 'status' and 'settings' of the clockface from ‘running’ and ‘included’ become ‘unavailable’. So, I am wondering if this is because of the clock face is still a private developer version? Or are there any special settings I need to take care of when coding for pushing data to the external API?

I need to deploy this clockface in multiple watches (with different accounts) and collect their data continuously through the API. The research project has been significantly delayed because of this issue so I'd appreciate any feedback you can provide. 

[nenazarian]

Hi, any help on this would be appreciated as I'm sure this is not the first time someone has tried to get feedback from Fitbit. Thanks, Negin

[Gondwana]

Without having thought it through too much, could this be because of a mismatch between device and account?

A Fitbit account can only have one Fitbit OS device associated with it. If you change accounts and want to use the same device, you need to remove the device from the first account (I think) and then add it to the second account. This may involve the equivalent of a factory reset on the watch, because apps associated with the first account won't necessarily apply to the second account.

I don't think the use of a developer-specific account should make any difference, unless it's giving you access to unofficial versions of firmware or APIs.

Side-loading apps could create problems when swapping accounts (because non-developer accounts shouldn't be able to side-load). You could try removing the side-loaded build (if any) and install it via a private GAM link. This should work regardless of account type — but always bear in mind that a device should only be associated with one account at any one time.

All of the above could be totally wrong.

[JonFitbit]

If you're switching user accounts on the mobile phone, it's possible that the device/companion are not correctly installed or available.

In order to test with multiple users/devices, you should upload your fba file to gam.fitbit.com, then use the URL it provides to install your app on multiple phones/devices.