Custom Local Telemetry Provider (HTTP/MQTT)

Feature Request: Custom Local Telemetry Provider (HTTP/MQTT)

Description

Allow ABRP to retrieve live vehicle telemetry directly from a configurable local HTTP endpoint or MQTT broker, without requiring telemetry to be uploaded to ABRP's cloud servers.

Use Case

Some vehicles, particularly BYD models running Android, already have applications capable of reading vehicle telemetry locally.

For example, BYD Trip Stats provides:

A local HTTP server (Web Companion).

MQTT telemetry publishing.

Real-time vehicle data, including SoC, speed, power consumption, and GPS.

Currently, integrating this data with ABRP requires sending telemetry through the cloud API, even when both applications are running on the same Android device.

Proposed Solution

Add a Custom Local Telemetry Provider supporting:

HTTP: Configurable endpoint (e.g., http://127.0.0.1:8888/api/telemetry).

MQTT: Configurable broker address and topic.

Configurable polling intervals.

JSON field mapping for SoC, speed, power, GPS, etc.

Optional authentication.

Benefits

No mobile data required for live telemetry.

Lower latency.

Better privacy by keeping vehicle telemetry local.

Compatibility with existing telemetry applications.

Support for offline telemetry when Internet connectivity is unavailable.

This would make ABRP significantly more flexible for vehicles with built-in Android systems and third-party telemetry solutions.