Support for Tuya Blind Motor - Recognised as TS0601

[milobt]

Information about the device + link

https://www.aliexpress.com/item/1005001775235402.html?spm=a2g0s.9042311.0.0.24644c4dOe24TO

data/database.db entry of the device

{"id":22,"type":"EndDevice","ieeeAddr":"0x5c0272fffeca9e6c","nwkAddr":5763,"manufId":4098,"manufName":"_TZE200_rddyvrci","powerSource":"Battery","modelId":"TS0601","epList":[1],"endpoints":{"1":{"profId":260,"epId":1,"devId":81,"inClusterList":[0,4,5,61184],"outClusterList":[25,10],"clusters":{"genBasic":{"attributes":{"modelId":"TS0601","manufacturerName":"_TZE200_rddyvrci","powerSource":3,"zclVersion":3,"appVersion":68,"stackVersion":0,"hwVersion":1,"dateCode":""}}},"binds":[],"meta":{}}},"appVersion":68,"stackVersion":0,"hwVersion":1,"dateCode":"","zclVersion":3,"interviewCompleted":true,"meta":{},"lastSeen":1609436887877}

Log:
Zigbee2MQTT:debug 2020-12-31 17:48:07: Received Zigbee message from '0x5c0272fffeca9e6c', type 'readResponse', cluster 'genBasic', data '{"stackVersion":0}' from endpoint 1 with groupID 0 Zigbee2MQTT:debug 2020-12-31 17:48:07: Skipping message, definition is undefined and still interviewing Zigbee2MQTT:debug 2020-12-31 17:48:07: Received Zigbee message from '0x5c0272fffeca9e6c', type 'readResponse', cluster 'genBasic', data '{"hwVersion":1}' from endpoint 1 with groupID 0 Zigbee2MQTT:debug 2020-12-31 17:48:07: Skipping message, definition is undefined and still interviewing Zigbee2MQTT:debug 2020-12-31 17:48:07: Received Zigbee message from '0x5c0272fffeca9e6c', type 'readResponse', cluster 'genBasic', data '{"dateCode":""}' from endpoint 1 with groupID 0 Zigbee2MQTT:debug 2020-12-31 17:48:07: Skipping message, definition is undefined and still interviewing Zigbee2MQTT:debug 2020-12-31 17:48:07: Received Zigbee message from '0x5c0272fffeca9e6c', type 'readResponse', cluster 'genBasic', data '{}' from endpoint 1 with groupID 0 Zigbee2MQTT:debug 2020-12-31 17:48:07: Skipping message, definition is undefined and still interviewing Zigbee2MQTT:info 2020-12-31 17:48:07: Successfully interviewed '0x5c0272fffeca9e6c', device has successfully been paired Zigbee2MQTT:warn 2020-12-31 17:48:07: Device '0x5c0272fffeca9e6c' with Zigbee model 'TS0601' and manufacturer name '_TZE200_rddyvrci' is NOT supported, please follow https://www.zigbee2mqtt.io/how_tos/how_to_support_new_devices.html Zigbee2MQTT:info 2020-12-31 17:48:07: MQTT publish: topic 'zigbee2mqtt/bridge/event', payload '{"data":{"definition":null,"friendly_name":"0x5c0272fffeca9e6c","ieee_address":"0x5c0272fffeca9e6c","status":"successful","supported":false},"type":"device_interview"}'

[d-edge82]

I have the same curtain motor (returned the unsupported livolo one)
@Koenkk please advise

[Koenkk]

@d-edge82 see https://www.zigbee2mqtt.io/how_tos/how_to_support_new_devices.html

[d-edge82]

@d-edge82 see https://www.zigbee2mqtt.io/how_tos/how_to_support_new_devices.html

Thanks!
Managed to connect it, now I am struggling with it's behaviour..
Clicking "Down" on HA opens the curtain, "Up" does nothing and "Stop" closes it..

Any idea?

[milobt]

I got the same result after connecting, I figured it might be because I haven’t yet configured the up and down stopping points, but still might be an error in the Z2M profile.

