@sk229 I’ve tested the Tuya module and have both good and bad news. The module is properly discovered as a shutter controller, with up/down/stop capabilities and possibility to set the position from 0% to 100%. Position entity in HA is updated whenever the module stops the shutters, either automatically or by us hitting the stop button. It’s possible to use monostable buttons with it (thank God) and pressing the button starts or stops opening or closing the shutters.
Now, the worse part. The module doesn’t try to figure out when the shutters are fully open or fully closed, although it should be able to do so by monitoring the current pulled by the shutter motor - if it’s supposed to be opening and the motor stopped pulling current then it means it’s fully opened, isn’t it? Instead, it relies on us entering the “calibration mode” where we have to close the shutters, start calibration, open the shutters, click “stop” once they fully open, close the shutters, click “stop” once they fully close and finish the calibration. Long story short - it relies on time it requires for the shutters to fully open and close to determine the position. Without calibration it randomly stops in the middle of opening/closing and insists that the shutters have reached the end. I’ve found out about it in this github issue in deConz repository:
This is another vendor-specific attribute which is a real pain when it comes to working with ZHA. Home Assistant has an attribute browser for each Zigbee device, but these two Tuya-specific attributes - Calibration (0xF001) and some Motor Reversal (0xF002) - are not present on that list when I checked it. Assuming there is no way to sniff out those non-standardized attributes, the thread above might prove itself invaluable for a developer who chooses to write a custom ZHA handler for that device. If only there was a way to specify attribute ID and its value manually, I would be able to give it a try, but I don’t see any possibility to modify the attribute list anywhere in HA.
.
Interestingly, since you’re using deConz, you might be able to actually calibrate the module since they already have this custom channel attribute implemented. 