onstar2mqtt VS GM-Vehicle-API

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

Meanwhile Ford doesn't lock down the Fordpass APIs with OAuth client IDs and client secrets like GM does - https://github.com/q39JzrRa/GM-Vehicle-API - GM refuses to give client secrets to anyone writing an app intended for use by private owners.

(GM's API is protected by additional crypto that blocks "unapproved" applications, and they will only give API keys to fleet customers. Compare https://github.com/q39JzrRa/GM-Vehicle-API to https://github.com/itchannel/fordpass-ha )

GM explicitly blocks private end-users from any sort of third-party API integrations with cryptographic key bullshit no one else does - see https://github.com/q39JzrRa/GM-Vehicle-API for explanation of the cryptographic BS you don't see in Tesla or Ford's APIs, and https://developer.gm.com/vehicle-apis where GM outright tells private owners like ourselves that we're screwed

I’ve seen this https://github.com/q39JzrRa/GM-Vehicle-API but no practical usages. Also appears the login code is no longer working.

GM goes out of their way to lock out telematics API access to anyone who is not a fleet/commercial user with the exception of their app (see https://github.com/q39JzrRa/GM-Vehicle-API and https://developer.gm.com/ ), so no one can create an alternative app that isn't garbage. They refuse to bring the desktop web interface (my.chevrolet.com) up to feature parity with the app so we also can't precondition our car if we're in a location where our phone has no connectivity (such as a corporate environment with a metal building that does not allow personal devices on the WLAN)

That said pretty much everything else you've stated is valid. Infotainment and telematics in the Bolt is garbage. It's the only automotive headunit I've ever used that switches away from Bluetooth to SiriusXM on vehicle startup instead of waiting for Bluetooth to reconnect, GM explicitly blocks endusers from having any sort of useful API access (see the crypto-hackery needed by https://github.com/q39JzrRa/GM-Vehicle-API and https://developer.gm.com/vehicle-apis ) unlike Tesla, and GM still refuses to allow us to do basic things like precondition from a web browser via my.chevrolet.com . I work in a location that has no cell access and bans personal devices from wifi, so anything that is not Chrome on Linux or Windows is useless to me. The Bolt will connect to home wifi, but will not use it for anything but checking for OTA updates that do not exist unless you have a 2017 that hasn't been OTAed to remove features yet. As a result, if you park your Bolt in a location with weak cell coverage but strong wifi (such as my garage), telematics is unreliable/slow/flaky as hell.