javicalle

Hi @zoic21, I have a proposal, but there are a few changes I want to highlight: * I have renamed some classes to give them a more generic character (they...

Device operation traces are needed to see if it is possible to implement a quirk. Each trace must be able to be identified with the action, eg: open, close, stop,...

In the herdsman-converter seems that the door status is not reported. The most similar device doc that I have found it's the 'curtain switch'. Maybe the status report will be...

In case someone wants to try it, it seems that it has already been included as an on/off switch: * https://github.com/zigpy/zha-device-handlers/pull/1281/files

Without logs from device operation, nothing can be done. Enable logs and attach the relevant information: ```yaml zigpy: debug zigpy.zcl: debug custom_zha_quirks: debug zhaquirks.tuya: debug homeassistant.components.zha: debug ```

I think that the appropriate thing would be to create a new file for cover type entities (maybe `ts0601_cover.py`) and implement this class inside (better than in a switch class)....

Hi, there is my proposal for `_TZE200_nklqjk62` device and maybe others: ts0601_garage.py ```python """Tuya based cover and blinds.""" from typing import Dict from zigpy.profiles import zha from zigpy.quirks import CustomDevice...

Probably a `WindowCovering` device would be more appropriate, but not sure how cluster status is updated. I suppose that device doesn't have any 'door position', and `WindowCovering` seems that only...

So, from your comments (thanks for that) it would be more appropiate represent in HA as a button, isn't it? I am going to see how a button can be...

Another random test that can be done is to replace the `TuyaOnOff` cluster: 1. add the `TuyaOnOffNM` import: ```python from zhaquirks.tuya.mcu import ( DPToAttributeMapping, TuyaDPType, TuyaMCUCluster, TuyaOnOff, TuyaOnOffNM, ) ```...