cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

EE Smart Hub 2-hourly reboot problem & solution

GazzF
Established Contributor
Established Contributor

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…

 

  1. Send you their latest WHITE EE Smart Router because it has been confirmed by several people in this forum that it works perfectly and is not impacted by the 2-hourly rebooting issue. It looks like this: https://www.eehomebroadband.com/Home/ProductsDesc/110
    If they try to make you buy it or increase your fees then my advice is to refuse because they're providing a faulty service and it's up to them to pay for a solution.
    or...
  2. Refund you after you’ve bought your own 3rd party router. This gives you some choice in getting the router that best suits your needs, but do consider that EE may refuse a full refund if you buy an expensive model. A good router can be had for £35 to £60. EE may ask you to send them a receipt of your purchase so make sure you get one that can be emailed.

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:

 

  • TP-Link VR400 (V3): £60 from Amazon and other retailers. Better Wi-Fi than EE’s black router and more features such as MU-MIMO and Mesh support. Its quick setup lets you select your ISP from a list (EE is listed) and it automatically configures itself. Job done.
  • TP-Link TD-W9970: £35 from Amazon and other retailers. A cheaper alternative, not as fast as the VR400 for Wi-Fi speed, but you won’t notice the difference as your EE broadband is probably limited to a maximum of 80mbps anyway. You’ll only notice the difference if you transfer lots of data between wireless devices on your LAN such copying files from your mobile phone to your laptop via Wi-Fi. I think this router’s chipset is slightly slower so if you enable advanced security features such as DoS protection, it may slow down your network speed more than the VR400 would.
  • BT Home Hub 6 or BT Smart Hub: Some users have found these work without issue, without even having to set the EE Broadband Username and password.

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.

310 REPLIES 310
min1300
Established Contributor
Established Contributor

We can only speculate! It really depends where root cause lies, but they must be thinking of rollback as an option.

 

With regards to WiFi, yep you can switch off 2.4, 5ghz or both.

 

im isn’t a Tenda mesh for WiFi and actually forgot to switch off WiFi on the router, but all seems to be happily working together.

 

 

 

OK, something has definitely changed for me in the last 24 hours. From sometime late(ish) yesterday, my Smarthub hasn't been rebooting every 2 hours. It was up from 6pm until around 4am yesterday with no reboots - As I type, It has now been up for over 12 hours with no reboot? - Have EE changed/updated something. My Speed is still slow ( around 35mb compared to 70mb before the 'incident' ) but it seems stable so hopefully will come back once the DLM has settled down?. I did do a factory reset on the router but don't know if that made a difference or not? ... Has it resolved itself for any of you guys?

Since the 24th or 25th May our broadband has been resetting... I thought it was the line but from reading other posts that it's actually resetting.

 

My first 'HELP' to their SMS service resulted in an engineer coming around, but it didn't fix the issue. I've not moved or changed the router for several years.

 

I've since been onto support two more times, and each time they've palmed me off with 'give it 24 hours', and we've logged your error, and even admitted they've started getting more people with the issue — I've been patient and given it time to sort it itself out... it was embarrassing on Friday where I had to pre-warn a client on a zoom call that I may likely disappear for a few minutes, and lo and be-hold it dropped at a crucial point.

 

It's really starting to annoy me now, I just resigned a 24 month contract (Where I thought I was getting a new router but one never arrived)... but that was several weeks before the issue, so don't think the two are connected.

 

I've read that some people have received a new router and it's solved it, while others have been told they'll just swap like for like, and it's not fixed it. 

 

If they're not providing the service I'm paying for can I close the account (if they don't send a new router which seems to fix the issue)?

GazzF
Established Contributor
Established Contributor

20:21:44, 05 Jun.Booting firmware v0.06.01.08190-EE (Wed Aug 19 18:20:33 2020)
18:20:26, 05 Jun.Booting firmware v0.06.01.08190-EE (Wed Aug 19 18:20:33 2020)
16:19:11, 05 Jun.Booting firmware v0.06.01.08190-EE (Wed Aug 19 18:20:33 2020)
14:17:53, 05 Jun.Booting firmware v0.06.01.08190-EE (Wed Aug 19 18:20:33 2020)
12:16:35, 05 Jun.Booting firmware v0.06.01.08190-EE (Wed Aug 19 18:20:33 2020)
10:15:18, 05 Jun.Booting firmware v0.06.01.08190-EE (Wed Aug 19 18:20:33 2020)
08:13:58, 05 Jun.Booting firmware v0.06.01.08190-EE (Wed Aug 19 18:20:33 2020)

 

I hope that's answers your question. 😉 If you've got the same problem as me then resetting the router would make no difference. I was sent a brand new one and the issue continued. I'm glad your problem is fixed, but please let us know if it starts up again.

Mustrum
EE Community Star
EE Community Star

Just to add a bit more info, until last nights thunderstorm I gad been using my own Netgear router without issue. Alas a lightning strike not far away stopped my Broadband, after a quick bit of diagnostics, alas the Netgear had paid the price - the burning smell helped work it out!

 

Anyways, got the EE black Smart Hub out and connected it up. It picked up a newer firmware soon after and did a reboot see log below:

 

Time and dateMessage

01:51:49, 05 Jun.Booting firmware v0.06.01.08190-EE (Wed Aug 19 18:20:33 2020)
 

 

01:47:33, 05 Jun.Booting firmware v0.05.02.04290-EE (Wed Apr 29 18:51:15 2020)
 

 

23:46:18, 04 Jun.Booting firmware v0.05.02.04290-EE (Wed Apr 29 18:51:15 2020)
 

 

00:00:45, 01 Jan.Booting firmware v0.05.02.04290-EE (Wed Apr 29 18:51:15 2020)
 

 

10:10:13, 04 Aug.Booting firmware v0.05.02.04290-EE (Wed Apr 29 18:51:15 2020
 
You will spot I am on the same firmware - I think - as @GazzF  above, yet not getting reboots. As it happens I am also in Dorset, next to the Parkstone exchange. The other entries are from when I got the router and tried it after contract renewal and when I returned the BB2.
 
Not sure if this helps yet, the firmware dates from further back than 24th May,  but for those with the issue, it may help to show firmware version and rough location.

@mimeartist  Hi and welcome to the forum. Whilst you may be right with your diagnosis, it would help if you added to one of the posts, preferably the longest one, with more details. Your broadband router status page, which router and firmware version and rough location.

 

As for your last question, as with any ISP you must give them a reasonable time to fix the problem, and the more details you can share will help, you and others.

XRaySpeX
EE Community Star
EE Community Star

I think you'll find that the "System start Button press (PowerButton)" event just before any "Booting firmware" event is the actual indicator of these incidents.

If you think I helped please feel free to hit the "Thumbs Up" button below.

To phone EE CS: Dial Freephone +44 800 079 8586 - Option 1 for Mobile Phone & Mobile Broadband or Option 2 for Home Broadband & Home Phone

ISPs: 1999: Freeserve 48K Dial-Up > 2005: Wanadoo 1 Meg BB > 2007: Orange 2 Meg BB > 2008: Orange 8 Meg LLU > 2010: Orange 16 Meg LLU > 2011: Orange 20 Meg WBC > 2014: EE 20 Meg WBC > 2020: EE 40 Meg FTTC > 2022:EE 80 Meg FTTC SoGEA > 2025 EE 150 Meg FTTP

@mimeartist : You'll find this thread to which I've joined you, which also was triggered by a similar incident on 24 May, discusses this issue in great detail. I believe that only 1 of these users has received a new diff router & is so far incident-free.

If you think I helped please feel free to hit the "Thumbs Up" button below.

To phone EE CS: Dial Freephone +44 800 079 8586 - Option 1 for Mobile Phone & Mobile Broadband or Option 2 for Home Broadband & Home Phone

ISPs: 1999: Freeserve 48K Dial-Up > 2005: Wanadoo 1 Meg BB > 2007: Orange 2 Meg BB > 2008: Orange 8 Meg LLU > 2010: Orange 16 Meg LLU > 2011: Orange 20 Meg WBC > 2014: EE 20 Meg WBC > 2020: EE 40 Meg FTTC > 2022:EE 80 Meg FTTC SoGEA > 2025 EE 150 Meg FTTP

Openreach have been out this morning and found no faults on my line, he showed me the disconnects graph on his phone and it started on the 24th May as others have experienced. Aside from the dropouts he said the line is as healthy as it could possibly be. He has requested a new router from EE and I asked him to push for the white one based on what I have read here. Hopefully it will solve my issues, will update as when it arrives.

My black router has also been rebooting every couple of hours the last 2 weeks. Yesterday I rang and the tech team said it was like the 20,000 other EE customers who have been impacted by an update on the 24th May. They said they didn't have an ETA for fix but thought it could be related to an update that was pushed out. After reading @min1300 reponse about the white smart wifi hub resolving the issue I rang up again today to try and get one.

They made me go through a video call to show them my router was connected properly and ran more diagnostics and now I have to wait until an engineer visits Wednesday afternoon. They won't send me a white router because apparently my 70mbps connection package would need to be upgraded by £10/month and I don't need their WiFi as I run a 5 node Linksys velop mesh network - because the EE wifi was historically rubbish.

Trouble is, assuming  the engineer finds no fault on Wednesday (and I have had the line tested in the past) I'm still stuck with an unstable connection. 

So can I escalate this and get a white router even on my current package and turn off their wifi?

Should I buy another router and prove that it doesn't drop and therefore MUST be their crappy Smart Hub (or firmware)? If so to make myself future proof what routers are worth considering (with 4/5g backup) and Fibre-to-the-home?

Can I load an earlier firmware (I have v0.06.01.08190-EE)?

Should I switch to Swish fibre who are now in my area (but I'm moving house in the next few months so don't really want an 18month contract!)?

 

I run a web design business and I'm having outtages during zoom calls.  I have no 4g in the home yet. I've been with EE for several years and have 5 mobile connections with them too. I don't like the fact that 2 agents give me a totally different approach to resolving the problem, neither of which feel like they will lead to a fix.

 

Perhaps if more of the 20,000 other impacted customers find this forum post, something will happen.