r/MatterProtocol

I'm quite excited to share this video as this project has been a long time in the making!

Using the Matter protocol, I'm building a Home Energy Manager. I've shared a few posts about this on the sub, but this is the first end-to-end video. It's still a work in progress and I'm not ready to share the code just yet, but I plan to full open source this.

The initial goal is to help me maximize the amount of self generated solar power. The energy manager does this by using machine learning and forecasting. It learns energy usage patterns in the home and from individual appliances. It can then generate a schedule of appliance use to make the most of this surplus solar.

I don't know if the idea has any merit yet, but it's something I've wanted to try for a long time.

I've written up a lot of blog posts on the technical side of things, and you'll find them on my blog: https://tomasmcguinness.com/building-a-matter-home-energy-manager/

When I do publish the code, it will be on my github: https://github.com/tomasmcguinness You can find a few of my other Matter projects up there too.

I've been struggling with this device for a while. Does anyone have an idea what's going on and how to get it to properly pair?

2026-06-30 15:36:40.356 DEBUG  MdnsAdvertisement    Broadcast kind: operational service: mdns:6CA53F524F4442F3-000000000001B669._matter._tcp.local number: 578 next: 1m 30s
2026-06-30 15:36:57.771 INFO   WebSocketC~erHandler [3] WebSocket connection established
2026-06-30 15:36:57.773 DEBUG  WebSocketC~erHandler [3] Sending server info
2026-06-30 15:36:57.779 DEBUG  WebSocketC~erHandler [3] WebSocket request {"message_id":"499065763","command":"start_listening","args":{}}
2026-06-30 15:36:57.782 INFO   WebSocketC~erHandler WebSocket server start_listening
2026-06-30 15:36:57.782 INFO   WebSocketC~erHandler WebSocket server start_listening. Returned 0 nodes
2026-06-30 15:36:57.782 DEBUG  WebSocketC~erHandler [3] WebSocket response (start_listening) 499065763
2026-06-30 15:37:00.019 DEBUG  WebSocketC~erHandler [3] WebSocket request {"message_id":"499065764","command":"get_loglevel","args":{}}
2026-06-30 15:37:00.042 DEBUG  WebSocketC~erHandler [3] WebSocket response (get_loglevel) 499065764 { console_loglevel: "debug", file_loglevel: null }
2026-06-30 15:37:10.606 DEBUG  WebSocketC~erHandler [3] WebSocket request {"message_id":"499065765","command":"set_wifi_credentials","args":{"ssid":"SSID_REDACTED","credentials":"WPA_KEY_REDACTED"}}
2026-06-30 15:37:10.606 INFO   ConfigStorage        Set config key wifiSsid to SSID_REDACTED
2026-06-30 15:37:10.616 INFO   ConfigStorage        Set config key wifiCredentials to <redacted>
2026-06-30 15:37:10.620 INFO   WebSocketC~erHandler Broadcasting server_info_updated event { fabric_id: 2, compressed_fabric_id: 7828733150003217139, fabric_index: 1, schema_version: 11, min_supported_schema_version: 11, sdk_version: "matter-server/1.1.2 (matter.js/0.17.4-alpha.0-20260625-0f2168fd4)", wifi_credentials_set: true, wifi_ssid: "SSID_REDACTED", thread_credentials_set: false, bluetooth_enabled: false, ble_proxy_enabled: false, controller_node_id: 112233 }
2026-06-30 15:37:10.621 DEBUG  WebSocketC~erHandler [3] WebSocket response (set_wifi_credentials) 499065765 {}
2026-06-30 15:37:18.110 DEBUG  WebSocketC~erHandler [3] WebSocket request {"message_id":"499065766","command":"get_loglevel","args":{}}
2026-06-30 15:37:18.110 DEBUG  WebSocketC~erHandler [3] WebSocket response (get_loglevel) 499065766 { console_loglevel: "debug", file_loglevel: null }
2026-06-30 15:37:24.103 INFO   WebSocketC~erHandler [3] WebSocket connection closed
2026-06-30 15:38:10.358 DEBUG  MdnsAdvertisement    Broadcast kind: operational service: mdns:6CA53F524F4442F3-000000000001B669._matter._tcp.local number: 579 next: 1m 30s
2026-06-30 15:39:24.789 DEBUG  WebSocketC~erHandler [2] WebSocket request {
    "message_id": "65967dbc3da241d696dd9deaa68f7a13",
    "command": "commission_with_code",
    "args": {
      "code": "MT:KUAA0YBV01B68K4YI10",
      "network_only": true
    }
  }
2026-06-30 15:39:24.793 INFO   ConfigStorage        Set config key nextNodeId to 15
2026-06-30 15:39:24.802 INFO   Discovery            Initiating discovery of node with discriminator 2425
2026-06-30 15:39:24.832 INFO   CommissioningClient  Operational address for undefined set to udp://[fe80::d60a:dcff:fe22:8d13%enp6s18]:5540
2026-06-30 15:39:24.833 INFO   Endpoint             server-2-134b.peer1 ready endpoint#: (unassigned) type: RootNode (0x16) behaviors: 💤parts ✓index ✓commissioning ✓network
2026-06-30 15:39:24.840 INFO   Controller~missioner Establish PASE to device DT: 769 PH: 36 ICD: 0 VP: 5004+13825 PI:
2026-06-30 15:39:24.845 DEBUG  MessageExchange      New exchange » •unsecured#b33456a429f28624⇵b2c3 protocol: 0 peerSess: 0000 SAT: 4s SAI: 300ms SII: 500ms maxTrans: 5 MRP I
2026-06-30 15:39:24.852 DEBUG  MessageChannel       Message » for: SC/PbkdfParamRequest backOff: 636ms id: •unsecured#b33456a429f28624⇵b2c3✉0ac36e95 type: 0x0/0x20 reqAck size: 79 payload: 1530012065188dbbe53f3f0455ea90e8d6fd3d10fca6d5f16d05e0b5bb6be359784c7f962502ec59240300280435052501f40125022c012503a00f24041324050c26060001050124070a2408061818
2026-06-30 15:39:25.491 DEBUG  MessageChannel       Message » for: SC/PbkdfParamRequest retrans#: 1 backoff: 617ms id: •unsecured#b33456a429f28624⇵b2c3✉0ac36e95 type: 0x0/0x20 reqAck size: 79 payload: 1530012065188dbbe53f3f0455ea90e8d6fd3d10fca6d5f16d05e0b5bb6be359784c7f962502ec59240300280435052501f40125022c012503a00f24041324050c26060001050124070a2408061818
2026-06-30 15:39:26.109 DEBUG  MessageChannel       Message » for: SC/PbkdfParamRequest retrans#: 2 backoff: 1.05s id: •unsecured#b33456a429f28624⇵b2c3✉0ac36e95 type: 0x0/0x20 reqAck size: 79 payload: 1530012065188dbbe53f3f0455ea90e8d6fd3d10fca6d5f16d05e0b5bb6be359784c7f962502ec59240300280435052501f40125022c012503a00f24041324050c26060001050124070a2408061818
2026-06-30 15:39:27.161 DEBUG  MessageChannel       Message » for: SC/PbkdfParamRequest retrans#: 3 backoff: 1.49s id: •unsecured#b33456a429f28624⇵b2c3✉0ac36e95 type: 0x0/0x20 reqAck size: 79 payload: 1530012065188dbbe53f3f0455ea90e8d6fd3d10fca6d5f16d05e0b5bb6be359784c7f962502ec59240300280435052501f40125022c012503a00f24041324050c26060001050124070a2408061818
2026-06-30 15:39:28.648 DEBUG  MessageChannel       Message » for: SC/PbkdfParamRequest retrans#: 4 backoff: 2.79s id: •unsecured#b33456a429f28624⇵b2c3✉0ac36e95 type: 0x0/0x20 reqAck size: 79 payload: 1530012065188dbbe53f3f0455ea90e8d6fd3d10fca6d5f16d05e0b5bb6be359784c7f962502ec59240300280435052501f40125022c012503a00f24041324050c26060001050124070a2408061818
2026-06-30 15:39:31.440 DEBUG  MessageExchange      Message •unsecured#b33456a429f28624⇵b2c3✉0ac36e95: Wait additional 8.44s for processing time and peer resubmissions after all our resubmissions
2026-06-30 15:39:39.885 INFO   Session              •unsecured#b33456a429f28624 Session ended
2026-06-30 15:39:39.886 WARN   Commission~onnection Address udp://[fe80::d60a:dcff:fe22:8d13%enp6s18]:5540 unreachable for known-address-0-udp://[fe80::d60a:dcff:fe22:8d13%enp6s18]:5540
2026-06-30 15:39:39.888 DEBUG  ParallelPa~Discovery Failed parallel commissioning attempt: [peer-communication] Could not connect to device
2026-06-30 15:39:40.360 DEBUG  MdnsAdvertisement    Broadcast kind: operational service: mdns:6CA53F524F4442F3-000000000001B669._matter._tcp.local number: 580 next: 1m 30s
2026-06-30 15:41:10.364 DEBUG  MdnsAdvertisement    Broadcast kind: operational service: mdns:6CA53F524F4442F3-000000000001B669._matter._tcp.local number: 581 next: 1m 30s
2026-06-30 15:42:24.833 ERROR  WebSocketC~erHandler [2] WebSocket error response (commission_with_code) 65967dbc3da241d696dd9deaa68f7a13 Commission failed: discovery of node with discriminator 2425 failed: No device could be commissioned (1 of 1 started attempt(s) failed, 1 discovered)
    at ServerError.nodeCommissionFailed (/app/node_modules/@matter-server/ws-controller/src/types/WebSocketMessageTypes.ts:100:16)
    at ControllerCommandHandler.commissionNode (/app/node_modules/@matter-server/ws-controller/src/controller/ControllerCommandHandler.ts:969:31)
    at async WebSocketControllerHandler.#commissionWithRetry (/app/node_modules/@matter-server/ws-controller/src/server/WebSocketControllerHandler.ts:697:47)
    at async WebSocketControllerHandler.#handleCommissionWithCode (/app/node_modules/@matter-server/ws-controller/src/server/WebSocketControllerHandler.ts:741:24)
    at async WebSocketControllerHandler.#handleWebSocketRequest (/app/node_modules/@matter-server/ws-controller/src/server/WebSocketControllerHandler.ts:485:30)
  Caused by: [discovery-aggregate] discovery of node with discriminator 2425 failed: No device could be commissioned (1 of 1 started attempt(s) failed, 1 discovered)
    at CommissioningDiscovery.onComplete (/app/node_modules/@matter/node/src/behavior/system/controller/discovery/ParallelPaseDiscovery.ts:180:23)
    Cause #0: [peer-communication] Could not connect to device
      at ControllerCommissioner.#establishPaseFromCandidates (/app/node_modules/@matter/protocol/src/peer/ControllerCommissioner.ts:322:23)
      at async ControllerCommissioner.commission (/app/node_modules/@matter/protocol/src/peer/ControllerCommissioner.ts:232:29)
      at async CommissioningClient.commission (/app/node_modules/@matter/node/src/behavior/system/commissioning/CommissioningClient.ts:275:52)
      at async Peers.runCommissioning (/app/node_modules/@matter/node/src/node/client/Peers.ts:365:20)
2026-06-30 15:42:40.366 DEBUG  MdnsAdvertisement    Broadcast kind: operational service: mdns:6CA53F524F4442F3-000000000001B669._matter._tcp.local number: 582 next: 1m 30s

Works with or without a neutral, uses Matter over Thread, has energy monitoring for the platforms that support it, and is currently on Amazon (US) for $39.

Hi All,

I thought I’d “fixed” my Homey SHS running on a Mac Mini but it keeps loosing control of Matter devices.

I suspect it is an mDNS issue. Before I pull the pin, has anybody discovered a workaround for this issue?

Thanks.

I'm trying to add a door sensor to one of my doors (potentially looking at the Ikea PARASOLL Door/window sensor). I'm going to create an automation in Home Assistant that will trigger a sound to play after X seconds of the door being open but I can't find a cheap device that will play the beep/alarm.

Does anyone have any recommendations on a device that would work? Everything I've seen is just to use a HomePod mini but I'd like something that can be plugged into a nearby outlet and isn't very visible/stays on the wall. I don't need it to have a microphone either.

Ich hatte vor kurzem vom User u/Gloomy_Independent44 das Projekt Ikea Myggbett perfekt für eine unsichtbare Installation, gesehen und fand es genial. Also ab in den nächstgelegenen Ikea und mal (neben ein paar GRILLPLATS, die man immer brauch) einen Myggbett gekauft, da mir die Idee imponierte aber leider nicht die CAD Datei, daher hab ich mich heute Nachmittag mal hingesetzt und nach ein paar Prototypen ein neues Gehäuse für den Myggbett designed.

https://preview.redd.it/b55jf4fjmv9h1.jpg?width=1600&format=pjpg&auto=webp&s=aacd19df5fcbc7f78e5e21c85126b57848decfcc

https://preview.redd.it/uvxodsjlmv9h1.jpg?width=1600&format=pjpg&auto=webp&s=c3b84ad7e07d2d143c1d1c9fd1d1a06eb57c160b

https://preview.redd.it/u9fkbtdomv9h1.jpg?width=3024&format=pjpg&auto=webp&s=232c3a07c5f0f0041f35483a41c8f3c5176ce4e6

Position vom Magnet im Fensterrahmen (aktuell nur probehalber mit Doppelseitigem Klebeband)

https://preview.redd.it/tuvq5qcvmv9h1.jpg?width=3244&format=pjpg&auto=webp&s=6cdf012ff88ed6c2e38d3d71c98caef126fcaa9c

Alle Teile

Am Ende hab ich den Grundkörper verbessert und noch zwei getrennte Deckel ergänzt damit die Platine und Batterie fest sitzen.

Es sitzt 1A im Fenster und reagiert absolut zuverlässig und schnell.

Ich hoffe es gefällt euch, schreibt gern noch ein paar Verbesserungsvorschläge in die Kommentare!

Over the last 48 hours I’ve finally managed to get my thread fabric to behave and get my collection of IKEA matter devices (yes, I bought a lot when they came out and yes, I was very annoyed) and a very temperamental Eve Weather to consistently connect. I’ve been using HA for about a year and rebuilt my entire smart home using it so this has been a real first world annoyance.

With the new matter server update in HA to be able to view the thread topology there was fundamentally nothing wrong with the setup but my connections were all poor and the disconnected nodes wouldn’t update. I run my thread network on 3 eeros with good coverage in a small house so it’s been irritating that the performance has been so disappointing.

Using the settings in the matter server, I set the network credentials, removed the buggy devices and cleared connections to dashboards and automations… and started the re-adding process. I had tried this previously but it just didn’t work on the old server.

Not only did the devices all connect first time, connect to an appropriate parent and… work but where the Ikea firmware had refused to update or struggled, it just updated instantly. The Eve weather (which is a great piece of kit when it works) is also stable for the first time since I’ve owned it.

Previously I’d also had to disconnect an alexa I have with a thread router built in but it just ignores it now and connects to the right fabric every time. Even with the right credentials set in the previous functionality it was just buggy and inconsistent.

I know a lot of people have been disappointed with the performance of the Ikea Matter products but whilst I’m only 48 hours in… this is the most consistent connection I’ve ever had and my investment in the Ikea products finally feels worth it.

Just updated my 765S’s firmware and setup was really easy! Siri control for both power and oscillation works really well!

Dreo’s communication could have been better but so far the actual execution is good!

I recently added a new Matter dimmer to Smartthings and then shared it to the dimmer manufacturer's app. Does it make a difference if you initially set up on Smartthings vs the manufacturer's app and then share to the other?

BTW, it's a Matter over WiFi dimmer.

I just recently got a bunch of Ikea matter over thread devices, and set them up using my primary network, because it was easier and that is where my border routers are. I also have a few Matter over WiFi devices that I am configuring.

I already have a separate WiFi and subnet set up for some cameras I use. My question is specific to the Matter over WiFi devices. Since they do not need thread, can I configure another 'fabric' (yes, I know, thread is IPv6 and a mesh, Matter over WiFi is just IPv4 and no mesh) in the separate IoT WiFi network, and still have the thread network on my main network?

My thread devices connect to an Ikea Diragera, Google Hub, and my Home Assistant server with the ZBT antenna. The Home Assistant server can see both subnets, and acts as my primary Matter server.

Hi all!

I recently started a new site, https://matterhome.io, to talk all about matter, matter news, devices, etc. The site is still work in progress, but we already have a team working on creating content, and we are publishing new things every day.

I know there are sites like this already, but I want it to give it my own spin, I'm so crazy for matter and the whole matter ecosystem, that I want to bring my own views, and also have a place where all things about matter are discussed.

I'm thinking of building a community around it, for now, anyone can submit content requests, provide feedback on existing content, etc.

Thoughts?

Thanks to all!

I bought an Aqara G350 and an FP2 presence sensor on Prime Day. I am running HA with Zigbee. I have never been able to add any Matter devices regardless of how many times I’ve tried. Of course the FP2 is Matter and I can’t get it into the system to configure in the app. Any suggestions are greatly appreciated

I'm playing around with an ESP32, Matter and its group support. I'm trying to test groups using a Nanoleaf Essentials A19-A60 bulb.

Can anyone confirm if they work with Matter groups?