Problem with sharing Thread devices with the SmartThings ecosystem

[JohnD]

@Majestic12

I use shared 2.4/5GHz SSID anyway and these devices don’t use Wi-Fi.

Your smartphone, all hubs, and all boarder routers don’t use Wi-Fi?
I only know that shared 2.4/5GHz SSIDs can cause problems. So it’s worth trying to pair with 5GHz turned off.

@Majestic12

They all have the same “tv” version (1.3.0) but different “nn” parameter (“AqaraHome-xxxx” for M3 Hub and “ST-TIZEN” for both Samsung networks) but I think it’s supposed to look like this.

Okay, so you have two separate thread networks. The goal when using Matter is to actually have a single, large Thread network. If all your devices (e.g. the Aqara M3, your Samsung TV and your soundbar) were on the same network, they would amplify each other and improve the range (i.e. they would form a mesh network). All your devices are running Thread version 1.3, which means they can technically connect to form a single network.

@Majestic12

if I turn off the ST hub I can’t even start the matter device adding process in the ST app

This is also due to the separate networks. The Aqara Hub manages the devices in its network separately, and the ST hub manages its devices in its network. If you switch off the ST hub, there will be no Broad Router for SmartThings.

@Majestic12

Shouldn’t the “share to other ecosystem" process retain the original network?

Actually, yes, but there can be problems with two networks. The Matter controllers themselves decide which network a new device should join. Parallel thread networks should be avoided.

Apple writes Thread credentials to its keychain and makes them available to others. That’s why I suggested deleting it. I read somewhere that it may be stored in Google Play Services on Android, but I can’t tell you where exacly.

Here’s a reading tip. Especially point 10.

10 Tips for a Stable Thread Network

Aqara promises to recognise Thread networks that have been set up by Border Routers from Google. The Aqara hub should then join them automatically. It’s strange that this isn’t working for you.

This article may be helpful:

How to Change the Thread Network in SmartThings

But the technology is still in its early stages and, if I understand correctly, it only works with an external SmartThings hub. However, it doesn’t hurt to check whether the option is available.

@Majestic12

My Door and Window Sensor P2 is still using the 1.0.0.0 version (1.0.2.0 available in the database) and the Motion and Light Sensor P2 uses 1.0.2.0 version (1.0.3.0 in the database).

I was able to update my P2 via Home Assistant, but this option was not available in the Aqara app. This may be the reason:

@mocelet

Aqara controls the distribution (rollout) of the updates through their hub so it’s gradual, may halt it if they detect something and then resume it, so the latest firmware is not available for everybody at the same time.

Home Assistant access the so called Matter DCL where vendors can publish the firmware update files for certified firmware versions so the platform can apply them: everybody sees the latest firmware. Well, unless they invalidate it like happened with the P2 door sensor twice (1.0.1.1 because it bricked devices and 1.0.2.0 because, I believe, reported wrong states) which now cannot be updated from Matter, only with Aqara hubs and only if it appears for your account.

Is that still the reason?

@Majestic12

probably adding Matter 1.4.0

That’s exactly right.
Take a look at this video (it’s best to set the audio to English):

As an alternative, try connecting all Matter sensors to the Aqara Hub and then adding your SmartThings account in the Aqara Home app via the ‘Connect to Ecosystem’ option and selecting ‘SmartThings’. However, this may result in Zigbee devices being displayed twice in SmartThings, as you are already using the Matter Bridge. You will then need to remove the Matter Bridge.