From 2f274258436269e75c7afdf96e8d4e29c7e4e7fa Mon Sep 17 00:00:00 2001 From: "Steven B." <51370195+sdb9696@users.noreply.github.com> Date: Wed, 4 Sep 2024 22:07:34 +0100 Subject: [PATCH] Update tplink docs regarding Unavailable entities (#34505) Co-authored-by: J. Nick Koston --- source/_integrations/tplink.markdown | 13 +++++++++++++ 1 file changed, 13 insertions(+) diff --git a/source/_integrations/tplink.markdown b/source/_integrations/tplink.markdown index 0c7deaed884..78fc910ec3d 100644 --- a/source/_integrations/tplink.markdown +++ b/source/_integrations/tplink.markdown @@ -75,6 +75,19 @@ Devices not listed below may work but if you encounter issues submit a bug repor [^2]: Newer versions require authentication [^3]: Devices may work across TAPO/KASA branded hubs +## Unavailable entities + +Some entities might be showing as Unavailable if they have been removed from the integration. + +### Total consumption + +This entity is only reported by older kasa devices. +Currently, Tapo devices and newer Kasa devices do not report total consumption, although briefly during 2024.6, they incorrectly reported today's consumption as "total consumption." You can safely delete this entity if it is reported as unavailable on a newer Kasa or Tapo device. + +### Update + +This entity has been removed from the integration due to stability issues, calling the TPLink cloud API to check for updates. It will be replaced in a future release with a new Update entity, but if you have an Unavailable entity ID starting with `binary_sensor.` and ending with `update`, you can safely delete it. + ## Light effects If light effects are supported by a device they can be selected from the bottom of the light card.