Redirect URI Issue Withings and Fitbit

[ironlion27]

The problem

Getting the following error when trying to initiate Withings and Fitbit integrations:

{"errors":[{"message":"redirect_uri_mismatch: The redirect URI provided is missing or does not match partner callback url"}]}

Both integrations have been working for many months until about 3 days ago and they both asked to be reconfigured and this error starts to be thrown. I have many other integrations that also rely on the cloud and everything else is fine. I'm fully updated to:

Core 2024.6.4 Supervisor 2024.06.0 Operating System 12.4 Frontend 20240610.1

I deleted the previous integrations with both Withings and Fitbit and tried to go through the onboarding wizard from scratch but after logging into their sites this error is thrown. Please advise.

What version of Home Assistant Core has the issue?

2024.6.4

What was the last working version of Home Assistant Core?

2024.5.4

What type of installation are you running?

Home Assistant Container

Integration causing the issue

withings

Link to integration documentation on our website

https://www.home-assistant.io/integrations/withings/

Diagnostics information

No response

Example YAML snippet

No response

Anything in the logs that might be useful for us?

No response

Additional information

No response

[home-assistant[bot]]

Hey there @joostlek, mind taking a look at this issue as it has been labeled with an integration (withings) you are listed as a code owner for? Thanks!

Code owner commands

Code owners of `withings` can trigger bot actions by commenting: - `@home-assistant close` Closes the issue. - `@home-assistant rename Awesome new title` Renames the issue. - `@home-assistant reopen` Reopen the issue. - `@home-assistant unassign withings` Removes the current integration label and assignees on the issue, add the integration domain after the command. - `@home-assistant add-label needs-more-information` Add a label (needs-more-information, problem in dependency, problem in custom component) to the issue. - `@home-assistant remove-label needs-more-information` Remove a label (needs-more-information, problem in dependency, problem in custom component) on the issue.

_{^{(message by CodeOwnersMention)}}

---

withings documentation withings source _{^{(message by IssueLinks)}}

[home-assistant[bot]]

Hey there @allenporter, mind taking a look at this issue as it has been labeled with an integration (fitbit) you are listed as a code owner for? Thanks!

Code owner commands

Code owners of `fitbit` can trigger bot actions by commenting: - `@home-assistant close` Closes the issue. - `@home-assistant rename Awesome new title` Renames the issue. - `@home-assistant reopen` Reopen the issue. - `@home-assistant unassign fitbit` Removes the current integration label and assignees on the issue, add the integration domain after the command. - `@home-assistant add-label needs-more-information` Add a label (needs-more-information, problem in dependency, problem in custom component) to the issue. - `@home-assistant remove-label needs-more-information` Remove a label (needs-more-information, problem in dependency, problem in custom component) on the issue.

_{^{(message by CodeOwnersMention)}}

---

fitbit documentation fitbit source _{^{(message by IssueLinks)}}

[joostlek]

I am not sure why it raises this, it only needs the redirect Uri when setting up

[allenporter]

At some point all oauth urls for all integrations were changed to use "my home assistant" which requires changing the configuration of allowed urls on the other sides developer setup. Double check the latest instructions and re-peedorm setup with the latest instructions for urls.

[ironlion27]

@allenporter Bingo! Had to use the "my home assistant" for the uri. Now it's just missing the bed occupancy device but otherwise back to regular. Thanks!

[joostlek]

Oh I interpreted "many months" as <1 year, so I didn't see that as cause.

The bed presence will come back when you lay in bed again