Allow Enode to have a session with multiple vehicles and not only one at a time

Hi ABRP Team and Community,

I want to submit a feature request regarding live data connections via Enode.

Our household currently drives two different EVs from different brands: a Volkswagen and a new Xpeng. Both brands use Enode to bridge live data (like State of Charge) to ABRP.

The Problem:

Currently, ABRP only allows one active Enode session per user profile. When I try to connect the second car, it overwrites or disconnects the token of the first car. This means we cannot have live data for both vehicles active in our account at the same time without constantly logging in and out.

Proposed Improvement:

Please update the live data architecture to allow multiple concurrent Enode tokens/connections within a single ABRP profile. If a user has multiple vehicles in their garage that rely on Enode, ABRP should look up the specific Enode connection tied to that individual vehicle ID, rather than enforcing a limit of one Enode account per profile.

With multi-EV households becoming much more common, this would greatly improve the user experience for families driving different brands.

Thanks for considering this improvement!