Failing to connect to the LOQED integration

[Itsreallyjustme]

The problem

Hey, I tried integrating my Loqed Lock in Home Assistant. Unfortunately the integration always seems to fail to connect with the entered API key. The API Key seems to be OK according to reqbin.com, also tried different keys but all failed to connect.

What version of Home Assistant Core has the issue?

2024.1.6

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?

Logger: homeassistant.components.loqed.config_flow
Source: components/loqed/config_flow.py:81
Integration: LOQED Touch Smart Lock (documentation, issues)
First occurred: 16:29:58 (9 occurrences)
Last logged: 16:54:36

HTTP Connection error to loqed lock

Additional information

Also saw the other thread with the HTTP connection issue. Tried to ping https://integrations.production.loqed.com/ which was succesfull.

[home-assistant[bot]]

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. - `@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)}}

---

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

[mikewoudenberg]

This is an issue where Home Assistant is unable to connect to your lock/bridge. It has already connected to the cloud api and successfully obtained the required secrets to communicate to the lock. Can you verify that you are able to reach the bridge from your Home assistant installation?

[Itsreallyjustme]

This is an issue where Home Assistant is unable to connect to your lock/bridge. It has already connected to the cloud api and successfully obtained the required secrets to communicate to the lock. Can you verify that you are able to reach the bridge from your Home assistant installation?

Thanks for the reply. I pinged the IP address from the bridge and it seems to be reachable. Home Assistant also auto discovers the bridge.

I'm still new to all of this so I hope this was the right method to use.

[mikewoudenberg]

Hmm that's weird. Could you try curl http://<ip address of your bridge>/status from your home assistant machine? Does that repsond with a JSON containing stuff like battery percentage etc?

[Itsreallyjustme]

Hmm that's weird. Could you try curl http://<ip address of your bridge>/status from your home assistant machine? Does that repsond with a JSON containing stuff like battery percentage etc?

It does.

[mikewoudenberg]

In that case The only thing I can think of is that the cloud API is not giving you a correct key for querying the lock. You could contact Loqed support and maybe they can help you with this issue. This has helped some people in the past.

[Itsreallyjustme]

Opened a support ticket. Will update once I receive an answer.

[lapodomo]

check your (old) outgoing webhooks is these are set you always get a invalid message. had the same issue and removing these and re adding the integration worked for me. check https://app.loqed.com/API-Config/index.php and read https://support.loqed.com/en/articles/6144029-home-assistant-loqed-integration#h_2e2dbf2740 carfully . also make sure that the added new webhook does not use your external domain name of HA (if you have one) if so change then the domain on the webhook to http://homeassistant.local:8123/ @Itsreallyjustme

[firebowl]

I've had a Loqed since today and unfortunately I keep getting the message that the API key is invalid / incorrect. According to Loqed support, the problem lies with HA and they are working on it. Is that the case? I have no existing outgoing webhooks and I can reach the Bridge from my HA instance and get status informations via http request.

Fixed, it worked with a new API token.

[mikewoudenberg]

@firebowl glad you got it working!

@lapodomo that will only work until the next reload of the integration of I'm correct. It will re-register the webhook on initialization

[lapodomo]

No it is not, i had 2 old webhooks ( used that before there was a ha component) with these in place i got invalid api key until they where removed. When removed the api key was validated right away and no issues since then. ( also not when rebooting) noticed also that responses are a lot quicker now

[issue-triage-workflows[bot]]

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍 This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.

[mikewoudenberg]

@home-assistant close