Tuya TS0203 Door sensor(TS0203)

eWeLink CUBE
,
1

Hi, I’ve been looking for a solution for months now. I’ve opened countless requests, but it hasn’t been resolved yet!

I have some door and window sensors that aren’t exported via Matter, but they are recognized normally.

With the update that implemented the list of compatible devices, I could see that they aren’t being exported via Matter simply because they aren’t in the correct category!

I would like to know if there is a solution so that we users can fix these silly errors and make things export via Matter, or if you can fix it! This applies to a huge range of products!

Print of the door sensor I’m talking about!

image
image1114×271 18.9 KB

Product information within iHost itself

image
image603×453 12.7 KB

image
image633×703 23.7 KB

image
image436×387 15.8 KB

The FP1 is a classic example and a device that is paired and recognizes the functions but is not exported! I see this with the MMWAVE Tuya too, they are sometimes recognized but are not exported via Matter. I would really like to know why this is not exported!

image
image1071×253 25.5 KB

image
image1051×251 31.3 KB

image
image1043×254 29.6 KB

I would really like to know why devices that are normally recognized for all functions, etc., are left without a category and are not exported to Matter.

I understand that it is a lot of work to classify and test all devices, etc.! However, this ends up being a counter to the idea of ​​iHost!

I really like the idea of ​​CubeOS, I put the Zigbee devices there and it exports them via Matter to the platform I want! However, these small details are complicated! Because in the past this sensor worked and was exported via Matter! Since Ziggbee2Cube was incorporated into the operating system, this has changed!

And since they are launching a new iHost and so on… it would be great to give the more advanced user the possibility to change these things and create converters for devices that are not recognized correctly!

2

First, patience is key—because this won’t happen overnight. Secondly, expecting seamless third-party device support just because a platform exists? Wishful thinking. And thirdly, the Tuya ecosystem is like trying to organize a massive party where half the guests barely speak the same language. We’re talking about countless devices from vendors ranging from well-known brands to that one guy in his garage who thought, “Hey, I’ll make my own smart plug.”

Now, toss in the fact that some of these vendors insist on tweaking the Zigbee or Matter standards for reasons best known to themselves, and voilà! You have what can only be described as an absolute mess. And just for laughs, devices with the Tuya label sometimes refuse to cooperate—like distant relatives forced to share a holiday dinner.

If eWeLink wanted to go all in on this, it would have to ditch its own approach and bow down to Tuya, which, let’s be honest, is about as likely as my mother-in-law developing Wi-Fi 8 or 9.

So, if full compatibility is your goal, switch to Tuya and embrace the chaos. Home Assistant might patch things together for you, but given the above madness, there’s no certainty. The good news? The HA community is always there, ready to commiserate and possibly save the day.

3

Your answer is crazy. I understand that Tuya changes standards and so on… I’m not questioning that. What I’m questioning is that iHost understands all this madness of some devices, they operate correctly within iHost, but they are categorized incorrectly and I imagine that this causes the device not to be exported via Matter. Just like in the Z2M community, there are converters made by the community that translate this madness that you talk about, that Tuya and (I completely agree with this), iHost does not have this option for advanced users to be able to create their own converters for devices X or Y. The big question is that a simple door sensor that is recognized in iHost and works correctly is not exported via Matter due to a simple categorization error. It’s that simple. I’m not talking about something that is not recognized in iHost and that does not work in iHost, but rather something that works and operates correctly in iHost. It is not being exported via Matter because of this.

4

I’d be genuinely shocked if I turned out to be wrong—though, let’s be honest, it’s highly unlikely that this would be the reason.

Oh, absolutely, my answer is crazy—clearly, I must have lost all reason when assuming devices (including Tuya) should be categorized logically.

5

I apologize for the inconvenience and truly regret your disappointment! As you mentioned, addressing compatibility issues with third-party devices does take a considerable amount of time. The devices you referenced are currently categorized as UNKNOWN, which is why they are not recognized by Matter. I have confirmed with our product team that these issues will be addressed in the next version, which is expected to be released in June.

Thank you for your patience and attention!