HomematicIP-Rest-Api v2 - Test and Feedback

Hello, I am currently in the process of developing the complete library from scratch which can be accessed via Branch v2. But beware: everything is still very alpha-status :)

I want to know, how you use the library? What are your requirements? Are you interpret results from cli? Do you use the cli at all??? What are your needs?

Example Cli:

Which values need to be output via the CLI?
Everyone could use a json file to decide for themselves what they want to output for each type.
Does anyone use the Cli at all?

Information about status changes: Many people keep running into the throttle problem when retrieving the status via the Cli. The reason for this is that the Cli is restarted again and again. This leads to the complete configuration being downloaded each time. The problem does not occur if the changes are pushed via websockets. I now had the following ideas:

"Listen" mode that writes the received events to a file
"Plugin" system with pluggy??? But i guess this would be a little too much 😆
Connection to EventManager, which is already there

A few things will definitely change:

No more dedicated classes for each Device, Channel, Group, etc. There is a base class for Device, Home, Group, FunctionalChannel and so on, but no more class for AccessControlChannel, for example.
The actions are "loose" and are linked to channels, etc. via Decorator. If an action is executed, the decorator is testing, if the action is applicable for the device.
There is no "home" class anymore. Home is now just a stupid poco. There is the runner, which contains the model.
The Cli is now accessible via hmip.
The auth script does not exist anymore. Use hmip auth instead
Just explore the Cli via hmip --help
All new devices are there without the need of any code changes. But just "read-only" mode. If any rest requests should be made for the device, this must be implemented.

Any input is appreciated.

hahn-th / homematicip-rest-api

HomematicIP-Rest-Api v2 - Test and Feedback #526