12-13-2020 09:38
12-13-2020 09:38
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!
Answered! Go to the Best Answer.
12-13-2020 11:58
12-13-2020 11:58
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.
12-13-2020 11:58
12-13-2020 11:58
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.
12-13-2020 13:59
12-13-2020 13:59
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.
12-13-2020 22:15
12-13-2020 22:15
No worries. What you're wanting can still be done. There are hurdles, but those can be jumped.