Update tplink.markdown (#16080)

I just recently bought a TP-Link KP115 plug to monitor energy for my dishwasher since I had so much success monitoring energy for my washer with a HS110.  Using the same process I used on the washer, I was able to get energy monitoring for my dishwasher with the KP115.  I wanted to let the community know that there is another option for energy monitoring now that the HS110 is discontinued.
This commit is contained in:
codypet 2021-01-04 05:42:01 -05:00 committed by GitHub
parent 8e5d5ed86f
commit 82283f20e6
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23

View File

@ -38,6 +38,7 @@ Plugs are type `switch` when autodiscovery has been disabled.
- HS105 - HS105
- HS110 (This device is capable of reporting energy usage data to template sensors) - HS110 (This device is capable of reporting energy usage data to template sensors)
- KP105 - KP105
- KP115
### Strip (Multi-Plug) ### Strip (Multi-Plug)
@ -140,6 +141,7 @@ tplink:
Devices that are confirmed to support Consumption Reading; Devices that are confirmed to support Consumption Reading;
1. HS110 1. HS110
2. HS300 2. HS300
3. KP115
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 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 (without the domain). For example, if your entity is `switch.whale_heater` then replace `my_tp_switch` with `whale_heater`: 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`: