From fdbd075e0c209a59d14332f268759b46bbb88679 Mon Sep 17 00:00:00 2001 From: Nico Date: Thu, 24 Apr 2025 10:59:38 +0000 Subject: [PATCH 01/20] Add autoskope integration documentation --- source/_integrations/autoskope.markdown | 189 ++++++++++++++++++++++++ 1 file changed, 189 insertions(+) create mode 100644 source/_integrations/autoskope.markdown diff --git a/source/_integrations/autoskope.markdown b/source/_integrations/autoskope.markdown new file mode 100644 index 000000000000..ad934a464913 --- /dev/null +++ b/source/_integrations/autoskope.markdown @@ -0,0 +1,189 @@ +--- +title: "Autoskope" +description: "Instructions on how to integrate Autoskope devices into Home Assistant." +ha_category: + - Device tracker +ha_release: 2025.5 +ha_iot_class: Cloud Polling +ha_domain: autoskope +ha_platforms: + - device_tracker +ha_config_flow: true +ha_integration_type: integration +ha_codeowners: + - '@mcisk' +ha_quality_scale: platinum +--- + +The **Autoskope** {% term integration %} allows you to integrate your [Autoskope](https://autoskope.de) vehicle tracking devices with Home Assistant. Autoskope provides GPS tracking devices and cloud services for vehicles and other assets, offering features like location tracking, voltage monitoring, and various alerts. + +This integration connects to the Autoskope cloud service to retrieve the current status and location of your registered vehicles. + +{% include integrations/config_flow.md %} + +## Installation + +This integration can be set up via the Home Assistant user interface. + +1. Go to **Settings** > **Devices & Services**. +2. Click **Add Integration**. +3. Search for "Autoskope" and select it. +4. Follow the on-screen instructions to enter your Autoskope username, password, and the API host URL. + +## Configuration + +Configuration is handled entirely through the UI flow during setup. You will need to provide: + +* **Username:** Your Autoskope account username. +* **Password:** Your Autoskope account password. +* **Host:** URL of the Autoskope API server (e.g., `https://portal.autoskope.de`). + +These are the same credentials used for the Autoskope web portal and mobile app. + +## Entities + +This integration provides the following entities: + +### Device Tracker + +A `device_tracker` entity is created for each vehicle registered in your Autoskope account. This entity tracks the location of the vehicle. + +The state of the tracker will be the zone it is currently in (`home`, `not_home`, or a custom zone name) or `unavailable` if no position data is available. + +The following attributes are provided: + +| Attribute | Description | Example Value | +| ------------------ | --------------------------------------------------------------------------- | ------------------------------ | +| `source_type` | Source of the location data. | `gps` | +| `latitude` | Latitude coordinate of the vehicle. | `54.12345` | +| `longitude` | Longitude coordinate of the vehicle. | `12.54321` | +| `gps_accuracy` | Estimated accuracy of the GPS signal in meters. | `3.0` | +| `battery_voltage` | Voltage of the device's internal battery (if available). | `4.1` | +| `external_voltage` | Voltage of the vehicle's main battery connected to the device (if available). | `12.5` | +| `gps_quality` | Raw GPS quality indicator from the API (used to calculate `gps_accuracy`). | `1.5` | +| `imei` | Unique IMEI number of the tracking device. | `123456789012345` | +| `model` | Model name/type of the tracking device. | `Autoskope V3` | +| `speed` | Current speed of the vehicle in the unit system configured in Home Assistant. | `55.0` | +| `park_mode` | Boolean indicating if the device reports being in park mode. | `true` / `false` | +| `last_update` | Timestamp of the last position update received from the API (UTC). | `2025-01-01T10:05:00Z` | +| `activity` | Current activity state derived from `park_mode` and `speed`. | `parked` / `moving` | + +Note: Sensor entities for battery voltages and other values are planned for a future update. + +## Data Update + +The integration polls the Autoskope API every 60 seconds to retrieve the latest status and location data for all registered vehicles associated with the account. + +## Troubleshooting + +* **Authentication Errors:** If you change your Autoskope password, the integration will fail to connect. Home Assistant should prompt you to re-authenticate. Go to **Settings** > **Devices & Services**, find the Autoskope integration card, and click **Reconfigure** to enter your new password. +* **Connection Failed during Setup:** Ensure you have entered the correct **Host** URL for the Autoskope API. The default value (`https://portal.autoskope.de`) should be correct for most users. Also, verify your username and password. Check if your Home Assistant instance can reach the Autoskope host URL (e.g., firewall rules, DNS issues). +* **Vehicles Not Appearing:** If a vehicle you expect to see is missing in Home Assistant, log in to the Autoskope web portal or app and confirm that the vehicle is correctly registered, active, and associated with the account you used to set up the integration. +* **Entities Become Unavailable:** If entities become unavailable, check the Home Assistant logs (**Settings** > **System** > **Logs**) for errors related to the Autoskope integration. This could indicate temporary connectivity issues with the Autoskope API or problems with your account credentials. + +## Known Limitations + +* **Update Delay:** Due to the 60-second polling interval for the cloud API, there will be a delay of up to 60 seconds (plus processing time) before status changes (like location or activity) are reflected in Home Assistant. +* **Limited Sensor Data:** Currently, only the primary external voltage and internal battery voltage are exposed as attributes. Support for additional sensor data available on newer devices (like Autoskope V3's extra battery inputs or digital inputs) is planned for a future update. + +## Supported Devices + +This integration should work with all past, present, and future hardware devices offered by Autoskope. + +## Automation Examples + +Here are a few examples of how you can use the Autoskope device tracker entities in your automations. Replace `device_tracker.my_vehicle_name` with the actual entity ID of your vehicle's tracker. + +**Notify when the vehicle arrives home:** + +```yaml +# filepath: automations.yaml +alias: Notify when car arrives home +trigger: + - platform: state + entity_id: device_tracker.my_vehicle_name + to: "home" +action: + - service: notify.mobile_app_your_phone # Replace with your notification service + data: + message: "The car has arrived home." +mode: single +``` + +**Turn on porch light on arrival after sunset:** + +```yaml +# filepath: automations.yaml +alias: Turn on porch light on arrival after sunset +trigger: + - platform: state + entity_id: device_tracker.my_vehicle_name + to: "home" +condition: + - condition: sun + after: sunset +action: + - service: light.turn_on + target: + entity_id: light.porch_light # Replace with your light entity +mode: single +``` + +**Open garage when arriving near home:** + +```yaml +# filepath: automations.yaml +alias: Open garage when arriving near home +trigger: + - platform: zone + entity_id: device_tracker.my_vehicle_name + zone: zone.near_home # Replace with your zone entity + event: enter +action: + - service: cover.open_cover + target: + entity_id: cover.garage_door # Replace with your garage door entity +mode: single +``` + +**Enable Wallbox when car is home:** + +```yaml +# filepath: automations.yaml +alias: Enable Wallbox when car is home +trigger: + - platform: state + entity_id: device_tracker.my_vehicle_name + to: "home" +action: + - service: switch.turn_on # Or appropriate service for your wallbox + target: + entity_id: switch.wallbox_charging_enable # Replace with your wallbox switch +mode: single +``` + +**Arm garage alarm when car leaves home:** + +```yaml +# filepath: automations.yaml +alias: Arm garage alarm when car leaves home +trigger: + - platform: state + entity_id: device_tracker.my_vehicle_name + from: "home" +action: + - service: alarm_control_panel.alarm_arm_away # Or appropriate arming service + target: + entity_id: alarm_control_panel.garage_alarm # Replace with your alarm entity +mode: single +``` + +## Removal + +To remove the Autoskope integration: + +1. Go to Settings > Devices & Services. +2. Find the Autoskope integration card. +3. Click the three dots (...) menu on the card. +4. Select Delete. +Note: Entities and devices associated with vehicles that are removed from your Autoskope account (e.g., subscription canceled) will be automatically removed from Home Assistant during the next update cycle. From 4578fec7e9ea7755a3f29c35e848496b9d67fa7e Mon Sep 17 00:00:00 2001 From: mcisk Date: Thu, 24 Apr 2025 13:11:36 +0200 Subject: [PATCH 02/20] Update source/_integrations/autoskope.markdown Co-authored-by: coderabbitai[bot] <136622811+coderabbitai[bot]@users.noreply.github.com> --- source/_integrations/autoskope.markdown | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/source/_integrations/autoskope.markdown b/source/_integrations/autoskope.markdown index ad934a464913..413157ea82cf 100644 --- a/source/_integrations/autoskope.markdown +++ b/source/_integrations/autoskope.markdown @@ -4,7 +4,7 @@ description: "Instructions on how to integrate Autoskope devices into Home Assis ha_category: - Device tracker ha_release: 2025.5 -ha_iot_class: Cloud Polling +ha_iot_class: cloud_polling ha_domain: autoskope ha_platforms: - device_tracker From 65eb9153073302b81d5d599e30790a385b780171 Mon Sep 17 00:00:00 2001 From: c0ffeeca7 <38767475+c0ffeeca7@users.noreply.github.com> Date: Thu, 24 Apr 2025 13:55:17 +0200 Subject: [PATCH 03/20] move supported devices up --- source/_integrations/autoskope.markdown | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/source/_integrations/autoskope.markdown b/source/_integrations/autoskope.markdown index 413157ea82cf..cf5dee352cdb 100644 --- a/source/_integrations/autoskope.markdown +++ b/source/_integrations/autoskope.markdown @@ -19,6 +19,10 @@ The **Autoskope** {% term integration %} allows you to integrate your [Autoskope This integration connects to the Autoskope cloud service to retrieve the current status and location of your registered vehicles. +## Supported devices + +This integration should work with all past, present, and future hardware devices offered by Autoskope. + {% include integrations/config_flow.md %} ## Installation From e6d2a64a348eafe01cdc288f56cc776220cf3429 Mon Sep 17 00:00:00 2001 From: c0ffeeca7 <38767475+c0ffeeca7@users.noreply.github.com> Date: Thu, 24 Apr 2025 13:55:37 +0200 Subject: [PATCH 04/20] move config flow after prereqs --- source/_integrations/autoskope.markdown | 2 -- 1 file changed, 2 deletions(-) diff --git a/source/_integrations/autoskope.markdown b/source/_integrations/autoskope.markdown index cf5dee352cdb..f340a03e8eab 100644 --- a/source/_integrations/autoskope.markdown +++ b/source/_integrations/autoskope.markdown @@ -23,8 +23,6 @@ This integration connects to the Autoskope cloud service to retrieve the current This integration should work with all past, present, and future hardware devices offered by Autoskope. -{% include integrations/config_flow.md %} - ## Installation This integration can be set up via the Home Assistant user interface. From 0d0bf69b1680c4ac4881ef30998d8f8a60a0ce25 Mon Sep 17 00:00:00 2001 From: c0ffeeca7 <38767475+c0ffeeca7@users.noreply.github.com> Date: Thu, 24 Apr 2025 13:56:00 +0200 Subject: [PATCH 05/20] remove installation steps, they are covered by include element --- source/_integrations/autoskope.markdown | 8 -------- 1 file changed, 8 deletions(-) diff --git a/source/_integrations/autoskope.markdown b/source/_integrations/autoskope.markdown index f340a03e8eab..59559af777f8 100644 --- a/source/_integrations/autoskope.markdown +++ b/source/_integrations/autoskope.markdown @@ -23,14 +23,6 @@ This integration connects to the Autoskope cloud service to retrieve the current This integration should work with all past, present, and future hardware devices offered by Autoskope. -## Installation - -This integration can be set up via the Home Assistant user interface. - -1. Go to **Settings** > **Devices & Services**. -2. Click **Add Integration**. -3. Search for "Autoskope" and select it. -4. Follow the on-screen instructions to enter your Autoskope username, password, and the API host URL. ## Configuration From 16c610a56d29c2319407149271b088c3d91ee556 Mon Sep 17 00:00:00 2001 From: c0ffeeca7 <38767475+c0ffeeca7@users.noreply.github.com> Date: Thu, 24 Apr 2025 13:56:18 +0200 Subject: [PATCH 06/20] rename to Prerequisites --- source/_integrations/autoskope.markdown | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/source/_integrations/autoskope.markdown b/source/_integrations/autoskope.markdown index 59559af777f8..089840f3d8a4 100644 --- a/source/_integrations/autoskope.markdown +++ b/source/_integrations/autoskope.markdown @@ -24,7 +24,7 @@ This integration connects to the Autoskope cloud service to retrieve the current This integration should work with all past, present, and future hardware devices offered by Autoskope. -## Configuration +## Prerequisites Configuration is handled entirely through the UI flow during setup. You will need to provide: From 49622bbb4b45d3a7e68198b72b279d6ab31fdd7a Mon Sep 17 00:00:00 2001 From: c0ffeeca7 <38767475+c0ffeeca7@users.noreply.github.com> Date: Thu, 24 Apr 2025 13:56:35 +0200 Subject: [PATCH 07/20] move config flow after prereqs --- source/_integrations/autoskope.markdown | 1 + 1 file changed, 1 insertion(+) diff --git a/source/_integrations/autoskope.markdown b/source/_integrations/autoskope.markdown index 089840f3d8a4..44ad0660797e 100644 --- a/source/_integrations/autoskope.markdown +++ b/source/_integrations/autoskope.markdown @@ -34,6 +34,7 @@ Configuration is handled entirely through the UI flow during setup. You will nee These are the same credentials used for the Autoskope web portal and mobile app. +{% include integrations/config_flow.md %} ## Entities This integration provides the following entities: From bdef61055d5c86b4e8e081da11d8f5ecc254a98d Mon Sep 17 00:00:00 2001 From: c0ffeeca7 <38767475+c0ffeeca7@users.noreply.github.com> Date: Thu, 24 Apr 2025 13:56:42 +0200 Subject: [PATCH 08/20] Update source/_integrations/autoskope.markdown --- source/_integrations/autoskope.markdown | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/source/_integrations/autoskope.markdown b/source/_integrations/autoskope.markdown index 44ad0660797e..9b82613681d8 100644 --- a/source/_integrations/autoskope.markdown +++ b/source/_integrations/autoskope.markdown @@ -35,7 +35,7 @@ Configuration is handled entirely through the UI flow during setup. You will nee These are the same credentials used for the Autoskope web portal and mobile app. {% include integrations/config_flow.md %} -## Entities +## Supported functionality This integration provides the following entities: From 51599384e9ebd3fe325dba5973766011302867d8 Mon Sep 17 00:00:00 2001 From: c0ffeeca7 <38767475+c0ffeeca7@users.noreply.github.com> Date: Thu, 24 Apr 2025 13:56:58 +0200 Subject: [PATCH 09/20] apply capitalization --- source/_integrations/autoskope.markdown | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/source/_integrations/autoskope.markdown b/source/_integrations/autoskope.markdown index 9b82613681d8..6dcd83b8d437 100644 --- a/source/_integrations/autoskope.markdown +++ b/source/_integrations/autoskope.markdown @@ -65,7 +65,7 @@ The following attributes are provided: Note: Sensor entities for battery voltages and other values are planned for a future update. -## Data Update +## Data update The integration polls the Autoskope API every 60 seconds to retrieve the latest status and location data for all registered vehicles associated with the account. From ca522b87d7a6aaa8908cafc550e4c8abfde4f0c0 Mon Sep 17 00:00:00 2001 From: c0ffeeca7 <38767475+c0ffeeca7@users.noreply.github.com> Date: Thu, 24 Apr 2025 13:57:11 +0200 Subject: [PATCH 10/20] add glossary ref --- source/_integrations/autoskope.markdown | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/source/_integrations/autoskope.markdown b/source/_integrations/autoskope.markdown index 6dcd83b8d437..06416162e8c3 100644 --- a/source/_integrations/autoskope.markdown +++ b/source/_integrations/autoskope.markdown @@ -67,7 +67,7 @@ Note: Sensor entities for battery voltages and other values are planned for a fu ## Data update -The integration polls the Autoskope API every 60 seconds to retrieve the latest status and location data for all registered vehicles associated with the account. +The integration {% term polling polls %} the Autoskope API every 60 seconds to retrieve the latest status and location data for all registered vehicles associated with the account. ## Troubleshooting From 6db1632c360642d69597d5e9ce59b084e44541dc Mon Sep 17 00:00:00 2001 From: c0ffeeca7 <38767475+c0ffeeca7@users.noreply.github.com> Date: Thu, 24 Apr 2025 13:57:19 +0200 Subject: [PATCH 11/20] Update source/_integrations/autoskope.markdown --- source/_integrations/autoskope.markdown | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/source/_integrations/autoskope.markdown b/source/_integrations/autoskope.markdown index 06416162e8c3..a0cb815441a0 100644 --- a/source/_integrations/autoskope.markdown +++ b/source/_integrations/autoskope.markdown @@ -76,7 +76,7 @@ The integration {% term polling polls %} the Autoskope API every 60 seconds to r * **Vehicles Not Appearing:** If a vehicle you expect to see is missing in Home Assistant, log in to the Autoskope web portal or app and confirm that the vehicle is correctly registered, active, and associated with the account you used to set up the integration. * **Entities Become Unavailable:** If entities become unavailable, check the Home Assistant logs (**Settings** > **System** > **Logs**) for errors related to the Autoskope integration. This could indicate temporary connectivity issues with the Autoskope API or problems with your account credentials. -## Known Limitations +## Known limitations * **Update Delay:** Due to the 60-second polling interval for the cloud API, there will be a delay of up to 60 seconds (plus processing time) before status changes (like location or activity) are reflected in Home Assistant. * **Limited Sensor Data:** Currently, only the primary external voltage and internal battery voltage are exposed as attributes. Support for additional sensor data available on newer devices (like Autoskope V3's extra battery inputs or digital inputs) is planned for a future update. From 6ffddbc8f3c862076ef5ab2308d68804b43ab5e8 Mon Sep 17 00:00:00 2001 From: c0ffeeca7 <38767475+c0ffeeca7@users.noreply.github.com> Date: Thu, 24 Apr 2025 13:57:39 +0200 Subject: [PATCH 12/20] Apply suggestions from code review --- source/_integrations/autoskope.markdown | 12 +++--------- 1 file changed, 3 insertions(+), 9 deletions(-) diff --git a/source/_integrations/autoskope.markdown b/source/_integrations/autoskope.markdown index a0cb815441a0..0a95a3653201 100644 --- a/source/_integrations/autoskope.markdown +++ b/source/_integrations/autoskope.markdown @@ -81,9 +81,6 @@ The integration {% term polling polls %} the Autoskope API every 60 seconds to r * **Update Delay:** Due to the 60-second polling interval for the cloud API, there will be a delay of up to 60 seconds (plus processing time) before status changes (like location or activity) are reflected in Home Assistant. * **Limited Sensor Data:** Currently, only the primary external voltage and internal battery voltage are exposed as attributes. Support for additional sensor data available on newer devices (like Autoskope V3's extra battery inputs or digital inputs) is planned for a future update. -## Supported Devices - -This integration should work with all past, present, and future hardware devices offered by Autoskope. ## Automation Examples @@ -173,12 +170,9 @@ action: mode: single ``` -## Removal +## Removing the integration -To remove the Autoskope integration: +This integration follows standard integration removal. -1. Go to Settings > Devices & Services. -2. Find the Autoskope integration card. -3. Click the three dots (...) menu on the card. -4. Select Delete. +{% include integrations/remove_device_service.md %} Note: Entities and devices associated with vehicles that are removed from your Autoskope account (e.g., subscription canceled) will be automatically removed from Home Assistant during the next update cycle. From 54afb428f3b85f0c3f0386e034561b26d6186f4d Mon Sep 17 00:00:00 2001 From: c0ffeeca7 <38767475+c0ffeeca7@users.noreply.github.com> Date: Thu, 24 Apr 2025 13:57:54 +0200 Subject: [PATCH 13/20] Apply suggestions from code review --- source/_integrations/autoskope.markdown | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/source/_integrations/autoskope.markdown b/source/_integrations/autoskope.markdown index 0a95a3653201..28029030beed 100644 --- a/source/_integrations/autoskope.markdown +++ b/source/_integrations/autoskope.markdown @@ -175,4 +175,4 @@ mode: single This integration follows standard integration removal. {% include integrations/remove_device_service.md %} -Note: Entities and devices associated with vehicles that are removed from your Autoskope account (e.g., subscription canceled) will be automatically removed from Home Assistant during the next update cycle. +Note: Entities and devices associated with vehicles that are removed from your Autoskope account (for example, subscription canceled) will be automatically removed from Home Assistant during the next update cycle. From aee1e185874c2ce3c5c1e2d441e46248352a0bb5 Mon Sep 17 00:00:00 2001 From: c0ffeeca7 <38767475+c0ffeeca7@users.noreply.github.com> Date: Thu, 24 Apr 2025 13:59:50 +0200 Subject: [PATCH 14/20] add newline --- source/_integrations/autoskope.markdown | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/source/_integrations/autoskope.markdown b/source/_integrations/autoskope.markdown index 28029030beed..7e3788efa9bf 100644 --- a/source/_integrations/autoskope.markdown +++ b/source/_integrations/autoskope.markdown @@ -23,7 +23,6 @@ This integration connects to the Autoskope cloud service to retrieve the current This integration should work with all past, present, and future hardware devices offered by Autoskope. - ## Prerequisites Configuration is handled entirely through the UI flow during setup. You will need to provide: @@ -35,6 +34,7 @@ Configuration is handled entirely through the UI flow during setup. You will nee These are the same credentials used for the Autoskope web portal and mobile app. {% include integrations/config_flow.md %} + ## Supported functionality This integration provides the following entities: From 3ad78bcc3e58a592b1c6faf36203e463942f4f07 Mon Sep 17 00:00:00 2001 From: c0ffeeca7 <38767475+c0ffeeca7@users.noreply.github.com> Date: Thu, 24 Apr 2025 14:01:58 +0200 Subject: [PATCH 15/20] Apply suggestions from code review --- source/_integrations/autoskope.markdown | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/source/_integrations/autoskope.markdown b/source/_integrations/autoskope.markdown index 7e3788efa9bf..40c8fe99c408 100644 --- a/source/_integrations/autoskope.markdown +++ b/source/_integrations/autoskope.markdown @@ -82,7 +82,7 @@ The integration {% term polling polls %} the Autoskope API every 60 seconds to r * **Limited Sensor Data:** Currently, only the primary external voltage and internal battery voltage are exposed as attributes. Support for additional sensor data available on newer devices (like Autoskope V3's extra battery inputs or digital inputs) is planned for a future update. -## Automation Examples +## Automation examples Here are a few examples of how you can use the Autoskope device tracker entities in your automations. Replace `device_tracker.my_vehicle_name` with the actual entity ID of your vehicle's tracker. @@ -175,4 +175,5 @@ mode: single This integration follows standard integration removal. {% include integrations/remove_device_service.md %} + Note: Entities and devices associated with vehicles that are removed from your Autoskope account (for example, subscription canceled) will be automatically removed from Home Assistant during the next update cycle. From 279a3ff6c6664b900f30fe5210eff7da584ac80e Mon Sep 17 00:00:00 2001 From: c0ffeeca7 <38767475+c0ffeeca7@users.noreply.github.com> Date: Thu, 24 Apr 2025 14:06:10 +0200 Subject: [PATCH 16/20] add my link --- source/_integrations/autoskope.markdown | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/source/_integrations/autoskope.markdown b/source/_integrations/autoskope.markdown index 40c8fe99c408..4e780178b2aa 100644 --- a/source/_integrations/autoskope.markdown +++ b/source/_integrations/autoskope.markdown @@ -39,7 +39,7 @@ These are the same credentials used for the Autoskope web portal and mobile app. This integration provides the following entities: -### Device Tracker +### Device tracker A `device_tracker` entity is created for each vehicle registered in your Autoskope account. This entity tracks the location of the vehicle. @@ -74,7 +74,7 @@ The integration {% term polling polls %} the Autoskope API every 60 seconds to r * **Authentication Errors:** If you change your Autoskope password, the integration will fail to connect. Home Assistant should prompt you to re-authenticate. Go to **Settings** > **Devices & Services**, find the Autoskope integration card, and click **Reconfigure** to enter your new password. * **Connection Failed during Setup:** Ensure you have entered the correct **Host** URL for the Autoskope API. The default value (`https://portal.autoskope.de`) should be correct for most users. Also, verify your username and password. Check if your Home Assistant instance can reach the Autoskope host URL (e.g., firewall rules, DNS issues). * **Vehicles Not Appearing:** If a vehicle you expect to see is missing in Home Assistant, log in to the Autoskope web portal or app and confirm that the vehicle is correctly registered, active, and associated with the account you used to set up the integration. -* **Entities Become Unavailable:** If entities become unavailable, check the Home Assistant logs (**Settings** > **System** > **Logs**) for errors related to the Autoskope integration. This could indicate temporary connectivity issues with the Autoskope API or problems with your account credentials. +* **Entities Become Unavailable:** If entities become unavailable, check the Home Assistant logs {% my logs title="**Settings** > **System** > **Logs**" %} for errors related to the Autoskope integration. This could indicate temporary connectivity issues with the Autoskope API or problems with your account credentials. ## Known limitations From 780e4646fd0072cbbabdd6573b95c8092c7bfc66 Mon Sep 17 00:00:00 2001 From: c0ffeeca7 <38767475+c0ffeeca7@users.noreply.github.com> Date: Thu, 24 Apr 2025 14:09:44 +0200 Subject: [PATCH 17/20] Apply heading style instead of bold --- source/_integrations/autoskope.markdown | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git a/source/_integrations/autoskope.markdown b/source/_integrations/autoskope.markdown index 4e780178b2aa..e4accf05f0d4 100644 --- a/source/_integrations/autoskope.markdown +++ b/source/_integrations/autoskope.markdown @@ -86,7 +86,7 @@ The integration {% term polling polls %} the Autoskope API every 60 seconds to r Here are a few examples of how you can use the Autoskope device tracker entities in your automations. Replace `device_tracker.my_vehicle_name` with the actual entity ID of your vehicle's tracker. -**Notify when the vehicle arrives home:** +### Notify when the vehicle arrives home ```yaml # filepath: automations.yaml @@ -102,7 +102,7 @@ action: mode: single ``` -**Turn on porch light on arrival after sunset:** +### Turn on porch light on arrival after sunset ```yaml # filepath: automations.yaml @@ -121,7 +121,7 @@ action: mode: single ``` -**Open garage when arriving near home:** +### Open garage when arriving near home ```yaml # filepath: automations.yaml @@ -138,7 +138,7 @@ action: mode: single ``` -**Enable Wallbox when car is home:** +### Enable Wallbox when car is home ```yaml # filepath: automations.yaml @@ -154,7 +154,7 @@ action: mode: single ``` -**Arm garage alarm when car leaves home:** +### Arm garage alarm when car leaves home ```yaml # filepath: automations.yaml From 32cb5e3f1bfb2b74271a91fab20741471824bd45 Mon Sep 17 00:00:00 2001 From: c0ffeeca7 <38767475+c0ffeeca7@users.noreply.github.com> Date: Thu, 24 Apr 2025 14:13:27 +0200 Subject: [PATCH 18/20] tweak list style --- source/_integrations/autoskope.markdown | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/source/_integrations/autoskope.markdown b/source/_integrations/autoskope.markdown index e4accf05f0d4..552ba40169fd 100644 --- a/source/_integrations/autoskope.markdown +++ b/source/_integrations/autoskope.markdown @@ -27,9 +27,9 @@ This integration should work with all past, present, and future hardware devices Configuration is handled entirely through the UI flow during setup. You will need to provide: -* **Username:** Your Autoskope account username. -* **Password:** Your Autoskope account password. -* **Host:** URL of the Autoskope API server (e.g., `https://portal.autoskope.de`). +- **Username**: Your Autoskope account username. +- **Password**: Your Autoskope account password. +- **Host**: URL of the Autoskope API server (for example, `https://portal.autoskope.de`). These are the same credentials used for the Autoskope web portal and mobile app. From 84f575b6df52e9a8284df76e3f5bde875659ece3 Mon Sep 17 00:00:00 2001 From: c0ffeeca7 <38767475+c0ffeeca7@users.noreply.github.com> Date: Thu, 24 Apr 2025 14:25:51 +0200 Subject: [PATCH 19/20] replace bold by heading, apply sentence-style capitalization --- source/_integrations/autoskope.markdown | 30 ++++++++++++++++++++----- 1 file changed, 24 insertions(+), 6 deletions(-) diff --git a/source/_integrations/autoskope.markdown b/source/_integrations/autoskope.markdown index 552ba40169fd..35371b90bc40 100644 --- a/source/_integrations/autoskope.markdown +++ b/source/_integrations/autoskope.markdown @@ -71,15 +71,33 @@ The integration {% term polling polls %} the Autoskope API every 60 seconds to r ## Troubleshooting -* **Authentication Errors:** If you change your Autoskope password, the integration will fail to connect. Home Assistant should prompt you to re-authenticate. Go to **Settings** > **Devices & Services**, find the Autoskope integration card, and click **Reconfigure** to enter your new password. -* **Connection Failed during Setup:** Ensure you have entered the correct **Host** URL for the Autoskope API. The default value (`https://portal.autoskope.de`) should be correct for most users. Also, verify your username and password. Check if your Home Assistant instance can reach the Autoskope host URL (e.g., firewall rules, DNS issues). -* **Vehicles Not Appearing:** If a vehicle you expect to see is missing in Home Assistant, log in to the Autoskope web portal or app and confirm that the vehicle is correctly registered, active, and associated with the account you used to set up the integration. -* **Entities Become Unavailable:** If entities become unavailable, check the Home Assistant logs {% my logs title="**Settings** > **System** > **Logs**" %} for errors related to the Autoskope integration. This could indicate temporary connectivity issues with the Autoskope API or problems with your account credentials. +### Authentication errors + +If you change your Autoskope password, the integration will fail to connect. Home Assistant should prompt you to re-authenticate. Go to {% my integrations title="**Settings** > **Devices & services**" %}, find the Autoskope integration card, and select **Reconfigure** to enter your new password. +### Connection failed during setup + +- Ensure you have entered the correct **Host** URL for the Autoskope API. + - The default value (`https://portal.autoskope.de`) should be correct for most users. +- Verify your username and password. +- Check if your Home Assistant instance can reach the Autoskope host URL (for example, firewall rules, DNS issues). +### Vehicles not appearing + +If a vehicle you expect to see is missing in Home Assistant, log in to the Autoskope web portal or app and confirm that the vehicle is correctly registered, active, and associated with the account you used to set up the integration. + +### Entities become unavailable + +- If entities become unavailable, check the Home Assistant logs {% my logs title="**Settings** > **System** > **Logs**" %} for errors related to the Autoskope integration. This could indicate temporary connectivity issues with the Autoskope API or problems with your account credentials. ## Known limitations -* **Update Delay:** Due to the 60-second polling interval for the cloud API, there will be a delay of up to 60 seconds (plus processing time) before status changes (like location or activity) are reflected in Home Assistant. -* **Limited Sensor Data:** Currently, only the primary external voltage and internal battery voltage are exposed as attributes. Support for additional sensor data available on newer devices (like Autoskope V3's extra battery inputs or digital inputs) is planned for a future update. + +### Update delay + +Due to the 60-second polling interval for the cloud API, there will be a delay of up to 60 seconds (plus processing time) before status changes (like location or activity) are reflected in Home Assistant. + +### Limited sensor data + +Currently, only the primary external voltage and internal battery voltage are exposed as attributes. Support for additional sensor data available on newer devices (like Autoskope V3's extra battery inputs or digital inputs) is planned for a future update. ## Automation examples From 2bf7d6cf3721172823f52e3f4aa826b9cc6d93ae Mon Sep 17 00:00:00 2001 From: c0ffeeca7 <38767475+c0ffeeca7@users.noreply.github.com> Date: Thu, 24 Apr 2025 14:27:41 +0200 Subject: [PATCH 20/20] fix markdown issues I introduced in previous commits --- source/_integrations/autoskope.markdown | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/source/_integrations/autoskope.markdown b/source/_integrations/autoskope.markdown index 35371b90bc40..b4ec32a4bc56 100644 --- a/source/_integrations/autoskope.markdown +++ b/source/_integrations/autoskope.markdown @@ -74,12 +74,14 @@ The integration {% term polling polls %} the Autoskope API every 60 seconds to r ### Authentication errors If you change your Autoskope password, the integration will fail to connect. Home Assistant should prompt you to re-authenticate. Go to {% my integrations title="**Settings** > **Devices & services**" %}, find the Autoskope integration card, and select **Reconfigure** to enter your new password. + ### Connection failed during setup - Ensure you have entered the correct **Host** URL for the Autoskope API. - The default value (`https://portal.autoskope.de`) should be correct for most users. - Verify your username and password. - Check if your Home Assistant instance can reach the Autoskope host URL (for example, firewall rules, DNS issues). + ### Vehicles not appearing If a vehicle you expect to see is missing in Home Assistant, log in to the Autoskope web portal or app and confirm that the vehicle is correctly registered, active, and associated with the account you used to set up the integration. @@ -90,7 +92,6 @@ If a vehicle you expect to see is missing in Home Assistant, log in to the Autos ## Known limitations - ### Update delay Due to the 60-second polling interval for the cloud API, there will be a delay of up to 60 seconds (plus processing time) before status changes (like location or activity) are reflected in Home Assistant. @@ -99,7 +100,6 @@ Due to the 60-second polling interval for the cloud API, there will be a delay o Currently, only the primary external voltage and internal battery voltage are exposed as attributes. Support for additional sensor data available on newer devices (like Autoskope V3's extra battery inputs or digital inputs) is planned for a future update. - ## Automation examples Here are a few examples of how you can use the Autoskope device tracker entities in your automations. Replace `device_tracker.my_vehicle_name` with the actual entity ID of your vehicle's tracker.