Device class intro para: apply reuse (#32982)

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.

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:
 

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:
 

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:
 

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:
 

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:
 

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:
 

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:
 

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:
 

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:
 

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:
 

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: