FazBrowse GitHub Viewer | Trending |
URL:
| Home
Tools: [Download Repo ZIP]   [Original HTTPS Page]

Tapo L535E doesn't expose "usage" data · Issue #1548 · python-kasa/python-kasa · GitHub

Repository navigation

Tapo L535E doesn't expose "usage" data #1548

Closed as not planned
Closed as not planned

Description

Split from: #1545
Possibly related to: #1511

Firmware version: 1.1.8 Build 240708 Rel.165207
Hardware version: 3.0
python-kasa version: 0.10.2

After integrating the Lamp into Home Assistant via the TP-Link integration I notice that all the main features were available except for the power consumption. As per other (not Tapo) devices, I was expecting an entry in the Home Assistant energy module to see the power consumption overtime.

Reading this documentation I discovered that despite this library reads the get_device_usage (containing the required metrics for this lamp) via the DeviceModule, it seems the data is not properly exposed.

As a consequence:

  1. I'm not able to see an entry in the Home Assistant energy module
  2. I was not able to read the power consumption via the cli of this library as the energy command is based on the energy_monitoring component not offered by this device while the usage command is for the iot devices and not the smart devices

Activity

  1. fantandrea commented on Jun 2, 2025

    ContributorAuthor

    Hi @rytilahti as required I've opened a new issue with more details about the support issues mentioned in #1545

    A few days ago I've also sent you other details on this subject via discord.

  2. github-actions commented on Sep 1, 2025

    There hasn't been any activity on this issue recently. This issue has been automatically marked as stale because of that. It will be closed if no further activity occurs.
    Please make sure to update to the latest python-kasa version and check if that solves the issue.
    Thank you for your contributions.

  3. ZeliardM commented on Sep 1, 2025

    Collaborator

    @fantandrea I noticed after looking at the feature file that was submitted, the get_device_usage is there, but the actual energy_monitoring usage is get_energy_usage.

    The energy_monitoring component is not in the fixture so therefore the module is not supported.

    If you run the discover command again the device with the --debug flag it should notate this. From my looks, the only devices that support the energy_monitoring are specific outlets and power strips not bulbs.

    The required component, energy_monitoring, is missing and not reported by the device. This is not something the python-kasa library filters out or removes, the device simply does not support it from my understanding. Is there anything in the Tapo App that makes you think it should otherwise? For plugs or power strips that support it, there is an energy usage section that lists and shows voltage and wattage for timeframes.

  4. fantandrea commented on Sep 1, 2025

    ContributorAuthor

    Hi @ZeliardM, I was already working on it while in contact with your colleague.
    My device has the get_energy_usage exposed, the problem is that your tool doesn't discovery it because it tries to extract it only if the energy_monitoring is part of the list of components (that looks reasonable but it's not the case for my device).
    I currently have a working integration with my home assistant server where I bypassed the check for the component list and I'm able to get real time values for the instant power consumption.

    I didn't push any fix yet because this to me looks like a bug in the device (indeed from the official app I'm not able to see the information that I was able to extract with a customized version of your tool). I've opened a support request to TP Link that is still ongoing, to understand if they're going to release a patch for the device or what is a reliable way to understand if the get_energy_usage is available.

  5. ZeliardM commented on Sep 1, 2025

    Collaborator

    Ah, I see. I was going through and had a user with my Homebridge plugin that has a L535E bulb and I wanted thank you for submitting the fixture file.

    It's not my tool, I just submit a bunch of stuff since I use their library in my Homebridge plugin. I've been trying to get a better understanding of things and thought I would reach out. No offense meant.

    I would say if the device actually reports it and it's consistent, putting together a PR with the changes and submitting it wouldn't hurt I think. They are usually pretty open to improvements if they are there. It seems that energy_monitoring is only if the Tapo/Kasa App shows it but the device itself may support get_energy_usage regardless of if the app shows it and that would be a big benefit to others I believe.

    If you have other bulbs or devices that this also reports from not just the L535E, I would suggest also building the fixes into the testing functions as well so that this could be applied accordingly across different devices. This would allow for updated device fixtures and correct reporting for new devices as well.

  6. fantandrea commented on Sep 1, 2025

    ContributorAuthor

    Hi @ZeliardM the PR of just removing the check doesn't looks a reliable one and can cause issues with other devices, that's why I didn't push it as it is. As mentioned I've an ongoing support request with the device manufacturer, as soon as I get official answers from the vendor I'll give an update here or make a more reliable PR

  7. github-actions commented on Dec 1, 2025

    There hasn't been any activity on this issue recently. This issue has been automatically marked as stale because of that. It will be closed if no further activity occurs.
    Please make sure to update to the latest python-kasa version and check if that solves the issue.
    Thank you for your contributions.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions


      Back | FazBrowse Home | New Git URL