Skip to content
This repository has been archived by the owner on Oct 18, 2020. It is now read-only.

Error: invalid response, got HTTP 400: #105

Closed
nflute opened this issue Jun 25, 2020 · 27 comments
Closed

Error: invalid response, got HTTP 400: #105

nflute opened this issue Jun 25, 2020 · 27 comments
Assignees
@iRayanKhan
Labels
Api Used when Api has changed bug Used when an issue has occurred with the plugin

Comments

@nflute
Copy link

nflute commented Jun 25, 2020 •
edited
Loading

Explain the issue occuring:

My garage door is "No Response" and I received this HTTP 400 Error message today. MyQ app is working without problem.

I do not make any change. Restarting homebridge does not help.

Anyone come across this issue before, any idea on how to fix this?

Info

Plugin Version: homebridge-chamberlain v1.6.0
HomeBridge Version: Version 1.1.1
Node/Npm Version: v12.18.1/v6.14.5

Log Output:

[6/25/2020, 11:47:29 AM] [Garage Door] Error: invalid response, got HTTP 400: {
"SecurityToken": "",
"ReturnCode": "0",
"ErrorMessage": "please contact customer care, supportID: "11621071379429749844",
"CorrelationId": ""
}
at /usr/lib/node_modules/homebridge-chamberlain/src/api.js:27:15
at runMicrotasks ()
at processTicksAndRejections (internal/process/task_queues.js:97:5)
@nflute nflute added the bug Used when an issue has occurred with the plugin label Jun 25, 2020
@nflute nflute changed the title Issue Name Error: invalid response, got HTTP 400: Jun 25, 2020
@FearTheGrackle
Copy link

I'm having the same issues today... Lost internet for an hour or so, and after it came back I had the same... I've been racking my brain trying to figure out if related, but since you see the same issue I assume its not... phew... locked myself out of the house though until I found our extra key hidden outside lol

[6/25/2020, 2:00:51 PM] [Garage Door] Error: invalid response, got HTTP 400: {
"SecurityToken": "",
"ReturnCode": "0",
"ErrorMessage": "please contact customer care, supportID: " 1006672810473381074",
"CorrelationId": ""
}
at /homebridge/node_modules/homebridge-chamberlain/src/api.js:27:15
at processTicksAndRejections (internal/process/task_queues.js:97:5)

@schmidt660
Copy link

Explain the issue occuring:

My garage door is "No Response" and I received this HTTP 400 Error message today. MyQ app is working without problem.

I do not make any change. Restarting homebridge does not help.

Anyone come across this issue before, any idea on how to fix this?

Info

Plugin Version: homebridge-chamberlain v1.6.0
HomeBridge Version: Version 1.1.1
Node/Npm Version: v12.18.1/v6.14.5

Log Output:

[6/25/2020, 11:47:29 AM] [Garage Door] Error: invalid response, got HTTP 400: {
"SecurityToken": "",
"ReturnCode": "0",
"ErrorMessage": "please contact customer care, supportID: "11621071379429749844",
"CorrelationId": ""
}
at /usr/lib/node_modules/homebridge-chamberlain/src/api.js:27:15
at runMicrotasks ()
at processTicksAndRejections (internal/process/task_queues.js:97:5)

Same issue here. Happened at some point today. Guessing another API change?

@ghost
Copy link

ghost commented Jun 25, 2020

Same issue here.

@FearTheGrackle
Copy link

Forgot to mention:

Timezone GMT-0500
Alpine Linux (3.12.0)
v12.18.1
v6.14.5
root
/homebridge
/homebridge/config.json
/homebridge/node_modules
Yes

@iRayanKhan
Copy link
Owner

I hope the API didn't change again. My stuff isn't responding anymore either. I'll look into it, but if anyone is able to extract any new api info, please submit a PR.

@iRayanKhan iRayanKhan added the Api Used when Api has changed label Jun 25, 2020
@iRayanKhan iRayanKhan pinned this issue Jun 25, 2020
@bdjett
Copy link

bdjett commented Jun 25, 2020 •
edited
Loading

