From d6cdd63b4952c69f64764ab28b1d922eeeb89ef3 Mon Sep 17 00:00:00 2001
From: ha14937 <56581105+ha14937@users.noreply.github.com>
Date: Mon, 6 Jan 2020 02:04:27 -0500
Subject: [PATCH] HS110 clarifications (#11642)

Hi all - my first proposed change, and it's minor. I ran into this issue where I misread the original and believed other devices (HS103's in my case) were supported for everything (control and sensors) when it's really just the HS110 that can create sensors. Anyway, I thought I would make it more clear for anyone else who may have misread it like I did. Cheers!
---
 source/_integrations/tplink.markdown | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/source/_integrations/tplink.markdown b/source/_integrations/tplink.markdown
index 8a315124467..3fb5d2860ea 100644
--- a/source/_integrations/tplink.markdown
+++ b/source/_integrations/tplink.markdown
@@ -30,7 +30,7 @@ The following devices are known to work with this component.
 - HS100
 - HS103
 - HS105
-- HS110
+- HS110 (The only device capable or reporting energy usage data to template sensors)
 
 ### Strip (Multi-Plug)
 
@@ -129,7 +129,7 @@ tplink:
 
 ## Extracting Energy Sensor data
 
-In order to get the power consumption readings from supported devices, you'll have to create a [template sensor](/integrations/switch.template/).
+In order to get the power consumption readings from a TP-Link HS110 device, you'll have to create a [template sensor](/integrations/switch.template/).
 In the example below, change all of the `my_tp_switch`'s to match your device's entity ID.
 
 {% raw %}