The code in this repository helps with setting walking goals using a Fitbit device. Data obtained from the Fitbit API is downloaded to a folder called data; once downloaded, the data is used to count how many active steps the user has done each day and to set daily and weekly active step goals.

This project uses Deno and TypeScript.

Note that you'll need your Fitbit access tokens in this setup. You can see this page for instructions on how to get your access token.

1. Open a terminal (Windows PowerShell on Windows).

2. Install Deno. You can find install instructions on Deno's website or try the commands below.

   # For ubuntu/mac
   curl -fsSL https://deno.land/install.sh | sh

   # For windows (using PowerShell)
   iwr https://deno.land/install.ps1 -useb | iex

3. Next let's make an executable for the program on your computer (you also use this command to update this program to a newer version).

   deno install --allow-read --allow-write --allow-net --reload https://raw.githubusercontent.com/audrow/fitbit-goal-setter/deploy/build/fitbit-goal-setter.js

   Now you have my program!

   Note that you can uninstall the program by running the following command:

   # For ubuntu/mac
   deno uninstall fitbit-goal-setter

   # For windows
   deno uninstall fitbit-goal-setter.cmd

   You can test that the program works by running

   # For ubuntu/mac
   fitbit-goal-setter --help

   # For windows
   fitbit-goal-setter.cmd --help

   which will output something like the following:

   deno run <command>
   
   Commands:
     deno run list-devices                  List all devices
     deno run test-api-keys                 Test API keys
     deno run goal-status                   Get goal status
     deno run pull-data                     Pull data from the Fitbit API
     deno run call-fitbit-api <request>     Make your own call to the fitbit API fo
                                           r all devices
     deno run make-config-file [--minimal]  Make a config file. This doesn't overwr
                                           ite existing config files, so if you wa
                                           nt to make another config file, delete
                                           or rename the existing one.
   
   Options:
     -h, --help     Show help                                             [boolean]
     -v, --version  Show version number                                   [boolean]
   

   Note that each command begins with deno run <command>, this is a quirk of the library that I'm using for the command line interface. It should say fitbit-goal-setter.cmd <command> on Windows and fitbit-goal-setter <command> on Linux/macOS.

   Also, note that we haven't set up our config file, so you won't be able to run most of the commands yet.

4. Create a directory where you want, and go into it. The directory can be called whatever you want. In the following commands, we create a directory called fitbit, but you could use anything else.

   mkdir fitbit
   cd fitbit

   Note that this is the directory where your data will be downloaded to and where you should commands from in the future.

5. Now let's create a configuration file. This is how you'll set various aspects of the system up, such as how you define active steps, the Fitbit API credentials, the study and intervention dates, etc.

   # For ubuntu/mac
   fitbit-goal-setter make-config-file

   # For windows
   fitbit-goal-setter.cmd make-config-file

   You should see the following output:

   Created config file: config.yaml

6. Now we need to edit the configuration file. You can open the file in any text editor, for example on Windows you can use Notepad. Note that the config file will look better in a code editor, like Visual Studio Code.

   # For windows
   notepad.exe .\config.yaml

   The config file has several comments in it, which are lines that start with #. The comments are intended to help you understand how to use the config file. If you don't like the comments, you can delete the config file and then run the command again with the --minimal option.

   # For ubuntu/mac
   # rm ./config.yaml # remove the config file
   fitbit-goal-setter make-config-file --minimal

   # For windows
   # rm .\config.yaml # remove the config file
   fitbit-goal-setter.cmd make-config-file --minimal

   The main thing is that you must have at least one Fitbit device setup. This requires you to define study and intervention start dates, as well as to get an access token for each Fitbit device that you plan to use. For instructions on getting an access token from Fitbit, see here.

7. Once you have the configuration file setup, you can check the API keys to see if they are correct before proceeding. This command will check if you're able to connect to the Fitbit API at all and if you have access to the intraday steps. Both of these checks are necessary before you can run the rest of the commands.

   # For ubuntu/mac
   fitbit-goal-setter test-api-keys

   # For windows
   fitbit-goal-setter.cmd test-api-keys

   If this was not successful, make sure that you're using the right access token and that you have the right permissions to access the Fitbit intra process data. Make sure you've done everything correct in this page.

Now you're setup! The main command that you'll be using is goal-status, which prints information on the status of all devices in the configuration file.

# For ubuntu/mac
fitbit-goal-setter goal-status

# For windows
fitbit-goal-setter.cmd goal-status

All of the data generated from the Fitbit API as well as a summary of each days results is stored in a folder called data that will be created for you when you run goal-status or pull-data (pull-data is run automatically when you run goal-status). To see the generated data folder, run the command ls.

The files in the data folder are CSV files (Comma Separated Values), which separate data by commas. You can open this data file in Excel or any other spreadsheet program, like Google Sheets. For each device, there is a summary page and then a folder with all of the downloaded intraday steps data.

Makes a dummy configuration file for you. You can then modify the dummy configuration file to your own liking and add your own Fitbit devices. You can use the --minimal option to make a minimal config file, which doesn't have any of the comments or whitespace.

This gets the status of all devices in the configuration file. It will also list information about each device and its current state in the study.

This command also pulls data from the Fitbit API and stores it in a folder called data.

This command is implicitly run when you run goal-status. It pulls data from the Fitbit API and stores it in a folder called data. It will also create a summary of the data in a file called summary.csv.

This commands lists the devices in the config file. For more detail, see the config file.

This command performs two checks:

1. It checks if it can communicate with the Fitbit API at all.
2. It checks if it can access the intraday steps data.

