To be honest, this is the first time I've seen someone say that it works reliably for them on a consistent basis so that is interesting. I'm not sure if it makes me feel better or worse about the situation though. Because BMW's system is so "mysterious black box"-y, there's really no way to know why something failed except for end-user troubleshooting (well, if I set my AT&T phone on the windshield, it still has service, so the car should too...) and in my opinion, that alone is a failure on BMW's part. For instance, I don't have an AT&T phone, so anytime it fails in an area I think it should have service I'm going to blame BMW, not AT&T. And that's the piece I'm not sure BMW gets right now: connected drive (and I guess i3/electric owners in general) are a very small part of their business, but given the direction things are going, it's going to be a much bigger amount, so why not spend the money now to do it right and have an advantage over most your competitors? And as a side-effect, make a bunch of existing i3 owners happy.eNate wrote: But if you're aware it's reliable for me and many others, maybe that'll shape your (and others) expectations and you'll hold the company accountable to address your specific situation.
Anyway, rant over. The funny thing is, I actually revisited this thread to say that I'm on a roll with 10 consecutive remote commands and have to go all the way back to Dec 12th for a failure. In fact, I only have the one failure in the history the app keeps (back to Nov 26th), so I'm at 21/22 (95%) success rate right now. I could live with that, so I'm kindof hoping BMW has made meaningful improvements in the backend of their system.