Toyota Connected: Toyota, Lexus and Subaru as three plugins
One connector, registered once per brand with the brand fixed, so the
panel, the Web App and the Phone App each list Toyota, Lexus and Subaru
separately: own card, own account, own enable switch, own
/api/integrations/{brand} routes and vehicle provider. The brand picker
is gone.
Settings saved before the split under pluginSettings.toyota with brand
L or S move onto their brand's key on read, and are written back on the
next save. Cars linked as provider "toyota" read through their make's
brand.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This commit is contained in:
1 parent
9d8636ee73
commit
914aeeee23
21 files changed
+837
-471
No files matched your search
@@ -177,7 +177,8 @@ Restart the server. The plugin appears in the panel's **Plugins** card,
|
||||
**disabled** by default.
|
||||
|
||||
> DriverVault ships four built-in connectors today — `toyota` (Toyota Connected /
|
||||
> MyToyota, read-only vehicle data), `anker-solix` (Anker Solix V1 EV charger),
|
||||
> MyToyota, read-only vehicle data; registered three times, as `toyota`, `lexus`
|
||||
> and `subaru`, so each brand shows up as a plugin of its own), `anker-solix` (Anker Solix V1 EV charger),
|
||||
> `greencell` (Greencell HabuDen EV charger, read over the owner's MQTT broker
|
||||
> rather than a cloud API) and `apprise` (notifications, through an apprise-api
|
||||
> gateway the operator runs) — all blank-imported from `builtin/builtin.go`. The
|
||||
|
||||
Reference in new issue
Block a user