Now, if you could only figure out why the Thread stack on my fridge Family Hub hangs and becomes unresponsive periodically 
We are looking into a fix for the initial dbus issue; are you seeing device connectivity problems or are you just unable to inspect the thread network information on the family hub (due to said dbus issue)?
My thread network is restored. Depowering all powered matter over thread devices, power cycling hub, waiting for it to stabilise, then powering up the devices seemed to bring things back.
Very many thanks to @AClifford , @nayelyz and @Itati for all their support.
As to why this happened that’s another story, looking like the st hub had been demoted to a child in the thread network?
2 Likes
No, it’s more than just being able to see the Thread info on the AWA. That just seems to be a symptom of the stack becoming unresponsive, but at the same time, any Thread devices on the mesh become unmanageable and go offline.
Great news! So, this confirms the hypothesis that something was awry on the Thread mesh side of the hub, but not what caused it to happen. Our friendly chatgpt suggests this might not be an abnormal situation as described here:
“A SmartThings hub can be demoted to a child in a Thread mesh because Thread has no fixed hierarchy. Leadership and routing are decided dynamically based on network conditions, not on device importance.
Common reasons:
-
The router limit is already full (often 16), so the hub can’t become a router.
-
Other devices have better link quality or RF placement.
-
Border router status doesn’t give priority in Thread elections.
-
The mesh re-optimizes after joining, and the hub steps down to improve stability.
-
Vendor tuning may prefer the hub to stay a child unless routing is needed.”
1 Like
At the moment I’m pinning my hope on the root cause being that the firmware of my Nanoleaf lightstrip was out of date, everything else was at the latest generation available. I’ve updated my lightstrip to the latest firmware and am crossing my fingers it doesnt re occur. The main thing that has changed on my setup recently has been the addition of a range of ikea thread devices. All but one are battery powered. The one being the Alpstuga air quality monitor. I deleted it from SmartThings during the week when my thread network was down, it made no difference. I’m a little paranoid about adding it back in, especially to st and Alexa simultaneously so I can have Alexa routines based on air quality that make announcements. I’ll maybe wait a few days 
36 hours later after thread network and everything still seems OK 
Still pondering over whether the original error below i had in the run up to this prefix error about pending replies was a related precursor to this or entirely unrelated. Also Before this occurred I had a couple of thead devices connected via matter to both alexa and smartthings (still only using st thread though) which were kinda useful (the bilresa button and aplstuga aqm). I’m reluctant to put these back yet in case they were contributing factors.
Error loading hub Thread data: 500 NetworkManager error: Internal error: The maximum number of pending replies per connection
If you have not already, can you start a new post about this or open a support ticket and include your hub EUI so we can get this resolved through the usual channels?
Not clear, is this message directed at @h0ckeysk8er or myself?
I definitely had the pending replies issue, multiple times, but it’s not currently an issue for me, but it may come back 
Ah apologies that was replying to @h0ckeysk8er . The threading format (or lack thereof) here is not my favorite
1 Like
It’s been mentioned in multiple posts previously and @nayelyz might already have a case with engineering going way back.
2 Likes
Just to acknowledge that the ‘dbus error’ affecting display of thread network information in the mobile app and AWA would appear to have been fixed for me. Hopefully for everyone else affected by it too. No idea when as I haven’t looked for a while. So ta muchly.
It isn’t all joy as my wallet has been through a wash cycle this morning, but I can’t pin that one on SmartThings.
Update: spoke too soon.
1 Like
I still have the issue but I believe a fix is being tested in the beta firmware releases
Edit: for clarity this issue, it cleared with a reboot but occurred 2 days ago.
NetworkManager error: Internal error: The maximum number of pending replies per connection has been reached
My beta hub has never had the issue. Three hubs on the release firmware (and on the same thread network, but a different one to the beta hub) have had the problem. Currently my main hub doesn’t have the error. The other two do, though at least one of them was OK this morning.
1 Like
Might be load related. Or device related too, possibly coincidence but the error reappeared a day or two after I reinstated my Ikea air quality sensor, which is a very chatty device compared to most.
I doubt it has anything to do with load since I have zero Thread devices on my Family Hub and the problem keeps occurring.
1 Like
There must be some root cause though thats Triggering the condition, it’s not showing for everyone, so something must distinguish the setup between those that see the error and those that don’t.
@nayelyz Now my ST Station is showing the message “Error loading hub Thread data: 500 NetworkManager error: Internal error: The maximum number of pending replies per connection has been reached” on the AWA and I don’t get the “Manage Thread Network” in the mobile app. The stack itself is still working however, and I’m able to control devices. This is a different behavior than on the fridge hub where devices are not manageable when this message appears.
Hi AClifford,
I’m having the exact same problem @h0ckeysk8er is having with his Refrigerator’s with Built-In Hub via Dongle. The Thread Stack keeps crashing and becoming unresponsive. @h0ckeysk8er and I have been communicating with @nayelyz about this for over a year and a half now with mutliple post about the issue (heck we were the ones that started the whole investigation). I’ve even sent in error reports using the usual channels and never got anywhere. I had about 3-5 ticket open on the issue; sadly I’m not sure if they will show up anymore as the Samsung Members App only allows for a one year window and after that they get deleted and that window has come and gone. I still have the ticket numbers on record though both with @nayelyz and @h0ckeysk8er in a private chat only for us and can add you so you can look into it more, but using the usual channels has always been useless for me as Customer Support always seems to be clueless on anything we ask help on and never seems to want to escalate the issue(s) to the correct teams.
I had this again tonight (hub v4), along with 8 thread devices offline.
Rebooting cleared it and brought the devices back online, but I’d love a fix for this or even a workaround (if there’s something that’s triggering this that I can tweak let me know).