Where to start writing Custom driver for TS130F smart curtain switch (tuya clone)?

Mariano,

This revised driver (2023-03-14T17:18:20.824840108) was downloaded to my hub and I tested the blind’s operation. The blind is still reporting the state of ‘Closed’ when the blind is in fact OPEN and ‘Open’ when the blind is CLOSED. So this change did not fix the issue. What is now happening is that open and closed buttons in the detail screen now operate in reverse. The app requires that you tap “Close” to OPEN the Blind and “Open” to CLOSE the Blind. So I guess is was functioning better under the former configuration even though the blind status was reporting in reverse.

For what it is worth, the ‘Tuya Window Shade’ driver from the Iquix Channel Invitation works fairly accurate. It reports Open when the blind is OPEN visa-versa. The Open and Close buttons in the detail screen work correctly as as well, meaning the “Open” button OPENS the blind and the “Close” button CLOSES the blind. The only issue with it is that when the blind is fully open it reports a “Partially open”.

Sorry, Just modify the report not the command.
try this version

───────────────────────────────────────────────────
 Name         Zigbee Window Treatment Mc
 Version      2023-03-14T17:18:20.824840108
───────────────────────────────────────────────────

Yes. The buttons are now working correctly. However the ST App is still reporting a status of Closed when the actual state of the blind is OPEN and visa-versa…

@Buds_Smart_Home

I don’t understand anything that is happening.
If you don’t even send me information about the logs, I can’t analyze this strange thing.

This version uses the default handlers, which is the complete reverse of what it used before.

───────────────────────────────────────────────────
 Name         Zigbee Window Treatment Mc
 Version      2023-03-14T21:14:20.590515845        
───────────────────────────────────────────────────