First how this happened. The Nissan Leaf from about 2011 to mid 2015 on the SV and SL models included Telematics. Telematics in thse models let the owner use a web site or smart phone app to query battery status, start or stop charging and turn on/off the climate control as well as get performance statistics.
After years of warnings from AT&T that the 2G cellular network was going to shut down, AT&T did the shutdown in January 2017. This caused a lot of troubles in the M2M and Telematics space or business.
Nissan responded by offering a (discounted?) upgrade to 2011 to mid 2015 owners of the models affected. Cost was 200USD at the time.
The bug causes the +12V battery to drain overnight. Testing on my part seems to put this drain to inoperative car status around 8 to 10 hours depending on battery condition.
That's the background of how this bug titled "Nissan Leaf Battery Drain Problem" came to be.
As an early buyer of this upgrade I had it installed in January 2017 and immediately found my car would not start the very next day. I didn't think much of it at the time so I called the dealer and we figured out the +12V had run down so I put a charger on it and got the car back to the dealer. Over the next 4 months the dealer under warranty and no news from Nissan USA or Japan replaced the module a few times and then the NAV unit. The NAV unit out of warranty is about 4,500USD which would have meant the end of the car since it's so integrated into the car.
-> Finally at about 6 months Nissan USA figured out there was a problem and was talking to Nissan Japan. The bug got a name and dealers finally were made aware. I was case #117. I hate it when I get such a low case number as this is a sign of things to come.
September 24, 2018 and email arrives that Nissan has a fix. That's over 20 months since the problem surfaces.
I can see why it too so long as the host for the TCU (telematics control unit) is the Clarion made NAV unit. This Clarion NAV unit has some Microsoft OS in it but doesn't show any sign it being Windows CE. Just imagine trying to get developers back in the swing of things to gather up the dev kits and more to tackle this bug. I don't know how many of you have worked in this are but some of the battle is convincing everyone it's a real bug. Next up is "who's paying for this?"
I'll have to update if it's fixed later as it's only day one on the new firmware.