GM standardized subscription plans support
GM is migrating partner applications from legacy consent scopes to standardized subscription plans (API_STARTER, API_PRO, API_ELITE), with a new application ID per customer. The protocol now supports both the legacy and the plan based flow on one channel, so vehicles can be migrated gradually.
New channel configuration block "Plan credentials": the application client ID, secret and FAN assigned by GM for the subscription plans. The owner pair and the FAN of the main credentials are used when omitted. The main "Credentials" block and all existing commands keep working as before.
New device commands and setting, all using the plan credentials:
- provision_plan: consents the vehicle for the selected plan and opts in the selected data services (pick list). Consent with a new plan changes the plan of an already consented vehicle.
- deprovision_plan: revokes the plan consent, which opts out all data services on the GM side.
- plan setting: shows the plan the vehicle was consented for through flespi and changes it with a consent only request, without touching the data services.
The channel remembers which application each vehicle is consented under and sends all other commands (location, doors, ignition, data services, vehicle status and so on) with the matching credentials. Vehicles migrated by GM itself are detected by the daily data services refresh or by the data_services setting refresh. During the migration overlap the partner notification IDs of both applications are mapped to the vehicle, so data keeps flowing from either stream, and the data_services setting lists both.
Also new: optional "API URL" channel configuration field to point the channel at another GM REST host, and the channel now processes commands even without the Pulsar section configured.
