OnStarJS VS onstar2mqtt

OnStar is vastly overpriced given the extremely limited low-quality services it provides. Compare to FordPass, which lets you do stuff like change climate control settings remotely, vs. the Bolt's "whatever mode you were last in, that's what you're gonna get". FordPass also doesn't use cryptographic stunts to lock out anything but their crappy app like GM does - https://github.com/samrum/OnStarJS/commits/master/src/onStarAppConfig.json

There is an API. Its use by 3rd-party apps is not supported, but that hasn't stopped people from building stuff to leverage it. Here is an excellent place to start if you're interested in building something - https://github.com/samrum/OnStarJS

https://github.com/samrum/OnStarJS/commits/master/src/onStarAppConfig.json - OnstarJS operates by impersonating the official app, which as you can see from the commit history changes its crypto keys often. My guess would be that detecting an "old" app doing things an outdated MyChevrolet app would not do (as opposed to bitching at you to update) would be easy.

Being told that I, as a private owner, mean nothing to them is infuriating - and their Developer Relations page at https://developer.gm.com/vehicle-apis makes it explicitly clear that they only care about fleet customers. Private owners who want to integrate with HomeAssistant get to play endless cryptographic cat-and-mouse with GM - https://github.com/samrum/OnStarJS/commits/master/src/onStarAppConfig.json

https://developer.gm.com/vehicle-apis - "Fleet owners only. Private owners can go pound sand". Leading to constant cryptographic cat-and-mouse: https://github.com/samrum/OnStarJS/commits/4f381e50e4795aef2fbdb831b1cb4aa7090fcb96/src/onStarAppConfig.json

GM also explicitly tells private owners that GM doesn't care about them - https://developer.gm.com/vehicle-apis - GM makes it very clear they only care about fleet customers. Are you a private owner who wants to integrate with HomeAssistant? Enjoy the endless game of cryptographic cat-and-mouse ( https://github.com/samrum/OnStarJS/commits/master/src/onStarAppConfig.json ) because GM goes out of their way to try and block such use cases.

2) GM's developer documentation basically says that private owners like ourselves can go f*** ourselves, they only care about commercial fleet customers. https://developer.gm.com/vehicle-apis Private owners have the app and that's it - and GM goes out of their way to make sure we only have the app - see the endless whack-a-mole the OnstarJS maintainer plays on an average of roughly once a month: https://github.com/samrum/OnStarJS/commits/master/src/onStarAppConfig.json

For now just the docs for the Remote Access solution https://github.com/michaelwoods/onstar2mqtt

Correct. This is using onstar2mqtt. However, as I'm already saving $240/mo vs my old car, I can eat the OnStar subscription cost.

Install and run onstar2mqtt, following instructions for configuration. This uses OnstarJS to communicate with Onstar and publishes all data to MQTT. It also accepts commands, assuming your Onstar subscription is active.

onstar2mqtt