From 5a19d8505657811f9beefa8dc8c9a568c22ed9a0 Mon Sep 17 00:00:00 2001 From: Raman Gupta <7243222+raman325@users.noreply.github.com> Date: Thu, 26 Aug 2021 13:29:13 -0400 Subject: [PATCH] Add missed references to template integration docs (#19091) --- source/_integrations/template.markdown | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/source/_integrations/template.markdown b/source/_integrations/template.markdown index 715dccf25ac..ba2cb017568 100644 --- a/source/_integrations/template.markdown +++ b/source/_integrations/template.markdown @@ -40,7 +40,7 @@ Sensors, binary (on/off) sensors, numbers and selects are covered on this page. - [Vacuum](/integrations/vacuum.template/) - [Weather](/integrations/weather.template/) -Sensor, binary sensor, number and select template entities are defined in your YAML configuration files, directly under the `template:` key and cannot be configured via the UI. You can define multiple configuration blocks as a list. Each block defines sensor/binary sensor/number entities and can contain an optional update trigger. +Sensor, binary sensor, number and select template entities are defined in your YAML configuration files, directly under the `template:` key and cannot be configured via the UI. You can define multiple configuration blocks as a list. Each block defines sensor/binary sensor/number/select entities and can contain an optional update trigger. _For old sensor/binary sensor configuration format, [see below](#legacy-binary-sensor-configuration-format)._ @@ -224,7 +224,7 @@ select: type: boolean default: false "[all sensor, binary sensor, number, select entities]": - description: Fields that can be used above for sensors, binary sensors, and numbers. + description: Fields that can be used above for sensors, binary sensors, numbers, and selects. required: false type: map keys: