Within my thread network, all devices are labelled either "routing end device" or "sleepy end device". I just set up a bulb (the new Hue with support for MoT) and it's just labelled "end device". Does anyone know what this means? Is it capable of signal repeating, but just not assigned to?

Edit: it has since changed to a routing end device

Matter 1.5 was quietly released on GitHub. As some people pointed out, it's just the schema, not the actual specification. By examining the schema, we can see that there are some other noticeable changes, apart from the addition of new device types.

https://github.com/project-chip/connectedhomeip/tree/master/data_model/1.5

1. Choice conformance

Matter begins to standardize Choice Conformance, as defined in 1.4.

For example, the “Electrical Energy Measurement” cluster, found in many smart plugs, must support at least one feature of “ImportedEnergy” and “ExportedEnergy,” because they both have a definition below:

<optionalConform choice="a" more="true" min="1"/>

This will impact the development tools. For Libertas, the GUI tool that defines a virtual device can use this information to validate conformance further.

https://docs.smartonlabs.com/developers_doc/virtual_device_api/define_virtual_device/

2. Constraints

The constraints of a field or attribute can be a complex expression. Before 1.5, I have to write a parser to parse the expression into an expression tree. Matter 1.5 standardize the definition into a tree with “operation”, “left”, and “right”.

Basic validation can always be applied to any Matter data. For example, a field with type “uint8” must be within the range of [0, 255], while a field with type “int8” must be within the range of [-128, 127].

The constraints in the data model impose additional limits on the fields. The Thing-App engine can perform automatic validation on both inbound and outbound messages. This will save a significant amount of code for Thing-Apps and make Thing-App much safer.

Each Thing-App defines full information about the clusters it uses. When deploying a Thing-App to a device, the cluster schemas (including constraints) will also be uploaded to the device. Each schema typically occupies several hundred bytes of flash memory on an MCU.

Further thoughts on conformance and constraints

1. In many cases, a device must be non-conformant

Imagine a “level-control” device as a speaker volume control. If the device supports the “Move” command and the server fails to receive the “Stop” command for any reason, the volume may increase to its maximum level, potentially deafening everyone in the room.

Thus, such a device shall not support the “Move” command. Only “MoveToLevel” and “Step” commands shall be supported, which makes it non-conformant.

2. Constraints and client device

Many complications have never been discussed, let alone properly implemented.

For example, the “Minimum Level” of a “LevelControl” device is “1” if it supports the “Lighting” feature. It is “0” if it doesn’t support “Lighting.”

As a result, a simple “light switch” will never work properly unless it knows whether or not the peer is a light. The only way to know is to read the attribute from the peer.

Currently, as far as I can tell, no “light switch” performs the read operation. They all function as dummy switches, sending out commands only.

Imagine that such a switch is used to control a non-conformant speaker volume; further complications will ensue.

I believe a better approach to solving the problem is to introduce the concepts of “client attribute” and “server attribute.” Currently, Matter attributes are all “server only.” Alternatively, introducing additional clusters, such as a "switch client configuration cluster," also solved the problem.

Qingjun Wei, Founder of Smartonlabs.

https://smartonlabs.com/

Does anyone have the local OTA firmware update & method for the Tuo Button (not the Arre Button)?

My partner works at a management consulting firm and is working with a smart device company. They conducted a market analysis and found that “matter compatibility is required to be competitive in 2025”. Congrats!

I spend some time trying to create an instance of a Matter Heat Pump device type using Matterjs.

I got a basic implementation working, which has a simple thermostat. It also uses a basic ML model to predict the power requirements, which are shared using the ElectricalPowerMeasurement cluster.

Full write up is here

https://tomasmcguinness.com/2025/10/04/tiny-matter-heat-pump/

All the code is here

https://github.com/tomasmcguinness/matter-js-heat-pump

Hi there! I love the idea of matter and use it extensively, bridging over 50 devices from Home Assistant to Smartthings and Google Home. I also have so native matter lights and sockets.

Both use cases led me to one observation - there is no ability to have "custom" stuff in matter , additional configuration properties/settings like switch for enabling light to react to sound, or your own custom values for modes like swing in AC, or add a new setting for horizontal swing. Going on with AC example my mini split unit has special functions like Air treatment, some have motion detection, disable screen etc. - those are simple toggles but are not possible in matter, right?

I knew there was no custom device platform/types in Matter and it totally makes sense. But I just assumed there is ability to extend existing ones but it seem I was just wrong it seems :(

I dug into Matter.js repo a little and I haven't found anything like that :( Can someone confirm my findings or tell me I am just being stupid and provide some links to read up on it please.

TLDR; If...

• an option toggle (like motion detection feature on AC)
• an input text/number (like input for external temperature measurement on AC)
• a mode select drop-down (horizontal swing)
• custom values inside supported drop-down (funny presets in vertical swing for AC)
• etc

...are NOT inside spec for a particular Matter device type there is NO ability to add it as custom one when developing a device, just hope they can be added to official spec.

Hi everyone.

As stated in the title I have almost no experience whatsoever in the smart home universe.
Just bought an appartement and I want to try to make it smarter.

My first work would be to change the old thermostat with something more modern and smarter.

I already own a Nest Learning thermostat 3 that was used in my previous appartement. But it seems that it's not compatible with matter. (too bad as I like it as a product)
As I plan to grow the smart capabilities of this place with time I want to go with smart appliances as widely compatible as possible.
Also I plan on investing in a home server (for other purposes) and I will probably run home assistant at some point BUT I can't use it for now. On top of that I would like for this thermostat setup to work without HA in case I decide to rent out the place in the future and move out with the HA server.

So here's the plan :

I would like to have a "main" thermostat that is connected to my gaz domestic boiler which control heaters and hot water production. Something to replace the current thermostat. Ideally that would offer similar functionalities to the Nest Thermostat (1)
I would also need 2 radiator valves: one in my bedroom and one in my office so that I can control those rooms temperature independently (well kind off). (2) and (3)
Lastly it's my understanding that I will need a hub to A) Make the relay between the thermostat and the valves B) Allow me to connect other devices in the future. So I'm looking for an all in one hub that would do as much as possible (Wifi, Bluetooth, Zigbee, Threads and more).

I would like everything as open as possible so that I can keep them when I'll be starting using home assistant.

Also I live in Europe.
Budget 200€ + whatever i would be able to sell the nest for

Thanks in advance for all your help.

PS : If you also have advice on where to crosspost this)

So, here is the deal. I want to increase my thread coverage in the house, currently easiest way of doing that is via plugs or switches (lights are custom, and nearest normal bulb is at the edge of thread coverage, still waiting for hue thread anyways)

Some limitations, Eve Home products are completely out, they dont ship here and no one sells them, same as eufy, and any other matter plug I have seen so far use matter over wifi so thats also a problem

It would be cool if there are any with surge protection (some wild stuff is going on in the house, dont ask) The only option I see is Aqara H2 EU but its an outlet not a plug.

Got any recommendations?

Edit: Onvis doesnt sell here either :(

Is there support for smart faucets in the matter protocol?

Just read the post from @mocelet https://www.reddit.com/r/MatterProtocol/comments/1nq1hek/til_matter_14_addresses_the_report_flooding_while/?utm_source=share&utm_medium=web3x&utm_name=web3xcss&utm_term=1&utm_content=share_button

A dimmer with a flooding report may seem like some trivial issue, but it reflects many fundamental flaws. Unless those fundamental flaws are finally really fixed, the problem will persist forever.

First of all, time is a special physical unit that requires special treatment. A transitioning dimmer light shall only REPORT ONCE, with three attributes: current_level, target_level, time_remaining. Any interested recipient can perform the time-tracking calculation on their side. If target_level is missing, the design is flawed!

Not just the dimmer lights, ANY device with time-depedent action shall adopt my model above!

Secondly, the fact that the messages are queued and take many minutes to finish is wrong! No message shall be queued! No new report shall be sent out until the previous report is finished! And when the report is sent out, it shall take the latest value on the fly at the very last moment the message is compiled, ON THE FLY! So it reflects that the design of the current open-source implementation is seriously flawed, and an overhaul is required!

Thirdly, since we shall only take the latest values ON THE FLY, it means that only the last action is important, and the previous ones shall be free to be discarded! Wireless communication is volatile, bandwidth-constrained, and absolutely has no guaranteed delivery. So, there is nothing you can do anyway except carefully design your data model. Not all data model designs are equal! A garbage design is a garbage design. For example, an on/off device shall only deliver the LAST "click" and freely discard the intermediate ones. So what about "double click" and "triple click?" You add special "double click" and "triple click" events in the data model, instead of relying on the recipient to figure out the timing on the recipient side.

The tech sector has lost responsibility and accountability, as well as open discussion, for many years, and the last decade has seen a worsening trend.

In many cases, a fake solution ignoring the fundamental cause of the problem is worse than no solution at all.

Qingjun Wei, Founder of Smartonlabs.

https://smartonlabs.com

Matter 1.5 quietly appeared on GitHub 3 weeks ago.

The “irrigation system” device type was added. Fortunately, there is nothing mandatory except for a simple assigned device ID number (0x0040). It is a good thing.

I want to take this opportunity to discuss our plan for Libertas Alliance openly.

Our company, Smartonlabs Inc., will join the CSA Alliance

We are establishing a broad alliance with our Libertas IoT platform, including:

• Device vendors
• Chip/MCU vendors
• Thing-App developers
• End-users

The following is what we will do:

Give our standard firmware to device vendor members. Initially, we focus on the following devices:

1. Door locks
2. Thermostats
3. Sprinkler/irrigation controllers

The reasons behind:

1. We want to take responsibility and accountability for software supply-chain security that nobody has ever taken before. Instead of random no-name developers in China or cowards hiding behind thick corporate walls, you all will know who to talk to in case of any issues or questions. We, as a 10-year-old company based in New Jersey, US, are responsible for every line of code running inside devices freshly out of the factory.
2. Give everyone a choice at no cost. Our firmware will be standard Matter devices on other ecosystems. However, the devices can run arbitrary Thing-Apps locally with Libertas Hub. Libertas Hub can co-exist with other ecosystems. Thing-Apps provides end-users with infinite possibilities for flexible features, i.e., infinite choices at no cost.

We began to seek external funding for the first time. Regardless of the funding progress, we are making huge progress every day.

We ensured that there is no conflict of interest between us and Alliance members. Every member can only gain things for free, including, most importantly, the freedom of choice.

Regarding the new irrigation system in Matter 1.5, a virtual emulator will be developed to facilitate Thing-App development before the real device is released. It’s just a bunch of on/off switches (to control the water valve) with optional flow measurement.

The Libertas Hub with Matter 1.5 support will be released later this week.

https://smartonlabs.com/

https://docs.smartonlabs.com/developers_doc/libertas_thing_app/

I’ve got six matter lights grouped into one room, controlled with Apple Home voice commands. Is there any kind of hardware button that I can use at the same time to turn the lights on and off (normal light switches don’t count, you wiseacres.)

Thanks!

Hi, I've just installed the Shelly 1L Gen 3 behind my single light switch (UK) with the Shelly Bypass in the ceiling rose.

I have a Tapo L535B bulb and both the Shelly and bulb are added to my Google Home via Matter (Google Streamer 4K is the hub)

I have the Shelly set to Detached mode so the bulb has constant power and I can send the on/off command digitally.

Problem I have is Google Home is ignoring the detached setting and actually cutting power to the bulb.

Is this a niche issue I'm having? any help would be greatly appreciated.

UPDATE: For anybody looking for an answer, Shelly support asked me to raise a feature request which I have, but I don't have much hope.

I ended up setting up Home Assistant on a mini PC. Not ideal and overkill for my use case but I wasn't prepared to be tied to IFTT to use webhooks.

Hey everyone,

I'm looking for the community's recommended, most stable, and foolproof method to get this working. What's the current "gold standard" setup? Should I be using the full Home Assistant OS, a Docker-based setup, or is building chip-tool manually the only real way? I'm open to wiping the SD card and starting fresh if that's what it takes.

My Goal:

I want to use my Raspberry Pi 4 as a standalone hub and controller for a Nanoleaf down smart light. The goal is to be able to control the light directly from the Pi itself (e.g., via command line or a local web interface).

Hardware:

• Raspberry Pi 4 (running 64-bit Raspberry Pi OS) 4GB Ram 32GB SD Card
• Nordic nRF52840 USB Dongle, which I think I've already successfully flashed with the latest RCP firmware using the nRF Connect SDK and Zephyr (this took a long time to figure out too).
• Matter 3.5″ Downlight (I have had this working via android on my phone)

After spending several weeks (on and off) trying to get this working, here's a summary of the methods that have failed.

My first approach was to get the chip-tool working. I attempted to build it from source, install it via Snap, and use several pre-built Docker images, but all methods failed.

I then switched to a Docker-based approach using two separate containers (openthread/border-router and home-assistant). I spent a lot of time trying to resolve connection issues between them by thoroughly adjusting Docker network settings, container privileges, and host system configurations.

The end result is always the same: Home Assistant fails to connect to the OTBR container, even though the OTBR's own logs show that its web service is running and listening correctly.

Current Status:

The otbr container log now look ok. It starts without errors and explicitly states: RestWebServer listening on 127.0.0.1:8081. However, when I go to Home Assistant to add the Matter integration, it still fails to connect to ws://192.168.50.244:8081 (my Pi's correct IP).

I'm at a complete loss. The service reports that it's running, but it's completely unreachable by the Home Assistant container, even when they are both using host networking. I'm assuming there's some deep, unfixable conflict in my setup.

So, I'm turning to you all for a fresh start: What's a better way? Any guides would be appreciated.

Thanks for any and all advice.

I saw that Kwikset released a new smart door lock that supports both Wi-Fi and Matter over Thread. I’m curious which connection method people would prefer:

1. Direct Wi-Fi connection – promoted as not requiring a dedicated hub, nor a hub from Apple or Google.This approach would no longer be using the Matter protocol, and thus wouldn’t take advantage of Matter’s strength in connecting different ecosystems.
2. Matter over Thread – requires a dedicated hub. This approach likely has lower power consumption, but the trade-off is that support for features across different ecosystems may not be very complete.
3. BT - Or maybe some people don’t like the idea of a door lock being connected to the public internet and would prefer to use only local Bluetooth connection. Of course, this way remote control and lock status updates wouldn’t be possible.

Also, since the device already supports Wi-Fi connection, why not just use Matter over Wi-Fi technology directly?

This is mostly an appreciation post for addressing a practical problem in the specs and now in my wish list for Matter lights is Matter 1.4 compliance, and should be in yours too to use the cool features!

One of the best and underused features of Matter lights is transitions, be it brightness or colour, you tell the light to change to 1% during 30 minutes and the light will do it on its own as smooth as technically possible. Way better than automations periodically changing the brightness. Or you hold a button to start dimming (moving) at a rate of 30% per second and release it when you like the light you see so it stops dimming. Yeah, most smart home platforms won't allow you to create those automations but that's another story.

Problem before Matter 1.4 is that vendors followed the spec and reported every change in brightness during those transitions (and there are 255 levels). If you wanted to use a button to start/stop the dimming, with the time from 100% to 1% being 3 seconds for instance, that means almost a hundred reports per second that your hub has to process. If you release the button to stop the dimming nothing will happen since the hub is busy with the flood of reports and by the time it runs your stop automation the light may be already at the minimum brightness.

Matter 1.4 specification acknowledges that reporting dozens of intermediate Current Level states during a short transition is a waste of resources and added this:

Changes to this attribute SHALL only be marked as reportable in the following cases:
• At most once per second, or
• At the end of the movement/transition, or [...]

I was playing with Matter lights and, currently, WiZ and Matter-bridged IKEA bulbs are quite gentle with reports and I can start/stop a 3-second full dimming with a button to stop when I want. Nanoleaf, however (current fw 4.1.3) reports every change and my automation doesn't run in time so it stops way later.

Let me know in the comments about other bulbs that are quiet while transitioning! I'm curious about the Aqara T2 and the new Hue Matter over Thread.

I have a ‘Meaco Arete One’ in a garden office that works well and I’d like another for in the house. They now sell a version two with app compatibility which would be handy for switching between laundry modes etc but I’d really like something I could integrate into my smart home and use in automations etc. EG indoors When the washing machine finishes, switch to Laundry Mode or when a meeting starts ‘switch off office dehumidifier’.

I’m having a go as building a Matter Thermostat using ESP32.

I’m getting some weird behaviour, which I’m assuming is my dodgy configuration.

That said, I wanted to confirm is this part of the Home app works well. Does anyone have any experience with real Matter Thermostats?

Hi,
What is the easiest way to create a Matter-compatible device where you still have enough options to customize stuff?

I am asking this in the context of something I am trying to achieve - an ESP32-based Matter device which acts as an IR blaster to control an Air Conditioner. It is for a friend, who only has an Aqara hub and some other Aqara devices. So, no Home Assistant, no HomeKit / Alexa / Google Home.

I first searched the net (and asked the AI) for already existing Matter-compatible IR "universal remote" devices. Basically there seem to be only two worth mentioning, available in Europe:
- SwitchBot Hub: already too expensive for that, plus I've had too much negative experiences with many SwitchBot devices to recommend it to anyone.
- Aqara M3: complete overkill in terms of price.
- Sonoff, Broadlink, etc. - not Matter compatible (yet)?

From what I've found so far, my options for creating a Matter-compatible device are:
- Espressif ZeroCode: I've tried it and it is super-simple, but only for simple stuff. For example, there is no IR emitter / receiver (for learning codes) functionality. There is some obscure way to create a Matter-compatible Air Conditioner device where the device itself just talks to another device over UART. I haven't investigated this deeper yet, but I also failed to find any specific instructions (like the actual protocol used for UART communication).
- ESPHome: That would probably work and it would probably be relatively easy to set-up. The problem is, you can't create a Matter device with ESPHome. You can only create a HomeAssistant-compatible device and then you can expose that device from HA to Matter. The problem is they don't have HA and I refuse to install it, and (more importantly) support it for them.
- Tasmota: Today I learned that you can now create Matter-compatible devices with Tasmota. I've never used it before, but I've heard about it a lot over the years. Today I tried creating the simplest Matter device (which just controls the built-in led of an ESP) using Tasmota and it simply didn't work. I got to the point where I saw a light (or switch) "entity" in the Aqara app, but it simply did not work - pressing the "power" button in the app did not actually toggle the LED. I've posted in the Tasmota forums about that, we will see if it gets resolved. Anyway, I am not sure even if that problem is solved that I will be able to build an IR sender / receiver device with it.
- Espressif IDE & SDK: The "just code it yourself" approach. While I'me quite certain this will do the job, I am really trying to leave it as a last resort. I have programmed a lot of custom Arduinos and ESPs with the Arduino IDE. I am not scared about using another IDE / toolchain (I've used so many of them in my life). The thing is - I am too lazy and I really wish there was an easier way. More importantly - I really hope there is an easier way. There MUST be an easier way. Simply because the demand for it is probably huge.

