Skip to content

Conversation

@sdb9696
Copy link
Collaborator

@sdb9696 sdb9696 commented Dec 4, 2023

No description provided.

@sdb9696 sdb9696 mentioned this pull request Dec 4, 2023
@codecov
Copy link

codecov bot commented Dec 4, 2023

Codecov Report

All modified and coverable lines are covered by tests ✅

Comparison is base (01f3827) 79.66% compared to head (2bd670b) 79.66%.

Additional details and impacted files
@@           Coverage Diff           @@
##           master     #566   +/-   ##
=======================================
  Coverage   79.66%   79.66%           
=======================================
  Files          36       36           
  Lines        2995     2995           
  Branches      779      779           
=======================================
  Hits         2386     2386           
  Misses        536      536           
  Partials       73       73           

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

Copy link
Member

@rytilahti rytilahti left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks like dump_devinfo is currently broken for me:

Testing Call(module='child_device_component_list', method='get_child_device_component_list')..FAIL Unable to connect to the device: 192.168.xx.xx: 'NoneType' object has no attribute 'cookies'
Unable to query all successes at once: Unable to connect to the device: 192.168.xx.xx: 'NoneType' object has no attribute 'cookies'

The device responds with {"error_code":-1002} to that call and fails after retries.

@sdb9696
Copy link
Collaborator Author

sdb9696 commented Dec 4, 2023

Hmm that's strange, I got a similar error testing my HA changes today. I'll spend a bit more time on this tomorrow.

@sdb9696 sdb9696 marked this pull request as draft December 4, 2023 19:52
@sdb9696
Copy link
Collaborator Author

sdb9696 commented Dec 5, 2023

I think this should be fixed in #568. I'm guessing the AesTransport returns the error code pre-decryption so it raises an error from the transport which hit a bug in the retry logic (introduced to make mypy happy). This does mean it'll probably retry this query even though it's returning a non-authentication error code so there's probably a bit of work to do interpreting the error codes. Sadly I can't test with my device anymore.

I'll rebase this once #568 is in so you can re-test.

@sdb9696 sdb9696 marked this pull request as ready for review December 5, 2023 07:18
Copy link
Member

@rytilahti rytilahti left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Seems to work as expected, updated #562. Thanks again!

@sdb9696 sdb9696 force-pushed the readd_tapo_regional_fixture branch from 71f81c6 to c97a872 Compare December 5, 2023 15:14
@sdb9696 sdb9696 marked this pull request as draft December 5, 2023 15:17
@sdb9696
Copy link
Collaborator Author

sdb9696 commented Dec 5, 2023

Not ready for merge yet. It seems this dump_devinfo is still appending .smart to the fixture name.

EDIT: Ok this is ready for merge. Made some tweaks to tell users to put the file in the smart subdirectory.

@sdb9696 sdb9696 force-pushed the readd_tapo_regional_fixture branch from c97a872 to 2bd670b Compare December 5, 2023 15:34
@sdb9696 sdb9696 marked this pull request as ready for review December 5, 2023 15:37
@rytilahti rytilahti merged commit 5e2fcd2 into python-kasa:master Dec 5, 2023
@sdb9696 sdb9696 deleted the readd_tapo_regional_fixture branch December 6, 2023 19:25
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