Closed LightningManGTS closed 1 year ago
Unfortunately, OnStar seems to have blocked API access again. I'm hoping they can figure out a solution here: https://github.com/samrum/OnStarJS/issues/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?
@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?
@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?
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.
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.