And I don’t think that’s a professional engineer/product designer should do to “let the customer think of hacky bypass”. It’s what we can think, but not what they can assume.
I happen to be a professional engineer/product designer. If this were my feature to design, I would employ something similar to existing limiters in the firmware, for example:
- regen limiters kick in to protect the battery when adversarial conditions are met (temperature, state of charge, etc)
- keep climate on will work until battery drops below 20% SoC.
In your hypotheticals, if SoC were low, or the routing to an SC was cutting it close by some threshold, the preheating feature should be automatically disabled. Clearly it's better to reach the SC and charge a bit slower than get stranded trying to get there to charge faster.
I've recently seen evidence that when SoC is low, all available regen is restored (if it had been currently nerfed due to low temps) to minimize the chances of you running out of juice, at the sacrifice to battery health. I think it's a good call.
That said, I've seen some iffy firmware features upon initial release that later get refined, so it's definitely within the realm of possible that initially we users have to do the hacky pin drop next to the SC to prevent auto-preheat from kicking in.