-
Notifications
You must be signed in to change notification settings - Fork 2
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
"Error: Request Failed with status 400 - Bad Request" #60
Comments
Unfortunately, OnStar seems to have blocked API access again. I'm hoping they can figure out a solution here: samrum/OnStarJS#233 |
This should now be fixed in the latest release. Please verify. Thanks. |
Can confirm that after restarting Node Red I was successfully able to send commands again. |
@BigThunderSR I am now getting the 400 error on all requests. Is this another instance of GM blocking the key(s) used in the upstream onstarJS library? |
It's working for me. Are you running the latest version? |
I just realized i was on an old version. I just updated and restarted Node Red. Looks like its working. Sorry about that. |
No worries. Probably the easiest thing would be to enable a custom watch on the GitHub page and just enable the releases notification. |
heck yea! I didnt know you could do that. Thanks for the tip! |
Today I started to get bad request errors
I double checked that my login info for onstar was correct and it is.
The text was updated successfully, but these errors were encountered: