FYI… My Samsung Fridge Family Hub updated to 58.8 around the same time as the 58.10 rollout was happening.
Still hasn’t fixed the Thread stack from becoming unresponsive @nayelyz Get this message in the AWA:
Error loading hub Thread data: 500 NetworkManager error: Internal error: The maximum number of pending replies per connection has been reached
Hi, @h0ckeysk8er
I moved your post here since this is a different hub maintained by a different team.
I’ll comment on the ticket we already have about this.
I can’t confirm if the thread network is still giving me errors on my Family Hub with the new firmware as it just updated to 58.13, but it was still acting up on firmware 56.10 which was what it was previously. My Family Hub never got 58.8 like h0ckeysk8er’s did. I can confirm though that 3 out of my 5 hubs (appliances with built in hubs, not my 2 SmartThings Stations) won’t allow me to unify my thread networks like they were supposed to bea ble to do with the release of firmware 58.xx. Also, I’ve been having the thread network drop on my HW-Q990F Soundbar as well. Right now I’m trying to test it to see if it will happen again after a few adjustments, but am afraid I might have to have warranty service on it if it continues as I had to replaced a HW-Q990C as it had a firmware bug that Samsung said didn’t exist (only happened when the Soundbar was using the latest firmware 1010.5, it worked fine via firmware 1004 but that firmware had other issues like rear speaker dropouts). Not only this it was out of warranty and I had to pay to get it fixed twice (the second time they didn’t charge me) and both times it wasn’t fixed as it was a firmware bug Samsung refused to acknowledge. They even broke the Soundbar button cover making it almost impossible to use the physical buttons. Anyway what was happening was if using Wi-Fi to wireless sound from my compatible TV if switching inputs say as an example TV via Wi-Fi to phone via bluetooth within 10 seconds it would disconnect my phone via bluetooth and revert back to Wi-Fi about 4-5 times until it would stay on phone via bluetooth. But the next time I switched it back to Wi-Fi it would bug out again and not allow me to switch to any other input without reverting to Wi-Fi again. But due to the terrible repair process I’m worried about having to get my HW-Q990F fixed if the Thread Network keeps crashing. I’d rather have it replaced with a new one since it’s still under warranty, but since I got it at a retailer that had limited quantities I can’t just get them to replace it like many box stores do and doubt Samsung will replace it without warranty service first.
My Family Hub also updated to 58.13 but it doesn’t have the “Manage Thread network" option in Settings like I see on my Station.
That’s what I’m saying, both my SmartThings Stations (Firmware 58.10) have the option to “Manage Thread Network”, but my Refrigerator, S95C TV, and my HW-Q990F Soundbar don’t (all on Firmware 58.13). This is why I replied on the firmware post and asked if we are getting this update as the Aeotec Smart Home Hub 2 got this feature with the 58.12 update and never hear back. Aeotec Smart Home Hub 2/Aeotec Smart Home Hub/2018/2015 Model Hub Firmware Release Notes - 0.58.10 - #56 by MPHDodgeDaytona
Hi nayelyz,
I can confirm now that my Family Hub Thread Stack is still dropping as well on firmware 58.13. I’ve dumped the hub logs. Can you please update the ticket for me as well.
Thanks
Thanks for the post, @MPHDodgeDaytona
When this happens, we also need a timestamp or time range of when the “offline” event occurred to:
Someone on my team will help me check whether anything is outstanding on the ones you submitted to confirm the above. I’ll let you know if that’s not the case.
In your case, @h0ckeysk8er
It would be useful to have your hub logs as well, so, please, whenever this happens again, take note of the date and time and share it with us.
Submit the hub logs as follows:
- In the Advanced Users app, enter the “Hubs” section
- Enter the corresponding Hub and click on “Dump Hub logs”
- Confirm the process by clicking on “Dump Hub logs” again in the pop-up.
- You’ll get a green box at the top confirming the Hub logs were requested.
Hi nayelyz,
I totally forgot about time stamps. LuckilyI remember the exact times. I dumped the hub log at about 2:45AM Nov. 11th, 2025 Eastern Standard Time and the event had to happen between 12:45AM Nov. 11th, 2025 Eastern Standard Time as this is when I restarted my Family Hub Fridge and it was working then and the Thread Network was already offline for sure before I wrote the reply at 2:48AM Nov. 11th, 2025 Eastern Standard Time.
Hi, @MPHDodgeDaytona
So, if I understand correctly, the Thread network went offline, and you immediately restarted the hub, which didn’t bring it back. After two hours, you submitted the hub logs, correct?
The correct order should be sending the hub logs before restarting it, because they get deleted during this process. The ones you sent might have something about the Thread radio not being “initialized” but, it would be useful to have another set of logs when it goes offline all of a sudden.
I restarted the hub at 12:45AM, sometime between 12:45AM and 2:45AM so 2 hours the Thread Network went down. I then dumped the hub log around 2:45AM. Then I replied here at 2:48AM. So events should go as followed; Restarted Hub, then Thread Network Crashed, then Dumped Hub Logs, then replied to you on forums. Hope that clears up the confusion.
I guess hubs running on Tizen use OpenThread but for some reason they do not support thread 1.4 yet. My dongle has 58.13 and it’s same.
Yes, they do use OpenThread as evidenced by doing a service discovery on your local network:
= 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=\007" "pt=\012:\\" "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"]
But what you’ll notice is that the Thread version (tv) is still 1.3 even though it’s running 58.13.
My Stations running 58.10 are at 1.4.
= ens33 IPv6 Samsung SmartThings-Station #A2DF _meshcop._udp local
hostname = [smartthings-station-3KWW.local]
address = [2600:1700:dce0:4790::28]
port = [49154]
txt = ["omr=@\253\015w\238D\224\000\001" "dn=DefaultDomain" "bb=\240\191" "sq=\013" "pt=\246\015US" "at=\000\000h\230\186e\000\000" "sb=\000\000\015\177" "xa=R\019\031GN\229\162\223" "tv=1.4.0" "xp=s8\164ic>\251\191" "nn=ST-3KWW" "mn=SmartThings-Station" "vn=Samsung" "id=su\2406tm\210\221u[\194\01774'\255" "rv=1"]
So, looks like they still need to, at least, rev the Thread version before we’ll get more Thread management capabilities for appliances.
Hi nayelyz,
Just wanted to add my HW-Q990F Thread Network went offline again. I repeat this isn’t my refrigerator, like normal, but my Soundbar. The Thread Network went offline sometime between 12:00PM Nov 26th, 2025 and 3:00AM Nov 27th, 2027. I dumped the hub logs about 3:00AM Eastern Standard Time Nov 27th, 2025. This has been happening ever since I got the soundbar and when it does it also drops the Zigbee Network as well (See attached photo below). I have it as a secondary hub in a hub group, but it seems to work fine for about 3-4 weeks without issue after a factory reset, then the hub networks drop. When they drop the only way I can get them to come back online is to unplug the soundbar and replug it into an outlet again, but this only works temporarily for about 3-7 days and then it happens again. The only way I can get it to stay running longer then a few days after that is to factory reset the whole soundbar again. Even deleting the SmartThings Hub and reinitiating it doesn’t fix the issue like my other hubs and causes it to permanently bug it out so even rebooting the hub via unplugging and replugging it in doesn’t bring back the networks and then it needs a factory reset for sure to work again. Do you think I should try to get warranty service on it or try to see if Samsung will replace it with a new one as I only have 7 months left on the warranty? I also ask as the Samsung repair facility damaged my HW-Q990C when I tried to get that repaired due to a firmware issue, which they never fixed and it cost me as it was out of warranty.
Hi, @MPHDodgeDaytona
As we haven’t received feedback from the other case of the refrigerator, I think it’s best if the Customer Support side can do something else for you before losing the warranty.
Since we don’t have any contact with the Customer Support team, I can’t guarantee you anything about the results of that approach, but this seems to be a device-related issue since there are times when it doesn’t recover, so there’s not much that can be done remotely.
Hi nayelyz,
Well after a long hassle with Customer Service wanting me to send my HW-Q990F Soundbar in for a repair to replace the hub (which I didn’t want to do as they damaged my old HW-Q990C that I sent in for other issues) I received that back damaged as well. So I then sent it back and finally got them to send me a brand new replacement HW-Q990F Soundbar after they realized they were caught damaging it during the repair. Either way I finally got a brand new one after about 1.5 months from Early December to late January. Sadily come today after having it setup less then 3 weeks now the new one has done the same thing. All SmartThing Hub Networks are dead; no Zigbee, no Matter over WiFi, and no Matter over Thread. So now I’m back to square one with a soundbar that doesn’t have a functioning hub again. I sent in an error report, but I think that is useless. I believe it to be a firmware issue, but don’t know what to do other than ask for a full refund if I even can. If I’m lucky I could get the new HW-Q990H that is to be releasing soon as a warranty replacement as I still have just under 4 months warranty and that should be releasing this the next few months. If I do hopefully that doesn’t have the same issue, I know my old HW-Q990C didn’t have this issue as the Built-In hub worked flawlessly. The problem I had with that Soundbar was if I was using it connected to a WiFi Source (like for Q-Symphony on my TV) and I went to use another source later (didn’t matter the source, but I used mostly Bluetooth with my phone) it would disconnect the other source and revert back to WiFi within seconds. After about 4-6 attempts the new source would stay connect and the soundbar wouldn’t revert back to WiFi, but the next time I connected to WiFi again (aka watch TV) I’d have to go through this whole rigamarole all over again. Come to find out it was an issue with firmware version 1010.5 for the HW-Q990C that Samsung refused at the time and still refuses to acknowledge, but I couldn’t stay on the the older firmware 1004 either as this was causing the Rear Surround Speakers to dropout and not function. I was able to get a refund from that and bought this HW-Q990F in hopes of fixing all issues (Especially since the whole Bricked HW-Q990D fiasco), but looks like that isn’t the case.
