Fails on startup with 400 bad request - OnStarJS keys expired - UPDATE: New version with alternate access method now available

[CamSoper]

Has been solid for months. Problem started today. I pulled latest, no change.

Output

**Attached as logs.txt
logs.txt
**

docker-compose.yml

version: '3'
services:
  onstar2mqtt:
    container_name: onstar2mqtt
    # image: michaelwoods/onstar2mqtt
    # image: bigthundersr/onstar2mqtt:latest
    image: ghcr.io/bigthundersr/onstar2mqtt
    restart: unless-stopped
    env_file:
      - ./onstar2mqtt.env
    environment:
    - ONSTAR_DEVICEID=<snip>
    - ONSTAR_VIN=<snip>
    - MQTT_HOST=<snip>

onstar2mqtt.env

ONSTAR_USERNAME=<nope>@outlook.com
ONSTAR_PASSWORD=<nope>
ONSTAR_PIN=<also nope>
MQTT_USERNAME=<mqttnope>
MQTT_PASSWORD=<further nope>

[BigThunderSR]

The API key expired on October 23. Unfortunately, there is only one person (@nilathedragon) who knows how to get the keys as of now and his latest attempt was unsuccessful (samrum/OnStarJS#258). Until someone can figure out a way past this, there is nothing I can do at this point. 😞

See: BigThunderSR/homeassistant-addons-onstar2mqtt#744

[CamSoper]

Totally understood, @BigThunderSR.

Thanks for everything you do for this community!

[Frazou1]

Same problem here as well :(

[glassbase]

How do we use this new method?

start container without OTP, get OTP, add OTP to config and restart container?

[metheos]

@glassbase
See the instructions in the readme of my OnstarJS fork that has enabled this functionality 👍

https://github.com/metheos/OnStarJS?tab=readme-ov-file#new-requirement-as-of-2024-11-19

[glassbase]

Been trying g to turn off email MFA, follow their steps, get email saying it’s disabled, but go back into account settings and email MFA is re-enabled automatically 😡

oh I see that it is maybe because I have a Canadian account

[Frazou1]

Been trying g to turn off email MFA, follow their steps, get email saying it’s disabled, but go back into account settings and email MFA is re-enabled automatically 😡

Me too, and i cant get the QR Code ... there is another way ?

[HaTaX2]

Just wanted to add my experience as everything is working for me now within HA, or at least the core functionality as it can take a few hours or a day to update things like battery & ambient temps along with tire pressure and mileage / energy usage.

I logged into my account on my computer in Brave browser and had to disable email as my MFA of choice, it sent an email with a code to verify and I did that. After a refresh of the account page I had the option to enable a 3rd party application for MFA and I enabled it. Clicking through things until I got to the QR code to be scanned, I then copy and pasted information on that page which included the QR's "otpauth" URL and also a separate block of text which had my account email address and "Secret XXXXX" where the X's are the TOTP key that was needed. (Edited to add, I did setup Microsoft's Authenticator app on Android with the QR code after I had extracted the TOTP information. It doesn't have an easy way to extract this information so getting that info on the setup QR page was a big help. If you have a raw QR code scanning app you could also use that to extract this information from just the QR code image.)

After putting all of that into the configuration section, I saw in the log it was able to successfully connect to my account and I finally saw information in HA again! So thank you so much everyone that put the effort and for sure some time into resolving this!! BigThunderSR, metheos, and everyone else behind the scenes.... you're awesome and I appreciate your dedication!

[CamSoper]

Awesome work, guys!

I've got my commands back, but my sensors aren't updating. I've got this in my logs:

onstar2mqtt2   | info: Button Configs Published! {"timestamp":"2024-11-22 23:47:09"}
onstar2mqtt2   | error: Error Polling Data: {"error":{"error":{"message":"Request Failed with status 504 - Gateway Timeout","request":{"method":"POST"},"response":{"data":"","headers":{"cache-control":"no-store","connection":"keep-alive","content-length":"0","date":"Fri, 22 Nov 2024 23:47:19 GMT","pragma":"no-cache","request-context":"appId=cid-v1:a7e19842-5b19-4b47-a9cf-85cc6e87a746"},"status":504,"statusText":"Gateway Timeout"},"stack":"Error: Request Failed with status 504 - Gateway Timeout\n    at RequestService.<anonymous> (/app/src/deps/index.cjs:35166:32)\n    at Generator.throw (<anonymous>)\n    at rejected (/app/src/deps/index.cjs:44:65)\n    at process.processTicksAndRejections (node:internal/process/task_queues:95:5)"}},"timestamp":"2024-11-22 23:47:20"}

Since it's a 504 I'm guessing it's probably a transient condition upstream, but I wanted to see if anybody else is seeing this. Is it just me?

EDIT: Never mind! It just went through! I've got my dashboards back!!!

Thanks again, @BigThunderSR!

[BigThunderSR]

Awesome work, guys!

I've got my commands back, but my sensors aren't updating. I've got this in my logs:

onstar2mqtt2   | info: Button Configs Published! {"timestamp":"2024-11-22 23:47:09"}
onstar2mqtt2   | error: Error Polling Data: {"error":{"error":{"message":"Request Failed with status 504 - Gateway Timeout","request":{"method":"POST"},"response":{"data":"","headers":{"cache-control":"no-store","connection":"keep-alive","content-length":"0","date":"Fri, 22 Nov 2024 23:47:19 GMT","pragma":"no-cache","request-context":"appId=cid-v1:a7e19842-5b19-4b47-a9cf-85cc6e87a746"},"status":504,"statusText":"Gateway Timeout"},"stack":"Error: Request Failed with status 504 - Gateway Timeout\n    at RequestService.<anonymous> (/app/src/deps/index.cjs:35166:32)\n    at Generator.throw (<anonymous>)\n    at rejected (/app/src/deps/index.cjs:44:65)\n    at process.processTicksAndRejections (node:internal/process/task_queues:95:5)"}},"timestamp":"2024-11-22 23:47:20"}

Since it's a 504 I'm guessing it's probably a transient condition upstream, but I wanted to see if anybody else is seeing this. Is it just me?

I have a note about this here: https://github.com/BigThunderSR/onstar2mqtt?tab=readme-ov-file#helpful-usage-notes

You should start getting data after you drive around for a few until the vehicle goes back into hibernation.

[CamSoper]

I'mma close this now, it's all good.

Thanks again, folks!