Select Data Source per Data Type (Location, SoC, Charging, etc.)

As recommended in my previous support ticket I would like to submit this feature request. https://abrp.featurebase.app/p/incorrect-vehicle-track-when-using-generic-live-data-enode

Currently ABRP only allows using all data from a connected integration or none at all. Additionally when multiple integrations are active at the same time ABRP appears to switch between the available data sources. This can lead to inconsistent values inaccurate vehicle tracking, or unrealistic averaged values in the recorded history when different integrations report data with varying quality or update.

However data quality can vary depending on the source brand and vehicle.

For example some vehicles may provide accurate battery and charging information through Enode or a Generic API while location or SoH data may be more accurate through Android Auto.
In my case vehicle telemetry works well through Enode, but location tracking is more reliable through Android Auto.

It would be very useful if users could choose which data source ABRP should use for individual data types, such as:

• Vehicle location

• State of Charge (SoC)

• Charging sessions

• Charging power

• Vehicle status

This would allow users to combine the best available data from Enode, Generic API, Android Auto, CarPlay and improve overall data accuracy and user experience.