Anyone else get this error?
This is about the third time I’ve spotted this, could be there more often but I’m not checking frequently.
Typically goes away after a reboot.
Is something flooding requests to hub?
Wrt thread devices I have
11 Nanoleaf bulbs
2 Onvis outlets
IKEA door sensor
IKEA leak sensor
IKEA timmerflotte
IKEA Alpstuga
2 x bilresa button
Which doesn’t feel like an enormous load.
Error loading hub Thread data: 500 NetworkManager error: Internal error: The maximum number of pending replies per connection has been reached
I see that message on three of my hubs (one is my main hub and the other two are just sitting around on the same Thread network as replace candidates and don’t have any devices connected). It is the same three hubs that don’t show the me the Thread network in the hub information in the mobile app, and also don’t offer ‘Manage Thread networks’.
Update: I’ve got this error message again in the thread section of AWA
I’ve also had 3 thread battery powered devices go offline today . It’s frustrating. IKEA timmerflotte, ikea water leak sensor and a lafaer presence sensor.
I’m thinking the only thing that’s putting a significant load or rush of requests on my hub might be using the scene switcher @mocelet ?
I’ve zero evidence to suggest it’s this, it’s just the only thing I use that would send a lot of commands in rapid succession, eg if I cycle round 4 scenes involving 5 devices it would be sending 20 commands to thread devices in very short order?
As for the devices going offline it’s a real PITA as it involved repairing two of them and rebuilding broken routines.
I’m hoping the next hub firmware update helps with this
In an attempt to clear the error from AWA mentioned at top of thread I rebooted my hub again.
Now after rebooting all thread devices are offline.
I waited 20 mins and no more came online and the thread section of AWA now shows
So I powered down the job for about 3 mins and power it up again.
I get the same scenario, same message, 30+ devices offline, all the zigbee ones are back of, but not the thread ones. I decided then to delete the Alpstuga air quality monitor since I know it’s very chatty to see if it was somehow blocking other devices. Again no difference, this is really bad timing as I’m travelling tomorrow and could really do without this.
I’ve analysed this is a spreadsheet and I have 2 matter devices online which are both matter over Wi-Fi. All the matter over thread devices, I think all using the matter switch driver are offline.
For the two working matter devices using WiFi I can see they are on matter switch driver which is as updated within the last 48hours so it is possible it may have just landed on my hub?
Anyone else on this version 2026-01-26T20:59:37.726787365
And having issues ?
I get that message for my fridge Family Hub that uses the Thread/Zigbee dongle and has zero Thread devices attached. When I get that message, the Thread stack is unresponsive. Additionally, on occasion, the TBR won’t resolve hostname and additional information when querying with dns-sd. Only a software or hardware reset on the fridge fixes it.
I’ve had this problem going on around 2 years and there has never been any resolution. @nayelyz has looked at the issue for me and @MPHDodgeDaytona, but the engineering team has never indicated they found a problem nor suggested additional troubleshooting steps.
I have one Nanoleaf bulb using this driver connected to an ST station. I just rebooted the hub, and it is still working. I only have one other thread device (an Ikea contact sensor) on that hub.
I don’t think it’s related to Matter over Thread traffic or load at all but something failing in the communication between the internal software components of the hub, possibly because the Thread software stack is down as has been mentioned.
I agree with mocelet, I don’t think it’s related to load or traffic as just like h0ckeysk8er said we both have been having this issue on our refrigerators with dongles for over 2 years now (going on 3 now) and I don’t have a single device connected to that hub not even a Zigbee or Matter over WiFi one. I can get the hubs Thread Stack (network) to come back online by rebooting the fridge by using the system menus on the fridge or by flipping the screens physical power switch off and on again. But sadly it will eventually crash again. When it comes back online I’ve had it stay online anywhere from 5 minutes to 6 weeks. It just depends on what it wants to do. I’ve had other hubs do this but only on older firmware versions and they eventually were fixed around version 52.xx. This is why I was hoping in firmware version 58.xx, built-in appliance hubs would give us the ability to manage the Thread Network and combine it with other networks, but sadly the only built-in hub that did was the SmartThings Station.
Same driver here. Only 5 Thread devices but no issues.
Probably nothing to do with this but I would comment that I had problems a month ago with Matter, which I have bridging from both an iHost and a Moes hub, also to a Homepod. Sonoff support connected and told me that there was excessive traffic from the only 2 Matter-over-wifi devices I have (Sonoff energy plugs!). They are in the drawer and everything is running fine.
My internet hub/router is the isp (Vodafone) provided hub. It has no ipv6 settings avail other than pin holes. The Aeotec home hub is connected to a 16 port switch directly connected to the isp hub, it’s always been this way, nothing new. I’ve rebooted the isp hub, it didn’t seem to help, and am now going to reboot Aeotec hub 2, if this doesn’t sort it it will have to wait till Sunday as I’m travelling
. I only have one hub in play, so it’s not a foible of multi hub setup.
