SimonWilkinson

The "broken" devices have a responsive web server on port 80, which claims to be "Server: SHIP 2.0"

Those failures look like problems with adding the new dependencies to poetry. Is there something that needs to happen to tell the builder that they are safe?

I did poetry add in order to get the new pyproject.toml, but didn't commit poetry.lock, as it seemed like there were a load of changes to other modules in there....

Thanks @kirichkov I think I finally got there in terms of the tests.

mypy running locally is happy with this, so I'm not sure what the problem is.

> Just wanted to check if this is likely to move forward and be integrated? I need to find the time to complete the necessary cleanup and testing. It's at...

I've opened pull request #117 which is a simple implementation of the new encryption protocol, currently tested with an HS110 and the command line interface. Comments appreciated.

@robbrad - so this will depend on how your broken plugs are configured. If they are associated with a kasa cloud account, you will need to use ```kasa --user --password...

Have a scan through and make sure there's nothing you'd rather not share. Providing you are using the PR with all of the changes, it won't log usernames or passwords....

Email is probably easiest - [email protected]