How fetzu/teslamate-abrp works
Main Components
a) External Systems (represented as external rectangles):
• TeslaMate System
• ABRP (A Better Route Planner) System
b) Core Components (represented as internal rectangles):
• MQTT Broker (Mosquitto)
• TeslaMate-ABRP Bridge (the main application)
• TeslaMate → MQTT Broker (vehicle data publication)
• MQTT Broker → TeslaMate-ABRP Bridge (subscription to vehicle data)
• TeslaMate-ABRP Bridge → ABRP API (data forwarding)
[TeslaMate] → [MQTT Broker] → [TeslaMate-ABRP Bridge] → [ABRP API]
Component Details
For each component, include these specific details:
a) MQTT Broker:
• Port (1883 default, 8883 for TLS)
• Authentication capabilities
• TLS support indicator
b) TeslaMate-ABRP Bridge:
• Configuration inputs (environment variables)
• Status reporting capability
• Model detection logic
Important Flows to Highlight
• Authentication flows (MQTT credentials, ABRP token)
• Vehicle data flow
• Status reporting flow (optional status topic)
• Configuration flow
Additional Elements
A configuration section showing:
• Environment variables
• Docker secrets support
• Required vs optional parameters
The unidirectional flow of data from TeslaMate to ABRP
Use standardized symbols:
• Services: Rectangles
• Security elements: Lock symbols