Thread unification of a smartthings dongle hub and Q990D hub

Devices & Integrations
,
1

To be blunt I have alot of questions and I am so lost in understanding how to fix anything, on the contrary I think I’ve been making it worse.

To start off is it even possible to unify these two hubs, I’ve looked at the firmware and in theory they should be able to but they aren’t external hubs so I’m assuming that changes things? Does that mean they aren’t on thread 1.4?

If they aren’t on thread 1.4 I would assume they are at the least running thread 1.3, therefore unification should still be possible.

When I initially set everything up I had set up the dongle first and that became the preferred, then I set up the Q990D. When I went into Google play services I can see the two networks, one being preferred and the other just being there. Since I wanted one network and I saw the different PAN IDs I reset the hubs set everything up again, I also have another TV which I plugged the dongle into to see what happens, PAN IDs were all different, went to look at thread networks and now they’re showing up as unavailable yet devices still connect so I have no idea what that unavailable is supposed to mean. I reset everything again cleared storage and cache from Google play services, and set up a single TBR, the q990d just to see what would show up and still showing up as unavailable.

If anyone understands what’s going on here would really appreciate the help!

Thanks

2

What version of hub firmware are the two devices running? My fridge hub is running 58.13 and is still on Thread 1.3 as evidenced by the output of dns-sd from my Linux computer:

=  ens33 IPv6 OpenThread BorderRouter #0B28                 _meshcop._udp        local
   hostname = [Samsung-FamilyHub.local]
   address = [192.168.1.148]
   port = [49154]
   txt = ["omr=@\253\024\227\216\018\166\000\001" "dn=DefaultDomain" "bb=\240\191" "sq=\026" "pt=\192\128\236{" "at=\000\000h\219\187F\000\000" "sb=\000\000\001\177" "xa=\230;\223\002\031\164\011(" "tv=1.3.0" "xp=\163\247Ng\236\205B\001" "nn=ST-TIZEN" "mn=BorderRouter" "vn=OpenThread" "id=\178A\249\253\138\1887c\161ZQ\131\222\195\134\208" "rv=1"]

So, while Thread 1.4 was introduced for the v2/v3/Aeotec hubs in 58.10, it appears it was not added for the appliance hubs.

For hubs that support Thread unification, you should have an option in the hub settings for “Manage Thread network”. If that is not present for your hub, then it’s likely not running Thread 1.4.

1 Like
3

They’re both 000.058.00013, and I get that they’re not 1.4 so manage thread network shouldn’t appear but aren’t 1.3 hubs able to unify the networks?

4

No, Thread network unification was introduced in Thread 1.4 by virtue of Thread credential sharing.

1 Like
5

I see, thanks for the help and sorry to pick at your brain but I have one more question. When it comes to unification, the ability to manually do it something introduced by 1.4, but with 1.3 hubs when different thread border routers join your network aren’t they supposed to be able to hop on the preferred network on their own. I see people complaining that their 1.3 hubs are creating their own separate network, and that leads me to believe that these border routers should be capable to run on a single network. If this isn’t true I assume the unification of these two border routers should be impossible until smartthings pushes out an update to the internal hubs, correct?