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

"Error: Request Failed with status 400 - Bad Request" #60

Closed
LightningManGTS opened this issue Sep 27, 2023 · 8 comments
Closed

"Error: Request Failed with status 400 - Bad Request" #60

LightningManGTS opened this issue Sep 27, 2023 · 8 comments

Comments

@LightningManGTS
Copy link

Today I started to get bad request errors

I double checked that my login info for onstar was correct and it is.

image

@BigThunderSR
Copy link
Owner

Unfortunately, OnStar seems to have blocked API access again. I'm hoping they can figure out a solution here: samrum/OnStarJS#233

@BigThunderSR
Copy link
Owner

This should now be fixed in the latest release. Please verify. Thanks.

@BigThunderSR BigThunderSR self-assigned this Oct 10, 2023
@LightningManGTS
Copy link
Author

Can confirm that after restarting Node Red I was successfully able to send commands again.

@mdezzi
Copy link

mdezzi commented Feb 22, 2024

@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?

@BigThunderSR
Copy link
Owner

@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?

@mdezzi
Copy link

mdezzi commented Feb 22, 2024

@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.
Any idea how to pull a current vs latest version into a flow so i can notify myself when you push a new version?

@BigThunderSR
Copy link
Owner

BigThunderSR commented Feb 22, 2024

I just realized i was on an old version. I just updated and restarted Node Red. Looks like its working. Sorry about that.
Any idea how to pull a current vs latest version into a flow so i can notify myself when you push a new version?

No worries. Probably the easiest thing would be to enable a custom watch on the GitHub page and just enable the releases notification.

Screenshot_20240222-072813.png

@mdezzi
Copy link

mdezzi commented Feb 23, 2024

heck yea! I didnt know you could do that. Thanks for the tip!

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

No branches or pull requests

3 participants