From afd1e37956c54a38b143fca0c6d0e33db8dc1204 Mon Sep 17 00:00:00 2001 From: akasma74 Date: Thu, 6 Feb 2020 09:22:02 +0000 Subject: [PATCH] added note about name variable (#11970) * added note about name variable I though that name is just for frontend and spent some time finding out where my sensor had gone when I had changed its name. Hope it will save others' time. Actually, I don't think this component's approach is great - would be much more intuitive to have name as a key of a dictionary (as with template sensors, for example) and a friendly_name for UI. Unfortunately, there are many of similar components - perhaps they are older than current template sensor's implementation? * links -> relative * :pencil2: Tweak Co-authored-by: Klaas Schoute --- source/_integrations/history_stats.markdown | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/source/_integrations/history_stats.markdown b/source/_integrations/history_stats.markdown index 0b6a2db934c..2b0df659073 100644 --- a/source/_integrations/history_stats.markdown +++ b/source/_integrations/history_stats.markdown @@ -47,7 +47,7 @@ state: required: true type: string name: - description: Name displayed on the frontend. + description: Name displayed on the frontend. Note that it is used by Home Assistant to generate sensor's `object_id` so it is advisable to choose a unique one and change name for frontend using [customization](/docs/configuration/customizing-devices/#friendly_name) or via [Lovelace](/lovelace/entities/#name). required: false default: unnamed statistics type: string