@nayelyz Don’t you know any solution for this?
Tuya devices using EF00 cluster are using proprietary code that is normally only used on the Tuya home automation platform. It is not standard Zigbee 3.0 communications. Consequently, it is not officially supported by SmartThings and it’s unlikely that staff can give you a solution.
This issue is the whole reason that we have a separate community FAQ for Tuya Zigbee devices and that there is a community created edge driver for tuya devices that use the EF00 cluster. 
It can be frustrating, because tuya devices are very inexpensive and have some cool features. But Tuya does not guarantee them to work with anything other than their own hubs and most other platforms can’t do anything with them at all.
SmartThings is unusual in that it does offer an option for community developers to dig deeper and try to reverse engineer what will be needed to communicate with a Tuya device using proprietary code, but it’s often a quite complex process and not always successful. 
3 Likes
Scroll down in settings (2nd screenshot) is there a lock option?
If there is no lock option maybe @w35l3y can provide some insight.
I just looked and there is no blocking option.
Thank you for providing me with this information, it is very useful for me to know this since I am quite new to the whole Smartthings topic.
1 Like
I haven’t implemented lockCodes capability.
Currently, the driver reached the limit of 100 profiles. I can’t add new profiles.
2 Likes
Question, is it too complex and complicated to create a profile like for the lock? Don’t you have a guide or something so I can learn how to do it?
The profile itself isn’t the problem.
The problem is that I reached the limit of the platform.
I can’t add any profile to the driver.
If I decide to add a profile, I would need to remove another.
Also, the problem is how to deal with lockCodes capability.
It would require a lot of logs to understand how the device communicates its status.
I am not actively working on this driver as I used to because I don’t use ST anymore.
2 Likes
It’s one of the most complex device classes using proprietary code that would have to be reverse engineered. Standard Zigbee uses different clusters for different functions. Tuya uses a single cluster for dozens of different functions depend on on the exact bit pattern sent. It’s really complicated and very hard to reverse engineer. Sometimes the exact same message has a different meaning, depending on the message that preceded or that follows it. Again, they designed their devices to work with their hubs, not anybody else’s. And they don’t have interest in making it easy for anybody else.
This approach is also why so far the community-created driver is a single driver with, as Wesley just mentioned, 100 different profiles. That means there are 100 different device classes all using the same cluster, which, to be honest, is ridiculous from a Zigbee design standpoint. It’s almost the opposite of what Zigbee was intended to be, which was different clusters for different functions. But it is what it is and again, tuya only intended these devices to work with their own platform.
The good news is that Eventually anything that Tuya makes available through a “matter bridge” Will be able to be connected to the Tuya app and Tuya hub, and then bridged out to other matter compliant platforms, including SmartThings, without requiring any custom code. That will be great, but we aren’t there yet. Tuya only recently released its first matter bridge and so far it only works with a few simple devices like on/off switches and open/close contact sensors. And not every model of those.
For now, you have three choices.
-
get a different lock that does use standard Zigbee and use that instead. Yes, these might cost a little more, but you will save so much time for yourself and other others if you do this.
-
Wait for Tuya to provide a “matter bridge” that works with your lock. You can write to them and ask when this might be available. This is usually the best solution from the customer point of view because it lets you use the same devices with both the Tuya/Smart life app and the SmartThings app at the same time. And no custom code required. But again, we aren’t there yet, so you have to be willing to wait for this. I think it will come eventually for locks, it’s just not here yet.
Zemismart does sell a rebranded Tuya “matter bridge”. You could ask them when it will support the lock model that you have.
- write your own edge driver. This is going to be really hard and take a lot of time because of that reverse engineering requirement. (It will help if you read Chinese, because then you can join forums in that language and see if other people have already done some of the research.) it’s too much work to be worth it for most people, which is why so far there have only been two community developers who have even attempted edge drivers for devices using tuya proprietary code, and it’s only been for the simpler devices. I’m not saying don’t do this, but I would be surprised if you get a reliable working version in less than 150 hours. And add another 100 hours since you’re new to the SmartThings platform. So I’m not saying don’t do it, I’m just saying it’s going to be a lot of work if your only desired outcome is to get an individual lock working with SmartThings.
3 Likes
From which online store could I get a standard Zigbee lock?