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.
10-06-2022 08:35 PM
I didn't realise what was happening at first, but soon started on at EE about the problem. I've had two EE phone calls, a QUBE engineer visit, when he broke my phone split socket and replaced it with an unfiltered simple socket, so I now have filters hanging out of the sockets again. Finally, I've received a new BLACK router, which I had already guessed would not cure the problem, so I've gone straight for buying a TP-Link AC1200.
In the midst of this, I found that EE dropped my connection to 20Mbps around the 6th April this year.
I had been with Vodafone, receiving 78Mbps most of the day, but 0Mbps fairly regularly in the early evening. I started monitoring my speeds every half-hour. I switched to EE at the end of May last year and was receiving around 56Mbps fairly consistently, all day. I was happy with that and didn't monitor my connection.
I went away at Christmas and in the process, managed to stop my monitor for the first two months of this year. I didn't notice that in March and April I was only getting 45Mbps. On 6th April, it dropped abruptly to 9Mbps, then crept back up over a week to 25Mbps. At the start of May it dropped to 20Mbps. Since the new two-hour reboot timeout + 78 seconds average reboot time, I'm now at about 15Mbps.
My AC1200 arrives tomorrow. Before switching over to it, I will do one additional test. I know that if I force a reboot, the next reboot that EE causes will come two hours after my reboot. I thought that that implied that a timer was going off in the EE router itself. However, I'm expecting a reboot to occur shortly, so I will unplug the phone line for a while and see if/when the reboot occurs. .... and - no reboot.
So, it is something that goes on at EE's end and they send something down the line which crashes the router. If you disconnect the router at the time you're expecting EE to wreck it, it doesn't get wrecked. Not exactly a solution to the problem.
Anyway, roll on tomorrow, when I can say goodbye to all this hassle (I hope). I can get down to having my £59.99 refund from EE for the new router and a refund of the last few months broadband bills (as they have not been supplying what they are contracted to supply) plus some compensation for my headaches. 🙂
10-06-2022 08:46 PM
PS. My thanks to everyone here.
There are probably many more people out there who have just not really noticed the reboots. I have quite a "smart" house and it's annoying when Alexa can't understand me when I ask her to turn on my lights.
My router needs to handle more than 30 devices. I think the EE router just can't handle that, plus it failed to handle my mesh devices and I've reverted to powerline.
10-06-2022 08:59 PM
@LauWR Hi and welcome to the forum. It sounds like you have more problems than the router reboot one.
Splitting the WiFi bands can sort a lot of WiFi problems, and EE do not reduce your speeds, that is done automatically by DLM (Dynamic Line Management in your local cabinet due to line problems such as noise - and now the constant drops.
Once you get your new router, if you start a new thread we can help make sure you are getting the best speeds your line can deliver.
10-06-2022 10:19 PM
My ADSL was better than this:
Downstream sync speed: 7.89Mbps
Upstream sync speed: 2.29Mbps
10-06-2022 10:41 PM
@Mustrum I didn't mention that absolutely nothing in my setup has significantly changed since I joined EE. The initial speeds I received matched the "Minimum Guaranteed Speed: 53.5 Mb/sec" well enough. The service has just degraded over the year to the current sorry state.
I have no idea why splitting the bands should have any effect. They are each capable of supporting 32 devices. Some years ago, I did keep the bands separate, as I liked to know which band I was connecting to. Once I realised that 5GHz won't go through a piece of cardboard, let alone a wall, I stopped really using it at all.
Some of my devices connect on 2.4GHz via the TP-Link powerline repeater on separate channels from the EE router (which refuses to let me select any channels other than 1, 6 or 11 - which everyone else in the close use).
I have 36 devices on at this moment. On the router's WiFi, 5 on 5GZHz and only 16 on 2.4GHz channel 6. The powerline repeater is servicing 4 devices on 2.4GHz on channel 13.
I have also noticed that the router does not do a "Factory Reset". None of the data on previously connected devices is erased.
And here's a interesting picture:
22:18:41, 10 Jun.Booting firmware v0.06.01.08190-EE (Wed Aug 19 18:20:33 2020)
18:17:25, 10 Jun.Booting firmware v0.06.01.08190-EE (Wed Aug 19 18:20:33 2020)
16:16:06, 10 Jun.Booting firmware v0.06.01.08190-EE (Wed Aug 19 18:20:33 2020)
12:14:49, 10 Jun.Booting firmware v0.06.01.08190-EE (Wed Aug 19 18:20:33 2020)
10:13:31, 10 Jun.Booting firmware v0.06.01.08190-EE (Wed Aug 19 18:20:33 2020)
08:12:14, 10 Jun.Booting firmware v0.06.01.08190-EE (Wed Aug 19 18:20:33 2020)
The above shows how, when I disconnected the phone line from the router, from 22:19 to 22:25, there was no reboot at all. That gap looks suspiciously like four hours and 78 seconds, rather than the usual two hours and 78 seconds.
Maybe I'll unplug the router from the phone overnight, tonight, and see what happens after I plug it back in in the morning. I'm guessing there'll be no reboots during the night? If I time the unplug and replug carefully, I'll be able to see clearly which affects the next reboot time, or is it entirely sourced from EE's side running a precisely two hour repeated timeout? We'll see.
10-06-2022 10:45 PM
@DavidFrankland to be expected with regular drops, it is just DLM slowing your line trying to get it stable. Get back to EE and ask for a DLM reset once you get the new router hooked up.
11-06-2022 10:00 AM
My overnight testing:
08:19:59, 11 Jun.Booting firmware v0.06.01.08190-EE (Wed Aug 19 18:20:33 2020)
22:18:42, 10 Jun.Booting firmware v0.06.01.08190-EE (Wed Aug 19 18:20:33 2020)
18:17:25, 10 Jun.Booting firmware v0.06.01.08190-EE (Wed Aug 19 18:20:33 2020)
16:16:06, 10 Jun.Booting firmware v0.06.01.08190-EE (Wed Aug 19 18:20:33 2020)
The time differences are:
10:01:17
04:01:17
02:01:19
Each reboot takes 78 seconds, on average, and that reboot resets EE's two-hour repeats.
When I unplugged the cable around 20:15-ish, last night, it was suggestive that EE was just issuing whatever rebooted the router on a two-hour cycle, and the command it sent to reboot just didn't succeed. I wasn't very careful about exactly when I unplugged and replugged the cable.
The overnight run shows clearly that my router escaped four of the two-hour resets and then took the standard 78 seconds. (Give or take a little jitter.) I was very careful to unplug at 11 pm and replug at 7:40 this morning, very out of sync with whatever was going on.
I won't change anything on my network, other than the router "Arriving today by 10 PM" at the moment. We'll see what happens next.
PS. And my half-hourly Ookla speed tests have been showing that over the last 24 hours, I've been getting a consistent 11.5 download and 1.8 upload, but I do have a 15ms ping!
VDSL Range A (Clean)
VDSL Range B (Impacted)
76.6 | 56.3 | 20 | 15.8 | ||||
74.8 | 52.1 | 20 | 14.3 |
Observed Speeds VDSLMax Observed Downstream SpeedMax Observed Upstream SpeedObserved Date
19.99 |
4.29 |
2022-06-06 |
(Tables above have been "changed because invalid HTML was found in the message body. The invalid HTML has been removed".)
The above was my QUBE engineer's visit, I guess, so it's getting worse. I'm now down to half what he measured.
11-06-2022 10:59 AM - edited 11-06-2022 11:00 AM
Spoke to a friendly customer service person Friday. Acknowledged a known issue but still no official resolution from them to give (other than it saying to send an engineer which they all know is pointless). I have put in a complaint as this issue not only is annoying but reduces your download speed. Surely they should just have reverted the 24 May change and then started worked on a fix in a test environment? I suggest every one with this issue post a complaint to them and see if that gets any speedier action!
11-06-2022 11:03 AM
So I got 11 hours re boot free and thought yes! They fixed it but alas nope it did another this morning:(
12-06-2022 06:19 PM
Having had the same problem as everyone else, I did some tests and managed to get to a stable (No reboots) situation by disconnecting my Orbi wireless from the router, over the past week and a bit I have been slowly adding my wireless devices back 2 by 2 and today tried to add 2 Sonos one speakers paired together this caused a reboot of the hub as experienced before, removing the Sonos pair has stopped the reboot, I have now added back my Ring door bell, associated chime and an Amazon Dot and no more reboots, not sure if this helps anybody else but I think was worth reporting to the community, I will continue adding back the rest of my devices but thought it was worth calling out my experiences so far. I have not experienced any reboots on any device that is wired and only the Sonos on wireless, current device count 30 wired and 10 wireless.