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 02:09 PM
This is a problem caused by EE. They are contractually bound to provide you with a service which they are failing to do due to the black routers rebooting every 2 hours. No one should need to adjust their settings, buy third party routers etc (though of course they can if they wish, however a lot of people are not competent / confident to make these changes, especially as if this is done wrong and causes other problems EE could claim they are not responsible). This is poor service from EE in fixing this problem in what is approaching 3 weeks, and putting policy hurdles in the way of people getting this resolved, such as having to have 1 EE engineer visit, and 2 BT Openreach engineer visits to prove the is no issue at the household end / with line in order to get this escalated to a department that can send you a router that works. I and my wife work from home and have been heavily disrupted, as well as having streaming services disrupted in our leisure time, and home security system repeatedly knocked off line. I have just had a new white router delivered and installed it app an hour and a quarter ago so will see if this works. Under no circumstances should anyone have to pay to upgrade their service to get the white router to get around this issue. It is EE legal responsibility to provide the service they have contracted to do, how they do it is their problem.
13-06-2022 02:09 PM
@LauWR wrote: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.
Thanks. So in theory those of you looking for a (temporary) replacement could buy a cheaper router, rather than the TPLink VR400 or higher versions.
e.g. a TPlink W9970 or Zyxel VMG3925, you can find them for less than £20 on eBay, and switch their wifi off, and instead use the EE Smart Hub as an access point. It would still maintain access to EE backend, and receive the firmware update which might fix this issue.
13-06-2022 02:16 PM
100% agree. They are sending me a white router and it should be with me by the end of the week. They make you feel like a second rate customer at times. And yep jump through hoops and chase them up for a fix....am sure it should have been the other way round ie EE chasing a fix and jumping through hoops for their customers
13-06-2022 02:17 PM
I completely agree with you. But meanwhile, given that broadband is basically not working, one can find some temporary solutions.
Working in software, I really cannot understand why it is taking so long to EE to acknowledge the issue and implement proper actions.
I've seen this same pattern with Sky Broadband, with their latest router having some bugs fixed after more than one year. Or more recently TalkTalk, which screwed up their routers with a firmware version which blocks all VPNs.
In my home country, a big ISP got their Nokia FTTH routers bricked following a firmware update, and after three days of outage, they started sending new routers out to impacted clients.
Why is EE still sending OpenReach engineers out or refusing to replace impacted routers with newer models, I really cannot understand.
13-06-2022 02:25 PM - edited 13-06-2022 02:26 PM
@flavione : The EE SH will not receive firmware updates when it is not being used as the main router but as an access point.
13-06-2022 02:39 PM
@XRaySpeX : The black EE SH does not work as an access point (for 78 seconds, every two hours). 🙂
13-06-2022 02:50 PM - edited 13-06-2022 03:20 PM
@LauWR : I use it as an access point occasionally w/out issue.
Have you seen it reboot every 2 hours when it is being used as an access point rather then the main router? That'll be an interesting experiment. It might even confirm that the issue is not with the router itself but with the EE system sending 2-hourly remote configuration instructions (TR-069) triggering its reboots, which wouldn't reach it when it is being used as an access point any more than they would reach an alternative router being used as the main router in its place.
13-06-2022 02:58 PM
Apparently people are having issues with the BT Smart Hub configured as WAP
so I'm afraid the EE Smart Hub might behave in the same way.
Shame.
13-06-2022 03:18 PM
@LauWR If you install some logging software on a computer, the TP-Link router can log directly to that. Don't forget to set the router's internal clock. You can also save the log and it will download a text file. (Much less hassle!) Not much is written to the log if there aren't any issues or if "debug" isn't set as the minimum level.
Any other VDSL router that is not the black EE hub will is not impacted by the reboot issue.
It's incredible that EE know the problem is a software update they did on 24th May, yet they insist on sending 3 engineers to each customer before they're able to agree what the problem is. It's madness within their management.
13-06-2022 03:22 PM
@flavione : But that's not the 2-hour reboot issue.