Use M100 hub as Thread Border Router with Smartthings Hub v2

Everything Matter
, , ,
1

I want to use the M100 as a Thread Border Router. I am able to add it to Smartthings, as well as to the Aqara app. When I try to add a Matter-over-Thread device in Smartthings, I get a prompt to choose the Thread network. I choose the one that my M100 hub is broadcasting. Smartthings then prompts to enter a “32-character network key” and I have no idea where to find this. How do I get through this stage?

1 Like
2

Hi. Try the following:

  1. Set up the Aqara Hub:
    First, ensure the Aqara Hub (M100) is fully set up and updated in the Aqara Home app, and that the Thread network was created. This step was likely already completed during your initial Aqara Hub setup.

  2. Add the device to Aqara:
    Add your Matter-over-Thread device to the Aqara Home app by scanning the physical QR code found on the device.

  3. Generate a Multi-Admin code:
    In the Aqara app, go to the settings of the device you just added: General Settings → Matter → Matter Pairing Code to generate a temporary code.

  4. Add to SmartThings:
    Enter the newly generated code from step 3. (Note: Do not use the physical sticker on the device for this step, as that code is already linked to the Aqara app).

1 Like
3

Thanks for the help. So, now I can’t seem to add anything to the Aqara hub directly. I get a page that says the Hub is not on the same network as my phone, and I should join that network with my phone. Except it is the same network.

At the same time, by connecting the Hub to the Aqara app, it lost connection with Smartthings. Now, if I try to connect to Smartthings, ST will see it, but can’t connect to it even on reset. So I currently have a Hub that can’t connect to anything.

1 Like
4

It’s possible that your smartphone, the Aqara Hub and maybe also the Samsung Hub are all connected to the same Wi-Fi SSID but using different frequencies: 2.4 GHz, 5 GHz or 6 GHz. Here’s an excerpt from my tutorial:

Try disabling the 5 GHz network and try again.

What exactly do you mean by that? Have you set up the Aqara hub as a Matter Bridge in SmartThings, or the SmartThings hub as Matter Bridge in Aqara, or are you using the third-party ecosystem service (Connect to Ecosystems) in the Aqara app?

2 Likes
5

OK, now I can get past the Matter controller stage in the Aqara app. I did so by going on my regular Wi-Fi for both the phone and the M100. I had it on the Guest Network before because I wanted to isolate to 2.4GHz only (which the GN does automatically), but it wouldn’t work. I had assumed it would because previously I was able to switch to that Wi-Fi network after setup.

Following that, the Aqara app couldn’t find the new Thread device I tried to add. I disabled by 5GHz radio entirely, confirmed that my phone is only running on 2.4GHz, and still the new Thread device can’t get past stage 3 (“The device is connecting to the network…”).

Which would be fine since I don’t want to use the Aqara app if I can help it, but even though the ST hub and app detect the new Thread device, I can’t get past the 32-character network key stage in that approach.

3 Likes
6

I’d love to get to some of these options. The closest I’ve gotten is

I can add the M100 to Aqara, but I can’t add devices to it
I can add the M100 to Smartthings, but can’t seem to leverage it as a Thread Border Router
I can add Thread devices to Smartthings, and select the Hub100’s Thread network, but I can’t get past the network key requirement

So, as far as I can tell, I’ve not been able to get to and Bridge options, third-party connection options, or any sort of Multi-Admin.

1 Like
7

Also, if I add the M100 to the Aqara app, and then try to use Connected Ecosystems, it creates a Matter pairing code. Smartthings can scan that code, but then demands that the device be in pairing mode…which disconnects it from Aqara (unless there is another mode besides holding the button for 10 seconds and getting flashing yellow). In fact, ST can’t connect at all this way, even if I activate the mode. I have to disconnect it from Aqara to get ST to accept it.

1 Like
8

If you add the Aqara Hub to SmartThings, the Aqara Hub acts as a Matter Bridge and can pass on Zigbee devices to SmartThings as Matter devices. If no Zigbee devices are connected to the Aqara Hub, you can just skip this step.

Conversely, if you add the SmartThings Hub to the Aqara App, the devices from SmartThings are bridged into the Aqara ecosystem. However, if you don’t actually intend to use the Aqara app, you can skip this as well.

Regarding the process - connecting a Matter-over-Thread device to the M100 Hub:

  1. When setting up the M100 Hub: a) If a Thread network already exists, the Hub joins it (with Thread 1.3, the Hub receives the credentials from your smartphone if the network was set up using your smartphone account). b) A new Thread network is created (the credentials are stored on your smartphone but are not viewable).
  2. When you add a Matter-over-Thread device to the M100 Hub (Thread Border Router), a Bluetooth connection is established from your smartphone to the device to share the Thread credentials. The device then attempts to join the Thread network. In your case, this fails—likely because it received outdated credentials. If the Hub was reset (holding the button for 10 seconds and getting flashing yellow) in the meantime, the old credentials became invalid. You must create a new Thread network in the Aqara app settings to save the current, valid credentials on your smartphone. Afterward, repeat the steps from my first post.
3 Likes
9

Thanks for he details. So, here’s what I did:

  • Reset the M100 hardware until it flashes yellow
  • Added the M100 to the Aqara app
  • Created and joined a new Thread network on the Aqara app
  • Attempted to add the new Thread device to the Aqara app

It still stays stuck on “This device is connecting to the network…” before failing.

Similarly, if I try to add it to Smartthings, I see the Thread network but have no network key to give it.

I thought maybe I needed to bind my Smartthings account to Aqara first, but even after successfully doing so I ended up with the same situation.

1 Like
10

Another possibility is that the credentials were correct and the device connected successfully, but the confirmation from the device is not reaching your smartphone. Is IPv6 still enabled on your network router, and are the M100 and your smartphone in the same Wi-Fi segment on the same frequency (e.g., 2.4 GHz)?

Technical Note: This is crucial because Matter relies on mDNS (Multicast DNS) via IPv6 for device discovery. If your router blocks IPv6 multicast or if there are communication barriers between the 2.4 GHz and 5 GHz bands (often caused by “Band Steering”), your smartphone will not be able to “see” the device, even if it is technically already connected to your network.

3 Likes
11

Definitely on 2.4GHz (I disabled the 5GHz band for this experiment, and can see that my phone has switched from the latter to the former). Fairly confident on IPv6, too. Steering is also disabled.

1 Like
12

Which smartphone (iOS or Android) are you using, and which Matter-over-Thread device are you trying to connect? There might be compatibility issues with certain device/smartphone combinations.

1 Like
13

That 32-character key is the Thread credentials (PSKc).

You normally shouldn’t have to enter it manually—if M100 is properly linked via Matter, SmartThings should pick up the Thread network automatically.

Make sure the M100 is fully set up in Aqara first and shared to SmartThings via Matter, then try adding the device again. If it still asks, the Thread network isn’t syncing between the hubs.

14

Thread network credentials are only exchanged if both hubs support Matter 1.4 and Thread 1.4. I could be wrong, but I think the M100 only supports Thread 1.3. In this case, the Thread credentials can only be exchanged via Bluetooth on a smartphone or as Workaround use Multi-Admin.

I explained this in more detail here:

2 Likes
15

Android and Sensereo MSC

Is there a way to know whether it’s properly linked / fully set up? If I add the hub via matter code to either Aqara or Smartthings, it shows up as a normal device, seemingly without issues. I just can’t add any Thread devices to it (or at least this one, I don’t have any others to test).

This is part of the problem. I can add the hub to either Smartthings or Aqara, but if I try to share it to the other platform via generating a Matter code, it just tells me to prepare the device, at which point the only way to get it into pairing mode is to hold the button down for 10 seconds until it flashes yellow, which I think effectively resets it. Is there a way to get the M100 to pair / Multi-Admin without resetting it?

1 Like
16

Another thought: The ST hub is connected via ethernet to my router. Does it only work with Wi-Fi for this scenario?

17

At this point, I’m thinking of giving up and returning the device, it’s too much headache for something that should be dead simple

18

As previously mentioned, the hubs act as Matter Bridges. They bring devices connected to the hub into the respective ecosystem—but specifically non-Matter devices, such as Zigbee devices, not Matter devices themselves. Therefore, if no devices are connected to the hub, adding it would not be useful for you.

That’s exactly what I was going to suggest next—testing it with an Aqara Matter-over-Thread device to rule out any basic connectivity issues first.

I think there is still a fundamental misunderstanding regarding the roles of the hubs. Sharing one hub with another platform via a Matter code (Multi-Admin) only serves the purpose of making the non-Matter devices (like Zigbee) that are connected to that specific hub visible in the other ecosystem. It does not “transfer”, “share”, or combine the hardware functionalities—like the Thread Border Router capabilities—between the hubs.

Since the hubs are not Matter-over-Thread end devices themselves, but rather both are Matter Controllers and Matter Bridges—and only one of them is a Thread Border Router (presumably Thread 1.3)—I find it unlikely that the two hubs exchange Thread credentials in this manner.

My recommendation is still to connect the Matter-over-Thread device directly to the Thread Border Router (Aqara Hub) first. Once that’s done, you can use Multi-Admin to share the device via Matter with the SmartThings Hub over LAN/Wi-Fi. In this scenario, no Thread credentials need to be shared with SmartThings at all, as the Thread connection is maintained by the Aqara Hub, and the communication between the hubs then happens via your local network (LAN/Wi-Fi).

No, Ethernet vs. Wi-Fi doesn’t matter—Matter is “transport agnostic”. The real issue is usually the network configuration. mDNS and IPv6 must be able to travel freely between all devices.

Please check these common blockers:

  • VLANs: If devices are on different VLANs, you need an mDNS Reflector/Proxy.
  • VPNs: Disable any VPN on your smartphone during setup.
  • Isolation: Ensure “Client Isolation” (common on Guest Wi-Fi) is turned off.
  • Firewalls: Make sure IPv6 and Multicast traffic (UDP 5353) aren’t being blocked between your LAN and Wi-Fi segments.

I totally hear you—it’s frustrating when “simple” tech feels this complex. Before giving up, try one last “clean slate” approach:

  • Reset: Factory reset both the M100 and the Thread device (Sensereo MSC-1).
  • One App: Focus only on the Aqara app for now; ignore SmartThings during the initial pairing.
  • Platform Swap: If possible, try the setup with an iPhone or iPad. iOS and Android handle Thread credentials differently, and switching platforms often bypasses hidden system bugs.
  • Network: Use 2.4 GHz Wi-Fi and ensure any VPN is OFF.

Once that first “handshake” is successful, the rest usually falls into place.

Note regarding the M100 Hub:

  • Long press for 10s: Reset the network and unbind the device
  • Press 10 times quickly: Restore the factory settings
1 Like
19

Thanks for the detailed reply. So, I did this:

  • Factory reset the M100 (red lights)
  • Nothing for the Sensereo MSC-1 (it’s already in pairing mode and the method for factory reset doesn’t do anything)
  • Checked VLANs (none)
  • Checked VPNs (none)
  • Checked Client Isolation (none, also not on Guest Network)
  • Confirmed my router (MX4200) automatically allows IPv6 (enabled, auto) and Multicast traffic
  • Made one possible significant change: enabled “Homekit integration”, which I believe might be my router’s user-friendly term for mDNS
  • Connected M100 to Aqara app
  • Created a new Thread network (note, the app hangs on this, which hadn’t happened previously, but if I tap out of the Thread network screen and re-enter, it shows a new network and the old one disconnected, and I delete the old one)
  • Attempt to pair Sensereo MSC-1 with Aqara app

At this point, the pairing gets stuck on the 3rd step (“The device is connecting to the network…”) as usual.

I’ll also note that the Aqara app detects the M100 when pairing the Hub to the app, but I have to scan the Matter code for the Sensereo MSC-1 to get started pairing.

20

I’ve just thought of something else. You also need an IPv6 prefix. However, some ISPs don’t provide one. Perhaps that’s the case for you.

It’s better to specify a prefix in the router anyway. Can you find such a setting in your internet router?

Can you check your smartphone’s settings to see if you can view the IPv6 addresses? There should be three different addresses visible for your smartphone.