TeslaFi.com

[Cyclone]

So, don't update to Firmware 8.1. That will go over well around here. Hopefully an alternative field will be found soon!

 

[Jdeck]

So, don't update to Firmware 8.1. That will go over well around here. Hopefully an alternative field will be found soon!

There's only 3 users on it so far. I'm HOPING it was a mistake and it will return on the next version.

 

[HankLloydRight]

There's only 3 users on it so far. I'm HOPING it was a mistake and it will return on the next version.

If you have any contacts in the API group at Tesla, it might be worth dropping a line -- it's possible it was an oversight and not intentional. Even an email to [email protected] could end up in the right department.

 

[rypalmer]

Well....we have a big problem. Tesla appears to have removed the battery_current response from the API in software version 17.11.3. Unfortunately I rely on this field pretty heavily and parts of the site are not going to work without it.

I'll monitor what's going on today but I won't be able to dig in deeper until tonight. All versions before 17.11.3 still work fine.

Are there really no alternative fields there to support the display of charging rates within app? I'd find that hard to believe!

 

[brkaus]

Is that how people were coming up with direct horsepower measurements? If so. probably gone on purpose.

 

[Jdeck]

If you have any contacts in the API group at Tesla, it might be worth dropping a line -- it's possible it was an oversight and not intentional. Even an email to [email protected] could end up in the right department.

Thanks Hank. I sent an email. We'll see what happens.

 

[Jdeck]

Are there really no alternative fields there to support the display of charging rates within app? I'd find that hard to believe!

There's a 'power' field available in the the REST API and streaming API but it doesn't have anywhere near the accuracy that I'm used to using and will require a significant rewrite to certain areas.

 

[Jdeck]

Well....we have a big problem. Tesla appears to have removed the battery_current response from the API in software version 17.11.3. Unfortunately I rely on this field pretty heavily and parts of the site are not going to work without it.

I'll monitor what's going on today but I won't be able to dig in deeper until tonight. All versions before 17.11.3 still work fine.

Actually it doesn't look too bad. Supercharger efficiency is going to have to be recalculated and seep modes are going to have to be imagined. So far that's all I've found.

If anyone finds any issues please enter them in the bug tracker.

Thanks

 

[mbhforum]

Is it normal for Teslafi to miss a couple of drives? I was idle all day yesterday. I took a couple of drives today and it has me idle still since yesterday. I am still on 17.6.5.

 

[Jdeck]

Is it normal for Teslafi to miss a couple of drives? I was idle all day yesterday. I took a couple of drives today and it has me idle still since yesterday. I am still on 17.6.5.

No, not at all. You can look at the raw data logs and check out what was going on or open at ticket in the support section and I'll take a look at it.

 

[mbhforum]

No, not at all. You can look at the raw data logs and check out what was going on or open at ticket in the support section and I'll take a look at it.

Thx opened a private ticket

 

[appleguru]

Actually it doesn't look too bad. Supercharger efficiency is going to have to be recalculated and seep modes are going to have to be imagined. So far that's all I've found.

If anyone finds any issues please enter them in the bug tracker.

Thanks

So you've already made some changes and it is "safe" to update to 8.1 without risking losing (significant) data?

I haven't got the update yet (and will be away from my AP2 MS for roughly another week still), but am very eager to install 8.1 and try out the new features. Don't want to lose teslafi logging though!

 

[Jdeck]

So you've already made some changes and it is "safe" to update to 8.1 without risking losing (significant) data?

I haven't got the update yet (and will be away from my AP2 MS for roughly another week still), but am very eager to install 8.1 and try out the new features. Don't want to lose teslafi logging though!

Yes, it's safe to upgrade. Everything is still being logged as before it's just a matter of interpreting the data in new ways. 99% of things are displaying properly on 8.1. Even if things don't appear to be working right now I can recalculate to display them properly later.

The biggest unknown right now is the sleep modes. The TeslaFi sleep mode really relied on the detailed 0.x accuracy of the battery_current data to know when to allow the car to sleep. If I try to use the power data it's accuracy is 0 or 1. The power only really reads anything other than 0 when the heating/cooling is on or a drive/charge is occurring. It's kind of a shame since I spent so much time on sleep modes based on the battery_current data point. In fact, sleeping and reducing vampire loss is the reason I started my own data logger. HOPEFULLY this is just an oversight and the data point will reappear. However, I'm starting to think that since the Amps were removed from the cars display during supercharging recently that this may have been intentional though.

 

[qadaemon]

Yes, it's safe to upgrade. Everything is still being logged as before it's just a matter of interpreting the data in new ways. 99% of things are displaying properly on 8.1. Even if things don't appear to be working right now I can recalculate to display them properly later.

The biggest unknown right now is the sleep modes. The TeslaFi sleep mode really relied on the detailed 0.x accuracy of the battery_current data to know when to allow the car to sleep. If I try to use the power data it's accuracy is 0 or 1. The power only really reads anything other than 0 when the heating/cooling is on or a drive/charge is occurring. It's kind of a shame since I spent so much time on sleep modes based on the battery_current data point. In fact, sleeping and reducing vampire loss is the reason I started my own data logger. HOPEFULLY this is just an oversight and the data point will reappear. However, I'm starting to think that since the Amps were removed from the cars display during supercharging recently that this may have been intentional though.

Thanks for all your work. It's quite the bang for the buck with as dedicated you are to the usefulness of the site & as quick as you are to investigate issues.

 

[rfmurphy81]

Thanks for the updates, James. Just so I'm understanding correctly, it's safe to upgrade to 8.1 but it's likely that these vehicles won't sleep as often/much as before (under the same conditions). Is that accurate?

 

[Jdeck]

Thanks for the updates, James. Just so I'm understanding correctly, it's safe to upgrade to 8.1 but it's likely that these vehicles won't sleep as often/much as before (under the same conditions). Is that accurate?

I wanted to watch what happened since more cars are upgrading to 8.1. Unfortunately they are not sleeping at all. I'll have to try using the power field and see how it goes.

 

[brkaus]

Mine slept last night. Gained 192.44 while sleeping (got confused and thought it started at 0).

Sleep 14 Battery Address Time Started Ended Starting Range Ending Range Range Loss kWh Loss Delete
% 7 Hour 13 Minutes 12:00 AM 7:14 AM 241.98 -198.44 -52.73

 

[Jdeck]

Mine slept last night. Gained 192.44 while sleeping (got confused and thought it started at 0).

Sleep 14 Battery Address Time Started Ended Starting Range Ending Range Range Loss kWh Loss Delete
% 7 Hour 13 Minutes 12:00 AM 7:14 AM 241.98 -198.44 -52.73

Thanks. What is your username or car ID on TeslaFi so I can take a look? You can direct message me if you prefer.

 

[brkaus]

Thanks. What is your username or car ID on TeslaFi so I can take a look? You can direct message me if you prefer.

Car is 1326

I have energy savings enabled.

Always connected off

 

[Jdeck]

Car is 1326

I have energy savings enabled.

Always connected off

Thanks! I fixed the range loss issue and it's showing correctly.

Now I just need to figure out why yours slept and others are not. It slept very well too!