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.
Neh, the one is just slower - each had a short blink followed by long blink, so still an "A"I think it's right headlight "M" and then left headlight "A" but still creepy.
It happened 3 minutes before midnight PDT for me.
Car locked. Key away. No updates (it did update the day before). No meaningful internet traffic (see below traffic graph for just that Model S - lights blinked just before midnight).Any updates happen around when you noticed the blinking? Maybe this is some sort of easter egg where the car gets woken up in the middle of the night (by a software update downloading, or another command from the mothership), and it gets "sleepy eyes" or something like that.
Maybe Christmas Show code intermingled with sleep code. Just wait until the racing game code intermingles with auto-pilot!our MS's are jealous of the MX Xmas show ? Want to join in on that action ?
I have the same issue. Talked to Tesla today and they haven’t heard anything. The couldn’t see anything in the logs.I happen to be walking in the garage last night and I noticed that our newest Tesla (2018 MS) was blinking its headlights. Noone was controlling via the app (late night) so I was a little worried the car was being hacked? So went in and checked out security camera footage, and apparently it is blinking in Morse Code, first the right headlight "A" and then left headlight "A". Any hacker groups out there with initials AA? Or is this a known regression of Tesla software (back in early days ~2012/2013 Teslas used to be "possessed" when parked, especially while applying updates (and no, the blinking MS was not applying updates at the time). Here is a video of this. Any ideas?
Point them to this thread, 2 videos on page 1 - one on each continent so it's not limited to geographical area.I have the same issue. Talked to Tesla today and they haven’t heard anything. The couldn’t see anything in the logs.
Has anyone seen this happen before yesterday? I wonder if this is related to a firmware version, or some sleeper code which activated itself on a specific date.