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

Add P125M fixture for firmware 1.4.4 by HarryPehkonen · Pull Request #1746 · python-kasa/python-kasa · GitHub

Add P125M fixture for firmware 1.4.4 - #1746

Open
HarryPehkonen wants to merge 2 commits into
python-kasa:masterfrom
HarryPehkonen:feat/p125m-1.4.4-fixture
Open

Add P125M fixture for firmware 1.4.4#1746
HarryPehkonen wants to merge 2 commits into
python-kasa:masterfrom
HarryPehkonen:feat/p125m-1.4.4-fixture

Conversation

Copy link
Copy Markdown

Summary

Adds a device fixture for the Tapo P125M on firmware 1.4.4 Build 260521 Rel.100818 (US), captured from a live device via devtools/dump_devinfo.py.

The existing P125M fixture covers firmware 1.1.0 (Build 231009). This newer firmware:

  • reports matter component v3 (vs v2 in the old fixture)
  • adds the get_matter_setup_info module (Matter setup code/payload)

Validation

  • Fixture generated with python -m devtools.dump_devinfo --host <ip> --autosave (credentials redacted by the tool's standard redactors)
  • Full test suite filtered to P125M: 488 passed, 8 skipped, 0 failed
488 passed, 8 skipped, 23246 deselected, 47611 warnings

Newer firmware (Build 260521) than the existing 1.1.0 fixture.
Adds the get_matter_setup_info module and matter component v3.

codecov Bot commented Aug 25, 2026
edited
Loading

Copy link
Copy Markdown

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 93.29%. Comparing base (a29d061) to head (6a9478e).

Additional details and impacted files
@@           Coverage Diff           @@
##           master    #1746   +/-   ##
=======================================
  Coverage   93.29%   93.29%           
=======================================
  Files         157      157           
  Lines        9932     9932           
  Branches     1022     1022           
=======================================
  Hits         9266     9266           
  Misses        471      471           
  Partials      195      195           

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

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

HankB commented Aug 25, 2026

Copy link
Copy Markdown
Contributor

Good evening, I have just purchased several of these outlets. While configuring them via the Android app, I updated the firmware on the first two. On the third, I skipped that. While testing, I found that kasa was unable to communicate with the ones with updated firmware but did work with the one with original firmware.

  • updated firmware: 1.4.4 Build 260521 Rel.100818
  • firmware as received: 1.4.2 Build 251204 Rel. 103056
  • All are hardware version 1.0 (US)
  • kasa is as installed using pip install python-kasa and identifies itself as kasa, version 0.10.2 and is running in a venv on Debian Trixie.

Earlier today I saw a note (WRT Matter integration with HASS IIRC) that these had to be enabled in the app to share with other devices. In the Tapo Android app I found "Third Party Compatibility" which is a user setting, not per plug. I enabled that and found kasa now works with the updated outlets. However, it no longer works with the non-updated outlet.

(I'm sure the devs that work with this are likely more frustrated than myself with the state of things and I worry that some future update may render the plugs non-working again.)

In the mean time, I did not see any mention of this "feature" in the README on the repo. I found two mentions of "Third Party Compatibility" in readthedocs in reference to cameras and it appears that this behavior has now been incorporated into the P125M.

It would have been helpful if this was mentioned in the very clear instructions already in the README. Of course if I can be of any help with any sort of testing in the field, please let me know.

Thanks to all who are carrying on with this work.

best,

This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters. Learn more about bidirectional Unicode characters
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants


Back | FazBrowse Home | New Git URL