Does your glovebox open in Valet mode?

  • SUPPORT THE SITE AND ENJOY A PREMIUM EXPERIENCE!
    Welcome to Tesla Owners Online, four years young! For a low subscription fee, you will receive access to an ad-free version of TOO. We now offer yearly memberships! You can subscribe via this direct link:
    https://teslaownersonline.com/account/upgrades

    SUBSCRIBE TO OUR YOUTUBE CHANNEL!
    Did you know we have a YouTube channel that's all about Tesla? Lots of Tesla information, fun, vlogs, product reviews, and a weekly Tesla Owners Online Podcast as well!

Brokedoc

Kick-Gas Contributor
Joined
May 28, 2017
Messages
1,715
Location
New York
Tesla Owner
Model X
Country
Country
#2
DEFINITELY it should not. Report the bug and get it fixed.

Valet mode should disable:
Frunk
Glovebox
Rapid acceleration (Model X is limited to about 120 kW)
Autopilot
NAV features
Homelink
And hide your home/work address presets as well as all of your phone synched data
 
Last edited:

SoFlaModel3

T≡SLATUNITY
Moderator
TOO Supporting Member
Joined
Apr 15, 2017
Messages
10,052
Location
Florida
Tesla Owner
Model 3
Country
Country
#3
DEFINITELY it should not. Report the bug and get it fixed.

Valet mode should disable:
Frunk
Glovebox
Rapid acceleration (Model X is limited to about 120 kW)
Autopilot
NAV features
Homelink
And hide your home/work address presets as well as all of your phone synched data
Checklist time:

Valet mode should disable:
Frunk - PASS
Glovebox - FAIL
Rapid acceleration (Model X is limited to about 120 kW) - PASS
Autopilot - PASS (but access to autopilot setup menu was there)
NAV features - PASS
Homelink - PASS
And hide your home/work address presets as well as all of your phone synched data - COULDN’T TEST (I have an iOS 11 bug)
 

Love

Tesla Quad Cities
TOO Supporting Member
Joined
Sep 12, 2017
Messages
2,145
Location
Iowa
Tesla Owner
Model 3
Country
Country
#5
So, I can’t even report the bug through the car because apparently “valet mode” disables the voice command feature! I’ll call their 877 number and report it, though it’s probably a known issue...never know.
Could this have been fixed in an update? I’m on 2017.50.13.

Edit: called and relayed the bug to Tesla, the guy I spoke to didn’t know if it was specific to my software. Great catch @SoFlaModel3!
 
Last edited: