UPDATE for Nissan LEAF Owners: CARWINGS Restored
Code and configuration updates have sucessfully returned LEAF CARWINGS service connectivity to normal and we have seen no issue recurrence over the last 14 hours. Customers should be able to use all services normally. Our technical teams will continue to closely monitor systems and service performance to ensure you are able to fully enjoy all your CARWINGS services, and we will continue to troubleshoot and work to improve our service performance and stability. Thank you all for your patience and feedback. We apologize for an inconvenience this may have caused you.
- Nissan Social + Nissan Vehicle Connected Services
http://www.facebook.com/nissanleaf/post ... 0344747796
-- UPDATE from Nissan - 12/20/12 --
We'd like to take this opportunity to share the status of the CARWINGS connectivity issue we shared with our LEAF owners yesterday afternoon. A cross-company team has worked throughout the night and has been able to identify a problem which has contributed to latency and error conditions our owners are experiencing. Tuning changes and a code correction have reduced but not eliminated failures. Our team continues to investigate and we will provide updates via this thread as they develop. Thank you for your all your comments and feedback!
– Nissan Social + Nissan Vehicle Connected Services
http://www.facebook.com/nissanleaf/post ... omments=48
-- UPDATE - 12/20/12 --
Not that it'll matter tomorrow anyway but Nissan seems to have put some people on the job and it's a little more usable now, but still about 50% failure rate for me. Haven't seen much buzz in the thread this morning so maybe it's a bit more reliable, either that or everyone's already posted in the thread. Not yet had a single confirmation of "it's been working for me this whole time", so it's a fair bet that this is affecting all LEAF owners. Also still no word from Nissan that the issue's been fixed. We'll see...
-- UPDATE and THREAD SUMMARY - 12/19/12 --
Nissan has finally acknowledged a problem with CARWINGS (I guess that's the proper stylizing, so I'll use that). https://twitter.com/NissanLEAF/status/2 ... 3863950336
-- UPDATE and THREAD SUMMARY - 12/18/12 --
This is definitely a system-wide issue, confirmed to be "still spotty" by a Nissan social rep, but as of this time, still not resolved.
Summary of past 7 pages of replies: "Yep, it's messed up for me too."
- not related to geography
- not resolved by resetting the car's TCU (telemetrics communications(?) unit)
- not a problem with the app, phone, or the browser
- kind of a huge pain in the rear
Please continue to post your findings as Nissan is said to be monitoring this thread for information on the problem. Personally, I think it's a server-on-fire problem: viewtopic.php?f=31&t=10936&start=10#p250535 - and another post on the problem: viewtopic.php?f=31&t=10936&start=70#p251402
-- ORIGINAL POST --
Lately, seems like ever since I moved (to another area in the dead center of the city), I can't get Carwings to work for a crap. Whenever I request an update while at home, it's almost a 25% chance it'll actually go through, and a 75% chance I'm going to sit around for 5 minutes waiting for the request to fail and have to try it again.* That defeats the purpose. This morning I spent 10 minutes trying to remote-activate climate control, and I gave up since I was running late trying to get the function to work.
Who could I even contact to report this issue? I don't think Nissan could bend AT&T's arm to come out here and fix the defective tower that's causing this, if that's the case...
Anyone else have the same experience? I'm guessing it's just me, since Google sure doesn't know what "carwings request failed" means...
* - side note. Let's assume Carwings operates on an SMS-based system, where Carwings sends a text message to the car's AT&T modem, which is how the telemetrics operates - receives requests via SMS, replies via web or SMS reply. So why is this a difficult thing to accomplish? If it fails to respond in a certain number of seconds, try again - and a sequence number would rule out duplicate commands if a "burst" of repeated commands is received. Not that effing hard. As for replying, that could be made quicker by always responding via web, since SMS is sent out on tower control signals, establishing a connection to reply would be quicker than sending another SMS on the next signal and waiting for the Carwings server to get the SMS. Much room to improve, for sure...