@rytilahti Not sure if I need to tag you to see this. Just wondering if these will be usable by this project or if I should return them.

Thanks so much!

There is no recent PR, as dimmers generally have been supported for a long time. I cannot help much without some more specifics:

• What's the exact error message you are getting? You could also try using --debug to get a bit more output, e.g., kasa --debug --host <addr>.
• Is discovery working? If no, you could try if it gets discovered with Adding support for the new encryption protocol (updated version) #267
• If you can do a packet trace from the device's communications, you could check out if it's using the port 9999 for communication.

So I'm not sure why it didn't work last time. Ping was fine but it errored out with failed to connect. I tried again today after plugging it in again and looks like all is working properly. Luckily it wasn't on the new protocol.

Please see my earlier comments in this discussion, it would be great to have a fixture file for the test suite. Also, would you try if the kasa cli tool works fine with the device?

The device type is detected using the dev_name key in system information (https://github.com/python-kasa/python-kasa/blob/master/kasa/discover.py#L223), so if you execute kasa --host <ip addr> sysinfo on your KP405 what does it output?

See https://python-kasa.readthedocs.io/en/latest/#getting-started - I think the easiest way is to install it on the host or any other device that has a working python setup. Alternatively, you could find a way to access the container running your homeassistant installation (using the terminal or the ssh addon, I think), but that might be more complicated than simply installing this project locally for testing.