I have had this issue for months. It occurs roughly 2-3 times per week. My car, which is scheduled to charge at midnight, would interrupt and so I would wake to find I had a continuous stream of notifications on my phone and a partially charged car. Like others posting here, unplugging and plugging in again fixed the problem - for a while. It even happens when the charging is reduced to 30A.
I took my car in and they replaced the charging cable (under warranty). It made no difference. So when I called to tell them, I was told to bring the charging cable in for my next visit to the Tesla service place here near Chicago. I did this during my annual "physical" that took place 3 weeks ago. When my car was returned to me they said that there is nothing on the car or in the charging cable that is causing the problem. I was told that a couple of other customers in the area had similar problems and had needed to get an electrician in to check the house wiring or contact the electric company (CommonWealth Edison).
So I was prepared to do this (reluctantly). BUT - the problem has been completely cured. I have not had a single interruption since. Not one.
So I am very happy. However, it raises a big question. How was the problem cured when Tesla service did not think they had found a problem or a cure. Here is some of my speculation:
- Most of the work done in the annual service (wheel rotation, alignment, etc) is unrelated
- Something was done during the diagnosis that fixed the problem. possible but somewhat unlikely as they didn't find a problem.
- Firmware or software version upgrade. Possible but then other people should have similar results.
- Motor replacement. Because of a hum that was growing louder I had an under-warranty replacement of my motor. While I do not believe that the motor is connected during charging, maybe there is something that gets replaced as part of a motor replacement that has an effect. Possible but I have no evidence.
I mentioned this to the service department (dropped my car off to have a TPMS issue fixed today). If I get an update, I will post details here. Unfortunately when I dropped it off I got the one person in that department that tends to give me glib answers rather than fact based insights. Her view was that it must be something ComEd did. Clearly, in this case the coincidence is too great. I did ask her to pass on to the service technicians what has happened as whatever solved my issue may impact other people too.