If you want to add multiple Fitbit accounts check out the instructions I created here: GitHub - TheTroubleshooter/Home-Assistant
Does this also fix the authentication issue?
When I used the core component it repeatedly stopped working after a month or so requiring the whole authentication process to be followed again to get it working.
I have not had any issue but no significant time has gone by.
Try it out: GitHub - TheTroubleshooter/Home-Assistant
I have installed this custum component for my wifes account and my own. (fitbit1, fitbit2)
After setting the internal URL the same as the external URL it worked great!
It’s a test, but for now, its looking good!
Thanks
Glad it worked for you as well.
Brian
So - adding three accounts.
Created fitbit1,fitbit2, fitbit3 directories and copied respective files into place.
Edited const.py to update sensor names and config file to include our names.
Config for fitbit1 works fine.
Config for fitbit2 works fine.
fitbit3 threw the following error when going to authorize via https://mydomain/api/fitbit3
The app you’re trying to connect did not provide valid information to Fitbit. Please report this issue to them. Developer information: unauthorized_client - A “Personal” application is only authorized to request access tokens from the owner of the application.
I deleted and recreated the App in dev.fitbit.com for this account, updated ID and secret in the config file and the link in the persistant notification still references the OLD client ID [even after restart of HA] so I now get the following error when requesting the authorisation URL:
The app you’re trying to connect did not provide valid information to Fitbit. Please report this issue to them.
Developer information: unauthorized_client - Invalid client_id
Any ideas how I resolve this, other than trying again with fitbit4 instead?
Thanks
Honestly, I only have two accounts so I only know that number of accounts to work. I am interested in knowing if three or more accounts will work or not. To help the cause, I will create a few more accounts to setup on my system to see if it works or not.
If it works, I will report back with the steps I did to get it to work. If it doesn’t work, I will see what I can do to get it to work. I am not a coder; I like to tear stuff down and put it back together a little differently than it was before. With that said, if I have the same issue you did, it is possible that Fitbit may have some limits of the number of accounts you can call from the same IP address to the dev.fitbit.com website.
Regards,
Brian
Looks like I got caught with some browser weirdness. Tried again by opening the auth link in another browser and all was well this time, so now have three accounts successfully collecting data.
Thanks
This has worked perfect for more then a week here now And I made a scoreboard if someone are interested:
Thank you for sharing your integration!
Brian
If you are still about, I have raised a ticket because there is a deprecation warning against your versions of the Fitbit integration suggesting it will stop working in 2023.1.
Any chance you can take a look?
Thanks
Anyone else find it pretty aggravating that the core integration doesnt allow multiple accounts? Ugh.
While it would be ideal to support multiple accounts, I didn’t want to wait or play too much around with HA, so built this solution: Displaying multiple Fitbit accounts in Home Assistant using Azure Logic Apps – Loryan Strant, Microsoft 365 MVP