I see that some people ask that support devices via other matter hub (for example HA). The devs answer it very quickly and make some changes (not need FW update, only they do some config changes on backround) and after it works!
I’m courius, because i have two Zigbee thermostat (a wall type and a TRV) that not seeable in HA matter integration (if i add Tuya matter hub to HA)
So i open a topic, send the device type and ID. One day (!!!) later i get the answer that “please try to re-pair the device and test it” I do it and see a miracle , it showing HA perfectly!!
It possible that first time not perfect and need some optimalization or something, but if you report the problems, they are fix it really fast! (My thermostat work perfect one first try)
So i to encourage everyone, that report ALL OF devices that not seeable in HA, because we are also help other people that want to use similar type of device (of course not need to configure same type again)
Here the device list that Tuya Matter SDK are support it:
Hi, may I know if your working door lock has the data of the user who unlocks the door via fingerprint? Like if I registered both me and my wife’s fingerprint, can HA know who unlocked the door via fingerprint? I am referring to pure matter without cloud.
A good news update. Having worked with the engineers at Tuya, I now have my Tuya Zigbee locks working seamlessly in Home Assistant via a Zemismart M1 Matter/ZIgbee hub. Th elocks are connected to the hub via Zigbee, and the hub exposes them via Matter to HA. There is nothing to do once they are connected to the hub; they just appear as Matter locks in HA.
Bizarrely, when the locks first appeared in HA via Matter, I was able to unlock them, but not lock them from HA.
I’m on beta code for the hub while they are testing and finalising, but I trust it will be made GA and rolled out soon.
The integration is simply exposing the lock state and allowing HA to lock and unlock them. You don’t get any of the info of who has unlocked the doors, or facility to set PINs etc, but for what I need, it works.
Even though it took many months to get this working as it should, props to the Tuya team for responding to user feedback and working to get this implemented.