01-03-2024 09:08 AM
We've been with EE full fibre with the back-up hybrid connect 4G router system for around 4 months and while the service is good when the router's connected, it feels clunky to have to manually restart the Smart Hub router every couple of weeks to reconnect to the service after the connection is dropped.
I know that in the greater scheme of things a weekly router reset is a small price to pay for an otherwise good service, but there does seem to be something up with the SH31B router/firmware/software. Connecting to the router's home page through a browser can be a painfully slow process, often taking 20 seconds or more to log in to the home screen, before getting a "We experienced difficulty getting the data. Could you kindly reload the page? [CHOP3-800]" error. This usually happens before it stops letting you log in entirely and forces you to power cycle it.
After a router restart this log in speeds back up to 5 seconds, doesn't get the CHOP3-800 error and everything's fine and dandy again. It's as though the longer the router stays up, the more errors it develops before it falls over again.
It would also be good if the router's error log kept all the errors BEFORE the router restart, so you can see what happened as it fell over. As it stands the log appears to be wiped after every reboot, so is as good as useless to troubleshoot from. Especially seeing as just before a reboot is needed, the router often doesn't let you log in at all, just timing out on the EE logo/spinning balls screen.
I'd swap it out with an alternative router, but we're tied into the EE smart hub because we wanted to keep our landline phone number and the 4g hybrid back up system, two services which I'm not sure third part routers would support.
Is anyone else having similar issues?
Thanks
(The smart hub is running App 1.11.0 and firmware version: r1.29.0-R-950306-PROD-83002. My home set up is the SH31B with its WIFI capabilities switched off, and a TP link Deco system handling the wifi duties through the house, each post connected individually via ethernet to the back of the SH31B.)
Solved! See the answer below or view the solution in context.
31-07-2024 12:18 PM - edited 31-07-2024 12:22 PM
Just checking back in, five months after I first started this thread.
Went through many different routes in an attempt to sort out my issue, culminating in selling my TP-link Deco posts on, thinking that their incompatibility with the EE Smart Hub might have been at the root of the issue (when they weren't connected and I was simply using the main EE Smart Hub Wifi, the router behaved itself).
I attempted to upgrade my EE subscription to the full package that included EE's own Wifi booster system but, after a month of EE not sending the Wifi boosters to me (another story for another time) I gave up and looked to try another Mesh system that might play nicely with the Smart Hub.
I ended up getting a newer set of TP-Link Deco posts (X20 AX1800). But - and I think this may be the important bit - before I set them up I found a page, hidden away on TP-Link's support pages that explaining something called Ethernet Backhaul which appeared to match the configuration that I was attempting to set up.
https://www.tp-link.com/uk/support/faq/1794/
My home network is mainly wired between the three floors of my property, but I wanted a Wifi mesh post on each floor, connected to this wired network, which would broadcast this strong wired signal over Wifi. In order to do this, I had to initially connect each of the Deco posts together by an ethernet cable connected directly to the SmartHub until they registered the Backhaul mode (or something), then disconnect them once they'd gone into this mode and then reconnect them to the wired network via network switches on each floor. When I looked at the network diagram on the Deco app on my phone, each post then showed as being directly wired to the main network and were all broadcasting a strong signal via wifi. The main takeaway from all this is that the SmartHub stopped falling over and I haven't had to restart it since.
This probably means that my original set of TP-Link posts would have probably worked fine if I'd have seen how to set them up properly in this way. Ah well, sometimes you have to go round the houses to get back to where you need to be.
To confuse issues slightly, while I was troubleshooting the original issue, EE support did set me up on some new SmartHub firmware. However, I don't think it was solely this that fixed the problem I was experiencing. I think it was setting up the backhaul mode on the TP Link Mesh system that made everything tickedy-boo.
01-03-2024 10:05 AM
How do you have DHCP configured? It should only be enabled on one of your two systems, either the EE hub, or the Deco.
01-03-2024 10:12 AM
Hi
The EE router is set up to handle DHCP allocation. The Deco is just set to bridge mode (or equivalent)
thanks
01-03-2024 10:57 AM
@Mozza76 did you mean bridge mode, or is it Access Point mode?
01-03-2024 11:24 AM - edited 01-03-2024 11:25 AM
Sorry - I meant Access Point mode. I don't think it's doing any DHCP allocation, though. Might this be causing an issue?
This has been hovering over me as a possibility that I should set the SmartHub to handle everything, including Wifi, and just set the Deco to wifi extender mode (I think that was an option when you set it up...)
Thanks for everyone's help with this, btw...
01-03-2024 09:18 PM
This has just happened to me for the first time today. Had an issue with Plex so tried to log in to view addresses etc and now the router is telling me nothing is connected to it (that's via desktop and the app as well).
02-03-2024 12:50 PM
I think this comes down to a memory leak within the router, as it does seem to get slower over time, things such as loading the admin page takes forever, all you see is loading circles all the time, even between pages takes forever, this shouldn't be how web apps work.
I'm also running:
App version: 1.11.0
Firmware version: r1.29.0-R-950306-PROD-83002
I don't know how regularly they role out firmware updates, but it's something that's in EEs hands to fix.
02-03-2024 01:15 PM
Yep. This seems to resemble my experience. In which case I think a memory leak in the router is potentially the culprit, since when the router's working I very rarely log in to the web app, but I know it's slowing down in the background since cloud apps get slower to load (my wife and I work from home) and after a couple of weeks a reboot is required to make it speed up again.
Funnily enough we got the 4G backup from EE as a preemptive strike against the outages we'd had with BT at our local exchange, but I'm not sure how effective a router that can't even keep itself connected to the main fibre connection would be at switching to the 4G supply should a major outage happen again.
07-03-2024 03:16 PM
The router restarts are getting to be more and more regular. Is it possible that there could be a problem with my router?
It's infuriating. I'm sure I had a similar issue with an old Plusnet router where it would just slow over the course of a week and then eventually fall over, requiring a restart.
11-03-2024 05:22 PM
I have exactly the same issue and just reboot it weekly now but it does slow down and I get the [CHOP3-800] error after a few days.