[Koenkk]

Try adding it to model: 'TS0601_roller_blind', instead of model: 'TS0601_curtain',

[d-edge82]

Try adding it to model: 'TS0601_roller_blind', instead of model: 'TS0601_curtain',

Can you please explain where I need to change it?
I am on Hassio with the latest Z2M (edge does not recognize the device)

[Koenkk]

@d-edge82 can you provide the data/database.db entry of it?

[d-edge82]

Is this what you are after?

{"id":2,"type":"EndDevice","ieeeAddr":"0x5c0272fffecc0047","nwkAddr":44405,"manufId":4098,"manufName":"_TZE200_rddyvrci","powerSource":"Battery","modelId":"TS0601","epList":[1],"endpoints":{"1":{"profId":260,"epId":1,"devId":81,"inClusterList":[0,4,5,61184],"outClusterList":[25,10],"clusters":{"genBasic":{"attributes":{"modelId":"TS0601","manufacturerName":"_TZE200_rddyvrci","powerSource":3,"zclVersion":3,"appVersion":68,"stackVersion":0,"hwVersion":1,"dateCode":""}}},"binds":[],"configuredReportings":[],"meta":{}}},"appVersion":68,"stackVersion":0,"hwVersion":1,"dateCode":"","zclVersion":3,"interviewCompleted":true,"meta":{},"lastSeen":1610387106467}

[Koenkk]

Can you try if it is fixed now?

