Cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

Websocket in native API

ANSWERED

Hi,

I see in some topics that if you want to create an application to send heart rate data in real time to a web server, you have to use the native and companion API. Why not just build the app on the native API and not use an intermediate app on a device like a phone if Fitbit Dense has a Wifi connection? I am thinking of using the websocket functionalities in the native API to send my data to my server.

 

Thanks!

Best Answer
0 Votes
1 BEST ANSWER

Accepted Solutions

The Fitbit Device (native??) API doesn't provide access to WiFi. The only code with which it can communicate is the app's companion code (and that's done via bluetooth). The Companion API can onforward the data using websocket over WiFi.

Peter McLennan
Gondwana Software

View best answer in original post

Best Answer
3 REPLIES 3

The Fitbit Device (native??) API doesn't provide access to WiFi. The only code with which it can communicate is the app's companion code (and that's done via bluetooth). The Companion API can onforward the data using websocket over WiFi.

Peter McLennan
Gondwana Software
Best Answer

 I didn't know that I websocket functions are only available in the companion API. I thought it was available in the device API.

 

Thank you very much for your help.

Best Answer

No worries. What you're wanting can still be done. There are hurdles, but those can be jumped.

Peter McLennan
Gondwana Software
Best Answer
0 Votes