TWCManager
TWCManager copied to clipboard
Charge Session messages can get Slave TWC ID wrong
Not sure if it's related, but I observed this when I restarted TWCManager with an active charge session on the slave.
Note that the slave is actually ID 8244, but the Start/Stop Session messages reference 8282.
How odd - I'll take a look at it @MikeBishop, thanks for pointing that out