Both of these are necessary for this program to work. If the first check fails, you likely haven't obtained your Fitbit API key correctly. If the second check fails, you likely didn't create the application on Fitbit's site with the correct permissions. You can either select the application as a personal application, or get explicit permission from Fitbit to access the intraday data.

This command lets you run an arbitrary request to the Fitbit API. It will run the command and print the output to the console. For example, you can use this command to get the last sync information with the Fitbit request URL: https://api.fitbit.com/1/user/-/devices.json and you will get something like the following:

Device: My Fitbit Device
[
  {
    battery: "Medium",
    batteryLevel: 60,
    deviceVersion: "Alta HR",
    features: [],
    id: "554003533",
    lastSyncTime: "2021-11-06T08:53:36.000",
    mac: "AA3A580A09C9",
    type: "TRACKER"
  }
]

Run the following command (same command as getting this program for the first time):

deno install --allow-read --allow-write --allow-net --reload https://raw.githubusercontent.com/audrow/fitbit-goal-setter/deploy/build/fitbit-goal-setter.js

Make sure you have gotten the API keys correctly. You may want to retry the steps in getting the Fitbit access token.

Make sure that your Fitbit application is setup correctly. Double check that in creating your application on Fitbit that you have the correct permissions for intraday steps data. This can be through selecting a "personal" application type or from getting explicit permission from Fitbit to use your app with intraday steps data. See getting the Fitbit access token for more information.

I'm not sure. I found that this occurred occasionally when I tested on Windows. If it does, just hit Ctrl-C and try again and probably it will finish up and give you the correct output.

Make sure that you are in the same directory that you created the config file in. You can do a ls to see what files and folders are in your current directory, and use cd to move into the correct directory.

YAML is a format for storing data. One of the way data is structured in YAML is through the spacing. Often you'll get an error where the error mentions how to fix it. For example:

Check that your config file 'config.yaml' is valid YAML format
 YAMLError: bad indentation of a mapping entry at line 18, column 2:
     daily:
     ^
    at generateError (https://deno.land/[email protected]/encoding/_yaml/loader/loader.ts:161:10)
    at throwError (https://deno.land/[email protected]/encoding/_yaml/loader/loader.ts:174:9)
    at readBlockMapping (https://deno.land/[email protected]/encoding/_yaml/loader/loader.ts:1227:14)
    at composeNode (https://deno.land/[email protected]/encoding/_yaml/loader/loader.ts:1502:13)
    at readDocument (https://deno.land/[email protected]/encoding/_yaml/loader/loader.ts:1688:3)
    at loadDocuments (https://deno.land/[email protected]/encoding/_yaml/loader/loader.ts:1750:5)
    at load (https://deno.land/[email protected]/encoding/_yaml/loader/loader.ts:1780:21)
    at parse (https://deno.land/[email protected]/encoding/_yaml/parse.ts:18:10)
    at load (file:///Users/audrow/Code/fitbit-script/src/config/index.ts:5:25)
    at async loadConfig (file:///Users/audrow/Code/fitbit-script/src/index.ts:20:12)

In this case, you know the line number and that something to do with the indentation is wrong. If you go and have a look, you can probably tell what is wrong.

Other cases may not be that straight forward. If the error is very confusing, I recommend just regenerating the config file and copying your settings into it. You can do this piece by piece and rerun a command, like test-api-keys to see what you are doing wrong.

It's likely that you have exceeded Fitbit's call request limit. They let personal applications have up to 150 requests in an hour. If you have exceeded this limit, you will need to wait until the next hour to make another request. If this is the case, here is an example of the error you'll be seeing in console.

Response {
  body: ReadableStream { locked: false },
  bodyUsed: false,
  headers: Headers {
  "cf-cache-status": "DYNAMIC",
  "cf-ray": "6a7e4a5c1fb92530-SJC",
  connection: "keep-alive",
  "content-length": "99",
  "content-type": "application/json",
  date: "Tue, 02 Nov 2021 15:10:34 GMT",
  "expect-ct": 'max-age=604800, report-uri="https://report-uri.cloudflare.com/cdn-cgi/beacon/expect-ct"',
  "fitbit-rate-limit-limit": "150",
  "fitbit-rate-limit-remaining": "0",
  "fitbit-rate-limit-reset": "2966",
  "retry-after": "2966",
  server: "cloudflare",
  via: "1.1 google",
  "x-frame-options": "SAMEORIGIN",
  "x-gateway-error": "ABOVE_RATE_LIMIT"
},
  ok: false,
  redirected: false,
  status: 429,
  statusText: "Too Many Requests",
  url: "https://api.fitbit.com/1/user/-/activities/steps/date/2021-11-02/1d.json"
}
error: Uncaught (in promise) Error: Trouble connecting to Fitbit - make sure your credentials are correct: status 429
    throw new Error(
          ^
    at fitbitRequest (file:///Users/audrow/Code/fitbit-script/src/fitbit-api/index.ts:77:11)
    at async getIntradaySteps (file:///Users/audrow/Code/fitbit-script/src/fitbit-api/index.ts:19:16)
    at async getStatus (file:///Users/audrow/Code/fitbit-script/src/caching/index.ts:417:29)
    at async file:///Users/audrow/Code/fitbit-script/src/caching/index.ts:439:13

The most important part of the error to look for is statusText: "Too Many Requests", which tells you that you've exceeded the number of requests you can make in an hour.

It is also possible that a token you were using expired, although not likely if you followed the instructions in getting the Fitbit access token, since we set the token to expire after one year. In this case, follow the instructions again to get a new token.

Probably, just make an issue or send me an email, and we can discuss it.

You can email me, or better yet, create an issue on GitHub (my preference). In either case, be sure to tell me what is going on and try to tell me how to reproduce it.