You can install our site as a web app on your iOS device by utilizing the Add to Home Screen feature in Safari. Please see this thread for more details on this.
Note: This feature may not be available in some browsers.
Is this fixed in .36?
So... Anyone with .36 still seeing this behavior?
Alas, I still had it happen last night with .36 -- it didn't happen the first night, but I've had it work something like one night in three.
Ditto. 2.5.36 does not resolve this one. The car ends up charging normally every time this happens, and I don't get the interrupted message every time either. It occurred to me today when thinking about the messaging architecture that the notifications don't come from the car directly. The way the notifications work is the car sends events to the mothership servers, which interpret those events and send the notification to the corresponding app. A recent server update could have introduced a "bug" in the messaging chain.
Can someone actually observe the car when this event is triggered? I mean is the master charger really cycling on/off in rapid succession or is it just a reporting issue?
Can someone actually observe the car when this event is triggered? I mean is the master charger really cycling on/off in rapid succession or is it just a reporting issue?
The one time it happened to me the chargeport ring had turned red and the car was silent; I forget what the charge screen on the center console said I think it was just 'charging interrupted', in any case it wasn't cycling.
That's exactly what happened to me when my UMC started going bad (was replaced by Tesla) and when my J1772 cables at work started going bad (replaced by ClipperCreek).
<snip>
Are you guys sure it's not a bad connectivity issue? Maybe more current firmware is more sensitive to a bad connection? Just wondering because I don't think the problem is universal.