Hello,

I am a first-time Tesla owner and hence first-time TeslaFi user. With Sentry mode off the vehicle sleeps through the night ("Schedule Sleep Mode" and "Deep Sleep Mode " enabled in TeslaFi - which is great), While I understand Sentry Mode prevents the vehicle from sleeping, I enabled Sentry mode with the "Exclude Home" selected. The TeslaFi dashboard, however, continued to show Sentry mode enabled and the 2023 Model Y was not sleeping (the vehicle was located in my driveway, which is actually closer to me neighbor's house than mine do to the setback of our house from the road). 

Any insights of suggestions? I recognize that this might be as much a Tesla questions as it is a TeslaFi question.

Can you please add "start" and "end" of the State of Charge (SoC) at the drives? Actually there is only the usage of the battery in percent. In the past the start and end of the SoC has been displayed as well. Or can I customize this in the settings? But I haven't found anything about this issue.

I am confused by the prior and actual charging costs: For example:

I have 19 Charges at Location A.

Location A changed its price from 0,28 to 0,22 cent per kWh.

I go into my last charge on Location A, click on Location A > go to Price > enter the new 0,22 Cent price (added) than > save ... I get asked" Would you like the prior pricing to prior charges and the new pricing on future charges? > I say: Yes... and ALL prior pricing are changed to 0,22. Why? 
I do not understand this.

I use Raspberry Pi running TeslaUSB for archiving the dashcam videos to the server. The device needs to be kept powered up until it is done archiving. I've tried using the TeslaFi API calls for either 'wake' or'wake_up' every few minutes and noticed the car still goes to sleep after seemingly random times. I'm calling the API every 5 minutes, so as not to waste or exceed the max calls/minute and run into lock-outs. Is my problem not calling often enough? or something else?

I ran into a situation where one of my drives returned a data point with a Null latitude (and maybe longitude?). This - breaks the lifetime map entirely. Not the end of the world, but the lifetime map is one of the main reasons I like TeslaFi so much. 

I ended up using the monthly maps and going through day by day to find the offending drive, and had to delete it (the "hide" functionality did not work, I think due to the bad data in that particular drive?). Looking at the web developer tools - I saw that "latitude cannot be NaN" in one of the js files used by TeslaFi. Unfortunately I closed that window 😬.

So - long story short - I guess my suggestion is - one "bad" data point within a drive should not break the entire lifetime map. Perhaps you could flag data points where Lat/Long are NaN so we can exclude those points within the individual drive? or exclude the bad data points automatically - perhaps with a message that "bad data was found during this drive, automatically excluding those points from all viz" or something? I'll leave that up to you to interpret how best to handle.

My wife frequently accidentally turns things on - like climate control or sentry mode - needlessly using the battery. I would like to display a report of actions be each user.

Thanx

It would be great if the Shared Location page (/sharedLocation) would auto refresh ever 10 seconds or so.

Hi,

On each drive i can see which profile was driving and the safety score, but i don't find a solution to have this information when i download the data, why ? I would like to see how is the safety score for each driver profile. 

Hello 

I use TeslaFI on IOS and I am close to quitting. I have to enter both my Tesla credentials and the TeslaFI credentials manually each time I log in. 
it is really a pain. 
what am I doing wrong?