Recent content by Jdeck

This is most likely the case. The develop is messing up multiple parts of the version checking. I’m traveling this weekend but will try to get it resolved tonight.

This is on my shortlist of things to do as well as revamping the notifications and scheduling into one page. I've added a date range to the charge page and I started implementing it to the calendar page but it's much more in work including the drive info and charging info so it's taking a bit...

I need to dig into this a further. As of now it appears the model 3 seems to report the car as 'offline' via the API during most idling sessions as opposed to just 'online' and the rest of the good data from the model S. I originally put this notification option in place for cars to alert them...

The temperature page uses the average temperature of the entire drive from the first drive (or reverse) datapoint to the last park datapoint. I just tested tested it by identifying the one drive I have with an average temperature below 0 F but started at 15 F in my garage. It shows in the -10...

Hi everyone. There does to be something going on with the offline status of the model 3 through the API. As far as I could tell most of the cars do appear 'offline' from the API calls after a little bit of idling. It's hard for me to tell exactly what's going on however since I can't tell...

It was an error on my end. The user also has a P100D on their account which logged a few data points before being switched to log the model 3. Since the model 3 doesn't report trim_badging it wasn't replaced in the firmware database. I cleared it out and it's showing '3' now.

Looks like you're on to something there- http://firmware.teslafi.com/uncorked.php It appears non D models are P1 for non performance and P2 for performance. And D models are P3 for non performance and P1 for performance. At least that's what it looks like to me.

I’ve seen a few cars having trouble sleeping in the days leading up to a software update. That could be the issue but it doesn’t look like this new release is going out to many cars. Did you get updated to a new version at the sc?

That’s actually the response from Tesla’s servers. It means your password is incorrect or Tesla’s servers are acting up which happens every once in a while. Make sure you’re entering the correct Tesla credentials and/or try again in a little bit. You can open a ticket in the help desk or email...

It means I forgot to put my error handler back in place after the server move. I’ll work on that.

Everything ok now?

Is it working correctly now? I’m in the middle of getting prepared to move things over to AWS and moved the nameservers over to Cloudflare today. The Cloudflare move is supposed to be seamless but apparently not.

I'm hoping the 2017.28 c528869 is actually supposed to be 17.28.27. Only time will tell, but a few cars have been updated to 17.28.27 and then within a few minutes they change to 2017.28 c528869. Hopefully it goes back to the i.i.i format just to keep things simple.

I think my detection code got out of sync between some of the pages. It looks like it's identifying it correctly at the bottom of the settings page but not on the actual firmware page. I'll fix it tonight. Thanks.

Hi. You're correct. You can dial that factor down based on what you see in the car trip readout. I do need to go back and revisit this. I'm sure I have plenty of data now to set a default factor for each model.