Hi, just got myself this curtian rail from zemismart.
Tuya converted succesfully then flashed Tasmota and tried this:
Specifically:
From the tasmota command line:
change to TuyaMCU with module 54 (will reboot)
Switch from U0RX/TX to U1RX/TX with backlog gpio1 0; gpio3 0; gpio15 107; gpio13 108 (will reboot)
Treat DpId 0x65 as a Dimmer with tuyamcu 21,101
Allow the dimmer to get down to 1% with setoption69 0
The curtain motor now presents as a Dimmer, with 100% full brightness = fully closed, and 0% full darkness = fully open.
The curtain motor also presents DpId 0x66 as a single event “Full Open” 00 , “Full Close” 01 , and “Stop” 02 command; but as of September 2019, I can’t see how to get that working.
The curtain motor also presents DpId 0x67 as a Boolean. I have only seen value 0x01 in all my prodding. 55 aa 00 07 00 05 67 01 00 01 01 75 = 07 Status, 0005 length, 67 DpId, 01 type, 0001 length, 01 value, 75 checksum
However when the motor controlled by a remote and curtain is closed it sets brightness to 0 and light switch is turned off automatically (did not find any ways to avoid this) what leads to curtain goes to closed position and open again.
Now I flashed Tasmota and it does not have such problem.
Is there any way to control only brightness slider without any feedback on the light?
I am able to close the curtains once, from Home Assistant using the UP arrow and the curtain closes, but the DOWN button then gray’s out and I am not able to close them then.
Also the STOP button only stops shortly and then continues opening.
I have this curtain rail working perfectly using Tasmota and MQTT. Perhaps some of the information in this post will help you to figure out how to get your ESPHome versions working?
If not, you could flash Tasmota and follow the instructions. The Curtain operates perfectly in Home Assistant, Homekit, and Alexa. When the RF remote control is used, the position is updated to Home Assistant, so it is also reflected in Homekit. Alexa knows the position too!