jeans/home-assistant.io
jeans/home-assistant.io
1
0
Fork 0
mirror of https://github.com/home-assistant/home-assistant.io.git synced 2025-07-18 23:06:58 +00:00
Code Issues Packages Projects Releases Wiki Activity

d-g-building block entities (#29153)

Browse Source
This commit is contained in:
c0ffeeca7 2023-10-04 19:20:35 +02:00 committed by GitHub
parent 626d123493
commit 5cbfc37ceb
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
6 changed files with 16 additions and 6 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
source/_integrations/date.markdown
View File

@ -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

4
source/_integrations/datetime.markdown
View File

@ -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

2
source/_integrations/device_tracker.markdown
View File

@ -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):

2
source/_integrations/event.markdown
View File

@ -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

6
source/_integrations/fan.markdown
View File

@ -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:
<div class='note'>
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**.
</div>

2
source/_integrations/geo_location.markdown
View File

@ -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: