Great article! That’s a pretty tidy panel too!
EVSEs matter very little in detection. We’re really looking at the signature of the circuitry that’s in the car itself. That may change as EVSEs become more advanced, but it remains the case for now. Hopefully Sense picks up on your m3 soon.
And nice to see another semi-local Sense user. We’re just over in Boston and try to get users in the office for pizza and discussion. We’ll have to get you in here at some point.
Thank you, RyanAtSense! Your reply about EVSEs sounds promising, and makes sense.
By the way, I drive to the Boston area pretty regularly, and stopping by the office someday sure sounds good to me. I can easily be contacted here, and if you’re ever passing through Connecticut, feel free to reach out!
This morning, my iPhone greeted me with a push notification that my Tesla had been found, this is good!
FYI, slow charging missed:
! I did have an issue with my first very slow charging, likely just because of cold overnight temps last night, let me know if you want more details, happy to help. I can also share a detailed 27min. video of the very slow ramp-up seen in both the Tesla and Sense apps, with some screenshots below my same article (I’m unable to direct link here).
Good news!
Subsequent warmer-battery charges worked just fine, Sense picked it right up and showed realtime stats. Thank you!
For the charging session that wasn’t picked up by Sense, here’s my TeslaFi charging log.
Footnote added hours later:
Taking another look at my first successfully monitored Model 3 Long Range charging session, I see that TeslaFi shows 22 min to add 3.02 kWh, but the Sense app only shows 9 min to add 1.9 kWh.
Curious how this is going for the other M3 owners. My full charge cycle is regularly not being captured correctly (less than half the time). Sometimes the M3 doesn’t get identified at all and other times Sense throws it back into the other category part way through a charge cycle.
I’m charging with the NEMA plug. Any better results with the wall charger?
I’m still using my Wall Connector with 14-50 Plug (40 amp) and you’re right, sometimes it misses a charging session, such as when I had one going for about 3 minutes today. Admittedly, that’s kind of short, but I don’t believe it would have found it, usually it picks a session up and identifies it in well under a minute.
Just a heads up, we’ll be pushing out some improvements to model 3 detection models. They should help net detections for those still missing their model 3, as well as improve the reliability of detections for those whose model 3 has been found.
This doesn’t mean that every single model 3 in the field will now be detected, but it should be a significant improvement!
Has the push happened? Seems like my detection rate has dropped to nearly zero in the last few weeks.
Models roll out to different people at different times, so it might be a few days to a week before you see the benefits of the new models.
Question for the M3 owners here:
Have you been updated to the latest Tesla software update (build 2019.5.4)? We could use your help. Based on the data we’re seeing from current Tesla M3s in the field, something changed in Tesla signatures recently. We’re thinking it might be related to this firmware update, but need to dig a bit deeper.
If you’re on this firmware, could you let us know and give us permission to dig into your Tesla data? A simple “Yes, I’m on 2019.5.4 and you have permission to look at my data” will suffice.
Ryan if it helps I have a Tesla Model 3 on 2019.5.4 and a Model S on 2018.50.6, Neither has been detected yet, after many months. You have my permission to look at any of my data you want.
Steve
Yes, I’m on 2019.5.4 and you have my permission to look at my data.
Another thought I had on the loss of identification of the M3 is the weather. It’s been so cold, there is a restriction based on Temp of the battery pack via the BMS. If I’m right, you should be able to see a difference if you add GEO into your model for the last few weeks. I’m betting Florida doesn’t have the same problem.
@RyanAtSense - I am now on 2019.5.15 from 2018.50.6. My M3 has not been detected yet but you may see a clear difference between Friday evening’s charge and Monday evening’s charge.
Adam
I noticed that once I went from 2018.50.6 to 2019.5.15 on Tue evening Mar 12 2019, all Tesla Model 3 Long Range charging detection seems to have vanished. I was never offered 2019.5.4.
I also noticed that my Model 3 now charges for 2 minutes every 55 minutes for no apparent reason (other than new software), going from 90% to 90%, for about 3 minutes. But one charge was legit, pictured (screenshot taken before token issue fixed). the only workaround for now is to move the full charge limit slider from 90% to 80% after charging is complete, to keep it from cycling needlessly like this, 24x7.
Happy to help, here’s my permission:
Yes, I’m on 2019.5.15 and you have permission to look at my data
Noted. I sent along your info to the DS team.
Great, thank you!
Ryan,
I’ve had sense meter for over 14 months and had model 3 for about 9 months now,I am using 48amp wall connector to charge, but nightly I only (top off) charge about 70 miles. If I wait a few days and perform a larger capacity charge, will this help detection. I am running 2019.x firmware. Knowing what part of my other is actually my a Tesla is still my greatest need from my sense meter.
First, welcome to the community!
Larger charges definitely help, rather than short top offs. But do keep in mind this known issue: FIX ISSUED: Tesla Model 3 detection accuracy issues - #6 by RyanAtSense
