From 5cbfc37ceb46d387c23ad27d8296531deed8f9d7 Mon Sep 17 00:00:00 2001 From: c0ffeeca7 <38767475+c0ffeeca7@users.noreply.github.com> Date: Wed, 4 Oct 2023 19:20:35 +0200 Subject: [PATCH] d-g-building block entities (#29153) --- source/_integrations/date.markdown | 6 ++++-- source/_integrations/datetime.markdown | 4 +++- source/_integrations/device_tracker.markdown | 2 ++ source/_integrations/event.markdown | 2 +- source/_integrations/fan.markdown | 6 ++++-- source/_integrations/geo_location.markdown | 2 ++ 6 files changed, 16 insertions(+), 6 deletions(-) diff --git a/source/_integrations/date.markdown b/source/_integrations/date.markdown index fc8426fa593..c5df8ac46ff 100644 --- a/source/_integrations/date.markdown +++ b/source/_integrations/date.markdown @@ -11,9 +11,11 @@ ha_codeowners: ha_integration_type: entity --- -The Date integration is built for the controlling and monitoring of dates on devices. +The date integration is built for the controlling and monitoring of dates on devices. -Date entities cannot be created manually, but can be provided by other integrations. If you are looking for a way to create a similar entity, please take a look at the [Date/Time helper](/integrations/input_datetime). +{% include integrations/building_block_integration.md %} + +If you are looking for a way to create a similar entity, please take a look at the [Date/Time helper](/integrations/input_datetime). ## Services diff --git a/source/_integrations/datetime.markdown b/source/_integrations/datetime.markdown index 82127536a8d..4511c5a3287 100644 --- a/source/_integrations/datetime.markdown +++ b/source/_integrations/datetime.markdown @@ -13,7 +13,9 @@ ha_integration_type: entity The Date/Time integration is built for the controlling and monitoring of timestamps on devices. -Date/Time entities cannot be implemented manually, but can be provided by other integrations. If you are looking for a way to create a Date/Time entity, please take a look at the [Date/Time helper](/integrations/input_datetime). +{% include integrations/building_block_integration.md %} + +If you are looking for a way to create a Date/Time entity, please take a look at the [Date/Time helper](/integrations/input_datetime). ## Services diff --git a/source/_integrations/device_tracker.markdown b/source/_integrations/device_tracker.markdown index 50e7d8bee73..deda639a96f 100644 --- a/source/_integrations/device_tracker.markdown +++ b/source/_integrations/device_tracker.markdown @@ -13,6 +13,8 @@ ha_integration_type: entity The device tracker allows you to track devices in Home Assistant. This can happen by querying your wireless router or by having applications push location info. +{% include integrations/building_block_integration.md %} + ## Configuring a `device_tracker` platform To get started add the following lines to your `configuration.yaml` (example for Netgear): diff --git a/source/_integrations/event.markdown b/source/_integrations/event.markdown index 3563ba13092..ba6f28cc175 100644 --- a/source/_integrations/event.markdown +++ b/source/_integrations/event.markdown @@ -17,7 +17,7 @@ These events are stateless. For example, a doorbell does not have a state like b The event entity can capture these events in the physical world and makes them available in Home Assistant as an entity. -Please note, the event integration cannot be directly used; you cannot create your own event entities using this integration. This integration is a building block for other integrations to use, enabling them to create event entities for you. +{% include integrations/building_block_integration.md %} ## The state of an event entity diff --git a/source/_integrations/fan.markdown b/source/_integrations/fan.markdown index f7b95510d90..8b5844cf9e8 100644 --- a/source/_integrations/fan.markdown +++ b/source/_integrations/fan.markdown @@ -11,7 +11,9 @@ ha_codeowners: ha_integration_type: entity --- -The Fan integration allows you to control and monitor Fan devices. +The fan integration allows you to control and monitor fan devices. + +{% include integrations/building_block_integration.md %} ## Services @@ -22,7 +24,7 @@ Available services:
-Not all fan services may be available for your platform. You can check which services are available for your fan(s) under **Developer Tools** -> **Services**. +Not all fan services may be available for your platform. You can check which services are available for your fan(s) under **Developer Tools** > **Services**.
diff --git a/source/_integrations/geo_location.markdown b/source/_integrations/geo_location.markdown index dc09f3f06fc..8e5b79e61c4 100644 --- a/source/_integrations/geo_location.markdown +++ b/source/_integrations/geo_location.markdown @@ -15,6 +15,8 @@ Geolocation aware entities are typically related to events in the real world in Entities can have associated geolocation coordinates (latitude and longitude) so that they are displayed on the map. The distance from the entity's coordinates to Home Assistant's location can be used for filtering. +{% include integrations/building_block_integration.md %} + ## Geolocation trigger The [Geolocation trigger](/docs/automation/trigger/#geolocation-trigger) can be used in automations triggered by Geolocation entities appearing in or disappearing from zones. The following value must be used as `source` of the trigger depending on which platform is managing the entities: