From 2d206f8fef701f22c6a8a81cd01a6b1d3ec4c01a Mon Sep 17 00:00:00 2001 From: Dubh Ad Date: Thu, 29 Oct 2020 14:57:54 +0000 Subject: [PATCH] Clarity edit (#15459) A few folks have replaced `my_tp_switch` with `switch.whale_heater`, and obviously errors abound at that point: > invalid slug switch.whale_heater(try switch_whale_heater) Trying to make it a bit clearer --- source/_integrations/tplink.markdown | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/source/_integrations/tplink.markdown b/source/_integrations/tplink.markdown index a611cf925a8..356a8220b0c 100644 --- a/source/_integrations/tplink.markdown +++ b/source/_integrations/tplink.markdown @@ -141,7 +141,7 @@ Devices that are confirmed to support Consumption Reading; 2. HS300 In order to get the power consumption readings from a TP-Link HS110 device, you'll have to create a [template sensor](/integrations/template/). -In the example below, change all of the `my_tp_switch`'s to match your device's entity ID. +In the example below, change all of the `my_tp_switch`'s to match your device's entity ID (without the domain). For example, if your entity is `switch.whale_heater` then replace `my_tp_switch` with `whale_heater`: {% raw %} ```yaml