Split cover.py

[tetienne]

In order to ease maintenance and reduce complexity, as we did for the climate platform, I think we should split the cover module.

Next candidate will be the DiscreteGateWithPedestrianPosition

[iMicknl]

Good proposal!

[iMicknl]

I will have a good look tomorrow. Should we keep it the same as climate device? Thus naming the class Awning instead of TahomaAwning`? (Or maybe rename all the climate devices eventually).

I would love to see our base cover most of the cases, where we have specific classes for groups of devices. (like Awning). Eventually I will have a look if I can implement the rts:VenetianBlindRTSComponent :-).

jcallaghan/home-assistant-config#277 (comment)

[tetienne]

I will have a good look tomorrow. Should we keep it the same as climate device? Thus naming the class Awning instead of TahomaAwning`? (Or maybe rename all the climate devices eventually).

I’ve renamed my class to Awning. It’s indeed more homogeneous with what you did for the climate.

I would love to see our base cover most of the cases, where we have specific classes for groups of devices. (like Awning). Eventually I will have a look if I can implement the rts:VenetianBlindRTSComponent :-).
It will indeed reduce the complexity of our main cover class. It probably ease the code review for the Core repo...

[tetienne]

Ready to be merged.

[vlebourl]

Fine by me. Suggestions are cosmetic. I'd prefer we have either Awning and VerticalCover, or TahomaAwning and TahomaVerticalCover. I's also prefer to keep the TahomaGenericCover code in cover.py as the base code for all other implementations. But I won't fight for it too much.