Skip to content

Feature request: Expose energy/usage sensors for Tapo L530E bulbs #1701

Description

@gugahdl

The L530E firmware returns usage and power consumption data via get_device_usage, but python-kasa does not currently expose these as features, so they don’t surface as sensors in Home Assistant. The Tapo mobile app shows runtime hours, kWh consumed today/7d/30d, and “saved energy” for these bulbs — all of that data is already coming back from the device.

Device info:
• Model: L530 (hw_ver 2.0)
• Firmware: 1.4.2 Build 260113 Rel.172011
• python-kasa: 0.10.2
• Home Assistant: 2026.5.3
Evidence from the HA diagnostics dump:

"get_device_usage": {
"time_usage": {
"today": 217,
"past7": 1404,
"past30": 1404
},
"power_usage": {
"today_mwh": 26444,
"past7_mwh": 175635,
"past30_mwh": 175635,
"today": 26,
"past7": 176,
"past30": 176
},
"saved_power": {
"today_mwh": 190556,
"today": 191,
"past7mwh": 1228365,
"past7": 1228,
"past30_mwh": 1228365,
"past30": 1228
}
}

What currently shows up for the L530E in HA (matches the kasa discover output in the docs): State, Brightness, Color temperature, Light effect, Signal Level, Overheated, Cloud connection, Device time, HSV, Auto-update, Light preset, Smooth on/off. No energy/ usage features.
Request: Expose time_usage and power_usage from get_device_usage as features so the HA tplink integration can surface them as runtime and energy sensors (consumption today / past 7 days / past 30 days). The "saved _power" block is nice-to-have but lower priority.
Happy to test a PR against my L530E if useful.

Related: #1150 (L630/L530 owners thread)

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions