[Feature Request] Support for Tessie API as a Data Provider in TeslaMate

[Mewks]

Feature Request: Support for Tessie API as a Data Provider in TeslaMate

Dear Devs/Community,

First and foremost, thank you for the incredible work you've done with TeslaMate. It has become an essential tool for many Tesla owners, myself included, and I truly appreciate the effort that goes into maintaining and enhancing this platform.

Feature Request: Support for Tessie API as a Data Provider

I would like to request the addition of native support for the Tessie API as a data provider within TeslaMate. Tessie offers robust streaming capabilities and comprehensive access to Tesla vehicle telemetry, making it an excellent alternative or supplement to the existing Tesla API.

Background:

I recently attempted to integrate Tessie's streaming capabilities with TeslaMate using the following Docker environment variables:

TESLA_WSS_HOST=wss://streaming.tessie.com
TESLA_WSS_TLS_ACCEPT_INVALID_CERTS=true
TESLA_WSS_USE_VIN=true
TOKEN=?access_token=xxxxxxxxxxxxxxxx

However, I encountered the following error repeatedly:

2024-08-05 11:55:37.743 [error] ** (CaseClauseError) no case clause matching: {:remote, 1008, "Invalid VIN"}
2024-08-05 11:55:38.537 car_id=1 [info] Start / :online
2024-08-05 11:55:38.554 car_id=1 [info] Connecting ...
2024-08-05 11:55:39.317 [error] ** (CaseClauseError) no case clause matching: {:remote, 1008, "Invalid VIN"}
2024-08-05 11:55:40.067 car_id=1 [info] Start / :online
2024-08-05 11:55:40.101 car_id=1 [info] Connecting ...
2024-08-05 11:55:40.856 [error] ** (CaseClauseError) no case clause matching: {:remote, 1008, "Invalid VIN"}
2024-08-05 11:55:41.685 car_id=1 [info] Start / :online
2024-08-05 11:55:41.717 car_id=1 [info] Connecting ...
2024-08-05 11:55:42.468 [error] ** (CaseClauseError) no case clause matching: {:remote, 1008, "Invalid VIN"}

This error suggests that the current implementation may not fully support the Tessie API or that there might be some compatibility issues with the way TeslaMate is attempting to interface with Tessie.

Tessie API Overview:

Tessie provides a well-documented API that supports real-time streaming and comprehensive access to Tesla vehicle data. Here are some key aspects of the Tessie API that could be beneficial for TeslaMate:

• Tessie Quick Start Documentation
• Tessie Authentication Documentation
• Tessie Fleet Telemetry API

The Tessie API uses a token-based authentication system, which is straightforward to implement and secure. Additionally, the streaming capabilities provided by Tessie could offer a reliable and consistent data stream, potentially reducing issues related to Tesla's native API limitations.

Benefits of Tessie Integration:

• Enhanced Reliability: Tessie's API might offer improved reliability, especially in cases where Tesla's native API is rate-limited or temporarily unavailable.
• Simplified Configuration: Integrating Tessie directly could simplify the setup process for users who already have a Tessie subscription.
• Expanded Telemetry Access: Users could benefit from additional data points or improved data resolution provided by Tessie.
• Replacing General API: The Tessie API could potentially replace the Tesla Fleet API as the primary data provider, reducing the impact of recent Tesla API changes and avoiding rate-limiting issues.

Potential Implementation:

Given the structure of the Tessie API, the implementation could involve:

• Direct API Integration: TeslaMate could natively support Tessie as an alternative API provider, allowing users to select Tessie during setup.
• Streaming Support: Full support for Tessie's streaming capabilities, allowing for seamless data flow into TeslaMate's dashboards and databases.
• Data and Telemetry: The integration should support both standard data and telemetry from Tessie, ensuring full compatibility with existing TeslaMate features.

Recent API Changes by Tesla:

In light of recent API changes by Tesla, which have caused all sorts of issues and disruptions, I believe that supporting Tessie as a data provider would allow users like myself to continue using TeslaMate's Grafana dashboards with minimal changes to our existing setups.

Conclusion:

I believe that adding support for Tessie as a data provider would greatly benefit the TeslaMate community. It would provide users with more flexibility and potentially enhance the reliability of data collection. I am happy to assist with testing or provide any further information if needed.

Thank you for your consideration. If this has been discussed before or isn't possible due to the way TeslaMate works, then I understand, and I thank you for your time.

Additionally, I’m aware of this discussion, and I've looked at other posts, most of which talk about importing data, which is not what I'm suggesting here. Instead, I want to configure TeslaMate to pull the same data from Tessie rather than the Tesla Fleet API.

Best regards,
Mewky Dewky