A year ago, an article about the construction sites in the Matter standard appeared here in the blog. It took stock of the situation. Where there is a backlog in the implementation of the standard – and what needs to happen for Matter to fulfill its promise: to become an uncomplicated, self-explanatory and manufacturer-independent solution for the smart home. A lot has happened so far. Manufacturers and standardization organizations have been working hard on solutions. But where are we 12 months later? Let’s take a closer look at the issues,
Contents
Thread and Border Router: solutions in sight
Current situation: Matter envisages the Thread protocol as a second wireless standard alongside Wi-Fi. Its mesh network reacts quickly, requires little energy and grows with the requirements. In contrast to long-established alternatives such as Zigbee, it is IP-based (IPv6), which facilitates the direct exchange of information in the smart home. However, Thread got off to a bumpy start.
Initially, only a few households had one of the necessary Border Routers to connect products to the home network. And Thread Border Routers from different manufacturers sometimes compete with each other. They set up their own networks instead of forming a common mesh. With the effect that devices react unreliably or can only be reached by certain apps. All of this has hindered the spread of the wireless protocol and brought it criticism. Some manufacturers even suspended the launch of new Thread products.
Solution approach: To create a shared mesh, Border Routers must communicate with each other. As in a Wi-Fi network with several access points or repeaters, this requires the exchange of access data so that all devices can join the same environment. These “Thread Credentials” can be transferred in various ways.
The way to date has been via the operating system on the smartphone: Apple and Google store access data in their software and make it accessible to Android or iOS apps when setting up devices. However, the manufacturer’s app must support this approach. If it does not, the border router does not join an existing network, but sets up its own instead. Amazon, for example, stores Wi-Fi and Thread access data on the company’s servers instead of using Android and iOS on-board resources.
With the Thread Group and the Connectivity Standards Alliance (CSA), both responsible standardisation bodies have addressed this issue. In September 2024, the Thread Group first published an update to its wireless protocol. With Thread 1.4 (link), a border router can share its access data with others on request – regardless of the smartphone operating system or the Matter platform used.
In November 2024, the CSA followed suit and presented the Matter 1.4 specifications, which include the new device type HRAP, an abbreviation for “Home Router and Access Point”. Correspondingly certified devices should have a secure storage area in which the Thread credentials are stored. This allows apps and new devices to access them during setup.
Prospects of success: In addition to the programming interfaces (APIs) of Android and iOS, there will be two other options for exchanging Thread credentials in the future. Both are standardised and manufacturer-independent. This should also convince providers who have so far shied away from an Apple or Google solution because they prefer to remain independent.
For Thread 1.4, existing border routers must receive a software update or be replaced by new, compatible devices. The Thread Group expects this transition to be quick: “We have some policies in place where we expect them (the ecosystems) to implement 1.4, and we haven’t gotten much pushback,” explained Vividh Siddha, President of the Thread Group, in an interview with “The Verge” (link). The rapid phasing out of previous Thread generations should further accelerate the changeover.
More time could pass before a sufficient number of certified HRAPs are available. It is conceivable that the Matter ecosystems will support two or three methods in parallel. How they organize the release of credentials is up to them. According to The Verge, Vividh Siddha assumes an on-screen dialog: “I expect there to be at least one minimum step where the user is involved in sharing (credentials), similar to sharing your Wi-Fi netzwork”. In other words, the system asks whether access is desired and users give their consent.
Multi-Admin: Improvements in Matter 1.4
Current situation: The Matter ecosystems organise the device setup process differently. This is particularly noticeable when several of them are in play: in Multi-Admin mode. One of the achievements of the standard is to share installed devices across platforms – so that they can be controlled simultaneously by Alexa, Apple Home, SmartThings or another Matter-enabled system.
However, it is precisely this sharing that makes things complicated. Because sensors and actuators, lights, robotic vacuum cleaners and bridges have to be authorised individually. Each device has to go through an approval process with a code, just like when it was first commissioned. But this time, the QR or numeric code is generated individually by the ecosystem and displayed in its app – a consequence of the strict security guidelines that only allow encrypted connections.
Solution approach: With the specifications of Matter 1.4, Multi-Admin has learnt something new. A Fabric – as the secure communication network of Matter ecosystems is called among developers – can now talk with others. If it receives permission from the user to “Fabric Synchronisation”, its connected devices also appear on the target platform. Repeated approval steps and code entries are no longer necessary. The CSA calls this improved process “Enhanced Multi-Admin”.
Prospects of success: The technical prerequisite for Enhanced Multi-Admin is support for Matter 1.4 in the ecosystems. Home Assistant has started implementing this version, and the SmartThings developers are also working on it. However, the function will only reach its full potential once Amazon, Apple, Google and other platforms are ready as well. Experience shows that this takes time, and many are currently still busy switching from version 1.2 to 1.3.
However, it is probably only a matter of time before the new feature becomes standard in all systems. It remains to be seen how they will implement it in practice. Ideally, shared devices should appear on the target platform with their assigned name. Otherwise, manual work will be necessary again and each device will have to be touched individually in the app to change its name.
Ecosystems: still good for surprises
Current situation: Nanoleaf CEO Gimmy Chu has expressed what many people are thinking: “It doesn’t make sense that not all Matter controllers control all Matter products”. Nevertheless, it happens: devices work differently depending on which platform they are connected to. The patchy implementation of the standard is causing confusion among consumers. Because – contrary to their expectations – the Matter logo is not a free pass for operation on all Matter-enabled platforms.
Current example: The door/window contact from the [+M] series from Bosch also has a push-button on the housing. It could appear in Matter systems as two functional devices: opening contact and push-button sensor. As the test on digitalzimmer.de (link) shows, this is true for Alexa, Apple Home and Home Assistant. In Google Home, however, there is no wireless push-button available, and in SmartThings the opening contact is missing.
And where devices appear as expected, their range of functions can vary. For example, push-buttons with several keys are often recognized as solo switches. Some systems register single, double or long button presses, while others make no distinction. In the case of blinds, some systems do not allow the opening angle of the slats to be set, and so on.
Solution approach: As the platforms themselves decide how quickly and comprehensively they implement the standard, there is no common approach. Each ecosystem publishes when it is ready. This applies to device types and their range of functions. So we have to wait and be patient.
Prospects of success: The ongoing development and spread of the Matter standard will alleviate the problem. At some point, all systems should support the most important product types. The differences will then level out and the range of functions will be sufficient for most applications. Only extras that are introduced in new Matter releases will then take some time again.
Matter certification: simpler and less expensive
Current situation: Bringing a Matter-certified product onto the market costs the manufacturer money. The company must invest in development, commission an authorized test laboratory (ATL) to carry out the testing and pay a fee to the CSA. Product variants, for example for different markets, each receive their own certificates. Special programs are available for this purpose (Product Family Certification and Certification by Similarity), but these are complex.
Even more bothersome for many providers was the chargeable recertification: certified devices that were to receive a new software version had to go through the process again, causing costs in the five-digit range. It didn’t matter whether it was a security update or new features. The Matter-specific parts of the firmware did not even have to be affected. They could remain unchanged and still trigger a new testing obligation.
The time and financial outlay was a deterrent for smaller companies in particular. There was also the risk that manufacturers would no longer update their certified products in order to save costs. Without updates, however, it will be difficult for Matter to develop further on the market. Why publish new specifications – Matter 1.4, 1.5, 1.6 – if the installed base is stuck on previous versions?
Solution approach: For CES in January 2025, the Connectivity Standards Alliance revised its guidelines and adopted two new programs. The Portfolio Program simplifies the certification of similar products because in future only one “parent” will have to go through the fee-based process. It already contains the code of all possible family members. These “inherit” their approval from the main certificate.
The Fast Track Program speeds up the recertification of Matter products and reduces costs at the same time. Instead of sending the updated product to an ATL for a fee, as was previously the case, the manufacturer checks it itself using CSA software. Trained employees carry out tests and submit their protocols to the Connectivity Standards Alliance. The Alliance issues the certificate without any additional fees. Any checks can be carried out retrospectively and do not delay the market launch.
Prospects of success: All manufacturers that matter-smarthome.de has spoken to welcome the development. “Most importantly, these are not declarations of intent,” explains Tim Böth, Head of Brand & Business Initiatives at Eve Systems. “Almost all innovations were implemented as soon as they were announced. Taking into account the training requirements, FastTrack and portfolio certifications are already possible.”
Christopher Zoggolis, Business Development at Mediola, also sees advantages in the new recertification: “The external costs are practically zero”. This eliminates a central point of criticism regarding the previous procedure. It seems that the CSA has listened to the objections of its members. Now they just have to deliver.
Share this information:
