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.

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

How do I resolve: Error getting structure readings this is usually incorrect credentials, ensure you entered the right credentials. #381

Open
obversepebble opened this issue Dec 17, 2022 · 4 comments

Comments

@obversepebble
Copy link

Hi, I'm using Hoobs, and I've entered my client id, secret, username, and password from Flair in my plugin configuration. It keeps throwing the same error:

Flair Bridge starting
12/17/2022, 11:45:02 AMFlair BridgeLoaded plugin 'homebridge-flair'
12/17/2022, 11:45:02 AMFlair BridgeLoading 1 platforms...
12/17/2022, 11:45:03 AMFlair BridgeBridge is running on port 51836.
12/17/2022, 11:45:03 AMFlair BridgeFlairERRORError getting structure readings this is usually incorrect credentials, ensure you entered the right credentials.

I'm fairly certain I have the correct credentials. Thoughts on what I might be doing wrong or how to troubleshoot further?

Thanks in advance!

@QandnotU
Copy link

+1, having the same issue. Any insight would be grateful.

@QandnotU
Copy link

@obversepebble I figured out the issue on my end. I was using Flair's OAuth 2.0 credentials. Once I plugged in OAuth 1.0 (Legacy), everything is working as advertised.

@obversepebble
Copy link
Author

Oh nice. Unfortunately I tried both, and they don't work. Still getting the following error:

1/14/2023, 2:17:18 AMFlair Bridge starting
1/14/2023, 2:17:24 AMFlair BridgeLoaded plugin 'homebridge-flair'
1/14/2023, 2:17:24 AMFlair BridgeLoading 1 platforms...
1/14/2023, 2:17:24 AMFlair BridgeBridge is running on port 51836.
1/14/2023, 2:17:24 AMFlair BridgeFlairERRORError getting structure readings this is usually incorrect credentials, ensure you entered the right credentials.
1/14/2023, 8:25:21 AMWARNINGunhandled rejection: Error: getaddrinfo EAI_AGAIN dl.hoobs.org
1/24/2023, 1:22:53 PMWARNINGunhandled rejection: Error: getaddrinfo EAI_AGAIN dl.hoobs.org
1/24/2023, 1:28:47 PMWARNINGplugin site unavailable
1/24/2023, 1:28:47 PMWARNINGplugin site unavailable
1/24/2023, 1:28:49 PMWARNINGplugin site unavailable
1/24/2023, 1:28:51 PMWARNINGplugin site unavailable
1/24/2023, 1:29:49 PMFlair BridgeConfiguration change
1/24/2023, 1:29:49 PMflairbridge stopping
1/24/2023, 1:29:54 PMFlair Bridge starting
1/24/2023, 1:29:59 PMFlair BridgeLoaded plugin 'homebridge-flair'
1/24/2023, 1:29:59 PMFlair BridgeLoading 1 platforms...
1/24/2023, 1:29:59 PMFlair BridgeBridge is running on port 51836.
1/24/2023, 1:29:59 PMFlair BridgeFlairERRORError getting structure readings this is usually incorrect credentials, ensure you entered the right credentials.
1/24/2023, 1:30:19 PMWARNINGplugin site unavailable

@randymassey
Copy link

I stared having this issue myself this week. It seems after numerous attempts it gets the info & the child bridge I have it dedicated as will finally run. I have tried the v2.0 credentials I was issued & those worked one time for me briefly, I do try to re-check it, but I have to revert to the v1.0 Legacy OATH as well.

Unrelated to this specific topic, but recently, I have been having numerous non response in Apple Home just for the Flair vents. I have started from scratch rebuilding & reinstalling HomeBridge etc, even doing all plugin reconfigs manually, which was fun, but usually when I delete & re-add it will work for a while, & then after about 1-2 weeks it will show in Apple Home No response. I do run other plugins in HB, but I began making everything a child bridge, as originally this issue was taking down ALL of my HomeBridge accessories in Apple Home, but after setting everything up fresh & as child bridges; it quickly became apparent it was only the Flair plugin that was exhibiting the issue. Curious if anyone has been seeing that. Nothing really shows in the basic logs as far as errors for this no response secondary issue I am seeing. I am not clear if these 2 topics are directly or indirectly related, as the Structure error is recent only in the last week or so.

Thanks..

Randy Massey

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants