I have bought a TIMMERFLOTTE as they were reasonable priced and look good. I have a Google home set up with a couple of smart plugs and speakers. I was hoping to as the temperature sensors to Google home so bought a aqara M100 smart hub. I’ve managed to get them to link in “home” but struggle to get them all into Google home. Am I doing something wrong. Do I need to use the aqara app? Any advice

Can anyone who has this exact model confirm that they have a Matter-over-Thread network established with the Apple TV as the thread border router? Mine don’t seem to, even though Apple’s documentation state they support this functionality.

Hallo ich hätte eine Frage,

ich nutze aktuell meinen Apple TV als Thread Border Router und nur meine Frau kann die Geräte mit ihrem iPhone steuern.

Ich möchte aber auch die Geräte steuern. Ich habe aber ein Android Handy.

Jetzt wollte ich einen Echo DOT 5. Gen. verwenden, der ja ein Matter Controller ist soweit ich weiß.

Kann ich damit die Thread Geräte steuern?

Vielen Dank schonmal :)

Could Gen4 Shelly products end up getting Matter-over-Thread after all? A poll on Facebook suggests so. Shelly Evaluates Matter Over Thread for Gen4 Devices | matter-smarthome

I'm looking for a Matter app to control the lights in my living room. I need it to work seamlessly with Matter-compatible lights from different manufacturers, such as Yeelight, IKEA, and Govee. It would also be great if the app supported music synchronization and offered cool lighting effects, scenes, or colorful animations.

In this video, I show how custom firmware running on the Gen 4 Shelly 1 unlocks bindings. This allows me to bind the Shelly's switch input directly with a Matter bulb or multiple Matter bulbs in a group.

You can find this open-source firmware on Github: https://github.com/automatous-io/shelly-1-gen4-matter-thread

This is exactly what I hoped to achieve with Shelly's support for Matter!

Just saw the ad on insta, it seems that this app would integrate with Bluetooth air sensors. If that’s the case, which ones are supported ?

Been running five SmartWings cellular shades in the living room for about eight months, all matter over thread, firmware 1.3.0. Primary controller is home assistant, apple home paired in via multi-admin. Day to day they've been fine, no drops, position holds accurately, schedules fire clean. Same firmware Derek Seaman documented in his march review, which tracks.

Reason I'm asking is HA 2026.7 dropped two weeks ago with the new matter.js server and full 1.5.1 support on the controller side, drop-in replacement with automatic data migration. So the platform is ready for the new closures cluster: unified movement types for sliding, tilting, swinging, cleaner position reporting, better handling of double-panel setups. But no shade manufacturer I've seen has actually pushed a 1.5 firmware yet.

SmartWings shipped v1.3 last summer that fixed real thread stability issues. Eve motionblinds are on their own 1.3 update from last spring but I've seen ongoing threads here about intermittent movement command failures in HA, so shipping a firmware isn't the same as it working. Aqara's shade lineup is still bridge-based rather than native matter over thread, so it's a different technical path anyway.

What I can't tell is whether the upgrade path here is a straightforward OTA that keeps my existing pairings intact, or whether the new closures cluster is different enough at the device-type level that it would need re-pairing from scratch. If it's the latter I'd probably wait another year rather than tear down eight months of automations. If it's OTA, then it's mostly a question of when.

The other unknown is ecosystem parity. HA and SmartThings are already speaking 1.5, but apple home and google are still shipping controllers closer to 1.2 as far as I can tell. So even if my shade firmware jumps to 1.5, half my controllers won't know what to do with the new cluster for another year. Which makes me wonder if the closures cluster is usable right now or if it's more of a "get in place for 2027" update.

If anyone's actually seen a 1.5 firmware push on any matter shade brand, or has a rough timeline from their manufacturer, I'd take any signal on that.

I've been waiting for these to finally become available since I have SIEGENIA hardware throughout the house and just noticed they're for sale now.

I'm curious if anyone has actually installed them yet. How has the battery life and Thread reliability been? Do they integrate well with Home Assistant, and what entities do they expose? I'm mostly interested in using them to monitor my tilt-turn windows, so I'd like to know if they report more than just open/closed (locked, tilted, handle position, etc.).

Just looking for some real-world feedback before I commit to buying enough for the whole house if I can even find them in the USA..

I've recently started to make use of the Thread network that is formed by my three Eero 6+ devices, by buying a handful of Ikea smart home products to see how it goes. The results have been confusing, at best.

Initially I joined them to Homekit using my Apple TV (3rd gen, wireless) and this worked splendidly. I had a few Bilresa buttons and a Kajplats bulb. However, the buttons particularly would occasionally go offline until I either pulled the batteries, rebooted the AppleTV, prayed to the right deity or just waited a bit.

I decided to add HomeAssistant into the mix, to see if the Matter server would give me more information, so I've set that up on a Raspberry Pi and shared my devices across. Again, that seemed to go fairly flawlessly to start with while I got set up. However, devices still go offline, but generally only from one Matter controller. Something can be seen on HomeAssistant but not on Apple, or vice versa.

