Open caradas opened 1 year ago
bschmidt006
commented
9 months ago In case is helps someone in the future, I was able to use the above quirk to integrate a different model number: _TZE200_xu4a5rhj
I simply changed the model number in the quirk from _TZE200_r0jdjrvi to _TZE200_xu4a5rhj.
Open/Stop/Close seems to work fine.
I did have to set the motor reverse flag to get those going the correct direction.
KirkKirk
commented
9 months ago Hello, guys.
I was having problem pairing and using a similar model curtain motor. But the the quirk file that @danidask posted on his last comment worked like a charm. I just had to change TZE200 to TZE204 on line 261, because my motor model is _TZE204_r0jdjrvi.
The one thing that still isn't working is the curtain state whenever i use the set_position service (either by calling it manually or by selecting the appropriate position on the scroller in the UI).
If click on the half of the bar (50%) and the curtain goes to that position, the state of the curtain keeps on "Opening" forever. I have to click the Stop button for the state to change to Open. The same thing happens with the Closing state.
Is there a way to fix this?
Hi @utech-git We have the same model (_TZE204_r0jdjrvi) and have encountered the same issue. I don't use rails and the only solution I have found is to set limits by forcing the motor to stop. However, I have to do this every time after a power outage because the motor forgets the limits. Have you found any other solution to set the limits?
utech-git
commented
9 months ago Hello, guys. I was having problem pairing and using a similar model curtain motor. But the the quirk file that @danidask posted on his last comment worked like a charm. I just had to change TZE200 to TZE204 on line 261, because my motor model is _TZE204_r0jdjrvi. The one thing that still isn't working is the curtain state whenever i use the set_position service (either by calling it manually or by selecting the appropriate position on the scroller in the UI). If click on the half of the bar (50%) and the curtain goes to that position, the state of the curtain keeps on "Opening" forever. I have to click the Stop button for the state to change to Open. The same thing happens with the Closing state. Is there a way to fix this?
Hi @utech-git We have the same model (_TZE204_r0jdjrvi) and have encountered the same issue. I don't use rails and the only solution I have found is to set limits by forcing the motor to stop. However, I have to do this every time after a power outage because the motor forgets the limits. Have you found any other solution to set the limits?
Well, every time after a power outage it loses the limits. But I don't do anything to get the limits back. Once the power is back, the first time I open the curtain it goes slowly to the beggining of the rail and when it reachs it automatically knows where the start limit is. The same way when I first close the curtain, it goes to the end of the rail and set the finish limit. And there it goes.
It knows where the end/beggining is when it feels resistance and can't go any further (just like you said when you force the motor to stop).
utech-git
commented
9 months ago In case is helps someone in the future, I was able to use the above quirk to integrate a different model number: _TZE200_xu4a5rhj
I simply changed the model number in the quirk from _TZE200_r0jdjrvi to _TZE200_xu4a5rhj.
Open/Stop/Close seems to work fine.
I did have to set the motor reverse flag to get those going the correct direction.
Could you please tell me how to set this "reverse flag"? I couldnt find it on the ZHA. I had to first pair the motor on a tuya zigbee gateway, set the reverse flag on the tuya app, then delete it from tuya and pair on ZHA.
bschmidt006
commented
9 months ago In case is helps someone in the future, I was able to use the above quirk to integrate a different model number: _TZE200_xu4a5rhj I simply changed the model number in the quirk from _TZE200_r0jdjrvi to _TZE200_xu4a5rhj. Open/Stop/Close seems to work fine. I did have to set the motor reverse flag to get those going the correct direction.
Could you please tell me how to set this "reverse flag"? I couldnt find it on the ZHA. I had to first pair the motor on a tuya zigbee gateway, set the reverse flag on the tuya app, then delete it from tuya and pair on ZHA.
In ZHA - select the device. Under device info - hit the 3 dots -> Manage zigbee device.
This is reflect in the quirk here:
0xF002: ("motor_steering", t.enum8, True), # 0: default, 1: reverse
Hello, guys. I was having problem pairing and using a similar model curtain motor. But the the quirk file that @danidask posted on his last comment worked like a charm. I just had to change TZE200 to TZE204 on line 261, because my motor model is _TZE204_r0jdjrvi. The one thing that still isn't working is the curtain state whenever i use the set_position service (either by calling it manually or by selecting the appropriate position on the scroller in the UI). If click on the half of the bar (50%) and the curtain goes to that position, the state of the curtain keeps on "Opening" forever. I have to click the Stop button for the state to change to Open. The same thing happens with the Closing state. Is there a way to fix this?
Hi @utech-git We have the same model (_TZE204_r0jdjrvi) and have encountered the same issue. I don't use rails and the only solution I have found is to set limits by forcing the motor to stop. However, I have to do this every time after a power outage because the motor forgets the limits. Have you found any other solution to set the limits?
Well, every time after a power outage it loses the limits. But I don't do anything to get the limits back. Once the power is back, the first time I open the curtain it goes slowly to the beggining of the rail and when it reachs it automatically knows where the start limit is. The same way when I first close the curtain, it goes to the end of the rail and set the finish limit. And there it goes.
It knows where the end/beggining is when it feels resistance and can't go any further (just like you said when you force the motor to stop).
Thank you for your response. In my situation, I have vertical curtains that do not have a physical limit when they are lowered, so I need to force them to stop. I was wondering if it is possible to save the limits in Home Assistant or somewhere else, so that they can be uploaded in case of a power outage.
utech-git
commented
9 months ago In case is helps someone in the future, I was able to use the above quirk to integrate a different model number: _TZE200_xu4a5rhj I simply changed the model number in the quirk from _TZE200_r0jdjrvi to _TZE200_xu4a5rhj. Open/Stop/Close seems to work fine. I did have to set the motor reverse flag to get those going the correct direction.
Could you please tell me how to set this "reverse flag"? I couldnt find it on the ZHA. I had to first pair the motor on a tuya zigbee gateway, set the reverse flag on the tuya app, then delete it from tuya and pair on ZHA.
In ZHA - select the device. Under device info - hit the 3 dots -> Manage zigbee device.
- Ensure you're on the CLUSTERS tab.
- Select the TuyaWindowCovering cluster.
- Select the motor_steering attribute
- Read attribute to see what it's set to.
- Flip the value if needed and hit Write Attribute.
This is reflect in the quirk here:
0xF002: ("motor_steering", t.enum8, True), # 0: default, 1: reverse
I did try to change this "True" to "False" on the quirk, at first. But nothing happened.
Now I tried on the Manage Zigbee Device menu... when I click "Read Attribute" it shows "None". I try to write attribute to 0 or 1, but when I read it again it continues "None" and the motor is still not reversed.
Maybe it doesn't work with this model, but thanks any way! :)
Onepamopa
commented
9 months ago @utech-git works fine with zigbee2mqtt ... I'm using it until zha gets enough supported devices working properly ....
ATaylor5596
commented
6 months ago I have a similar motor, model TZE200_idkvxabg. Thanks to everyone here I was able to get it to work with the most recent quirk, however, my open/close percentage stays out of sync with the remote control. Switching the motor direction will always have the remote and HA be opposite controls. Does anyone have any idea how to invert the display percentages?
IntegersOfK
commented
4 months ago In case is helps someone in the future, I was able to use the above quirk to integrate a different model number: _TZE200_xu4a5rhj I simply changed the model number in the quirk from _TZE200_r0jdjrvi to _TZE200_xu4a5rhj. Open/Stop/Close seems to work fine. I did have to set the motor reverse flag to get those going the correct direction.
Could you please tell me how to set this "reverse flag"? I couldnt find it on the ZHA. I had to first pair the motor on a tuya zigbee gateway, set the reverse flag on the tuya app, then delete it from tuya and pair on ZHA.
In ZHA - select the device. Under device info - hit the 3 dots -> Manage zigbee device.
- Ensure you're on the CLUSTERS tab.
- Select the TuyaWindowCovering cluster.
- Select the motor_steering attribute
- Read attribute to see what it's set to.
- Flip the value if needed and hit Write Attribute.
This is reflect in the quirk here:
0xF002: ("motor_steering", t.enum8, True), # 0: default, 1: reverseI did try to change this "True" to "False" on the quirk, at first. But nothing happened.
Now I tried on the Manage Zigbee Device menu... when I click "Read Attribute" it shows "None". I try to write attribute to 0 or 1, but when I read it again it continues "None" and the motor is still not reversed.
Maybe it doesn't work with this model, but thanks any way! :)
I have the same issue, _TZE204_r0jdjrvi model doesn't appear to accept any 0, 1, True, or False for reversing the motor. I wonder if there's a way to tell Home Assistant to treat it as the opposite. Did you figure out any other way to deal with that? I do have a remote but there's nothing described on the docs as to how one might reverse it on the device itself.
Describe the bug Curtain motor has no entities.
Expected behavior Entities for opening and closing curtain and if possible slider to set partially closed
According to https://github.com/zigpy/zha-device-handlers/issues/1602#issuecomment-1322763054 its already fixed.