Fitbit Integration Authentication Instructions?

Third party integrations
21

I followed JeeSee post above and also didn’t succeeded. You are refering to some “All options” and changes in hassio 0.102 - can you help me clearify thoose parts?

22

Hi I created a new API instance at the FIT APP site and then it started work again. I don’t if something changed when Google acquired Fitbit.

23

Ok, did you do these parts?

  • Created a folder named ‘fitbit’ in my ‘custom_components’ folder
  • Copied the file from Github as ‘sensor.py’ in this folder.
24

Nope - or actually that I did at first. But What made the different (I think) was creating a new Fitbit/Google App connection (Token)

1 Like
25

Hi All,

I’m trying to set up the Fitbit Integration and I can’t figure it out. When I go to dev.fitbit.com/apps/new/ the following information is required:

Application Name
Description
Application Website
Organization
Organization Website
Terms Of Service URL
Privacy Policy URL
OAuth 2.0 Application Type (Server, Client, Personal)
Callback URL
Default Access Type (Read & Write, Read-Only)

Application Name, Description, OAuth 2.0 Application Type and Default Access Type are either self explanatory or provided by HA Notifications - CONFIGURE. I did change the Callback URL to HTTPS. But, where do I find the additional information required to register an application.

The information that I still require is Application Website, Organization, Organization Website, Terms Of Service URL and Privacy Policy URL. Must I build a website to provide these URL’s?

Thanx

26

@williamwhoch Just make them up. I pasted the same URL for my home assistant that you used in the callback

27

Anyone know what the sensor names will look like if it’s working? I think I messed up the authorization and I don’t know how to fix it. I have a sensor.steps but I think that’s from the HA app.

28

Nevermind, It’s “sensor.steps_2”. Looks like I did it ok.

29

Thank you, that worked. All I have to do now is setup HTTPS.

30

I have this problem…
My Hass.io run on a Synology NAS under Docker. It works well but two days ago I was no longer able to reach the Home Assinstand interface. I reinstalled it and recovered everything through a snapshop I had done. But Fitbit is no longer configured. I tried to delete it from the configuration, restart, reinsert it and restart again but nothing.
Anyone have any ideas?

31

I’m trying to add this, but there’s a problem. The callback url is set to the local ip for some reason (http) and not https (because that’s not configured). I go via the nabu casa cloud. If I set that as callback url, the integration fails miserably. Ok, I change the wrong http local ip url in that adress to the naby casa url and I get the authorize page, I select every option hit authorize and than i get a big fat 500 internal server error. How does this work? And what’s the correct callback url if you use Nabu Casa cloud? Is that a bug that it only works on the local ip? Because I don’t want to set that up again with let’s encrypt and the whole stuff. Nabu Casa is easier and I support HA with that money.

2 Likes
32

I have the exact same issue as stefan. I remember setting this on my previous HA instance before and I had to try a million things until it worked, but now for the life of me I can’t figure it out.

33

Tried everything, same as mrkesu had it working in a previous installation but now really stumped.

we now have .

  external_url: https://redacted.duckdns.org
  internal_url: http://192.168.0.63:8123
  

#http:
#  ssl_certificate: /ssl/fullchain.pem
#  ssl_key: /ssl/privkey.pem 
#  base_url: https://redacted.duckdns.org

Tried it with NGINX turned on / off, DuckDNS on / off, some of or all configurations in .yaml commented out.

Also tried

I remember months back in my original setup I used my external I.P. but again cannot remeber exactly what worked.

Have HA given up on the fitbit Integration?

34

I got mine to work now with Nabu Casa.

  1. With the new internal\external URL settings in the UI I set both to “https://.ui.nabu.casa”
  2. Edited fitbit app to use “https://.ui.nabu.casa/api/fitbit/callback” as callback
  3. Rebooted home assistant
  4. Opened notification to configure fitbit and clicked the link.
  5. Nothing happened (?)
  6. Checked states under developer tools and YAY, sensor.weight is there from fitbit!
  7. Get depressed about my weight.
1 Like
35

explain number 2; there’s no such thing as a fitbit app, where does it say that?

36

I was able to use the Fitbit integration for several months. Then one day it stopped working. I can’t remember when or what changes I made around that time,or if it was when I was making changes, or if I was making changes around that time, or if it was weeks or months ago that it stopped working. Then I set it up with the Nabu Casa url. I wanted to spend time trying again to set it up without Nabu Casa in case I ever stop using Nabu Casa. Now. I can’t see Fitbit in the Integrations page of Home Assistant Configuration even if I take the Fitbit data out of the sensors.yaml. I haven’t signed out of Nabu Casa and am wondering if that is the reason it doesn’t show up.I think I am giving up and leaving it as is unless it breaks.

edit: I also realized that I could have tried deleting the app on the Fitbit end

37

I think he is talking about the app at Login

38

Hey guys, im trying since a few days now and no matter what i do i always get this message when i want to authorize the app.

Developer information: unauthorized_client - Invalid client_id

I have no idea what i did wrong, as i just copied and pasted the client_id given to me into the fitbir.conf

Any ideas?

39

I see this issue got closed and merged (Fitbit authorization always ends up with Server Code 500 · Issue #49285 · home-assistant/core · GitHub), does anyone know when this makes it into a core HA release? I just updated to 2021.6.6 but I still get the same issues trying to authenticate…

40

i still have problems with the docker home assistant container :frowning: