Problem:
This morning I setup Schedule & Reminders for a Set Charge Limit at 8am.  TeslaFi did not log the new charging until 8:18am, because it was trying to sleep (Not polling). This is because I have the TeslaFi Sleep Mode Time To Try to Sleep and Nighttime, etc.  I would not like to change the TeslaFi Sleep Mode settings for when I have a Schedule & Reminder setup.
Suggestion:
If a Schedule & Reminders item will end up in the car not being able to sleep.  Then, TeslaFi should start polling for about 5 minutes. And, reset the TeslaFi sleep counter after 5 minutes.
This would only happen if the Schedule & Reminders item would end up in the car not being able to sleep, e.g. Set Charge Limit is higher then what the charge state is at now.

Hi,

We drive our ModelY to an off grid location and there is no cell coverage there. This leads to an interesting data artifact that I can be solved more correctly.

1) Internet on, car is sleeping

2) Interne is on, car wakes up

3) Internet is off, drive starts

4) Drive goes into cell coverage, first data report comes in

In the summary, this is reflected as

Sleep+Park -> High range loss

Drive -> Starting point on the map shown as our cabin, but distrance for drive is only the in range distance

The ODO reading shows me what happened. There is a jump from the last drive report finish ODO, to the start ODO of the drive when it enters cell coverage. The ODO gap is outside of cell coverage.

It would be nice to maybe reflect that part of the drive as a disconnected drive (data coverage 0%). So that the listing becomes

a) Sleep + Park

b) Disconnected drive (Start of next report ODO - Sleep ODO, Startr of next report battery level - Park bttery level)

c) Normal drive

Other small issue, if temperature increases during a Park event, the battery level often goes up (and is reported as such). However the range loss number is shown as a loss still, maybe it would be better to show a negative loss?

Thanks for all the work on the platform. It's super cool to have all this data. Love all the recent improvements.

Happy holidays!

Bas

I love the Fleet Software Tracker. I think all of the data after the "week" portion of the branch causes it to be a noisy when looking for what certain things like "what percentage of the fleet is on a version of the latest branch (currently 2022.44._). It would be cool if this data was either 1) shown separately, or 2) toggle that entire page to summarize the data by branch

Is it possible to display “New to FSD Beta” vehicles? Currently I don’t see any cars showing a “previous build” that’s NOT FSD Beta with a “current build” that IS FSD Beta. Would be nice to see how quickly Tesla is accepting vehicles in to the Beta Program. 

Please explain?

It would be cool if I could be notified when software versions have NO TeslaFi users on them anymore (when they are removed from the tracker). There seems to be so many versions so tracking how many different versions are used by TeslaFi users is interesting. Maybe a chart for that metric as well (# of active versions over time, bar chart stacked by major branch/week).

Please, consider add a simple total charging cost/total kilometers to have a cost per kilometer, in general calendar.

Thanks.

Software Tracker could include a toggle to show/hide the FSD Beta versions on the list. This could be useful for markets where FSD Beta is not available (essentially any market outside of North America), to have more meaningful statistics of e.g. percentage of fleet on what SW version, etc

I may ask for a feature to add automatically drives sessions in between idle sessions.

here you have drive A ends on 117863km and drive B starts on 117867.

Their may not have a drive occured. Their HAVE a drive occured. Otherwise the end and start km. would be the same.

So please add calculated drives even if they are deteced.

It´s realy often here that the mobile conection is bad and a drive will not be recorded. a calculated drive could help in this case.