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!
This commit is contained in:
ha14937 2020-01-06 02:04:27 -05:00 committed by Fabian Affolter
parent d383a54324
commit d6cdd63b49

View File

@ -30,7 +30,7 @@ The following devices are known to work with this component.
- HS100 - HS100
- HS103 - HS103
- HS105 - HS105
- HS110 - HS110 (The only device capable or reporting energy usage data to template sensors)
### Strip (Multi-Plug) ### Strip (Multi-Plug)
@ -129,7 +129,7 @@ tplink:
## Extracting Energy Sensor data ## 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. In the example below, change all of the `my_tp_switch`'s to match your device's entity ID.
{% raw %} {% raw %}