Hey folks,

I've been playing with my EC70 and want to integrate it with HomeAssistant but don't have time to maintain my own library so I'd like to contribute support for it (and other KasaCam devices) to yours. The trouble is I don't think it fits the same paradigm as currently supported devices.

For example, there's no central call (besides system.get_info) to get the device state so there's a choice between sending 10+ different commands to gather state or breaking the convention of caching to the .data attribute. Worse, it seems this device doesn't accept multiple commands in a single call so those would be discrete calls.

Next, they don't support discovery so the Smart device child class will always need to be created manually (not a deal breaker, but still "different").

Finally, all the available API calls (I've found 30+ looking through the android app) are spread across multiple namespaces making it a hard fit for the Modules concept (either 1 massive module or a bunch of modules with only one or two functions).

I've written a working Transport for these devices and stubbed out all the function calls, but I'm running low on time to spend on the project.

I guess my questions are:

1. How would you prefer to tackle the challenges above?
2. How far does an implementation need to be before you'd accept it as "a good start to iterate on later?" I hope that I'd have more time to iterate on it in the future and contribute more, but I can't promise that yet