Took a quick look at this, looks like MyQ has just blocked the app build number in the User-Agent. Updating it to myQ/19569 (the current build in the App Store) seems to work.

@Moneyroks2
Copy link

Same issue.

Your on top of it IRayanKhan! Thanks being so responsive to your plugin's users!

@magnus319
Copy link

Took a quick look at this, looks like MyQ has just blocked the app build number in the User-Agent. Updating it to myQ/19569 (the current build in the App Store) seems to work.

That works, thanks.

@a-rodriguez
Copy link

Glad I am not the only one.

@mbierman
Copy link

Same here.

@HunterJKirby
Copy link

Took a quick look at this, looks like MyQ has just blocked the app build number in the User-Agent. Updating it to myQ/19569 (the current build in the App Store) seems to work.

How would someone go about changing the user agent? I’m relatively new.

@FearTheGrackle
Copy link

can confirm changing line in src/api.js to " 'User-Agent': 'myQ/19569 CFNetwork/1107.1 Darwin/19.0.0'," worked!

@FearTheGrackle
Copy link

Took a quick look at this, looks like MyQ has just blocked the app build number in the User-Agent. Updating it to myQ/19569 (the current build in the App Store) seems to work.

How would someone go about changing the user agent? I’m relatively new.

In your home bridge docker config directory find the api.js (for me its /home//config/homebridge/node_modules/homebridge-chamberlain#)

Line 17 ( I think) you'll see User-Agent setting, just edit out the myQ/ to myQ/19569 and save, restart home bridge...

That being said I'm sure @iRayanKhan is going to push a new build of the plugin very shortly, might as well just wait

@mbierman
Copy link

@FearTheGrackle @iRayanKhan would it make sense to make this a config item so that if it changes again it doesn't require a release for people to just tweak it on their own? I know, that might be overkill, just a thought.

@HunterJKirby
Copy link

HunterJKirby commented Jun 25, 2020 via email

@mbierman
Copy link

The fix seems to have worked for me too.

@joconor joconor mentioned this issue Jun 25, 2020
Closed
@mwhaley99
Copy link

mwhaley99 commented Jun 25, 2020 •
edited
Loading

Same issue here using HOOBS

@iRayanKhan
Copy link
Owner

@FearTheGrackle @iRayanKhan would it make sense to make this a config item so that if it changes again it doesn't require a release for people to just tweak it on their own? I know, that might be overkill, just a thought.

Yes, I will add this soon. I am working on other projects, and right after releasing V2 of homebridge-tuya, I will make this a config option.

And thank you @bdjett and @FearTheGrackle for finding out this info. I will publish a new build, and it will be live on NPM within the next 15-30 minutes.

@mwhaley99
Copy link

mwhaley99 commented Jun 25, 2020 via email

@iRayanKhan
Copy link
Owner

I don't know what the HOOBS interface is like, but I imagine it would day "x Plugin(s) are out of date". So just update it like that.
@mwhaley99

@iRayanKhan
Copy link
Owner

Closed:

Please update the plugin to the latest release.

@andrewturko
Copy link

andrewturko commented Jun 25, 2020 •
edited
Loading

@iRayanKhan Thank you for the fast response on this. I'm not seeing the new build on npm, do you have an ETA on when this'll be live (needed for update via config-ui-x)?

@iRayanKhan
Copy link
Owner

NPM shows its published on my end

@kevinjgibb
Copy link

@mwhaley99, just go to Hoobs/local then plugins and select Update under Chamberlain. Thank you @iRayanKhan for the fix!

@mwhaley99
Copy link

mwhaley99 commented Jun 25, 2020 via email

@furenberger
Copy link

@bdjett Where in the app store do you see that 19569? I'm wondering if it is something I can scrape off of their site?

@chris-jh
Copy link

I have updated to latest and the api has 19569 and i am getting this error.

Where do you find the new version numbers?

@craile craile mentioned this issue Aug 26, 2021
Closed
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees

@iRayanKhan iRayanKhan

Labels
Api Used when Api has changed bug Used when an issue has occurred with the plugin
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests