Version 2.0.0
Fitbit sunset it's OAuth 1.0a connections on August 1, 2016. In doing so, this bot's underlying fitbit-js
library no longer worked. The library has been replaced with fitbit-node
, which is a bit rougher around the edges but gets the job done.
Upgrading from 1.0.x?
You will need to update your FITBIT_CLIENT_ID
and generate a new FITBIT_OAUTH_TOKEN
using the steps below. You no longer need the FITBIT_OAUTH_TOKEN_SECRET
configuration variable. Note that you will have to go through this process at least once a year (the Implicit grant type token is time-limited.)