Feature Request: Stop only connected VIN if it is populated

It would be good to check currentVIN when requesting vehicles to stop charging via API.

It’s probably more complex than I am giving it credit for, though. For example, two Slave TWCs, one with VIN capability and one without. We drop below minAmpsPerTWC - what do we do? Perhaps what we need is a quorum where if all Slave TWCs are marked as supporting VINs, we only send stop messages to those VINs - otherwise we stop all vehicles per today’s behaviour. Or is this just an overly complex rabbit hole to go down?

[MikeBishop]

Unless you’re envisioning a mode where one charger is allowed to proceed and the other isn’t (which there is a use for – two cars that want to charge, with available power between minAmpsPerTwc and 2*minAmpsPerTwc), I don’t see a real use for limiting the stop command to the TWC’s connected vehicle.

Actually, I take that back – a garage with both a TWC and an outlet, and TWCManager shouldn’t be stopping the car on the outlet. That’s fairly niche, though; I’d think if you’re investing in TWCs and TWCManager, you have one per car you intend to charge at once.

[MikeBishop]

I think another way you could scope it, since we’ve already taken the step of keeping home/not-home status for each car, is to send the stop command to all cars at home, instead of all cars. This already exists in the code, but it’s gated behind a default-off config value. Default on, or just remove the setting?