Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

build: update website dependencies, doc: fix markdown linter warnings in faq #4046

Merged
merged 12 commits into from
Jul 6, 2024
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension


Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
1 change: 1 addition & 0 deletions .node-version
Original file line number Diff line number Diff line change
@@ -0,0 +1 @@
20
3 changes: 3 additions & 0 deletions CHANGELOG.md
Original file line number Diff line number Diff line change
Expand Up @@ -22,6 +22,8 @@

- build(deps): bump crate-ci/typos from 1.21.0 to 1.22.9 (#4021)
- build(deps): bump express from 4.18.2 to 4.19.2 in /website (#3790)
- chore: update @docusaurus/core and @docusaurus/preset-classic dependencies to v3.4.0 and react and react-dom to 18.3.1 (#4046 - @JakobLichterfeld)
- build: specify node.js version for Netlify in base dir as latest lts major version (#4046 - @JakobLichterfeld)

#### Dashboards

Expand All @@ -48,6 +50,7 @@
- doc: update the Contributor's Guide with the latest requirements (#4017 - @JakobLichterfeld)
- doc: Documentation for new endpoint changes (#3978 - @jlestel)
- doc: Add Grafana VS Code extension documentation (#4025 - @JakobLichterfeld)
- doc: fix markdown linter warnings in faq (#4046 - @JakobLichterfeld)
- doc: fix typo in MQTT location JSON format (#4047 - @JakobLichterfeld)

## [1.29.2]
Expand Down
8 changes: 5 additions & 3 deletions website/docs/faq.md
Original file line number Diff line number Diff line change
Expand Up @@ -12,7 +12,8 @@ There are multiple apps available to securely generate access tokens yourself, f

## Why are no consumption values displayed in Grafana?

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. Charging sessions have to be longer than 10 minutes and less than 95% state-of-charge (SoC). Each future charging session will slightly improve the accuracy of the estimate, which is applied retroactively to all data.
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. Charging sessions have to be longer than 10 minutes and less than 95% state-of-charge (SoC). Each future charging session will slightly improve the accuracy of the estimate, which is applied retroactively to all data.

## Why "null" is displayed above the panels in Grafana?

Expand Down Expand Up @@ -41,7 +42,7 @@ With these settings the MCU1 cars should fall asleep within some 15 minutes of i

In this example the driver's door was opened and closed:

```
```bash
teslamate_1 | 2021-03-16 11:41:19.336 car_id=1 [info] Start / :online
teslamate_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 logging
Expand All @@ -56,7 +57,8 @@ teslamate_1 | 2021-03-16 12:03:28.139 car_id=1 [info] Disconnecting ...

## Why am I missing data when not using the Streaming API?

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](https://www.teslaapi.io/vehicles/state-and-settings#vehicle-data) would reset the car's inactivity timer, preventing the car from falling asleep.
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](https://www.teslaapi.io/vehicles/state-and-settings#vehicle-data) would reset the car's inactivity timer, preventing the car from falling asleep.

Calling the [Vehicle API](https://www.teslaapi.io/vehicles/list#vehicle) 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.

Expand Down
Loading
Loading