I guess it's known enough to not need its own thread. There is help on the TeslaFi site that explains how the various options control the requests that TeslaFi makes to the Tesla api. I'm happy to try to answer your questions if you have specific ones.
In general, TeslaFi (as well as other data aggregators) call Tesla APIs that wake the car if it sleeps because it's the only way to get the required information. TeslaFi's way of letting the car sleep is to stop calling those APIs during a time window (typical 15 minutes). After that window, it first calls an API that does NOT wake the car and tells it if the car is awake or sleeping. If sleeping, it leaves it at that and only calls this api (every minute or so) to figure out when the car wakes up, and it only resumes tracking data when the car is awake. There's a chance that a drive might happen during that window of sleep attempt, meaning TeslaFi would miss some tracking. That's why there'S so many options, so you can tailor it to how you use your car and miss as little data as possible.
