diff --git a/source/_includes/integrations/device_class_intro.md b/source/_includes/integrations/device_class_intro.md new file mode 100644 index 00000000000..dbd76244078 --- /dev/null +++ b/source/_includes/integrations/device_class_intro.md @@ -0,0 +1 @@ +A device class defines how the entity is represented in the [dashboard](/dashboards/). This can be modified in the [customize section](/docs/configuration/customizing-devices/). For example, different states may be represented by different icons, colors, or text. \ No newline at end of file diff --git a/source/_integrations/binary_sensor.markdown b/source/_integrations/binary_sensor.markdown index f6d8f778a17..9c32a30e630 100644 --- a/source/_integrations/binary_sensor.markdown +++ b/source/_integrations/binary_sensor.markdown @@ -31,7 +31,7 @@ or using an [input boolean helper](/integrations/input_boolean). ### Device class -The device class defines how the entity is represented on the [dashboard](/dashboards/). This can be modified in the [customize section](/docs/configuration/customizing-devices/). For example, different states may be represented by different icons, colors, or text. +{% include integrations/device_class_intro.md %} The screenshot shows a few examples of different device classes for binary sensors: diff --git a/source/_integrations/button.markdown b/source/_integrations/button.markdown index ee8ebdb33de..ae885ea9ae8 100644 --- a/source/_integrations/button.markdown +++ b/source/_integrations/button.markdown @@ -60,7 +60,7 @@ This service can be called to trigger a button press for that entity. ## Device class -The device class defines how the entity is represented on the [dashboard](/dashboards/). This can be modified in the [customize section](/docs/configuration/customizing-devices/). For example, different states may be represented by different icons, colors, or text. +{% include integrations/device_class_intro.md %} The screenshot shows different icons representing different device classes for buttons: diff --git a/source/_integrations/cover.markdown b/source/_integrations/cover.markdown index f88b92ee3ae..ee34b926e00 100644 --- a/source/_integrations/cover.markdown +++ b/source/_integrations/cover.markdown @@ -22,7 +22,7 @@ Home Assistant can give you an interface to control covers such as rollershutter ## Device class -The device class defines how the entity is represented on the [dashboard](/dashboards/). This can be modified in the [customize section](/docs/configuration/customizing-devices/). For example, different states may be represented by different icons, colors, or text. +{% include integrations/device_class_intro.md %} The screenshot shows different icons representing different device classes for covers: diff --git a/source/_integrations/event.markdown b/source/_integrations/event.markdown index bac1741cc2b..61891cfc804 100644 --- a/source/_integrations/event.markdown +++ b/source/_integrations/event.markdown @@ -82,7 +82,7 @@ When creating automations in the automation editor in the UI, the event types ar ## Device classes -The device class defines how the entity is represented on the [dashboard](/dashboards/). This can be modified in the [customize section](/docs/configuration/customizing-devices/). For example, different states may be represented by different icons, colors, or text. +{% include integrations/device_class_intro.md %} The following device classes are supported by event entities: diff --git a/source/_integrations/humidifier.markdown b/source/_integrations/humidifier.markdown index f1e5040eb96..db5b2bf5567 100644 --- a/source/_integrations/humidifier.markdown +++ b/source/_integrations/humidifier.markdown @@ -23,7 +23,7 @@ The `humidifier` integration is built for the controlling and monitoring of humi ## Device class -The device class defines how the entity is represented on the [dashboard](/dashboards/). This can be modified in the [customize section](/docs/configuration/customizing-devices/). For example, different states may be represented by different icons, colors, or text. +{% include integrations/device_class_intro.md %} The screenshot shows different text and UI for different device classes for humidifiers: diff --git a/source/_integrations/media_player.markdown b/source/_integrations/media_player.markdown index d6bf08e5951..cf1295695a7 100644 --- a/source/_integrations/media_player.markdown +++ b/source/_integrations/media_player.markdown @@ -185,7 +185,7 @@ Allows to group media players together for synchronous playback. Only works on s ### Device class -The device class defines how the entity is represented on the [dashboard](/dashboards/). This can be modified in the [customize section](/docs/configuration/customizing-devices/). For example, different states may be represented by different icons, colors, or text. +{% include integrations/device_class_intro.md %} The following device classes are supported for media players: diff --git a/source/_integrations/number.markdown b/source/_integrations/number.markdown index e1ec775fbdf..636ff6316ed 100644 --- a/source/_integrations/number.markdown +++ b/source/_integrations/number.markdown @@ -25,7 +25,7 @@ If you are looking for a way to create a number entity, please take a look at th ## Device class -The device class defines how the entity is represented on the [dashboard](/dashboards/). This can be modified in the [customize section](/docs/configuration/customizing-devices/). For example, different states may be represented by different icons, colors, or text. +{% include integrations/device_class_intro.md %} The following device classes are supported for numbers: diff --git a/source/_integrations/sensor.markdown b/source/_integrations/sensor.markdown index cb5c550c05c..83c1b091acc 100644 --- a/source/_integrations/sensor.markdown +++ b/source/_integrations/sensor.markdown @@ -22,7 +22,7 @@ Some of these sensors are built-in to Home Assistant, some are created automatic ## Device class -The device class defines how the entity is represented on the [dashboard](/dashboards/). This can be modified in the [customize section](/docs/configuration/customizing-devices/). For example, different states may be represented by different icons, colors, or text. +{% include integrations/device_class_intro.md %} The screenshot shows different icons representing different device classes for sensors: diff --git a/source/_integrations/switch.markdown b/source/_integrations/switch.markdown index d81c418bd97..dfd32c369da 100644 --- a/source/_integrations/switch.markdown +++ b/source/_integrations/switch.markdown @@ -27,7 +27,7 @@ Keeps track which switches are in your environment, their state and allows you t ## Device class -The device class defines how the entity is represented on the [dashboard](/dashboards/). This can be modified in the [customize section](/docs/configuration/customizing-devices/). For example, different states may be represented by different icons, colors, or text. +{% include integrations/device_class_intro.md %} The following device classes are supported for switches: diff --git a/source/_integrations/update.markdown b/source/_integrations/update.markdown index 57b2cc9d366..6b67d7f775f 100644 --- a/source/_integrations/update.markdown +++ b/source/_integrations/update.markdown @@ -56,7 +56,7 @@ information on the update state: ## Device class -The device class defines how the entity is represented on the [dashboard](/dashboards/). This can be modified in the [customize section](/docs/configuration/customizing-devices/). For example, different states may be represented by different icons, colors, or text. +{% include integrations/device_class_intro.md %} The following device classes are supported for update entities: diff --git a/source/_integrations/valve.markdown b/source/_integrations/valve.markdown index 0ed0a7a745b..3bab9def981 100644 --- a/source/_integrations/valve.markdown +++ b/source/_integrations/valve.markdown @@ -22,7 +22,7 @@ The valve entity in Home Assistant provides an interface to control valves such ## Device class -A device class defines how the entity is represented on the [dashboard](/dashboards/). This can be modified in the [customize section](/docs/configuration/customizing-devices/). For example, different states may be represented by different icons, colors, or text. +{% include integrations/device_class_intro.md %} The following device classes are supported for valves: