06-06-2026 03:27 PM - edited 06-06-2026 03:30 PM
It is now pretty much confirmed that the recent (circa 25/5/26) firmware update on EE Smart Hub Plus (with Wifi 6) to version r4.26.1-R-1860948-PROD-83002 is causing a lot of problems around wi-fi dropouts, probably all on the 2.4 GHz frequency (and probably on both Main and Compatibility). The update was something to do with aligning BT and EE routers, no other details given.
Many people are suddenly getting random dropouts which were not there before, which temporarily stop after a reboot, particularly by powering down for at least 5 minutes. I personally also found our phones could not even see both Main and Comp networks when the problem was occurring. Almost universally, the fix is to go into the router Wi-Fi configuration page (Change Settings) and change the 2.4 GHz channel config from Auto to Fixed (many are using channel 6).
I have also seen a laptop reconnect every 6 seconds (to the 2.4 GHz Comp network) where I have tried all the usual - update Wifi adapter driver version, back off certain adapter sensitivity settings - and I even bought a new USB Wifi Dongle, which also would not connect stably. This laptop was absolutely fine before the update (as were the phones that were dropping off the wifi). We're now using that laptop on Ethernet-over-mains, somewhat less convenient but totally solid (and Amazon have refunded the Wifi Dongle 🙂 )
Today I had an excellent conversation with one of the EE Guides (using their callback system which imho is a pretty good way of getting hold of them) and he agreed I'd already done pretty much everything I or EE could do, and will escalate this.
He indicated that any sort of routine firmware update is unlikely very soon, but that they are aware of these wifi problems, and implied (or maybe I read into it) that an update can sometimes be rolled out to fix specific problems.
So I think the best thing to move this forward positively is for everyone to report the problem to EE. Text GUIDE to 66033 and they will call you back in usually less than an hour. The more who report, the stronger the case.
Before doing this it may speed things up if you do a Factory Reset on your router (under Advanced Settings / System) and then reconfigure it the way you had it before (e.g. turn Comp on, etc.) then check the issue is still there. We pretty much know this reset does not work, but the support team do have a sequence they need to go through and a Factory Reset is one of those steps, so doing this before will speed things up.
Thanks everyone - fingers crossed.
25-07-2026 11:27 AM - edited 25-07-2026 11:52 AM
@Pervs2 Did you say that the Ring Doorbell is connecting to the EE Hub direct or is a Netgear where it's latching on too, just checking those out now? The spec's look real good on them and have the ability to go WPA3 so chipset must be up there, see there is also some lights on them for checking, also would look at them with the Netgear app to see if WPA2-PSK which is the same as WPA2-Personal if given a choice.
Honestly you just do not know what EE has done with all the latest FW update, and yes i do appreciate it was all tickety boo before and now pear shaped.
Not using a landline then this is what i would be looking at to complete what you have.
on 25-07-2026 11:50 AM
The ring doorbell has only ever been set up to connect directly to the main network on the hub as it is right next to it. The NetGear’s are only used for 2 cameras at the back and I have no issues with these ones generally.
as mentioned when my phone can’t connect to the main WiFi it sometimes connects to my extenders which work fine. And the bizarre thing is these use the hub to boost signals!
I think the issue is with devices connected to the hub and around security issues hence the password is incorrect problem.
on 25-07-2026 12:47 PM
The extender is In the room above the kitchen and hub in room next to it . It’s literally happened overnight . I’ll do that text thing you said and take it from there I’ll do on Monday when they’re at full capacity staff wife
on 25-07-2026 12:54 PM
@MartCAFC No need to wait 7 day's working and automated system you just need to be at home when they call you back.
on 26-07-2026 10:12 AM
Hi Jim, thought I’d give you an update….
The BT Smart Hub 2 arrived yesterday. I set this up yesterday evening. A lot of my devices were still not connecting to the EE one especially my laptop which I tried all day yesterday, and my ring devices kept dropping in and out yesterday.
I Went in to hub settings and changed all my details, Network Name, password and Admin password so it all matched my existing one. I also noticed its security setting was WPA2.
So far all my devices connected without any issue to the BT hub. Every device reconnected and I had no issues trying to connect or ‘password incorrect’ errors. My ring devices all connected and I checked and they all seem to have much better signal too! My ring doorbell is now at RSSI-36 which is what is expect. All cameras signals have improved.
So far nothing has disconnected and this morning I’ve checked and all my ring devices are still connected! The only issue is I can’t see the hub in my EE app but I will contact EE as I should be able to access it from what I’ve researched.
I have read more online and have seen that the ‘incorrect password’ issue I get is a direct side effect of the recent EE FW update forcing WPA3 security and all devices keep disconnecting due to a glitch called a handshake loop again caused by the recent update. So I 100% believe there is still a bug and their router is most def the cause of all the issues. Not my devices as they had suggested!
considering the EE hub is supposed to be stronger in signal and better than the BT hub I would totally disagree from my experience. The fact all my ring devices have better signal on the BT hub and I ran the WiFi analyser test and my 2.4 came out stronger this time not my neighbours, proves this.
I’ll give you one last update in a few days to let you know how I’m getting on with the BT hub but I’m feeling like this will have fixed all my problems.
26-07-2026 10:21 AM - edited 26-07-2026 10:31 AM
@Pervs2 All correct just did not wish to lead you down the EE Smart Hub 6+ is a piece of sugar or a 💩 been there done that already and gone. The BT being a WiFi 5 device is way better, and NOT the object that WiFi 6 is trying hard to achieve but just now not making that good a job off it, and as before WPA3 is really for the most security that a simple home network does not require in the slightest.
WPA3-T being the Transition simple mode to allow both ways to go, older / newer devices when it does not play nice HAVOC is the outcome.
You should be good to rock in roll with what you have setup wise, your netgear RE's hopefully hold up on a wifi 6 connection but do think they may just fold back wifi 5, if your mobile is android take a look on your wifi bars, a 6 in those when connected to the netgear will be a very good sign.
The EE App will be somewhat more restricted as the BT has nowhere near the EE Smart hub bells and whistles. But it in theory should connect, you may still see the App shows you your EE Hub as it's base, NOT and never was a app lover it's up there with the rest of it....
on 26-07-2026 11:03 AM
My NetGear extenders have all connected fine. I have an Apple phone and the signal for my extenders are all full bars except the one outside in my shed as it’s furthers away.
2 of my ring devices connect to my extenders and they are all working well.
I’ve been thinking alot about all of this and I think I know why I’m having these issues. So when they did the FW update they updated the security to WPA3. In doing this all my devices get stuck in the handshake loop and cannot always reconnect.
I have read that I can go into my network settings and clear the network so all the cache is deleted including all the old certificates. Perhaps doing this and reconnecting might have helped however this is not something I can do to my RING devices or others so I would have to manually reset them all!
I also read that changing the network name and password can help fix the issue so devices see it as a NEW network and then create new certificates when it joins. However, for me I wanted to avoid doing this as I have mane devices in my home and having to connect them all one by one would be an absolute headache.
I reckon those customers no longer having issues have probably done this.
I reckon I might have been able to fix EE hub if I had changed my network name and password to something new, cleared all cache where I can and reconnected all my devices one by one! Who knows without truly testing it but logic now tells me that this makes sense as updates to security settings caused these handshake loop glitches and incorrect password issues. This is my conclusion on all of this. Although EE never once suggested this as being the issue. They just wanted to blame my devices which are all now working!
Also, the BT seems to be providing a better signal from all internal my tests done so although on paper the EE HUB is meant to be better for me the BT seems to be working better. Let’s just hope EE can connect it to my app.
26-07-2026 11:08 AM - edited 26-07-2026 11:15 AM
@Pervs2 Here is a little off the back list not going to go all the way back but if you need just say.
FW: r3.8.11-R-1414606-PROD-83002 and the gui is at App version 2.36.9 23/06/2025
FW: r3.8.17-R-1464067-PROD-83002 and the gui is at App version 3.1.3 03/09/2025 Https:// now!
FW: r3.8.24-R-1531355-PROD-83002 and the gui is at App version 3.1.3 10/10/2025 Now https://
FW: r3.8.29-R-1627298-PROD-83002 and the gui is at App version 3.1.18 Op Posted
FW: r3.8.30-R-1627300-PROD-83002 and the gui is at App version 3.1.18 05/12/2025
FW: r4.26.1-R-1860948-PROD-83002 and the gui is at App version 3.14.5 25/05/2026 OP Posted Stability Problem
FW: r4.26.2-R-1923137-PROD-83002 and the gui is at App version 3.14.5 New OOB installed version
FW: r4.26.3-R-1923144-PROD-83002 and the gui is at App version 3.14.5 12/06/2026 OP Posted
From the mentioned below.
The name change and the password change is a load off tosh. It's NOT needed, you had a fully working system End off May it all went belly up and as you have not been following @Gelert5 is posting where the newest is heading down the pan currently.
on 26-07-2026 11:34 AM
What is this? A list of all the. Firmware updates?
you are right changing network name and password should not be needed!
I think though they are all getting stuck and confused in a security certificate loop since the change to WPA3.
Perhaps a complete name change would create a new certificate and stop it getting g stuck and confused in a loop between WPA2 and WPA3.
only way to know is to test it and I’m not going to do this if my BT hub does everything I need.
26-07-2026 12:08 PM - edited 26-07-2026 12:10 PM
@Pervs2 It's a partial list off what has been going on from the Inception off the EE Smart Hub 6+ and there has been a lot more wrong than just what you are surmising with the WPA3, the hub has always supported it as a requirement from WiFi 6 onwards. Added the rest now below.
SH31B
FW: r1.35.0-R-1138091-PROD-83002 and the gui is at App version: 1.13.1
FW: r2.68.11-R-1260390-PROD-83002
FW: r2.68.12-R-1270837-PROD-83002 and the gui is at App version 2.36.4 09/01/2025
FW: r2.68.16-R-1296172-PROD-83002 and the gui is at App version 2.36.4 31/01/2025
FW: r2.68.17-R-1303190-PROD-83002 and the gui is at App version 2.36.4 14/02/2025
FW: r2.68.18-R-1303195-PROD-83002 and the gui is at App version 2.36.4 11/02/2025
FW: r2.72.2-R-1302577-PROD-83002 and the gui is at App version 2.36.9 11/04/2025
FW: r2.72.3-R-1302579-PROD-83002 and the gui is at App version 2.36.9 11/04/2025