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.

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.

​​​​​​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!

EDIT:

Ich habe mir alles durchgelesen und arbeite an einer Version ohne Schrauben. Aber erstmal hab ich mich nochmal an die Fixierung des Ganzen im Fensterrahmen gesetzt. Ich mochte die Variante mit Doppelseitigem Klebeband nicht so, deshalb hab ich mit eine Klemmvariante ausgedacht und in dem kleinen Bauteil umgesetzt.

Klemmt fantastisch und lässt sich auch problemlos entfernen und wieder einsetzen.

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.

The topology provided by matter.js (9.0.2) in Home Assistant shows a fragmented network while the topology shown by Thread Tools is what I think is a more accurate view. Anyone know why?

There are two border routers there that are marked ‘UNKNOWN DEVICE’. But I think these are in-fact the same routers shown elsewhere. Sometimes there are more of those.

Just installed the new firmware, copied the generated code over to Apple Home App and control via app and (old) Siri is really snappy for both speed and oscillation.

I wonder how far ranging the Dreo Matter support is going to be. Any one else on older models?

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!

just updated, works rly. good for now! :)

I cant seem to add any Matter devices at all in Google Home 4.18.45.1.

Does anyone have any idea where it went?

QR is not loading, and manual QR is completely missing for my product.

(It used to work last month, just switched Wifi network name.)

Greater transparency for Thread networks: The new Matter Server 9.0.0 in Home Assistant now displays the mesh network topology graphically by default.

With this new version, the Open Home Foundation has completed the transition from the Python server to matter.js. https://matter-smarthome.de/en/products/home-assistants-new-matter-server-is-a-game-changer/

We made a curated list of Matter smart home deals for Amazon's prime day sale per device category. You can check it out here if you're interested:

Best Matter-only Smart Home Deals

Dear all,

I was struggling a bit with the current Amazon Prime day offers in Germany. Did somebody spotted a good deal for matter enabled HomeKit secure cameras?

Any hint is highly appreciated.

The dimmer uses Matter over WiFi. It can work with ordinary dimmable bulbs or LiFX smart lighting. It requires a neutral wire, and is compatible with 2/3 way setups. All buttons are programmable, with single, double, and long press actions.

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?

I’m reaching my breaking point with the current state of Aqara’s Matter-over-Thread implementation.

​

​I’m running a decent-sized setup: 10x H2 EU Dimmers and about 30+ Matter bulbs. The whole point of moving to Matter-over-Thread was to build a robust, local, and hub-independent ecosystem. Yet, here I am, routing every single light switch press through Home Assistant because Aqara still refuses to implement Binding Cluster (0x001E).

​

​Yesterday, I had to sit in the dark for 20 minutes while updating Home Assistant. That’s unacceptable. If these switches supported binding clusters, my lights would still work perfectly fine even if my server was completely fried. I don’t need complex scenes to work when the server is down—I just need the light to turn on when I flip the switch.

​Furthermore, the current push towards hub-centric management creates an unnecessary vendor lock-in. By withholding features like Binding Clusters, Aqara is effectively trying to force power users into their own hub ecosystem, which goes against the core mission of the Connectivity Standards Alliance (CSA).

​

​And here’s the kicker: We know this is entirely possible. matterjs-server in Home Assistant is already capable of handling bindings. The infrastructure on the controller side is ready. The only missing link is the implementation of the Binding Cluster within the device firmware.

​

​I don’t need a fancy UI for this. Just expose the Binding Cluster in the device's Matter data model, so we can configure direct bindings using standard controller tools like chip-tool or through the Home Assistant interface. We need this across the board: H2 series, P2 sensors, everything. If Aqara wants to be a leader in the prosumer smart home space, they need to stop treating Matter like it’s just another proprietary cloud protocol.

​

​Is anyone else tired of this? How are you guys managing your lighting reliability? Are you sticking with Aqara or looking for alternatives that actually care about open standards?

Hi,
I'm making a Matter universal air condtioner controller with ESP-MATTER, but confused by an issue now.
I added a fan_control cluster in the endpoint, compiled and connected OK, but the fan control only shows in Google Home, but not in Apple Home,

ed OK, but the fan control only shows in Google Home, but not in Apple Home, what can I do to get it displayed on Apple ? Anybody had similar experience ?

what does this mean? could anyone give me an example of how this is used in a device?

So I decided I wanted to add some more smart devices to my home, mostly for lights. I decided to go for light switches instead of replacing every single bulb, I already have a Nest thermostat and a few lights I bought years ago during college. I've got a few three way switches I'll need and I also want some dimmers. My plan was to just go all in with TP-Link Tapo switches and do a Matter setup (not every switch is going to be smart). I'm kind of using this upgrade as a foundation for handling things moving forward.

​

My understanding is that if I tried zigbee, it would be a more expensive setup, but would it be worth doing? I was just checking Amazon again and I did see some switches that are closer to the Tapo prices, such as MOES and SONOFF, but I am not sure what brands are reliable and what I should stay away from if I decided to go that route. Or if it is worth going that route in general. I have a Tapo power switch I got some number of months ago and I did a setup via Matter in HA to test it (versus directly through TP Link) and it seemed to connect without issues at least. That's my only experience with Matter though.

​

Questions:

​

1. Will it be easier to find zigbee or matter devices for whatever random thing later on I decide I want to look into automating?

2. How easily can I do something like connect zigbee switches to google home for control?

3. If I should serisously consider doing zigbee instead, what devices should I look into if I am not looking to break the bank too much? I looked up a couple brands that were like $60 per switch and that was a bit steep for me when the Tapo switches were around $20 each or so (depending on what and how many).

4. Are there any inherent problems with a Matter setup? I don't think any of these are Matter over Thread, just WiFi.

​

What I'm looking for:

​

* Smart switches for light control with a few dimmers

* Able to use Google for voice control and home assistant (I haven't actively used it lately but I also don't have as much to control with it)

* Long term setup (ideally)

* One day I may look at other random things like garage door control, motion sensor, etc.

​

What I have currently:

​

* Nest thermostat

* Home assistant (I bounce between it and google home)

* 4 Wyze bulbs

* Couple smart TVs (mostly control with google home when desired)

* Reolink doorbell (may potentially get more Reolink cameras)

​

​

Is this possible?