Hey, everyone. Trying to setup the Fitbit Integration and I’m running into a couple of issues:
I’m running Hassio on a Raspberry Pi 3B+ with the Let’s Encrypt add-on for SSL
I’m port-forwarding my 443 port on my router to port 8123 for Home Assistant
I’ve created the fitbit app setting the callback to my public domain over the https protocol
Right-clicking into the permissions screen, everything shows up correctly, I authorize Home Assistant
When redirected to the callback URL I get a 500 API error. The logs mention oauthlib.oauth2.rfc6749.errors.InvalidClientError as the exception getting thrown.
This sounds like a bug with Home Assistant, the Fitbit component and newly created Fitbit apps, but I wanted to check if you guys have any ideas.
Are we all using Hassio based installations? So far I’m guessing that either the HA Fitbit platform is broken/incompatible with newly created Fitbit apps, or this is an error due to how HA is run on Hassio. I’m planning on trying out a Hassbian installation one of these days and see if the error is replicated on that environment as well.
The comment just above yours on that thread is actually mine But I’ll give that thread a bump as well shortly, hopefully we catch the eye of a HA developer.
@p1ranha I was actually able to authorize Fitbit successfully using a custom component. I’ve posted the steps on the Github thread, let me know if you need any help in getting things up and running.
@jegormeister + restart HA after adding the file. If everything went well, you should see a message in the logs that you are running a custom component that was not tested by the HA team.
You should then be able to proceed and authorize Fitbit.
Hey there. Did you take a look on the Github post referenced above? I’ve posted each step that’s needed there. Let me know if you’re stuck on any of them or what the specific issue you’re seeing is and I’ll try to help out as much as possible.