From 644b2e185fcc8af3d9c1deb3dc18e505cdb128bf Mon Sep 17 00:00:00 2001 From: Jakob Lichterfeld Date: Wed, 6 Nov 2024 15:47:47 +0100 Subject: [PATCH] docs: move car ID configuration details to the Configuration section in Home Assistant integration documentation --- website/docs/integrations/home_assistant.md | 6 ++---- 1 file changed, 2 insertions(+), 4 deletions(-) diff --git a/website/docs/integrations/home_assistant.md b/website/docs/integrations/home_assistant.md index 089237c25a..c2a7d95949 100644 --- a/website/docs/integrations/home_assistant.md +++ b/website/docs/integrations/home_assistant.md @@ -11,10 +11,6 @@ The ultimate goal of this guide is to consume as much of the TeslaMate polling d If your intention is to only use read-only sensor values, those provided by TeslaMate via MQTT are sufficient, and you do not need to utilise the official Tesla component. If however you would like to be able to write values to the Tesla API (Lock/Unlock Doors or automate Climate), there is a solution which involves configuring an extremely high polling interval for the Tesla component and using automation to populate the values from the TeslaMate MQTT parameters. -### Car ID - -The following configuarations assumes a car ID of 1 (`teslamate/cars/1`). It usually starts at 1, but it can be different if you have multiple cars in TeslaMate for example. - ### Screenshots import useBaseUrl from '@docusaurus/useBaseUrl'; @@ -29,6 +25,8 @@ import useBaseUrl from '@docusaurus/useBaseUrl'; ## Configuration +The following configurations assume a car ID of 1 (`teslamate/cars/1`). It usually starts at 1, but it can be different if you have multiple cars in TeslaMate for example. + ### configuration.yaml Proximity sensors allow us to calculate the proximity of the Tesla `device_tracker` to defined zones. This can be useful for: