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.
12-06-2022 06:27 PM
@DBT0721 : As this only involves the WiFi devices, are you sure these are reboots & not just discons? What colours are the light sequence when it happens?
12-06-2022 06:35 PM
I had the full no light, green light yellow light and happy (Aqua Marine) light, logs show reboot
12:01:22 12 Jun. Booting firmware v0.06.01.08190-EE (Wed Aug 19 18:20:33 2020)
11:59:38 11 Jun. Booting firmware v0.06.01.08190-EE (Wed Aug 19 18:20:33 2020)
23:57:20 08 Jun. Booting firmware v0.06.01.08190-EE (Wed Aug 19 18:20:33 2020)
21:55:58 08 Jun. Booting firmware v0.06.01.08190-EE (Wed Aug 19 18:20:33 2020)
19:54:34 08 Jun. Booting firmware v0.06.01.08190-EE (Wed Aug 19 18:20:33 2020)
11:52:43 07 Jun. Booting firmware v0.06.01.08190-EE (Wed Aug 19 18:20:33 2020)
19:51:08 06 Jun. Booting firmware v0.06.01.08190-EE (Wed Aug 19 18:20:33 2020)
17:49:51 06 Jun. Booting firmware v0.06.01.08190-EE (Wed Aug 19 18:20:33 2020)
13:48:28 06 Jun. Booting firmware v0.06.01.08190-EE (Wed Aug 19 18:20:33 2020)
11:47:10 06 Jun. Booting firmware v0.06.01.08190-EE (Wed Aug 19 18:20:33 2020)
09:45:53 06 Jun. Booting firmware v0.06.01.08190-EE (Wed Aug 19 18:20:33 2020)
07:44:35 06 Jun. Booting firmware v0.06.01.08190-EE (Wed Aug 19 18:20:33 2020)
05:43:17 06 Jun. Booting firmware v0.06.01.08190-EE (Wed Aug 19 18:20:33 2020)
03:42:01 06 Jun. Booting firmware v0.06.01.08190-EE (Wed Aug 19 18:20:33 2020)
01:40:39 06 Jun. Booting firmware v0.06.01.08190-EE (Wed Aug 19 18:20:33 2020)
23:39:21 05 Jun. Booting firmware v0.06.01.08190-EE (Wed Aug 19 18:20:33 2020)
21:38:04 05 Jun. Booting firmware v0.06.01.08190-EE (Wed Aug 19 18:20:33 2020)
19:36:45 05 Jun. Booting firmware v0.06.01.08190-EE (Wed Aug 19 18:20:33 2020)
17:35:30 05 Jun. Booting firmware v0.06.01.08190-EE (Wed Aug 19 18:20:33 2020)
15:34:11 05 Jun. Booting firmware v0.06.01.08190-EE (Wed Aug 19 18:20:33 2020)
13:32:54 05 Jun. Booting firmware v0.06.01.08190-EE (Wed Aug 19 18:20:33 2020)
11:31:36 05 Jun. Booting firmware v0.06.01.08190-EE (Wed Aug 19 18:20:33 2020)
09:30:19 05 Jun. Booting firmware v0.06.01.08190-EE (Wed Aug 19 18:20:33 2020)
07:29:03 05 Jun. Booting firmware v0.06.01.08190-EE (Wed Aug 19 18:20:33 2020)
05:27:43 05 Jun. Booting firmware v0.06.01.08190-EE (Wed Aug 19 18:20:33 2020)
03:26:25 05 Jun. Booting firmware v0.06.01.08190-EE (Wed Aug 19 18:20:33 2020)
01:25:07 05 Jun. Booting firmware v0.06.01.08190-EE (Wed Aug 19 18:20:33 2020)
23:23:48 04 Jun. Booting firmware v0.06.01.08190-EE (Wed Aug 19 18:20:33 2020)
21:22:33 04 Jun. Booting firmware v0.06.01.08190-EE (Wed Aug 19 18:20:33 2020)
19:21:16 04 Jun. Booting firmware v0.06.01.08190-EE (Wed Aug 19 18:20:33 2020)
17:20:01 04 Jun. Booting firmware v0.06.01.08190-EE (Wed Aug 19 18:20:33 2020)
16:52:04 04 Jun. Booting firmware v0.06.01.08190-EE (Wed Aug 19 18:20:33 2020)
12-06-2022 06:41 PM
No Lights, Green Light, Yellow Light, Happy Light (Aqua-Marine)
Logs confirm reboot
12:01:22 12 Jun. Booting firmware v0.06.01.08190-EE (Wed Aug 19 18:20:33 2020)
(Not sure what happened to my longer reply)
12-06-2022 06:48 PM
Same here. Light of then go through the various colours till back on the aqua. I called EE to update them again. I have already a complaint open mentioned this thread the lady was sympathetic to my cause. But I need to wait till the next engineer has been (tomorrow morning monday) see what they say then it may get escalated to the next dept. Quite frustrating
12-06-2022 08:20 PM
Reported the issue to BBC news, let’s see if they publish it…….
12-06-2022 09:46 PM
@adriancrowson1I emailed The Register but got no reply.
12-06-2022 11:19 PM
@DBT0721 seems your earlier post has now appeared! Dunno what happenned there.
It may be a big ask, but I wonder if the rebooting problem is triggered by having too many connections?
I only have 15, and don't have an issue.
It would help if those with an issue would say how many connections they have on the router.
12-06-2022 11:37 PM
I have 27 connected devices and, although I'm not sure, I believe the router should be able to handle 60. I would be hugely surprised though, if those who are affected went over by one extra connected device on the 24th of May and haven't dropped one or two since. It is surprising, however, that there aren't many more people affected. I'm guessing this is because lots more people haven't noticed but it is interesting that some people have said that the reboots didn't happen when they weren't using the internet so much. Could it be due to connected devices? It does seem unlikely that the router wouldn't inform us that it's reached its limit and most of the devices I have are very low bandwidth because they're things like temperature sensors, which only interact periodically with the internet.
12-06-2022 11:46 PM
@AJStubbsy ok but could you post the boot router logs up to now, and after you have less devices connected?
Thinking is good, but actual info may be more useful!
13-06-2022 12:10 AM - edited 13-06-2022 12:10 AM
I'm hoping the rest of the community is able to chip in on your hypothesis before I need to disconnect 12 devices and wait 2hrs to find out if you've sussed it out. Either way that won't be a fix for me because those devices serve a purpose in my home. I will definitely give it a go though, if there aren't more people discussing how many devices they have connected. I'm genuinely interested to see if it is a limitation of the router and not some software bug that got introduced on 24th May, or a combination of both.