14-06-2022 03:10 PM
The EE Smart Hub 2-Hourly Reboot Problem & Solution
The Problem
The BLACK EE Smart Hub (also called a “router”) loses Internet connectivity for a few minutes several times a day.
What’s actually happening is a software update on 24th May 2022 caused an issue that triggers this particular model of router to reboot every 2 hours. The result is Internet connectivity is lost for roughly 2 minutes while the router reboots.
You can verify if this is the cause of your current problem by logging into your router’s admin interface. Using a web browser on a device on the same network (LAN) as your router, go to http://192.168.1.254 or whatever IP address you may have changed it to. Log in using the password printed on the back of the router. Look for the “Admin password for Hub Manager”. This is not the same as your Wi-Fi password.
Go to Advanced Settings, then Technical Log. Click on the Event Log tab. You will see lots of entries listed. Filter it by clicking on Categories, scroll down the list and select BOOT. If you see dozens of entries starting with “Booting firmware…” and the time between each entry is exactly 2 hours (plus an extra 80 or so seconds) then your router is affected by this very issue. Your log may not go back as far as 24th May which is the fateful date EE customers in this forum agree the issue started.
How To Fix it
A fix can only come from EE, but at the time of writing (3 weeks into the problem) there’s no sign of any fix on the horizon. But don’t despair because using a completely different model of router is the quickest solution, but it could take a few days. If you’re lucky, the EE agent you speak to will recognise your issue and be willing to send you the latest WHITE EE Smart Router for free immediately. However, at the time of writing this is not the case and you will first need to go through several tedious hoops. The experience from most customers in this forum is as follows:
It’s important that you call EE’s broadband support to report the fault. Tell them the router reboots every 2 hours and you’ve read about it in the Community Forum. The agent you speak to should be aware of the problem as it’s been estimated that 20,000 customers have this issue.
EE’s standard process for dealing with issues is to send out one of their support guys who will have a poke around with your router and phone socket. When they realise they can’t fix it he might offer to give you a new router or get one posted out to you (they may not carry spare stock). If he does that then tell him you’ll only accept the latest WHITE EE Smart Router. Unless he can guarantee you a white one, you should refuse to save you the trouble of posting a black router back to them because it will have exactly the same issue.
The support guy will advise he needs to arrange for an Openreach engineer to visit you. (I advise you to call EE back to arrange your first Openreach visit in case the support guy doesn’t make this arrangement for you.) The Openreach engineer will check your master socket and replace it if it’s old or not looking good. He’ll check your extension wires too if you have any. He might change your port and/or line from the local street cabinet. This might appear at first to fix the problem, but about 6 hours later your router will start rebooting again.
Call EE back and they’ll send out another Openreach engineer who will either check everything all over again or roll his eyes and say a few choice words about EE knowing exactly what the problem is and wasting everybody’s time by sending engineers out for no good reason.
Once you’ve gone through these hoops, call EE and update them. At the time of writing this is the only point where an EE agent will be open to suggestions from you. (Try making the following suggestion the very first time you call EE as they may have updated their policy in light of this epic issue going on for so long.)
The Solution
Depending on your own preference, ask the EE agent to either…
If you want to buy your own router then choose one that you know will work easily with EE broadband. It must support VDSL. Two models that customers in this forum have bought and confirmed to work perfectly are:
Before you unplug your black EE router for the last time, be sure to write down your broadband username. Go to Advanced Settings > Broadband. Look for your “Broadband Username” and password. You’ll need this and your password for setting up your new router.
It won’t let you see your password, but you can work it out from the Broadband Username. If your username looks like PRODUCTIONHQNUN123456@fs, your password will look like HQNPASS123456. Simply replace the numbers in the password, with the ones found in your username. For very old legacy users whose username doesn't look like this & you've forgotten what you choose way back, give EE a call and ask them nicely for it.
Lastly, when your new white EE router or 3rd party router arrives and you’ve set it up, you may notice it’s not giving you your full expected Internet speed. This is because your maximum speed was lowered by the Dynamic Line Management (DLM) at your local cabinet when it detected your previous EE router was frequently dropping the line.
Check your current speed by Googling “speed test” and then click on Run Speed Test. If it’s notably slower than what you used to get you’ll need to call EE and ask if they can get Openreach to do a DLM reset. The engineer will visit you but if you ask him at the door for a DLM reset they probably won’t even bother coming in and will get the job done for you within the hour.
I hope this guide has been useful.
13-06-2022 12:21 AM
@AJStubbsy There "router rebooting every 2 hours" issue has nothing to do with Wi-Fi. I had Wi-Fi disabled since I got the black smart hub last year and my issues commenced on 24th May this year.
@DBT0721 You have the same issue as everyone else. Contact EE and say it's the well-known problem of the router rebooting every 2 hours. Ask them to send you the white router which has been confirmed by others in this forum to not be affected by the issue. Or ask them if they'll refund you if you buy your own 3rd party router (e.g. TP-Link VR400) which is not affected by the issue either.
EE may insist that they send out an Openreach engineer and/or send you a new black smart hub. This is entirely a waste of time, but others in this forum had to go through at least 2 engineer visits for EE to realise the issue can't be fixed by Openreach. The engineer may detect some issues or even replaced your master socket, but it won't fix the actual problem which is a software issue with the black smart hub.
13-06-2022 04:42 AM
So this morning I checked my status and its different! System uptime 15 hours 41 minutes ( a new world record for us) and network uptime 1 hour 2 mins. The latter usually matches system uptime so I guess its not done a full reboot this time?
13-06-2022 08:19 AM
This is not an issue caused by the number of devices connected to your wifi. It is purely caused by an update EE sent out on 24th May, though they are trying to keep this quiet while they try to find a fix. Under their rules you have to have an EE engineer visit, and then 2 BT Openreach engineer visits (finding no issues your end or with BT, before they escalate to the CAT team that can send you a white hub. Prior to that they will only send you the same black hub you already have that has the same problem. I am hopefully getting a white hub today so will see if this works for me. Should do.
13-06-2022 09:24 AM
I hope mine arrives today too.
13-06-2022 10:21 AM
Well, the VR400 arrived Saturday, early evening. It was a doddle to set up, and it doesn't seem to be rebooting (that I've noticed).
@GazzF Have you worked out how to save the System Log remotely? I will delve into Python to write some code to receive it - unless you have a better idea.
When I first started to look at the log, it had entries starting from:
2016-01-01 00:00:27 [5] System: DSL Training
I.e. the default epoch before it got the NTP up and running.
Now, that was using Google Chrome, and I'm glad I saved that log.
I tried to use the "Traffic Monitor" and just got a blank screen. I thought it might be saving up a minute of data, so I waited. Nope. Had to give up on that.
Now, Chrome shows a blank screen for both that and "System log".
Switching to Firefox, both "System Log" and "Traffic Monitor" work fine.
I gather this is a known bug with TP-Link and Chrome.
Anyhow, I now can see the log, and it tends to show nothing but a regular small amount of traffic - but it only shows about one hour or 500 lines. Looking at logs, I've seen no sign of reboot activity, but I may be missing it. I'll keep a watch.
More later... and I have my second engineer visit scheduled for tomorrow morning 7-9, which will be a waste of EE's time/money, but maybe I can get them to replace the socket they broke.
P.S. Speed now 11.5 down, 2 up, ping 20, so no change there, yet. Hopefully, the engineer can start improving that.
13-06-2022 11:37 AM
So, was at my wits end, and throught sod it, let's try again, so I spoke to an advisor, they told me that ALL their calls are about this issue at the moment.
I told them I either wanted a new white router or to close my account and I'll go elsewhere... they started going on about they'd been sending the same one out and not working and about going through the motions to get the white one... and after reading some of the comments on here it felt like I'd end up getting another engineer out... So I again thought, let's head this off and just throw money at the issue.
So I said can't I just upgrade to the Smart WI-FI thing for £10 more a month... so that's what I'm doing and a new router is supposedly arriving on Wednesday. I live in the sticks, and the router is up on the second floor... so hopefully it solves the connectivity on the ground floor, and might be useful for extending into the garden. (Telling myself this to less feel less crap having giving in and just paid to solve a problem)
I can't help thinking that the engineer thing is just a service level agreement they have with BT, so it costs EE nothing to keep sending them out as they have a contract with BT... so they'll keep doing that to fend people off.
They also gave me a £30 credit on my account. To put against the extra £240 I'm paying over the life of the contract 😞
13-06-2022 11:40 AM
PPS. I found a nice and tiny (38 lines) bit of Python:
I prefer python3, so I also changed "SocketServer" to "socketserver" and I changed the port from 514 to 5144 to hopefully avoid any hassle.
I suspect I could change the HOST from 0.0.0.0 to 192.168.1.1 to explicitly let only the VR400 come to me, though I doubt that anything else on my network will try to find my server on 5144.
Anyway, it's chugging along happily. I think I'll have to add in the time for the messages, as the router hasn't bothered to send me that.
13-06-2022 12:12 PM
If you look up the complaint policy there is a plan to follow. I have had a cube engineer and now to openreach engineers and my complaint was then passed or escalated to the next level. A solution has been put forward to try. I certainly do not think that upgrading your package even with the £30 would seem like a fair solution. If its a faulty hub then for me it's EE that should be fixing the issue but not at your expense.
13-06-2022 01:52 PM
Is the EE black router rebooting anyway, even if it's not connected to the phone line?
If not, then you could turn it into an access point (just disable its DHCP server) and connect it to one of the ports of the new router, if you are worried about this latter wifi coverage.
13-06-2022 01:58 PM
The black router does not reboot when it is not connected to the phone line. When reconnected, it reboots exactly a multiple of 2 hours after the last time is rebooted.
I.e. it is totally useless as a modem.