building block entities (#29181)

source/_integrations/humidifier.markdown

@@ -14,6 +14,8 @@ ha_integration_type: entity
 
 The `humidifier` integration is built for the controlling and monitoring of humidifiers, dehumidifiers, and hygrostat devices.
 
+{% include integrations/building_block_integration.md %}
+
 ## Services
 
 ### Humidifier services

source/_integrations/image.markdown

@@ -12,3 +12,5 @@ ha_integration_type: entity
 ---
 
 The image integration allows other integrations to display a static image.
+
+{% include integrations/building_block_integration.md %}

source/_integrations/image_processing.markdown

@@ -13,6 +13,8 @@ ha_integration_type: entity
 
 Image processing enables Home Assistant to process images from [cameras](/integrations/#camera). Only camera entities are supported as sources.
 
+{% include integrations/building_block_integration.md %}
+
 ## ALPR
 
 ALPR entities have a vehicle counter attribute `vehicles` and all found plates are stored in the `plates` attribute.

source/_integrations/lawn_mower.markdown

@@ -13,7 +13,7 @@ ha_integration_type: entity
 
 The lawn mower integration allows the control of robotic lawn mowers to be reflected within Home Assistant.
 
-Please note, the lawn mower integration cannot be directly used; you cannot create your own lawn mower entities using this integration. This integration is a building block for other integrations to use, enabling them to create lawn mower entities for you.
+{% include integrations/building_block_integration.md %}
 
 ## Services
 

source/_integrations/light.markdown

@@ -13,6 +13,8 @@ ha_integration_type: entity
 
 This integration allows you to track and control various light bulbs. Read the integration documentation for your particular light hardware to learn how to enable it.
 
+{% include integrations/building_block_integration.md %}
+
 ### Default turn-on values
 
 To set the default color, brightness and transition values when the light is turned on, create a custom `light_profiles.csv`, normally located in the default configuration folder where you find `configuration.yaml`.

source/_integrations/lock.markdown

@@ -16,6 +16,8 @@ Keeps track which locks are in your environment, their state and allows you to c
 - Maintains a state per lock and a combined state `all_locks`.
 - Registers services `lock.lock`, `lock.unlock` and `lock.open` (unlatch) to control locks.
 
+{% include integrations/building_block_integration.md %}
+
 ### Services
 
 A lock integration provides the following services:

source/_integrations/mailbox.markdown

@@ -13,3 +13,5 @@ Mailboxes provide a list of messages with short information about each. Mailbox
 Home Assistant currently supports only the [Asterisk Voicemail](/integrations/asterisk_mbox/) mailbox.
 
 Each mailbox also provides an entity to indicate the number of messages available on the main page.
+
+{% include integrations/building_block_integration.md %}

source/_integrations/media_player.markdown

@@ -13,6 +13,8 @@ ha_integration_type: entity
 
 Interacts with media players on your network.
 
+{% include integrations/building_block_integration.md %}
+
 ## Services
 
 ### Media control services

source/_integrations/notify.markdown

@@ -15,6 +15,8 @@ The `notify` integration makes it possible to send notifications to a wide varie
 
 If you want to send notifications to the Home Assistant web interface, you may use the [Persistent Notification integration](/integrations/persistent_notification/). The Persistent Notification integration is also available as an automatically configured notifier. See [its documentation](/integrations/persistent_notification/) for more details.
 
+{% include integrations/building_block_integration.md %}
+
 ## Service
 
 Once loaded, the `notify` platform will expose a service that can be called to send notifications.

source/_integrations/number.markdown

@@ -14,9 +14,9 @@ ha_integration_type: entity
 
 Keeps track on `number` entities in your environment, their state, and allows you to control them. This integration allows other integrations to get a value input from user within a range.
 
-Number entities cannot be implemented manually, but can be provided by other
-integrations. If you are looking for a way to create a number entity,
-please take a look at the [Number helper](/integrations/input_number).
+{% include integrations/building_block_integration.md %}
+
+If you are looking for a way to create a number entity, please take a look at the [Number helper](/integrations/input_number).
 
 ## Device Class
 

source/_integrations/remote.markdown

@@ -16,6 +16,8 @@ Keeps track which remotes are in your environment, their state and allows you to
 - Maintains a state per remote and a combined state `all_remotes`.
 - Registers services `remote/turn_on`, `remote/turn_off`, `remote/toggle`, and `remote/send_command` to control remotes.
 
+{% include integrations/building_block_integration.md %}
+
 ### Use the services
 
 Go to the **Developer Tools**, then to **Call Service** in the frontend, and choose `remote/turn_on`, `remote/turn_off`, or `remote/toggle` from the list of available services (**Available services:** on the left). Enter something like the sample below into the **Service Data** field and hit **Call Service**.