Just like Apple HomeKit you can add devices that aren't certified. It shows a warning, but apart from that it functions like a normal device (for as far as I can tell).
I’d say it was entirely incorrect. PKI and attestation are things done by the manufacturer using a publish open standard. Manufacturers are not required to certify anything or pay a single royalty. Certification is optional and has other benefits which includes jointing the Thread Group (which steers the standard); the costs are simply a way of funding both the certification process (which requires people) and the Group, which also provides support and other resources (which again, requires people).
Basically, it’s not much different than when an Open Source project is supported by a company that separately offers an “Enterprise” option where they host the application and provide additional Enterprise features and support. It’s not required, but a business might choose to do it.
> Just like Apple HomeKit you can add devices that aren't certified. It shows a warning, but apart from that it functions like a normal device (for as far as I can tell).
Just like Apple HomeKit you can add devices that aren't certified. It shows a warning, but apart from that it functions like a normal device (for as far as I can tell).
I have been using https://github.com/t0bst4r/home-assistant-matter-hub to expose my home assistant devices to Google Home without having to expose my Home Assistant to the cloud.
Second, certification is what separates Z-Wave from Zigbee which in my (n=1) experience means less issues in terms of compatibility.
Of course, with that GitHub package I shared all of that goes through the window, but who cares? I can clone the code and modify it.