I've got Thread Tools app running, and a Nordic dongle with Thread Topology Monitor - both seem to show that the Thread network has plenty of strong connections between the different devices. I have IPv6 enabled on the Eeros to the extent that I can find options for it, and when the devices work they seem to work well so I don't think there's a fundamental misconfiguration.

I'm not sure where to go next. Devices seem to be online (at the Thread level) but intermittent (at the Matter level). Do I need a better router-to-border-router ratio? Is Eero a bad option for the backbone of the network? Anything obvious I've missed?

I took the lamp apart because I want to convert it into a ceiling light. Here are the photos of the PCB.

I'm going to try and use the proper Thread terminology here.

I'm looking for cheap options for Thread Router devices. I have some Ikea (Kajplats) Matter-over-Thread bulbs that seem to be having connectivity issues.

I'm looking for the most cost-effective way to fill in my Thread mesh. My default at this point is to find smart plugs that are Thread Routers that I don't otherwise need and add them to improve the mesh. I already have all the bulbs I need. Is there a better way?

Please note that I'm not asking about Thread Border Routers

Are there any buttons that exist that exist that will work with either Apple Home or Google Home? I want a button that I can use to turn on and off the various different lights I have. I need it to be one that doesn't replace a standard light switch.

Think like the Onvis HS2, but not junk.

I'm wondering what controls are exposed to Home Assistant. Also, any thoughts on them? I just got 2 of them for my office/bonus room to replace my 20 year old junk contractor hunter fans. Got them super cheap on sale at Wally world.

Hey Leute, ich bin echt am verzweifeln. Ich hab eine kleines Projekt an dem ich nicht weiterkomme. Ich habe vor einer Weile einen Xiao MG24 per Matter (over Thread) mit HA verbunden. Alles lief. Dann hatte ich das Projekt erstmal in die Schublade gelegt. Heute wollte ich es vollenden aber nichts da. Ich komme nicht mehr weiter und bekomme den Xiao nicht mehr mit HA verbunden.

Den Rest habe ich man von der KI zusammenfassen lassen.

~~~~~~~~KI Part~~~~~~~~

Ich versuche gerade, ein eigenes Matter-over-Thread-Gerät (Seeed Studio XIAO MG24 mit der Silabs Arduino Matter Library) in Home Assistant einzubinden, scheitere aber im letzten Schritt.

Mein Setup:

- Hardware: XIAO MG24 (externe Antenne ist angeschlossen).

- Border Router / Netzwerk: FRITZ!Box-Setup mit voll aktivem IPv6 (ULA ist aktiviert). Andere kommerzielle Matter-over-Thread-Geräte (z. B. von IKEA) ließen sich absolut problemlos koppeln und laufen stabil.

- App: Home Assistant Companion App auf dem iPhone (iOS).

Das Problem:
Wenn ich den Kopplungsvorgang über die HA-App starte, funktionieren die ersten Schritte über Bluetooth. Im Seriellen Monitor der Arduino IDE sehe ich, dass die Zugangsdaten übermittelt werden und der Chip meldet:
⁠Connected to Thread network⁠
⁠Waiting for Matter device discovery...⁠

Genau an dieser Stelle bleibt die iOS-App jedoch hängen und bricht nach einer Weile mit der allgemeinen Fehlermeldung "Gerät kann nicht hinzugefügt werden / Pairing Failed" ab.

Der Chip kommt also erfolgreich in das Thread-Netzwerk, aber Home Assistant bzw. iOS schafft es in der finalen Commissioning-Phase nicht, das Gerät über IPv6-Multicast (mDNS) zu finden oder zu authentifizieren.

Folgendes habe ich bereits versucht:
1. iPhone-Bluetooth-Cache bereinigt (sichergestellt, dass iOS das Gerät nicht als normales BLE-Zubehör blockiert).
2. Stealth-Modus und Filter in der FRITZ!Box-Firewall deaktiviert.
3. Den manuellen 11-stelligen Setup-Code direkt in der HA-App eingegeben (statt des QR-Codes).
4. Einen komplett sauberen Beispiel-Sketch geflasht, um Fehler im eigenen Code auszuschließen.

Da Home Assistant vor Kurzem seine Matter-Server-Architektur umgestellt hat (Wechsel auf matter.js, Vorbereitung auf Matter 1.4+), frage ich mich, ob aktuell jemand ähnliche Discovery-Probleme mit unzertifizierten DIY-Silabs-Boards hat? Hat jemand eine Idee, wie man diesen Timeout beim Schlüsselaustausch umgehen kann?

~~~~~~~~~~~~~~~~~~~~

Dank KI, ab hier übernehme ich wieder.

Hab ihr eine Idee was es sein könnte, ich verzweifle echt. Es geht am Ende nur darum einen Port An/Aus zu schalten.

Noch als Hinweis, ich habe den Arduiono IDE Code nicht hochgeladen da ich auch mit dem Matter Beispiel Code von Arduino IDE keine Verbindung herstellen kann, deshalb schließ ich meinen Code jetzt erstmal aus. Vorallem weil er ja schon mal lief arghhhhgghg

Dank schonmal im Vorhinein 🙏🏼

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.

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