Fitbit: Difference between revisions

From Wildsong
Jump to navigationJump to search
Brian Wilson (talk | contribs)
mNo edit summary
Brian Wilson (talk | contribs)
mNo edit summary
Line 31: Line 31:


I tried it out in a virtualenv on Bellman (fitbit).
I tried it out in a virtualenv on Bellman (fitbit).
(fitbit) bwilson@bellman:~$ galileo -v
Tracker: 00B535851DF1: Synchronisation failed: INVALID_DEVICE_DATA:null
It can see my Charge 2 but sync fails.

Revision as of 01:54, 17 December 2018

TCX data

Summary: Fitbit's TCX data relies on getting GPS data from your phone, and the Charge 2 seems to have a sketchy idea on how to do this.

Even still I'd like to merge the Fitbit heart rate data with a better track log from my Garmin.

I have a Charge2 right now, and I want to try out the API to download TCX data from fitbit.com

I am working on Bellman.

Build an environment to try out oauth2 authentication

cd Projects/fitbit
git clone [email protected]:orcasgit/python-fitbit.git
virtualenv --python=python3 myapp
source myapp/bin/activate
pip install python-fitbit/requirements/base.txt

Then, you must read: http://python-fitbit.readthedocs.io/en/latest/

Register your app https://dev.fitbit.com/apps

Galileo and the Fitbit BLE USB device

2018-12-15 It sort of partially works, perhaps because I have a Charge 2 and it's not supported?

It was an interesting experiment all the same.

I tried it out in a virtualenv on Bellman (fitbit).

(fitbit) bwilson@bellman:~$ galileo -v
Tracker: 00B535851DF1: Synchronisation failed: INVALID_DEVICE_DATA:null

It can see my Charge 2 but sync fails.