From 0be2778d7b188e6c44e2f55e133576feaf5930b8 Mon Sep 17 00:00:00 2001 From: akasma74 Date: Thu, 28 Nov 2019 11:11:43 +0000 Subject: [PATCH] clarify options' use (#11189) * clarify options' use The current description looks outdated to me because: 1. In Lovelace the time/date is not displayed when we open default_view 2. If only - 'time' specified, no `sensor.date` or anything else exists (and it's not clear as the configuration variable name is `display_options` (maybe now it's better to make it deprecated and change to `options` or something)? * Update source/_integrations/time_date.markdown typo Co-Authored-By: Franck Nijhof * resolving #1 --- source/_integrations/time_date.markdown | 5 ++--- 1 file changed, 2 insertions(+), 3 deletions(-) diff --git a/source/_integrations/time_date.markdown b/source/_integrations/time_date.markdown index 31563206955..4261bf2807f 100644 --- a/source/_integrations/time_date.markdown +++ b/source/_integrations/time_date.markdown @@ -9,9 +9,8 @@ ha_release: pre 0.7 ha_qa_scale: internal --- -The time and date (`time_date`) sensor platform simple displays the time in various formats, the date, or both. - -To enable this sensor in your installation, add the following to your `configuration.yaml` file: +The time and date (`time_date`) sensor platform adds one or more sensors to your Home Assistant state machine. +To have these sensors available in your installation, add the following to your `configuration.yaml` file (each option creates a separate sensor that contains appropriate data): ```yaml # Example configuration.yaml entry