Fitbit Error

Configuration
1

Has anyone gotten FitBit to work with the latest release?

my sensor file:

- platform: fitbit
  monitored resources:
    - "activities/heart"
    - "activities/steps"
    - "sleep/efficiency"

I followed the steps to register a new app in the fitbit dev site.
for the application website and organization website, i’ve tried the local IP, loopback ip, and domain name.
for the callback url, i’ve tried: the local ip:8123/auth/fitbit, loopback, and domain as well.

I enter in the client id and client secret. The next phase of the configurator says to go to the localIP:8123/auth/fitbit site and authorizing. however, when i go to the site, i keep getting the following message:

{
    "message": "API password missing or incorrect."
}
2

Has your fitbit.conf file been created?

3

Yes it was created and I entered in the client is and client secret

4

This is not related with fitbit.
It’s your HA password

5

HA password for http? i’m able to view all of my frontend.

6

yes, but not fitbit.

You need to add “?api_password=yourpassword”, or remove your http pass from HA

7

Thank you. I added that and it brought me to this:

Developer information: invalid_request - Invalid redirect_uri parameter value

8

follow this: https://github.com/home-assistant/home-assistant/issues/2026

9

I was finally able to get it working. HA version 19.3 Here’s what worked for me:

sensors.yaml file:

- platform: fitbit
  monitored_resources:
    - "activities/heart"
    - "activities/steps"
    - "sleep/efficiency"

dev.fitbit:

Application Website *
http://localhost:8123/auth/fitbit

Organization Website *
http://localhost:8123/auth/fitbit

Callback URL *
http://172.16.1.18:8123/auth/fitbit/callback (Local IP of HA)
in a doc/example somewhere it has 127.0.0.1 as the IP and that didn’t work for me.

Last, when you go to the auth site… yours will be your local ip (http://172.16.1.18:8123/auth/fitbit) make sure that the correct client id is listed for your application. Mine was a wrong one, so i just changed it to relfect the new one i created. BTW, the new version, doesn’t require the ?api_password= anymore which is better for security.

10

FYI… heart doesn’t show up for me. shows unknown Bpm

11

Thanks, even i got it working, but seems it stops after sometime with error-

File “/home/pi/.homeassistant/deps/oauthlib/oauth2/rfc6749/clients/base.py”, line 194, in add_token
raise TokenExpiredError()
oauthlib.oauth2.rfc6749.errors.TokenExpiredError: (token_expired)

12

I too can confirm that i am receiving this error

13

It might be i am tracking too many values so the API limit is getting hit. Will try with just steps and verify today.

14

Were you able to get this working?

15

Nope,still broken

16

My Fitbit tracking started working yesterday. Not sure if it was Fitbit API issue but you might want to check to make sure if yours is working.

Also do you know of a way to not have to restart HASS to get the most updated information?

17

There seems to be an issue in the base python-fitbit library. I’ve issued a pull request to try to get it fixed: Catches OAuth token expired errors and fetches new token by shimeez · Pull Request #92 · orcasgit/python-fitbit · GitHub

I’ve verified that it fixes this locally