When using the legacy vehicle_data endpoint, it appears that drive_state data is no longer present if a user has not granted vehicle_location scope to the app/token. This change in behavior does not appear to be documented.
While it makes sense to hide gps fields such as active_route_latitude, active_route_longitude, latitude, or longitude from the drive_state data when vehicle_location scope is not granted or when location_data endpoint parameter is not passed into vehicle_data, other valuable fields like shift_state and speed are no longer coming through either, and these are important for an app to determine whether or not the vehicle is driving.
Even if the user has not granted vehicle_location scope, telemetry data still includes Gear and VehicleSpeed, so I would also expect those fields to still come through vehicle_data.drive_state.
Please advise if this is a bug or if there are any workarounds to get drive_state.shift_state and drive_state.speed to be returned when using the drive_state endpoint parameter in the vehicle_data endpoint.
Somewhat related:
When using the legacy vehicle_data endpoint, it appears that drive_state data is no longer present if a user has not granted vehicle_location scope to the app/token. This change in behavior does not appear to be documented.
While it makes sense to hide gps fields such as active_route_latitude, active_route_longitude, latitude, or longitude from the drive_state data when vehicle_location scope is not granted or when location_data endpoint parameter is not passed into vehicle_data, other valuable fields like shift_state and speed are no longer coming through either, and these are important for an app to determine whether or not the vehicle is driving.
Even if the user has not granted vehicle_location scope, telemetry data still includes Gear and VehicleSpeed, so I would also expect those fields to still come through vehicle_data.drive_state.
Please advise if this is a bug or if there are any workarounds to get drive_state.shift_state and drive_state.speed to be returned when using the drive_state endpoint parameter in the vehicle_data endpoint.
Somewhat related: