driver/power: Add support for TAPO devices by MarekSzczypinski · Pull Request #1630 · labgrid-project/labgrid

MarekSzczypinski · 2025-03-09T21:53:07Z

Description
This pull request adds support for TAPO/TP-Link programmable power strips and single socket devices using python-kasa.

This feature is used to manage TAPO power strip or single socket from Labgrid. It adds tapo model to NetworkPowerPort. As all Tapo devices require credentials this feature requires user to set KASA_LOGIN and KASA_PASSWORD env variables to work (see python-kasa website for details).

I have tested it manually with Labgrid (client build and run wth Python3.9 and 3.12). Additionally I wrote unit tests for it and also I have run the tox -r command (Python: 3.9, 3.10, 3.11 and 3.12). All worked without errors and all the tests passed.

I have used this driver with Tapo P300 power strip and Tapo P100 socket. So it should work with all Tapo strips and sockets.

While there already is support for KASA/TP-Link products in Labgrid using python-kasa, it doesn't work with TAPO devices as they apparently use some other protocol and require password and login to work. In order to not complicate the implementation of tplink model I decided to implement support for Tapo devices as a separate one. Additionally KASA products are not available in Europe so I didn't have means to test current (tplink) solution, which was one more reason to separate this into another model.

Because of the necessity to create credentials this solution is a bit more complicated than the tplink model.

This solution is based on the tplink model. Two key differences are:

Support for single sockets like P100 that ignores value of index
Requires Tapo cloud credentials in order to communicate with devices

Checklist

Documentation for the feature
Tests for the feature

The arguments and description in doc/configuration.rst have been updated

Add a section on how to use the feature to doc/usage.rst

Add a section on how to use the feature to doc/development.rst

PR has been tested

Man pages have been regenerated

Emantor · 2025-07-14T10:14:55Z

+    # Somewhere between python-kasa 0.7.7 and 0.10.2 the API changed
+    # Labgrid on Python <= 3.10 uses python-kasa 0.7.7
+    # Labgrid on Python >= 3.11 uses python-kasa 0.10.2
+    if sys.version_info < (3, 11):


We should instead check the python-kasa version instead of relying on the indirect python dependency here.

Done. All tests as written in the description of this PR were re-done.

Hey, @Emantor. Any update on this one? :-)

@Emantor just a friendly reminder that I'm still waiting for review ;-)

Hi @Emantor, still waiting for any comment ;)

Hey @Emantor, just a friendly reminder (checked with pylint and tox -r)

@Emantor maybe someone else would have time to take a look?

@Emantor just a friendly reminder that I'm still waiting for review ;-)

@Emantor ping :)

@Emantor friendly reminder that I'm still here waiting.

MarekSzczypinski · 2025-09-28T21:22:03Z

No changes - just updating to the master branch

MarekSzczypinski · 2025-11-06T22:48:59Z

Yet another update to master, nothing changed in my MR

MarekSzczypinski · 2025-11-11T13:01:44Z

Added pylint disables for python-kasa version compatibility. This suppresses unexpected-keyword-arg warnings for uses_http and http_port parameters that exist in different python-kasa API versions. Also files are now ruff formatted.

tox -r as been re-run and code has been checked with pylint on python 3.9 through 3.14

MarekSzczypinski · 2025-11-18T08:39:02Z

Yet another update to master, nothing changed in my MR.
tox -r as been re-run and code has been checked with pylint on python 3.9 through 3.14

MarekSzczypinski · 2025-11-24T09:00:15Z

Yet another update to master, nothing changed in my MR.
tox -r as been re-run and code has been checked with pylint on python 3.9 through 3.14

MarekSzczypinski · 2025-12-03T08:53:24Z

Yet another update to master, nothing changed in my MR.
tox -r as been re-run and code has been checked with pylint on python 3.9 through 3.14

MarekSzczypinski · 2025-12-19T09:23:09Z

Yet another update to master, nothing changed in my MR.
tox -r as been re-run and code has been checked with pylint on python 3.9 through 3.14

codecov · 2026-01-30T13:39:39Z

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 46.1%. Comparing base (0507604) to head (eb6f6f5).
✅ All tests successful. No failed tests found.

Additional details and impacted files

@@           Coverage Diff            @@
##           master   #1630     +/-   ##
========================================
+ Coverage    46.0%   46.1%   +0.1%     
========================================
  Files         180     181      +1     
  Lines       14464   14514     +50     
========================================
+ Hits         6654    6704     +50     
  Misses       7810    7810

Flag	Coverage Δ
3.10	`46.1% <96.0%> (+0.1%)`	⬆️
3.11	`46.1% <96.0%> (+0.1%)`	⬆️
3.12	`46.1% <96.0%> (+0.1%)`	⬆️
3.13	`46.1% <96.0%> (+0.1%)`	⬆️
3.14	`46.1% <96.0%> (+0.1%)`	⬆️

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Harness.
📢 Have feedback on the report? Share it here.

MarekSzczypinski · 2026-02-20T08:23:50Z

I've done unit tests refactoring for my driver. Apart from that - bunch of updates to current master branch.

MarekSzczypinski · 2026-03-09T08:46:35Z

Yay!! Happy anniversary to this PR! ;-)

Emantor · 2026-03-19T14:37:11Z

Please do a clean rebase on top of master without the merge commits. Sorry for the wait.

MarekSzczypinski · 2026-03-24T09:03:49Z

Please do a clean rebase on top of master without the merge commits. Sorry for the wait.

@Emantor Done. No worries :)

Emantor · 2026-03-30T09:13:11Z