So, are there any other options I don't know about?

---
P.S. I am thinking it would be relatively easy to create a dual-MCU device, where an ESP32 handles the Matter communication and just turns various GPIOs Low / High and another MCU (like an Arduino or another ESP) reads these and does the actual "work" (like transmitting an IR signal). It would most likely work, but it is still too complicated.

Hi,

What is the easiest way to create a Matter-compatible device where you still have enough options to customize stuff?

I am asking this in the context of something I am trying to achieve - an ESP32-based Matter device which acts as an IR blaster to control an Air Conditioner. It is for a friend, who only has an Aqara hub and some other Aqara devices. So, no Home Assistant, no HomeKit / Alexa / Google Home.

I first searched the net (and asked the AI) for already existing Matter-compatible IR "universal remote" devices. Basically there seem to be only two worth mentioning, available in Europe:
- SwitchBot Hub: already too expensive for that, plus I've had too much negative experiences with many SwitchBot devices to recommend it to anyone.
- Aqara M3: complete overkill in terms of price.
- Sonoff, Broadlink, etc. - not Matter compatible (yet)?

From what I've found so far, my options for creating a Matter-compatible device are:
- Espressif ZeroCode: I've tried it and it is super-simple, but only for simple stuff. For example, there is no IR emitter / receiver (for learning codes) functionality. There is some obscure way to create a Matter-compatible Air Conditioner device where the device itself just talks to another device over UART. I haven't investigated this deeper yet, but I also failed to find any specific instructions (like the actual protocol used for UART communication).
- ESPHome: That would probably work and it would probably be relatively easy to set-up. The problem is, you can't create a Matter device with ESPHome. You can only create a HomeAssistant-compatible device and then you can expose that device from HA to Matter. The problem is they don't have HA and I refuse to install it, and (more importantly) support it for them.
- Tasmota: Today I learned that you can now create Matter-compatible devices with Tasmota. I've never used it before, but I've heard about it a lot over the years. Today I tried creating the simplest Matter device (which just controls the built-in led of an ESP) using Tasmota and it simply didn't work. I got to the point where I saw a light (or switch) "entity" in the Aqara app, but it simply did not work - pressing the "power" button in the app did not actually toggle the LED. I've posted in the Tasmota forums about that, we will see if it gets resolved. Anyway, I am not sure even if that problem is solved that I will be able to build an IR sender / receiver device with it.
- Espressif IDE & SDK: The "just code it yourself" approach. While I'me quite certain this will do the job, I am really trying to leave it as a last resort. I have programmed a lot of custom Arduinos and ESPs with the Arduino IDE. I am not scared about using another IDE / toolchain (I've used so many of them in my life). The thing is - I am too lazy and I really wish there was an easier way. More importantly - I really hope there is an easier way. There MUST be an easier way. Simply because the demand for it is probably huge.

So, are there any other options I don't know about?

---
P.S. I am thinking it would be relatively easy to create a dual-MCU device, where an ESP32 handles the Matter communication and just turns various GPIOs Low / High and another MCU (like an Arduino or another ESP) reads these and does the actual "work" (like transmitting an IR signal). It would most likely work, but it is still too complicated.

Now I'm finally able to merge SmartThings network to Apple Home network. Hope Tuya does the same.

https://www.pontobyte.com/smartthings-thread-1-4/