Changes will be available in the latest dev branch in a few hours (https://www.zigbee2mqtt.io/how_tos/how-to-switch-to-dev-branch.html)

[d-edge82]

Cool, thanks!

Dev-branch means edge edition of the add-on, right?
I tried that a few days ago and it did not recognize the device,
Does this mean it will be recognized if I update it tomorrow morning?

[Koenkk]

@d-edge82 should be, first uninstall and install again

[d-edge82]

OK, waited, uninstalled and installed back again
I now see it shows up as roller_blind, but the issue is still there:

Stop: Closes the curtain
Up: Opens
Down: Stop

Should I wait longer?

[Koenkk]

@milobt is it working for you?

[milobt]

@Koenkk on edge I get the same @d-edge82. Although, I believe the operations to be as follows:

Lovelace Button <-> Blind Operation
Up <-> STOP
Stop <-> DOWN
Down <-> UP

[rbrueckner82]

same issue

Button

OPEN / doesn't work
CLOSE / open the blind
POSITION / doesn't work

the warning are at log when i start any event.

WARNING: owvfni3: Unhandled DP #105: {"status":0,"transid":0,"dp":105,"datatype":2,"fn":0,"data":{"type":"Buffer","data":[0,0,0,40]}}

[milobt]

I also find that position does not work at all.

Furthermore, considering that these motors run on batteries it would be useful if battery level was available on one of the endpoints.

[DomiStyle]

@milobt Does setting the position not work or receiving the position?

Judging by the warning @rbrueckner82 posted, receiving position can't work yet.

[d-edge82]

This is the current status for me (on Edge):

Z2M web:
Position - works fine.
Close=Stop
Open - Works.
0 = Open
100 = Closed (wish it was the other way around)

On HA the behavior is as following:

Stop = Close
Up = Open
Down = Stop

Position works.

Thanks for the support @Koenkk !

[eric-zimmer]

Hello, I have got the same zigbee blind motor. I am not able to pair it with zigbee2mqtt (HA) or deconz. How did you do this? Also I have a tuya gateway, also with this I cannot connect the motor. How can I put the device into pairing mode? I haven't found anything for this in the instruction

[d-edge82]

Hello, I have got the same zigbee blind motor. I am not able to pair it with zigbee2mqtt (HA) or deconz. How did you do this? Also I have a tuya gateway, also with this I cannot connect the motor. How can I put the device into pairing mode? I haven't found anything for this in the instruction

Hi Eric,

Hold the down button along with the set, this should reset the device and enter pairing mode

[eric-zimmer]

Hi, thank you for your fast answer. I thought it need to flash, it doesn't but it connected to deconz, so it should work with z2m, will try this next. thank you.

[Koenkk]

Can you guys check out the latest dev branch and see if it's fixed there? (@DomiStyle did some fixes here)

Changes will be available in the latest dev branch in a few hours (https://www.zigbee2mqtt.io/how_tos/how-to-switch-to-dev-branch.html)

[d-edge82]

Can you guys check out the latest dev branch and see if it's fixed there? (@DomiStyle did some fixes here)

Changes will be available in the latest dev branch in a few hours (https://www.zigbee2mqtt.io/how_tos/how-to-switch-to-dev-branch.html)

Just tried;
Close = Close.
Open = stop.
And I have no other options.

Position:
100 = Open
0 = Closed.

Should I try again in a few hours?

[DomiStyle]

@joseant Should work once Koenkk/zigbee-herdsman-converters#2150 is merged.

[JAJBrouwers]

Hello there,

I also have a cover blind on zigbee2mqtt, the only thing that's not working is the "state" it's unknown all the time... When I follow the documentation and publish a message to get the state nothing happens.

And that option for the motor speed, is that only in the dev branche? Because I don't have that option.

Thx in advanced, Jeroen

[DomiStyle]

@JAJBrouwers The fix for the state is not merged yet.

The option for motor speed is only available in dev and only works for supported devices.

[JAJBrouwers]

Oke then, thx for you're feedback, I have the normal version, when I take the Dev add-on... Do I need to install everything again?

[DomiStyle]

@joseant Can you try again with the latest dev version? Everything should work out of the box now.

[joseant]

@DomiStyle
Hello.
I have switch to the dev branch: https://www.zigbee2mqtt.io/how_tos/how-to-switch-to-dev-branch.html
But I can't see the changes yet

[joseant]

@DomiStyle
I have now tried the dev branch and everything has worked fine

[JAJBrouwers]

Nice, how do I get this update without using the Dev branche? Will there be a update or something?

[DomiStyle]

@JAJBrouwers Yes, once the next update releases it will be available without dev branch.

Since everything works I guess this can be closed now @Koenkk @milobt.

[JAJBrouwers]

Hi there I have just installed the dev branch, I get the option for the motor speed... when I set it and hit apply, nothing changes. for the state value, it still does not report back open or close.

[leroyloren]

Hi, same problem. Motor speed does not respond to change. For example, Setting motor speed to 34 is displayed in the log, but after the reload it is still 0 and the speed remains the same.

[DomiStyle]

@leroyloren Which model are you using? Changing motor speed is not supported for all.

If you do not receive a response from the motor it's most likely not supported or needs a different command.

[leroyloren]

Zemismart M515EGB

[JAJBrouwers]

I have the same model, you experience also no state change

[DomiStyle]

@leroyloren @JAJBrouwers The only model we know for sure supports setting the motor speed is _TZE200_zah67ekd (Zemismart AM43), so I would assume your model just doesn't support it.

[leroyloren]

Well, the weird thing is that until the motor is configured, it runs very slowly and quietly. But I understand if it can't be set.

[JAJBrouwers]

@leroyloren
That's normal

[JAJBrouwers]

@leroyloren

You have the same model as me, does yours also report only "running" is "true"?

[leroyloren]

yep,

[JAJBrouwers]

Oke, then it is not my only problem 😅, so you don't have the state report back.

@DomiStyle made a fix maby, but I can't test it.

[d-edge82]

Hi There!

After one of the latest updates - the motor no longer publish the "Cover" entity.
I can only see the LQI..

Any idea?

[DomiStyle]

@d-edge82 Update to 1.19.0.

#7680

[d-edge82]

@d-edge82 Update to 1.19.0.

#7680

Thanks! it worked.
How was I to know the repo has changed??

[nickwild-999]

Sorry to resurrect an old issue, but can a battery endpoint be added to this device. It would be really useful .

EDIT: just seen the issues on this here #7630