This is the weirdest thing my Model X has ever done, posting here for more visibility (and I can't see why it would be X specific).
Our X is on 2019.32.2.1, the 3 on 2019.32.2.2. Starting this week (and not when they both got these firmwares), the X has had two incidents of going into a lock/unlock loop. Literally. Walk-away honk starts going every 10-20 seconds. You can see the padlock flipping on the app.
Note:. There is zero chance of this being a fob issue. Both are in Faraday bags, where they have always been for two years. It also can't be an app issue, as apps don't control S and X's. I even tried putting my (new iPhone) in airplane mode in case that's what it was (as I was thinking for a few minutes, as it started happening Friday night after my new iPhone 11 Pro Max arrived).
The second time it started as soon as the 3 came home and triggered Homelink. The car was in the garage, awake and asleep at various times all day, no issues after the first power down, and was fine.
Originally, a two-finger reboot did nothing, then the first time (when GF was getting pretty upset about the honking at night) (yes, I could disable that.....), I tried a menu power down, and that fixed it. That was Friday night. Last night, she went to an event with a friend and came back, and that started it again.
Last night, I walked out to the garage to greet her, and the X is waking up. So, why is the X waking up? There is nothing to make it do so. It has never done so for two years. This obviously is part of the issue. What is waking up a sleeping X when the 3 opens the garage door and rolls in? Broken Homelink receiver? Sentry mode is always off at home (and still is, I checked). What else would do this?
So, basic thing here is WTF. Is this some weirdness in the 32.x software? Homelink module failing? I'll be calling support Monday, and hope they can see something in the logs, but after the charger fiasco (still not replaced after two visits and discussion with Tesla Home Charging, since they haven't seen the behavior in the flesh), not too optimistic.
Anyone seen this or have any ideas? This is truly strange.
Our X is on 2019.32.2.1, the 3 on 2019.32.2.2. Starting this week (and not when they both got these firmwares), the X has had two incidents of going into a lock/unlock loop. Literally. Walk-away honk starts going every 10-20 seconds. You can see the padlock flipping on the app.
Note:. There is zero chance of this being a fob issue. Both are in Faraday bags, where they have always been for two years. It also can't be an app issue, as apps don't control S and X's. I even tried putting my (new iPhone) in airplane mode in case that's what it was (as I was thinking for a few minutes, as it started happening Friday night after my new iPhone 11 Pro Max arrived).
The second time it started as soon as the 3 came home and triggered Homelink. The car was in the garage, awake and asleep at various times all day, no issues after the first power down, and was fine.
Originally, a two-finger reboot did nothing, then the first time (when GF was getting pretty upset about the honking at night) (yes, I could disable that.....), I tried a menu power down, and that fixed it. That was Friday night. Last night, she went to an event with a friend and came back, and that started it again.
Last night, I walked out to the garage to greet her, and the X is waking up. So, why is the X waking up? There is nothing to make it do so. It has never done so for two years. This obviously is part of the issue. What is waking up a sleeping X when the 3 opens the garage door and rolls in? Broken Homelink receiver? Sentry mode is always off at home (and still is, I checked). What else would do this?
So, basic thing here is WTF. Is this some weirdness in the 32.x software? Homelink module failing? I'll be calling support Monday, and hope they can see something in the logs, but after the charger fiasco (still not replaced after two visits and discussion with Tesla Home Charging, since they haven't seen the behavior in the flesh), not too optimistic.
Anyone seen this or have any ideas? This is truly strange.