IMO the commits can also be squashed down into one commit or do you see value in keeping the individual commits?

MarekSzczypinski · 2026-03-30T15:46:09Z

IMO the commits can also be squashed down into one commit or do you see value in keeping the individual commits?

For sure, but I've already rebased the branch anyways.

Edit:
@Emantor OMG, you didn't mean the update-to-main merge commits XD
Yes, my feature's commits can be squashed. I don't mind :)

threexc · 2026-04-13T19:37:55Z

Hi,

Following the community call, I've been looking this over and trying to compare it to my own PR to extend the tplink driver support: #1693

I don't think that the functionality added here overlaps with #1693, as despite the devices being similar I believe there are different protocols at play.

To test, I used the same HS103 I'd used previously with my PR, and the following exporter config:

smartplug-1:
  location: shelf
  kasa-smartplug-1:
    cls: 'NetworkPowerPort'
    model: 'tplink'
    host: '192.168.40.5'

and I see this error after changing to model: tapo with your branch, re-exporting, and running labgrid-client -p smartplug-test pw on:

labgrid-client: error: failed to create NetworkPowerPort for target 'Target(name='smartplug-test', env=None)' using {'host': '192.168.40.5', 'model': 'tapo'}
This is likely caused by an error in the environment configuration or invalid
resource information provided by the coordinator.

We may be able to combine some of the logic in both PRs, but it is worth noting too that they don't follow exactly the same flow - for example, the existing tplink driver makes async Discover.discover_single() calls as part of the set/get methods, while I don't see that here.

Maybe we need to align the two sets of code and implement a tplink_common module? Alternatively, we combine them into a single kasa module to avoid duplication at all? There is some appeal to making them distinct so that users can find them by product name, but maybe not for maintenance :)

@jluebbe @Emantor thoughts?

Signed-off-by: Marek Szczypiński <markacy@gmail.com>

Suppress unexpected-keyword-arg warnings for uses_http and http_port parameters that exist in different python-kasa API versions. Additionally tapo.py and test_tapo.py are now ruff formatted. Signed-off-by: Marek Szczypiński <markacy@gmail.com>

Signed-off-by: Marek Szczypiński <markacy@gmail.com>

MarekSzczypinski force-pushed the feature/add-tapo-support branch from d41c2fa to e544fc0 Compare March 23, 2025 20:27

MarekSzczypinski changed the title ~~Add support for TAPO devices~~ driver/power: Add support for TAPO devices May 4, 2025

Emantor requested changes Jul 14, 2025

View reviewed changes

MarekSzczypinski requested a review from Emantor August 14, 2025 06:48

onurcelep mentioned this pull request Mar 19, 2026

labgrid/driver/power: Add Tapo(Kasa) smart plug support #1555

Closed

7 tasks

MarekSzczypinski force-pushed the feature/add-tapo-support branch from cb34dd5 to 44f6bb1 Compare March 23, 2026 09:31

Emantor self-assigned this Mar 30, 2026

MarekSzczypinski force-pushed the feature/add-tapo-support branch 2 times, most recently from b72ca70 to 1d2c4ac Compare April 1, 2026 22:21

MarekSzczypinski force-pushed the feature/add-tapo-support branch from 1d2c4ac to a3df1cc Compare April 8, 2026 08:20

MarekSzczypinski force-pushed the feature/add-tapo-support branch from a3df1cc to 766e8f5 Compare May 5, 2026 20:03

MarekSzczypinski force-pushed the feature/add-tapo-support branch from 130ca1d to eb6f6f5 Compare June 8, 2026 08:17

MarekSzczypinski added 3 commits June 15, 2026 08:56

Add support for TAPO devices

4fabef8

Signed-off-by: Marek Szczypiński <markacy@gmail.com>

Fix regression

c81ca4b

Signed-off-by: Marek Szczypiński <markacy@gmail.com>

refactor: directly test kasa version in TAPO power model

6fe173e

Signed-off-by: Marek Szczypiński <markacy@gmail.com>

MarekSzczypinski added 2 commits June 15, 2026 08:56

refactor(tapo): unit tests refactored, typo fixed

051e0f5

Signed-off-by: Marek Szczypiński <markacy@gmail.com>

MarekSzczypinski force-pushed the feature/add-tapo-support branch from eb6f6f5 to 051e0f5 Compare June 15, 2026 06:56

Uh oh!

Conversation

MarekSzczypinski commented Mar 9, 2025

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

MarekSzczypinski commented Sep 28, 2025

Uh oh!

MarekSzczypinski commented Nov 6, 2025

Uh oh!

MarekSzczypinski commented Nov 11, 2025

Uh oh!

MarekSzczypinski commented Nov 18, 2025

Uh oh!

MarekSzczypinski commented Nov 24, 2025

Uh oh!

MarekSzczypinski commented Dec 3, 2025

Uh oh!

MarekSzczypinski commented Dec 19, 2025

Uh oh!

codecov Bot commented Jan 30, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Codecov Report

Uh oh!

MarekSzczypinski commented Feb 20, 2026

Uh oh!

MarekSzczypinski commented Mar 9, 2026

Uh oh!

Emantor commented Mar 19, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

MarekSzczypinski commented Mar 24, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

Emantor commented Mar 30, 2026

Uh oh!

MarekSzczypinski commented Mar 30, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

threexc commented Apr 13, 2026

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

3 participants

codecov Bot commented Jan 30, 2026 •

edited

Loading

Emantor commented Mar 19, 2026 •

edited

Loading

MarekSzczypinski commented Mar 24, 2026 •

edited

Loading

MarekSzczypinski commented Mar 30, 2026 •

edited

Loading