From 5edcd78e666fcf2eeae7c0a574e58710b9e99a19 Mon Sep 17 00:00:00 2001 From: Teemu R Date: Sun, 27 Jun 2021 17:32:29 +0200 Subject: [PATCH] Add a note about energy consumption info on tplink bulbs (#18237) --- source/_integrations/tplink.markdown | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/source/_integrations/tplink.markdown b/source/_integrations/tplink.markdown index 413919d05d8..a34f5d0e740 100644 --- a/source/_integrations/tplink.markdown +++ b/source/_integrations/tplink.markdown @@ -60,7 +60,7 @@ Plugs are type `switch` when autodiscovery has been disabled. ### Bulbs -Other bulbs may also work, but with limited color temperatures. If you find a bulb isn't reaching the full-color temperature boundaries, submit a bug report. +Other bulbs may also work, but with limited color temperatures. If you find a bulb isn't reaching the full-color temperature boundaries, submit a bug report. Bulbs do generally report some energy consumption information, see the entity state attributes to find out what information is available. - LB100 - LB110 @@ -150,6 +150,7 @@ Devices that are confirmed to support Consumption Reading; 1. HS110 2. HS300 3. KP115 +4. Bulbs (device-specific, only current power consumption is commonly available) 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`: