From e639edc05fc6734bf32403e30687d7c657d05500 Mon Sep 17 00:00:00 2001 From: c0ffeeca7 Date: Fri, 25 Apr 2025 09:25:55 +0200 Subject: [PATCH 1/9] Areas dashboard: improve adding and editing procedures, add troubleshooting --- source/dashboards/dashboards.markdown | 16 +++++++++++++--- 1 file changed, 13 insertions(+), 3 deletions(-) diff --git a/source/dashboards/dashboards.markdown b/source/dashboards/dashboards.markdown index 4e34707b77d0..1527527b94dd 100644 --- a/source/dashboards/dashboards.markdown +++ b/source/dashboards/dashboards.markdown @@ -55,13 +55,23 @@ The **Areas** dashboard is prepopulated by default and shows your {% term entiti Screenshot of the Areas default dashboard.

-After you [added the dashboard](#creating-a-new-dashboard), you can edit the **Areas** dashboard: +#### Adding an areas dashboard -1. In the top-right corner, select the {% icon "mdi:pencil" %} icon. -2. You can show or hide sections, rearrange the content, or [add badges](/dashboards/badges/). +- To add the **Areas** dashboard, follow the steps on [adding a dashboard](#creating-a-new-dashboard). + +#### Editing the areas dashboard + +1. Make sure all the {% term entities %} are [assigned to an area](/docs/organizing/areas/#assigning-an-area-to-multiple-items). +2. After you [added the dashboard](#creating-a-new-dashboard), you can edit the **Areas** dashboard. +3. In the top-right corner, select the {% icon "mdi:pencil" %} icon. +4. You can show or hide sections, rearrange the content, or [add badges](/dashboards/badges/). The **Areas** dashboard is still experimental. It is subject to change and may not always work as intended. +#### My entity is not showing on the areas dashboard + +If your {% term entity %} is not displayed on the areas dashboard, it is probably not assigned to an area. [Assign the entity to an area](/docs/organizing/areas/#assigning-an-area-to-multiple-items) and check the dashboard again. + ### History dashboard The predefined **History** dashboard is powered by the [History integration](/integrations/history/). To learn about the data sources used and how to export data, refer to the documentation of the History integration. From f19448a9c7e76089abff720dde2ebe78ab44dd2f Mon Sep 17 00:00:00 2001 From: c0ffeeca7 Date: Fri, 25 Apr 2025 09:32:48 +0200 Subject: [PATCH 2/9] Fix terminology --- source/dashboards/dashboards.markdown | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/source/dashboards/dashboards.markdown b/source/dashboards/dashboards.markdown index 1527527b94dd..688194bda203 100644 --- a/source/dashboards/dashboards.markdown +++ b/source/dashboards/dashboards.markdown @@ -55,11 +55,11 @@ The **Areas** dashboard is prepopulated by default and shows your {% term entiti Screenshot of the Areas default dashboard.

-#### Adding an areas dashboard +#### Adding an Areas dashboard - To add the **Areas** dashboard, follow the steps on [adding a dashboard](#creating-a-new-dashboard). -#### Editing the areas dashboard +#### Editing the Areas dashboard 1. Make sure all the {% term entities %} are [assigned to an area](/docs/organizing/areas/#assigning-an-area-to-multiple-items). 2. After you [added the dashboard](#creating-a-new-dashboard), you can edit the **Areas** dashboard. @@ -68,9 +68,9 @@ Screenshot of the Areas default dashboard. The **Areas** dashboard is still experimental. It is subject to change and may not always work as intended. -#### My entity is not showing on the areas dashboard +#### My entity is not showing on the Areas dashboard -If your {% term entity %} is not displayed on the areas dashboard, it is probably not assigned to an area. [Assign the entity to an area](/docs/organizing/areas/#assigning-an-area-to-multiple-items) and check the dashboard again. +If your {% term entity %} is not displayed on the **Areas** dashboard, it is probably not assigned to an area. [Assign the entity to an area](/docs/organizing/areas/#assigning-an-area-to-multiple-items) and check the dashboard again. ### History dashboard From 9a2ce7787b7e0ab00b52a0be7e4f2b94a6532525 Mon Sep 17 00:00:00 2001 From: c0ffeeca7 Date: Fri, 25 Apr 2025 10:01:01 +0200 Subject: [PATCH 3/9] Improve troubleshooting, add limitations --- source/dashboards/dashboards.markdown | 10 ++++++++-- 1 file changed, 8 insertions(+), 2 deletions(-) diff --git a/source/dashboards/dashboards.markdown b/source/dashboards/dashboards.markdown index 688194bda203..6b3185006535 100644 --- a/source/dashboards/dashboards.markdown +++ b/source/dashboards/dashboards.markdown @@ -55,6 +55,11 @@ The **Areas** dashboard is prepopulated by default and shows your {% term entiti Screenshot of the Areas default dashboard.

+#### Limitations + +1. Not all devices are automatically added to the Areas dashboard. Some motion detectors, door/window contact sensors, and BLE/third-party thermometer devices are not added to the dashboard. +2. Certain entity types and helpers are omitted from the Areas dashboard. For example, `input_select` and `input_boolean` entities do not appear, even when assigned to an area. + #### Adding an Areas dashboard - To add the **Areas** dashboard, follow the steps on [adding a dashboard](#creating-a-new-dashboard). @@ -68,9 +73,10 @@ Screenshot of the Areas default dashboard. The **Areas** dashboard is still experimental. It is subject to change and may not always work as intended. -#### My entity is not showing on the Areas dashboard +#### My entity is not showing -If your {% term entity %} is not displayed on the **Areas** dashboard, it is probably not assigned to an area. [Assign the entity to an area](/docs/organizing/areas/#assigning-an-area-to-multiple-items) and check the dashboard again. +1. Not all devices or entity types are automatically added to the Areas dashboard. Refer to the [Limitations](#limitations) section. +2. Make sure the entity is [assigned to an area](/docs/organizing/areas/#assigning-an-area-to-multiple-items) and check the dashboard again. ### History dashboard From d3a613af960baec52d161dd0678fb7eaa1f689e0 Mon Sep 17 00:00:00 2001 From: c0ffeeca7 Date: Fri, 25 Apr 2025 10:04:26 +0200 Subject: [PATCH 4/9] Fix typo --- source/dashboards/dashboards.markdown | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/source/dashboards/dashboards.markdown b/source/dashboards/dashboards.markdown index 6b3185006535..6ce302c40de3 100644 --- a/source/dashboards/dashboards.markdown +++ b/source/dashboards/dashboards.markdown @@ -57,8 +57,8 @@ Screenshot of the Areas default dashboard. #### Limitations -1. Not all devices are automatically added to the Areas dashboard. Some motion detectors, door/window contact sensors, and BLE/third-party thermometer devices are not added to the dashboard. -2. Certain entity types and helpers are omitted from the Areas dashboard. For example, `input_select` and `input_boolean` entities do not appear, even when assigned to an area. +1. Not all devices are automatically added to the **Areas** dashboard. Some motion detectors, door/window contact sensors, and BLE/third-party thermometer devices are not added to the dashboard. +2. Certain entity types and helpers are omitted from the **Areas** dashboard. For example, `input_select` and `input_boolean` entities do not appear, even when assigned to an area. #### Adding an Areas dashboard @@ -73,9 +73,9 @@ Screenshot of the Areas default dashboard. The **Areas** dashboard is still experimental. It is subject to change and may not always work as intended. -#### My entity is not showing +#### Troubleshooting: entity is not showing -1. Not all devices or entity types are automatically added to the Areas dashboard. Refer to the [Limitations](#limitations) section. +1. Not all devices or entity types are automatically added to the **Areas** dashboard. Refer to the [Limitations](#limitations) section. 2. Make sure the entity is [assigned to an area](/docs/organizing/areas/#assigning-an-area-to-multiple-items) and check the dashboard again. ### History dashboard From 56a24a95545e0ee21aa08f264f00f4f560e74401 Mon Sep 17 00:00:00 2001 From: c0ffeeca7 Date: Fri, 25 Apr 2025 10:16:37 +0200 Subject: [PATCH 5/9] Tweak --- source/dashboards/dashboards.markdown | 8 +++++--- 1 file changed, 5 insertions(+), 3 deletions(-) diff --git a/source/dashboards/dashboards.markdown b/source/dashboards/dashboards.markdown index 6ce302c40de3..a4cce511ad86 100644 --- a/source/dashboards/dashboards.markdown +++ b/source/dashboards/dashboards.markdown @@ -43,6 +43,10 @@ Not all of the predefined dashboards are listed under {% my lovelace_dashboards ### Areas dashboard +{% note %} +The **Areas** dashboard is still experimental. It is subject to change and may not always work as intended. +{% endnote %} + The **Areas** dashboard is prepopulated by default and shows your {% term entities %} [grouped](/docs/organizing/) by [areas](/docs/organizing/areas/). - It uses the [sections view](/dashboards/sections/) type and [tile cards](/dashboards/tile/). @@ -55,7 +59,7 @@ The **Areas** dashboard is prepopulated by default and shows your {% term entiti Screenshot of the Areas default dashboard.

-#### Limitations +#### Limitations of the Areas dashboard 1. Not all devices are automatically added to the **Areas** dashboard. Some motion detectors, door/window contact sensors, and BLE/third-party thermometer devices are not added to the dashboard. 2. Certain entity types and helpers are omitted from the **Areas** dashboard. For example, `input_select` and `input_boolean` entities do not appear, even when assigned to an area. @@ -71,8 +75,6 @@ Screenshot of the Areas default dashboard. 3. In the top-right corner, select the {% icon "mdi:pencil" %} icon. 4. You can show or hide sections, rearrange the content, or [add badges](/dashboards/badges/). -The **Areas** dashboard is still experimental. It is subject to change and may not always work as intended. - #### Troubleshooting: entity is not showing 1. Not all devices or entity types are automatically added to the **Areas** dashboard. Refer to the [Limitations](#limitations) section. From 3618af98ca6e218aa779ba8cbe3cf42d8b9fa07f Mon Sep 17 00:00:00 2001 From: c0ffeeca7 Date: Fri, 25 Apr 2025 11:14:14 +0200 Subject: [PATCH 6/9] Fix link --- source/dashboards/dashboards.markdown | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/source/dashboards/dashboards.markdown b/source/dashboards/dashboards.markdown index a4cce511ad86..d8d1418703f3 100644 --- a/source/dashboards/dashboards.markdown +++ b/source/dashboards/dashboards.markdown @@ -77,7 +77,7 @@ Screenshot of the Areas default dashboard. #### Troubleshooting: entity is not showing -1. Not all devices or entity types are automatically added to the **Areas** dashboard. Refer to the [Limitations](#limitations) section. +1. Not all devices or entity types are automatically added to the **Areas** dashboard. Refer to the [Limitations](#limitations-of-the-areas-dashboard) section. 2. Make sure the entity is [assigned to an area](/docs/organizing/areas/#assigning-an-area-to-multiple-items) and check the dashboard again. ### History dashboard From 5f5ca02652faace7b9a31b1093508d4623e633a5 Mon Sep 17 00:00:00 2001 From: c0ffeeca7 Date: Fri, 25 Apr 2025 14:59:42 +0200 Subject: [PATCH 7/9] Be more specific about the view --- source/dashboards/dashboards.markdown | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/source/dashboards/dashboards.markdown b/source/dashboards/dashboards.markdown index d8d1418703f3..23baff3dc3b5 100644 --- a/source/dashboards/dashboards.markdown +++ b/source/dashboards/dashboards.markdown @@ -61,7 +61,7 @@ Screenshot of the Areas default dashboard. #### Limitations of the Areas dashboard -1. Not all devices are automatically added to the **Areas** dashboard. Some motion detectors, door/window contact sensors, and BLE/third-party thermometer devices are not added to the dashboard. +1. Not all devices are automatically added to the **Areas** dashboard {% icon "mdi:house" %} (the first view). Some motion detectors, door/window contact sensors, and BLE/third-party thermometer devices are not added to the {% icon "mdi:house" %} view, but only to the area-specific view. 2. Certain entity types and helpers are omitted from the **Areas** dashboard. For example, `input_select` and `input_boolean` entities do not appear, even when assigned to an area. #### Adding an Areas dashboard From 9b09055cad2af736306aba7e0ec8fcd295cc3fb0 Mon Sep 17 00:00:00 2001 From: c0ffeeca7 Date: Tue, 29 Apr 2025 13:36:11 +0200 Subject: [PATCH 8/9] Implement review feedback --- source/dashboards/dashboards.markdown | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/source/dashboards/dashboards.markdown b/source/dashboards/dashboards.markdown index 23baff3dc3b5..a8a839adb84a 100644 --- a/source/dashboards/dashboards.markdown +++ b/source/dashboards/dashboards.markdown @@ -61,8 +61,8 @@ Screenshot of the Areas default dashboard. #### Limitations of the Areas dashboard -1. Not all devices are automatically added to the **Areas** dashboard {% icon "mdi:house" %} (the first view). Some motion detectors, door/window contact sensors, and BLE/third-party thermometer devices are not added to the {% icon "mdi:house" %} view, but only to the area-specific view. -2. Certain entity types and helpers are omitted from the **Areas** dashboard. For example, `input_select` and `input_boolean` entities do not appear, even when assigned to an area. +1. Not all devices are added to the **Areas** dashboard. Only a few sensors are displayed automatically. Such as temperature and humidity of the area, and door, window, and gate binary sensors. +2. Certain entity types and helpers are omitted from the **Areas** dashboard. For example, configuration and diagnostic {% term entities %} do not appear, even if they have been assigned to an area. #### Adding an Areas dashboard From d6fdc589727a0df0f630382bc6af3bed9b08130b Mon Sep 17 00:00:00 2001 From: c0ffeeca7 <38767475+c0ffeeca7@users.noreply.github.com> Date: Tue, 29 Apr 2025 14:28:08 +0200 Subject: [PATCH 9/9] Update source/dashboards/dashboards.markdown Co-authored-by: Paul Bottein --- source/dashboards/dashboards.markdown | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/source/dashboards/dashboards.markdown b/source/dashboards/dashboards.markdown index a8a839adb84a..518b7c665d8f 100644 --- a/source/dashboards/dashboards.markdown +++ b/source/dashboards/dashboards.markdown @@ -62,7 +62,7 @@ Screenshot of the Areas default dashboard. #### Limitations of the Areas dashboard 1. Not all devices are added to the **Areas** dashboard. Only a few sensors are displayed automatically. Such as temperature and humidity of the area, and door, window, and gate binary sensors. -2. Certain entity types and helpers are omitted from the **Areas** dashboard. For example, configuration and diagnostic {% term entities %} do not appear, even if they have been assigned to an area. +2. Certain entity domains and helpers are omitted from the **Areas** dashboard. For example, configuration and diagnostic {% term entities %} do not appear, even if they have been assigned to an area. #### Adding an Areas dashboard