Teemu R.

Looks like it's not using the same communication protocol. Is the mobile app you are using called kasa or something else? Did you already try to do a traffic capture?...

Ouch, also for local communications? Or does it only communicate over some cloud endpoint, i.e., there's no direct communication between the app and the device?

@AntonyKing7D those paths (and the `TPLINK_SESSIONID`) look similar to the protocol implemented in #267 that was never finished. Maybe you could give it a try to see if that's really...

Yes, it's that PR I linked, if you have github client installed, you can do this to test it: ``` git clone https://github.com/python-kasa/python-kasa/ cd python-kasa gh pr checkout 267 #...

Those are the ones of your tplink account when the device was set up. There's also https://github.com/fishbigger/TapoP100 that seems similar, see https://github.com/fishbigger/TapoP100/blob/main/PyP100/PyP100.py#L174-L196

I haven't heard anyone working on this, so the status is still that someone needs to figure out the protocol. I don't have time nor a device to work on...

This is not really that necessary for the .0 release (if at all?), so I removed the milestone but keep this open just in case we want to revisit it.

Hi, have you tried if the expected behaviour can be configured using the official mobile app? If yes, it would be great if you could set it up and check...

It isn't expected, but I think I have seen similar reports on the home assistant repository. It could be a firmware bug if it only happens sometimes. If you know...

Could you please elaborate more? I would expect that if these are kasa devices, they will be controllable just like other power strips. What exactly is not working?