-
Want to remove ads? Register an account and login to see fewer ads, and become a Supporting Member to remove almost all ads.
Firmware 5.0
- Thread starter riceuguy
- Start date
Don't think so. Have patience, soon we will all be exploring the new bugs, failing to open doors, random UI glitches, etc.
Wow. No one told him if he did not sleep in the car the first night that Ranger Service was going to take the car back because he was a 'bad' owner!
Sleep mode: I understand it does not go 'on' immediately when you leave the car. Also, if the car starts up in 10 seconds or less is that really that much of an inconvience to save
75% of the previous vampire loss?
Eggplant
Member
I wonder how the sleep mode will affect API access? I'm currently collecting stats on my car via the API. Will this break my polling, or will polling the car keep it awake?
dirkhh
Middle-aged Member
Interesting question. I was wondering the same.
Just out of curiosity... Which data are you collecting? I'm adding to the teslams project to be able to track more things, but am wondering what people really want.
So would you mind sharing which data you track and at what interval?
Wasted energy is a valid concern. If you are plugged in, you will still have an adequate enough charge for your needs, unless you need a range charge and need to push it.
My concern was for the times when I'm NOT plugged-in. If I'm away from home and don't have access to power, I would want to save as much juice as I can. When I'm local, I wouldn't mind losing some range here and there in exchange for a rapid wake up.
Ideally, there should be a setting for "Allow rapid wake-up" or "Prevent sleep mode". There could be the standard disclaimer: "If you select this option, you may lose range while parked a more rapid rate..."
OTOH, if there cannot be a setting, I'd take this new feature over the old.
(1) I'm curious if the wake up command actually wakes it up from sleep (which echoes what a Tesla rep said at one point, before we knew about 5.0). If it does, that's great for telemetry logging but bad for sleep being effective. If it doesn't, that's great for being able to leave telemetry logging on full-time without it "ruining" sleep mode power savings. So I'm curious to see which route they took.
(2) My logging does the following: (a) query all the non-streaming data, (b) being streaming, (c) when streaming rejects the token as expired return to (a). This means I'm not polling the non-streaming data often (meaning I don't see the state transitions between door opened and door closed) but I do get "periodic" updates which makes it easy to see stuff like "car_version changed" at semi-regular intervals.
dirkhh
Middle-aged Member
Interesting approach. I'm currently polling charge state every minute... Just to have a better data set for energy consumption and to be able to track voltage / currents.
But I like the idea of logging /everything/ else whenever the token expires.
I'll add that to the teslams streaming client in the next few days...
DrComputer
TeslaClubLA President
So has anyone who is not in the Early Adopter firmware program yet to receive the 5.0 version? (except for people taking delivery of new cars)
Vger
Active Member
FWIW, I was at the Vancouver, BC service center yesterday, and they assured me that the 5.0 OTA updates would start "soon."
Make the timeout configurable, along with a "sleep now one time" that puts the car to bed as soon as the cars locks for parking at the airport, etc.
dflye
S Sig Perf 414, VIN 814
Yeah, is that a regular person's definition of "soon", or the Tesla definition of "soon"? :tongue:
Good to hear. But I'm surprised people dont just do a reboot after an update. Actually surprised people dont think it's necessary.
dflye
S Sig Perf 414, VIN 814
Doesn't the update process implicitly do a reboot of both the touchscreen and console display?
Similar threads
