Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

[Abode Locks] Failed to updateStatus getaddrinfo EAI_AGAIN my.goabode.com #2

Open
mwm10 opened this issue Oct 27, 2021 · 1 comment
Open

[Abode Locks] Failed to updateStatus getaddrinfo EAI_AGAIN my.goabode.com #2

mwm10 opened this issue Oct 27, 2021 · 1 comment

Comments

@mwm10
Copy link

mwm10 commented Oct 27, 2021 •
edited
Loading

Hi there, occasionally I'm getting notifications that my doors are unlocked and then locked...when nothing is actually happening. The error that I think is causing this (but it's totally possible it isn't related) shows up in the logs is:

[Abode Locks] Failed to updateStatus getaddrinfo EAI_AGAIN my.goabode.com

I'm running HomeBridge on my Synology NAS in a Docker container.

Any thoughts on this?

Thanks!
@jasperpatterson
Copy link
Owner

As far as I can tell the EAI_AGAIN error happens if the DNS lookup fails, so basically Homebridge isn't able connect to abode's API. The plugin then sets the lock status to "Unknown" which I believe HomeKit sorta treats the same as "Unlocked".

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@mwm10 @jasperpatterson