Loqed integration gives wrong URL for tokens during setup

[pieterdevriesch]

The problem

When trying to add a (autodetected) Loqed smart lock, the wizard tells you to make a personal access token on https://integrations.production.loqed.com/personal-access-tokens

However any token made using this link does not work and gives Invalid Authentication.

After talking to Loqed support they suggested I use https://integrations.loqed.com/personal-access-tokens instead. While I can see the old tokens that I made before there as well, creating a new token using this url does result in a functioning API key. So maybe the url in the wizard can be adjusted?

What version of Home Assistant Core has the issue?

core-2023.8.4

What was the last working version of Home Assistant Core?

No response

What type of installation are you running?

Home Assistant OS

Integration causing the issue

Loqed

Link to integration documentation on our website

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

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]

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

Code owner commands

Code owners of loqed 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 loqed Removes the current integration label and assignees on the issue, add the integration domain after the command.

_{^{(message by CodeOwnersMention)}}

---

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

[mikewoudenberg]

Thanks for the heads up. I was told those URLs would produce the same tokens, but apparently that has changed. I'll create a PR to have this changed.

[pieterdevriesch]

Yeah it worked fine 7 weeks ago when I tried last time, I guess they changed something in the back end.