Unfortunately the Tesla API does not return consumption values for a trip. In order to still be able to display values TeslaMate estimates the consumption on the basis of the recorded (charging) data. It takes at least two charging sessions before the first estimate can be displayed. Each charging session will slightly improve the accuracy of the estimate, which is applied retroactively to all data.
At the moment geo-fences are a way to create custom locations like
🏡 Home or
🛠️ Work That may be particularly useful if the addresses (which are provided by OpenStreetMap) in your region are inaccurate or if you street-park at locations where the exact address may vary.
Cars with Media Control Unit version 1 (MCU1) require certain settings to be able to fall asleep. Model S and Model X cars built before 3/2018 have the MCU1 unit, this can also be checked from the Software -> Additional vehicle information. If the 'Infotainment processor' is 'NVIDIA Tegra', the car is equipped with MCU1.
The settings needed to enable the sleep mode with MCU1 are:
- 'Display' -> 'Energy saving' -> ON
- 'Display' -> 'Always connected' -> unchecked
- 'Safety & security' -> 'Cabin overheat protection' -> OFF
With these settings the MCU1 cars should fall asleep within some 15 minutes of inactivity. This is what you should see in the log when streaming mode is enabled in TeslaMate
[info] Suspending loggingafter 3 minutes of inactivity (doors locked)
[info] Fetching vehicle state ...about 21 minutes later. The car should have fallen asleep during this period
In this example the driver's door was opened and closed:
teslamate_1 | 2021-03-16 11:41:19.336 car_id=1 [info] Start / :onlineteslamate_1 | 2021-03-16 11:41:19.603 car_id=1 [info] Connecting ...teslamate_1 | 2021-03-16 11:44:41.380 car_id=1 [info] Suspending loggingteslamate_1 | 2021-03-16 12:03:27.356 car_id=1 [info] Fetching vehicle state ...teslamate_1 | 2021-03-16 12:03:28.123 car_id=1 [info] Start / :asleepteslamate_1 | 2021-03-16 12:03:28.139 car_id=1 [info] Disconnecting ...
Note! If you are using some other data logger like TeslaFi at the same time, the sleep attempts probably fail as the other data logger is keeping the car awake. Especially calling the Vehicle Data API will reset the car's inactivity timer.
The problem with the polling mode is that the car does not fall asleep before it have been inactive for some 15 minutes. TeslaMate will suspend all polling after the car has been idle for 3 minutes (the 'Idle Time Before Trying to Sleep' setting), and will resume polling 15 minutes later (the 'Time to Try Sleeping' setting). Any activity during this 15 minutes can't be detected, as calling the Vehicle Data API would reset the car's inactivity timer, preventing the car from falling asleep.
Calling the Vehicle API does not reset the inactivity timer, but it only tells if the car is either online (driving, charging, idle, about to fall asleep) or asleep. It can't tell if an idle car started driving during the 'Time to Try Sleeping' period.