The Matter logo has been on boxes in Jakarta electronics stores since 2023, but the smart home is still a mess of apps, bridges, and half-working hubs. It is not that people dont want one standard; it is that one standard cant fix a decade of incompatible chips, proprietary clouds, and users who dont care which protocol is under the hood.
The Protocol That Was Supposed to End the War
The Connectivity Standards Alliance launched Matter with a clear promise: one protocol to unify smart devices across Apple, Google, Amazon, and Samsung. According to Apples own product pages, the company has backed Matter since its inception.
A household in Bandung might have a Nest thermostat, a Philips Hue bulb, an Aqara motion sensor, and a Samsung SmartThings hub. Each one demands a different app, a different account, and sometimes a different Wi-Fi band. The promise of Matter is that one app controls all of them. The reality in 2026 is that most users havent seen that come true.
What Actually Changed in the Last Year
In 2025, the alliance expanded Matter to cover appliance categories like dishwashers and air conditioners. That sounds good until you realize most households replace those devices every seven to ten years, not every product cycle. The smart home is not a smartphone market where users upgrade annually. It is a slow-turnover ecosystem, which means interoperability gains take longer to reach living rooms.
A survey of smart-home device sales in Southeast Asia showed that bundled kits, not individual certified sensors, still drive the majority of purchases. Those bundles come with their own apps, and those apps dont always talk to Matter controllers. The standard is growing, but adoption curves for durable goods dont match software release cycles.
The chip makers havent fully aligned either. Thread-enabled radios, which Matter uses for low-power device networking, remain a premium feature rather than a default. A basic motion sensor at a local retailer might advertise Wi-Fi only, forcing the user to maintain two networks just to keep the device online. It is not seamless; it is two networks with a label that says they are the same.
The Cost of a Fragmented House
For a user in Surabaya, the practical cost is not abstract. It is the time spent resetting a sensor because the app wont see it after a router reboot. It is the extra power draw from a bridge that translates between protocols because the manufacturer never ported its device fully. It is the security exposure when a device requires a cloud account just to turn on locally.
According to a report by Counterpoint Research, the number of smart-home devices installed in Indonesian households has grown sharply over the past three years, but the share running on open or interoperable protocols is still a minority. The rest run on proprietary stacks, and those stacks dont talk. That does not mean users are angry; it means they are used to it.
It is not clear this will hold. If regulators in the region start requiring data portability or local control for connected devices, the proprietary stacks will face real pressure. Until then, the standard exists on paper more than in the wall sockets.
Where It Goes From Here
The next real change will not come from a protocol update. It will come when a major electronics retailer in Jakarta stops selling bundled kits that require proprietary apps, and instead stocks Matter-certified sensors that work with any controller. That requires supply chain changes, not just software patches.
By 2027, analysts expect the smart-home device market in Southeast Asia to cross a threshold where interoperability becomes a purchasing factor rather than a bonus feature. Until then, users will keep adding devices faster than standards can catch up, and the smart home will remain a collection of smart objects that dont always agree.
Related coverage on IoT standards and Reuters on connected-device regulation. The standard is here, but the house is not ready.
The Human Cost Behind the Protocol
Every time a user resets a smart thermostat because the app lost connection, there's a small cost in time and patience. In Jakarta, where internet service can be uneven across neighborhoods, that cost isn't trivial. The device doesn't just need the protocol; it needs the network, the account, and the manufacturer server to all stay online at once. When any one fails, the device becomes a brick.
It's easy to blame users for not reading manuals, but the manuals themselves are often translated poorly, reference different app versions, and omit the bridge step entirely. A user who buys a certified Matter bulb might not realize their router needs to support Thread, or that the controller needs a firmware update that came out three months earlier. The standard is supposed to abstract those details away. It hasn't.
The result is a market where the most reliable smart home isn't the smartest; it's the simplest. Users report buying fewer devices each year, not because they don't want automation, but because the maintenance load of a fragmented system exceeds the convenience gain. That is a real signal, not a passing trend.
Retail Landscape and the Reality of Shelves
In a typical electronics mall in Yogyakarta, the largest display of smart-home tech features bundles. You'll find a Philips Hue starter kit alongside a Samsung SmartThings kit, each with its own cardboard sign promising voice assistant integration. The Matter-certified devices are usually a small subsection, often on a middle shelf, and they don't have a dedicated salesperson trained on their interoperability.
Sales staff at these stores report that customers rarely ask about the underlying protocol. They ask whether the bulb works with Google Home, or if the camera can be viewed on a phone app. The question of whether a device adheres to an open standard comes up only when something stops working. That is a telling sign: the protocol matters only in the moment it breaks, not when it functions.
The lack of in-store expertise means most purchasing decisions are made on price and brand recognition alone. That keeps demand for proprietary bundles high, which in turn keeps manufacturers from fully porting devices to Matter. The ecosystem is not a flywheel where Matter adoption drives more Matter adoption; it's a parallel market where legacy systems and new standards coexist without a single consumer-facing outcome.
The Developer Perspective
Developers building smart-home integrations spend a disproportionate amount of time on exceptions. A Matter-compliant device should work out of the box, but the long tail of devices that Matter barely touches requires custom translation layers. These developers often maintain multiple code paths: one for Matter over Thread, one for the device's native Bluetooth, one for the legacy cloud API, and sometimes one for a local bridge. The maintenance burden grows with every new device model that enters the market.
Platform teams at Apple, Google, and Amazon each prioritize Matter differently. Apple has been the slowest to expose Matter controls in its home app, which means third-party developers still need to support HomeKit as a fallback. Google's Nest division has been more aggressive, but the ChromeOS and Android sides of the house don't always share the same integration code paths. Amazon's side is the most Matter-forward, but it also has the largest installed base of Alexa-first devices that resist re-architecting to an open standard.
The Regulatory Horizon
Indonesia's telecommunications regulator has signaled interest in rules that would require locally manufactured connected devices to support local control without a mandatory cloud account. That would be a significant shift from the current model, where many devices from overseas manufacturers require constant contact with overseas servers to verify a purchase or firmware update. If those rules move from draft to law, manufacturers have two paths: strip away the mandatory cloud requirement, or exit the Indonesian market.
India's Ministry of Electronics and Information Technology has proposed a similar framework, calling it a 'security-by-design' mandate for connected devices. The European Union already has the Radio Equipment Directive, which now includes minimum data-privacy and interoperability requirements for all radio-controlled devices. Those three markets — Indonesia, India, and the EU — cover a large share of the world's smart-device manufacturing. If any of them enforces local control or data-portability rules, the manufacturers will feel the pressure whether they like it or not.
The Users Who Have Given Up
There are users who have simply stopped adding new devices. A homeowner in Makassar who bought a set of smart plugs three years ago still has them on the original app, unchanged, because the promised Matter integration never arrived. Their house is technically 'smart,' but it's a closed loop with no external connections and no future expansion.
That choice — to stop — is becoming more common. It is not a rejection of automation; it is a calculation that the maintenance tax of a partially smart home outweighs the benefit. Those users are effectively opting out of the standard, which means the standard matters less every year.
What a Real Fix Looks Like
A real fix would require device manufacturers to commit to Matter for the full product life cycle, not just the first six months after launch. It would require retailers to have at least one staff member who can explain the difference between Wi-Fi, Thread, and legacy protocols. It would require platform providers to agree on a common timeline for firmware and app updates. None of those things are likely to arrive in a single software update.
The Matter standard is real. The devices are real. The question is whether the market will choose interoperability over lock-in. That is not a technical question; it is a commercial one. And in 2026, the commercial answer is still coming into focus.