topic Re: YVM102 in TV

YVM102

Den543 — Fri, 06 Jun 2025 12:50:31 GMT

I get errors on my EETV Mini boxes all the time, especially the one in our bedroom.

The main error we seem to get is YVM102, which seems to now be showing every time we turn on the EE Mini Box. This seems to have gotten worse. This is what I have found:

The error happens often. The box will have been working last time we turned the device off, and shows when we next turn it on again some hours or days later.
When the error occurs, If I navigate to the Configure your Wireless Connection screen, my WiFi is not showing as available.(this is EE Broadband WiFI with extensions).
Even Though the EE TV Mini thinks my WiFi is no longer available I know it is because: The Samsung TV next to the device is still connected to the WiFi.
A Speedtest on my smartphone of the WiFi next to the device shows that it over 300MBit download speed and over 40Mbit upload speed.
A test of wifi signals using the Wifi Analyser app shows that it things the router is 1 metre away (there is an extender in the room below).

Rebooting the EE TV Mini fixes it so that it can see my wifi again and use it. But this smells very strongly of a software issue with the box itself because it can only see a working and very strong wifi signal after a reboot.

My wife has lost all confidence in the box to the point that if these issues do not go away we will be leaving EE when it is time to renew our contract. We want a TV service that just works every time it is turned on rather than needing a reboot every time.

The box software is up to date. Previously we had Sky routers/extenders and Sky Q tv boxes - all in identical locations to where the EE kit now is, and everything used to work perfectly with no such issues. This again points to the EE box being at fault.

Re: YVM102

Leanne_T — Fri, 06 Jun 2025 15:58:39 GMT

Hi there @Den543

Thank you for coming back to the community and for letting us know what you have tried already to resolve the error code.

Have you been in touch with our tech guides and reported the error code? If not, please get in touch and they can run troubleshooting to let you know what is needed to get this sorted 🙂

Let me know how you get on.

Leanne.

Re: YVM102

Den543 — Fri, 13 Jun 2025 10:10:02 GMT

Engineer came out. To be honest he didn't know why these errors were happening because, as I have already said, everything looks fine on my WiFi and the box - the errors just happen.

His recommendation was to get another EE Smart Wifi Extender (even though he could see that my current wifi signal at the mini TV box is already very good) and hard wire the EE Mini Box into the extender. He says that often fixes connection issues.

After a slightly heated exchange with EE technical services on the phone to get another extender as had already been agreed with the engineer that visited, one is on the way. I will report back if that fixes the issues I am having. If it fixes it then it hints at issues with the EE TV boxes WiFi chip for issues to be happening in good wifi coverage areas needing hard wiring.

Re: YVM102

Michael_D — Fri, 13 Jun 2025 12:37:57 GMT

Thanks for coming back to us with an update @Den543.

I can understand your frustration with what is happening. Hopefully, the extender will help, but please do keep us posted with how it goes when it arrives and is set up.

Michael

Re: YVM102

Mellman — Thu, 23 Jul 2026 13:05:45 GMT

Did this resolve your issue? We are on the same merry go round with this

Re: YVM102

Katie_J — Thu, 23 Jul 2026 15:28:29 GMT

Hi @Mellman.

Welcome back to the community.

What was the latest advice provided by our technical care team?

Did you see any improvement when turning off sleep mode?

Katie

Re: YVM102

DDenEE — Tue, 04 Aug 2026 10:37:48 GMT

The solution EE gave me was for me to stop using WiFi for my EE TV boxes (Even though my Wifi was absolutely solid everywhere that i had a TV) and instead they provided me with lots of additional wifi extenders and powerline adaptors so I could plug a network cable into the tv boxes.

That solution improved things a bit but not 100% - I was still getting occasional errors. The solution that worked for me 100% was to stop using the IP TV option and revert my main EE TV box to using the working aerial socket I still had. For the mini TV boxes I simply stopped using them altogether and got Google TV dongles instead which worked perfectly over WiFi.

I then left EE when my subscription expired and kept the main TV box which still works fine over aerial without EE (I got a cheap one on ebay to return rather than pay EE the full price) and returned the mini boxes. I went for the cheapest broadband provider i could find (its all via the same BT Openreach lines) and purchased some cheap Chinese router+wifi extenders (Cudy is the brand) and my WiFi coverage is far better than it ever was with EE even with all the extenders they sent me - With the Cudy I only need one extender rather than then the three I had with EE and my Wi-Fi reaches the bottom of the garden which it never did on EE - that there tells us something about the quality of the EE kit.

Conclusion: leave EE when you can, their Wi-Fi kit and their mini-TV boxes are poor quality, and their main EE TV box only really works reliably over aerial (on aerial it is actually good and a bargain if picked up on ebay). If you want to keep Now TV you can usually pick up very good offers direct if you are patient - I'm currently on a 6 month offer far cheaper than what EE was charging me for Now TV.

Re: YVM102

Mellman — Sat, 08 Aug 2026 13:45:13 GMT

Hi Katie,

Sorry for the delayed reply. We have now done a huge amount of troubleshooting with EE, including a roughly three-hour call with technical support today, so I can give a much more complete update.

The original problem has been recurring connection issues with both of our EE TV boxes, often resulting in YVM102 and parts of the interface failing to load. Restarting the boxes and router has sometimes restored things temporarily, but the problems have kept coming back.

What made me question whether this was simply a problem with the TV boxes was that we then started seeing other WiFi devices affected at the same time. In particular, my gaming laptop would lose its WiFi connection completely and then refuse to reconnect, even after forgetting the network and entering the password again.

I went into the Smart Hub 7 Pro admin interface while this was happening and noticed something quite interesting. The hub was showing zero devices connected to the 5 GHz band, despite us normally having a number of devices that use or prefer 5 GHz. Devices on 2.4 GHz continued to work.

We did quite a lot of testing around this.

The 5 GHz radio was shown as enabled in the hub settings, but switching just the 5 GHz radio off, waiting, and switching it back on did not restore the connections. The hub was using Smart Channel 100, and using the Rescan option simply selected Channel 100 again. Unfortunately the Smart Hub 7 Pro does not appear to allow me to manually select another 5 GHz channel.

I also tested this using two completely separate Windows computers. My desktop has an Intel WiFi 6E AX210 adapter and was happily connected over 2.4 GHz. I temporarily configured the adapter to use 5 GHz only. At that point it could see the EE network but could not connect to it at all, displaying the same sort of behaviour as the gaming laptop. As soon as I restored dual-band operation it was able to connect again over 2.4 GHz.

We also unplugged the EE WiFi extender entirely to rule that out, but the gaming laptop still could not connect to either the main network or the Compatible WiFi network.

This was why I became doubtful that this was simply poor WiFi reception or a problem with one particular laptop. We had two separate computers unable to associate with the 5 GHz network while 2.4 GHz continued working normally, alongside the EE TV problems.

Today I spent around three hours on the phone with EE technical support. During that call we did the following:

1. Factory reset the Smart Hub 7 Pro.
2. Factory reset the downstairs EE TV box.
3. Set the downstairs EE TV box up again.
4. Connected the downstairs box using powerline adapters rather than WiFi.

Following the factory reset, the 5 GHz network has come back and the gaming laptop has also reconnected. At the moment things are therefore working again, but previous resets have also restored things temporarily, so I do not yet know whether this is a permanent fix.

The technical adviser ultimately said that we had effectively exhausted EE's troubleshooting options. He suggested that the location of our router, which is in a somewhat enclosed space, could be contributing to the problem, and recommended having Ethernet installed around the house so that devices such as the TV boxes can use wired connections.

I am certainly open to improving our home network and having Ethernet installed, but I am still not entirely convinced that WiFi coverage explains everything we have seen. In particular, it does not seem to explain why the entire 5 GHz side of the network appeared to stop accepting connections while 2.4 GHz continued working, or why a factory reset restored it.

I also noticed the reply from DDenEE above because their experience sounds worryingly similar. They were also advised by EE to stop using WiFi for the EE TV boxes and were given extenders and powerline adapters. That improved things but apparently did not completely resolve the errors. They ultimately found that using the aerial for the main EE box and replacing the mini boxes with other streaming devices was more reliable.

So at the moment I am going to leave the downstairs box connected through the powerline adapters and monitor it closely. I am particularly interested to see whether YVM102 returns even though that box is now effectively using a wired network connection.

I will also be watching the Smart Hub to see whether the 5 GHz device count suddenly drops back to zero again. If that happens after today's factory reset, I think it would point much more strongly towards either a Smart Hub firmware or state problem, or a fault with the hub itself, rather than simply WiFi coverage.

Regarding sleep mode, I don't think that explains the wider problem we have been seeing because the failures have coincided with other 5 GHz devices being unable to connect as well. The issue has not appeared to be isolated to the EE TV box waking from sleep.

Is there anything else you would suggest at this stage, particularly given the 5 GHz behaviour described above? I would also be interested to know whether EE are aware of any current Smart Hub 7 Pro or EE TV connectivity issues which could produce this behaviour.

Thanks,
Tom

Re: YVM102

Mellman — Sat, 08 Aug 2026 14:00:30 GMT

Hi all,

I'm hoping some of the more technically minded people here might be able to offer some advice, because we have been going around in circles with EE for quite a while now and I'm honestly getting pretty frustrated with the whole situation.

This is going to be a long post, but I want to explain everything that has happened because I don't think this is simply a case of one TV box having a weak WiFi signal.

OUR SETUP

We have an EE Smart Hub 7 Pro.

We also have two EE TV boxes, one downstairs and one elsewhere in the house, along with the usual collection of laptops, desktop PCs, Firesticks, phones and smart home devices.

We have also been using an EE WiFi extender.

The broadband connection itself generally appears to be fine. Even when these problems occur, some devices continue accessing the internet normally.

THE ORIGINAL EE TV PROBLEM

The problems initially became obvious through the EE TV boxes.

Both boxes have intermittently suffered connection problems, often showing YVM102 or failing to load certain sections of the EE TV interface.

Restarting the TV boxes and/or router has often brought things back temporarily, but the problem eventually returns.

What made me start questioning whether the TV boxes themselves were really the root cause was what happened to other devices at the same time.

THE 5 GHZ PROBLEM

My gaming laptop began randomly losing its WiFi connection.

Once this happened, it often would not reconnect at all.

I could forget the EE network, select it again, enter the correct password and Windows would either keep attempting to connect indefinitely or eventually say that it could not connect to the network.

Meanwhile, other devices connected over 2.4 GHz continued working.

I then checked the Smart Hub admin interface while this was happening and noticed something that seemed very significant.

The hub showed:

2.4 GHz: multiple connected devices
5 GHz: 0 connected devices

This was very unusual because we normally have several modern devices which either use or prefer the 5 GHz band.

The Smart Hub showed the 5 GHz radio as enabled.

It was using Smart Channel 100.

I tried switching only the 5 GHz radio off, saving the settings, waiting, switching it back on and saving again.

That did not fix it.

The hub continued showing zero 5 GHz clients and the gaming laptop still could not reconnect.

I also tried the 5 GHz "Rescan" option in the hub settings.

Unfortunately the Smart Hub does not appear to let me manually select a 5 GHz channel. Rescan simply resulted in it continuing to use Channel 100.

TESTING WITH A COMPLETELY DIFFERENT COMPUTER

This is the part that made me particularly suspicious of the Smart Hub rather than the gaming laptop.

My desktop PC uses an Intel WiFi 6E AX210 160 MHz adapter.

The desktop was working normally, but it had connected itself to 2.4 GHz.

We checked the adapter settings and temporarily configured it so that it could only use the 5 GHz band.

As soon as we did that, the desktop lost its connection.

It could see the EE WiFi network, but it could not connect to it.

Trying manually resulted in Windows saying it could not connect to the network.

This was essentially the same behaviour as the gaming laptop.

When I changed the Intel adapter back to normal dual-band operation, the desktop immediately connected again over 2.4 GHz.

So at this point we had two completely separate computers which:

1. Could see the EE network.
2. Worked over 2.4 GHz.
3. Could not establish a connection when restricted to 5 GHz.

That seemed difficult to reconcile with the idea that this was simply one faulty laptop or poor reception in one room.

We also unplugged the EE WiFi extender completely to rule that out.

The gaming laptop still would not connect.

COMPATIBLE WIFI

I also tried EE's separate Compatible WiFi network, which uses WPA2 rather than the main network's WPA3 configuration.

The gaming laptop could see the Compatible WiFi network but again reported that it could not connect.

I should point out that I could not make this a controlled 5 GHz-only test because the 2.4 GHz side of Compatible WiFi is used by our EV charger/solar equipment and I did not want to disrupt those devices.

THE 5 GHZ SIGNAL WAS ACTUALLY BEING BROADCAST

We also checked the available BSSIDs from the desktop.

Interestingly, the Smart Hub was still physically broadcasting the main EE network on 5 GHz, including a BSSID on Channel 100.

So this did not appear to be a simple case of the 5 GHz radio disappearing completely.

The network was visible, but devices appeared unable to associate with it.

This made me wonder whether the issue was somewhere in the Smart Hub's 5 GHz association, authentication or firmware rather than simply poor WiFi coverage.

TODAY'S EE SUPPORT CALL

Today I spent approximately three hours on the phone with EE technical support.

To be fair to the adviser, he spent a lot of time going through things with us.

During the call we eventually did the following:

1. Factory reset the Smart Hub 7 Pro.
2. Factory reset the downstairs EE TV box.
3. Set the TV box up again from scratch.
4. Connected the downstairs EE TV box using powerline adapters and Ethernet instead of WiFi.

Following the full Smart Hub factory reset, the 5 GHz network came back.

The gaming laptop also reconnected.

So currently everything is working again.

However, resets have restored things before, so at this stage I have no confidence yet that this is a permanent fix.

EE'S CONCLUSION

By the end of the call I was told that we had effectively exhausted EE's troubleshooting.

The adviser also raised the position of our Smart Hub, which is in a somewhat enclosed area, as something that could be affecting WiFi performance.

The recommendation at the end of the call was essentially to have Ethernet installed around the house and connect devices such as the EE TV boxes by cable wherever possible.

The frustrating part is that this is not something we have simply ignored. I have already spent quite a bit of time trying to arrange a proper Ethernet installation in the house.

Ours is a finished modern house with the router/BT entry point under the stairs and devices that I would ideally like to connect upstairs. The walls are dot-and-dab plasterboard over masonry, and I wanted a reasonably neat concealed Cat6 installation with proper wall plates rather than cables simply being run externally around the house.

I have contacted installers about this previously.

One contractor cancelled after seeing photographs and floorplans of what would be involved.

Another data cabling company explained that they generally preferred external cable runs and would not normally lift carpets, floorboards or parts of the staircase to create the internal route I was hoping for, and suggested that I would probably need an electrician instead.

So while I completely understand that Ethernet would be preferable for fixed equipment, "get Ethernet installed" unfortunately isn't quite the simple solution it sounds like.

Retrofitting a concealed wired network into an already finished house can involve a fair amount of disruption, and so far I have struggled to find somebody willing to take the job on in the way I would want it done.

That is partly why I am so frustrated that the apparent endpoint of EE's troubleshooting is effectively to redesign the network infrastructure of the house, particularly when we have also observed behaviour such as the Smart Hub showing zero 5 GHz clients and two completely separate computers being unable to associate with 5 GHz until the hub was factory reset.

I completely accept that Ethernet is preferable to WiFi and I would still like to have it installed if I can find somebody willing to undertake a neat concealed installation.

What I don't understand is why:

1. The hub suddenly showed zero 5 GHz clients.
2. Multiple devices which normally use 5 GHz stopped using it.
3. My gaming laptop could see the network but could not connect.
4. A completely separate desktop with an Intel AX210 behaved exactly the same way when forced onto 5 GHz.
5. 2.4 GHz continued working normally.
6. Switching the 5 GHz radio off and back on did not fix it.
7. Removing the EE extender did not fix it.
8. A complete Smart Hub factory reset did restore it.

That seems to me like there could be something else going on with the Smart Hub.

EE TV / YVM102

There is another thread here discussing YVM102 which I originally posted in.

One contributor has recently explained that EE also advised them to stop using WiFi for their TV boxes and supplied additional extenders and powerline adapters.

They said this improved the situation but did not eliminate the errors completely.

They eventually stopped using the mini boxes and later moved away from EE entirely. Interestingly, they also reported getting substantially better WiFi coverage using inexpensive third-party networking equipment than they ever achieved with EE's own router and extenders.

Obviously that is one person's experience and I am not taking it as proof of anything, but it does make me question whether continuing to add more EE extenders or powerline equipment is really addressing the underlying problem.

WHAT I AM DOING NOW

For the moment I am leaving everything as EE configured it today.

The downstairs EE TV box is connected through the powerline adapters.

The Smart Hub has been factory reset.

5 GHz is currently working again.

The gaming laptop is currently connected again as well.

I am now going to monitor two things very closely.

Firstly, whether the downstairs TV box develops YVM102 again despite now being connected through powerline/Ethernet.

Secondly, whether the Smart Hub's 5 GHz client count suddenly drops back to zero again and the laptops once again become unable to connect.

If either happens, particularly after today's full factory reset, I think we need to reconsider the explanation that this is simply poor WiFi coverage.

THIRD-PARTY ROUTER?

This is also why I am now seriously considering replacing the EE Smart Hub with a good third-party router or WiFi system.

I would be very interested to hear from anyone who has actually done this on a current EE connection.

In particular:

Which routers are people successfully using with EE broadband?

Has anyone replaced a Smart Hub 7 Pro specifically and seen noticeably better reliability or coverage?

Are ASUS routers a good option? I have been looking at some of their higher-end WiFi 6 and WiFi 7 equipment.

Does EE TV, including the live IPTV channels, work correctly through your third-party router?

I understand that EE TV uses multicast/IGMP for some live channels, so I assume simply having an internet connection is not necessarily enough.

If you are using EE TV successfully through ASUS, TP-Link, Cudy, UniFi or anything else, I would really like to know the exact model and whether any special IGMP or multicast settings were required.

Would another sensible option be to leave the EE Smart Hub handling the broadband and any EE-specific services, disable its WiFi completely, and use a proper third-party access point or mesh system for all wireless devices?

As mentioned above, I have already investigated having Ethernet installed properly around the house and would still like to do this if I can find somebody willing to undertake a neat concealed installation. It would obviously be useful regardless of which router we ultimately use.

I would really appreciate opinions from people who understand this stuff better than I do.

At this point I am less interested in another round of "restart the router / restart the TV box" troubleshooting because we have done that repeatedly, along with restarting individual wireless bands, removing the extender, testing two different computers, a full factory reset and several hours of EE support.

What I would really like to understand is:

Does the 5 GHz behaviour described above sound like a Smart Hub fault or firmware issue?

Has anyone else experienced the Smart Hub 7 Pro getting into a state where 2.4 GHz works but devices cannot associate with 5 GHz?

Has anyone continued receiving YVM102 after moving their EE TV box from WiFi to Ethernet or powerline?

Would you push EE for a replacement Smart Hub if the 5 GHz problem returns?

Has anyone found that replacing the EE Smart Hub actually cured similar WiFi or EE TV problems?

And if you decided to ditch the EE router, what equipment would you recommend that still works properly with EE TV?

Sorry for the extremely long post, but after repeated intermittent issues and another three-hour troubleshooting session today, I wanted to put the complete picture in one place.

Any advice or experiences would be massively appreciated.

Thanks.

Re: YVM102

JimM11 — Sat, 08 Aug 2026 17:57:19 GMT

@Mellman Have you checked that all your own 5Ghz equipment devices can operate up in the CH100 operation, do not just assume that they can, some do not!

EE Hub firmware versions - The EE Community check your FW has updated, the 5Ghz wifi issue may have been fixed.

From what you have done so far, next logical step is to ask EE to give you a replacement for your EE 7 Pro hub at least, but you maybe better to go the whole hog and switch the Extender out as well. Backhaul on the Hub/Extender is supposed to be using the 6Ghz band so 5Ghz working on an extender may also show the symptoms you express. 100% Asus XT8's and RP-AX58's with a little powerline in the mix, no issues hardware wise, all band's split TRI-Band model's but are only AX comp, if wifi 7 is your thing and MLO in use never mind the TV/DV issues if using, but EE TV is going to be another user for working that way, suggest you look on the TV part of the Forum.

Re: YVM102

Mellman — Sun, 09 Aug 2026 15:56:55 GMT

Thanks Jim. I've checked the hub status and it is currently running firmware r4.29.1-R-1930437-PROD-1, so it looks like I am already on the latest generally rolled-out firmware for the Smart Hub 7 Pro.

I noticed from the firmware information that r4.29.1 specifically includes a fix for "5GHz WiFi sometimes stops working after firmware update", which sounds particularly relevant given what we experienced.

The hub was factory reset yesterday, so I can't say with absolute certainty from the current status page whether it was already on r4.29.1 before the reset or whether anything changed around that reboot. The 5GHz side is currently working again following the factory reset.

Regarding Channel 100, one of the devices I used for testing was a desktop with an Intel WiFi 6E AX210 adapter. When the fault was present I forced that adapter to 5GHz only. It could still see the EE network but would not connect to it. As soon as I returned the adapter to normal dual-band operation it connected again over 2.4GHz.

From what I can find, the AX210 should support Channel 100, so I don't think Channel 100 alone explains what happened with that particular device. I agree that it would still be worth checking the capabilities of the other affected devices individually though.

Your suggestion of asking EE for a replacement Smart Hub 7 Pro is where I'm leaning if the fault returns. The fact that the current firmware apparently contains a fix for 5GHz stopping, yet we have experienced essentially that behaviour, makes me even more interested in ruling out the hub itself.

Thanks also for the information about your ASUS setup. The XT8 and RP-AX58 combination is exactly the sort of real-world experience I was hoping to hear about.

EE TV is the main thing making me cautious about replacing the EE hub completely, particularly making sure the live channels still work properly, so I'll have a look through the TV section as you suggested.

Thanks again.

Re: YVM102

Mellman — Sun, 09 Aug 2026 21:45:39 GMT

Quick update, unfortunately the exact same problem has already returned.

It is only around 30 hours since I spent approximately three hours on the phone with EE technical support, during which the Smart Hub 7 Pro was completely factory reset, the downstairs TV box was factory reset and set up again from scratch, and the downstairs TV box was moved onto powerline/Ethernet.

Following the factory reset, 5GHz came back and the affected devices were able to connect again.

Tonight I checked the Hub Manager and we are right back where we started. The 5GHz section is once again showing "No devices are connected".

I have to admit I am getting extremely frustrated with this now.

We have spent hours and hours troubleshooting this, restarting equipment, removing the extender, testing different devices, testing the separate Compatible WiFi network, switching the 5GHz radio off and back on, rescanning channels, forcing a completely separate Intel AX210 desktop onto 5GHz, and finally doing a complete factory reset of the hub with EE technical support.

The factory reset has apparently bought us little more than a day before exactly the same fault has returned.

This is precisely why I was uncomfortable with the conclusion from the support call that the main problem was the location of the router and that the answer was essentially to have Ethernet installed around the house.

I completely accept that wired Ethernet is preferable for fixed devices, and as I mentioned previously I have already tried to arrange a proper Ethernet installation. Unfortunately retrofitting a neat concealed installation into our finished house is not straightforward and I have struggled to find installers willing to undertake it.

More importantly though, I still do not understand how the physical location of the router explains this particular behaviour.

This is not simply one device at the edge of the WiFi range occasionally having a weak signal.

When the fault occurs, the Hub Manager shows zero devices on 5GHz. Previously my gaming laptop could see the network but could not connect to it, and we reproduced the same behaviour using a completely separate desktop with an Intel AX210 adapter. When that desktop was forced to 5GHz it could see the EE network but could not associate with it. Returning it to dual-band operation allowed it to connect immediately over 2.4GHz.

A full factory reset then restored 5GHz, only for the same problem to return roughly 30 hours later.

The hub is currently running firmware r4.29.1-R-1930437-PROD-1.

At this point I really do feel as though we are just going around in circles.

I do not think it is reasonable to keep repeating factory resets every time the 5GHz side of the router gets into this state, particularly when we now know that even a complete reset only appears to fix it temporarily.

Jim, I think your suggestion that the next logical step is to ask EE for a replacement Smart Hub 7 Pro is looking increasingly sensible.

I am going to contact EE again and ask them to replace the hub rather than simply repeat the same troubleshooting process.

At the same time, I am now seriously considering buying a good third-party router or WiFi system anyway. We rely on the network for too many things in the house to keep having this happen, and after all the time spent troubleshooting it I am reaching the point where I would rather pay for better equipment than keep going through the same cycle with the EE hardware.

Obviously EE TV compatibility is still the main thing I need to investigate before replacing the hub completely, which is why the ASUS information and the suggestion to look through the TV section are really useful.

I will update the thread again with what EE say about replacing the hub, but I am honestly pretty fed up with the situation now. After a three-hour support call and a complete factory reset I did not expect to be looking at exactly the same "No devices are connected" message on 5GHz barely more than a day later.

Re: YVM102

Mellman — Mon, 10 Aug 2026 09:51:27 GMT

Another update, and I am absolutely furious with EE now.

I called EE again this morning using the urgent callback link that the technical adviser gave me after Saturday's approximately three-hour support call.

That link was specifically provided so that I could get back in touch quickly if we experienced any further problems following all of the troubleshooting and the complete factory reset of the Smart Hub.

Before we could even properly discuss the continuing technical problems, I was suddenly told that EE could not deal with me without speaking to my dad first because I apparently do not have the correct level of authority on the account.

I cannot adequately express how angry and frustrated I am about this.

My dad is the account holder, but I have been authorised to deal with this account on his behalf for well over a year. We went through an enormous amount of hassle with EE about this exact issue last year. It resulted in a large complaint and, after considerable effort, the authority situation was eventually sorted out.

Since then I have personally dealt with EE countless times.

This is not a situation where I have occasionally phoned up to ask a simple technical question.

I have personally ordered new EE TV boxes.

I personally dealt with upgrading our equipment from the old BT setup to the current EE router.

I have personally had two EE WiFi extenders sent to our house.

I have personally dealt with numerous broadband and TV faults.

I have spent hours speaking to EE technical support.

I have been allowed to arrange, replace and reconfigure equipment.

Normally, when I call, EE sends a security code to my registered mobile number. I read that code back to the adviser, they verify me and we continue with whatever I am calling about.

This has happened repeatedly.

I would estimate that I have spoken to EE at least 20 times since the authority issue was supposedly resolved last year.

Indeed, only on Saturday EE technical support spent approximately THREE HOURS troubleshooting these current broadband and TV problems with me.

During that call we factory reset the Smart Hub, factory reset and reconfigured the downstairs EE TV box, discussed the WiFi problems in detail, moved the downstairs TV box onto powerline/Ethernet, and went through the history of all the troubleshooting I had already carried out.

At the end of that three-hour call the adviser gave ME a special urgent callback link to use if the problems continued.

I used that exact link this morning.

And somehow, less than two days later, I am suddenly being told that I do not have sufficient authority to deal with the account.

After a considerable argument, the adviser eventually agreed that he could continue discussing the technical problem with me provided that he did not disclose account or policy information.

Fine.

I was not asking him for confidential account information.

I was trying to get EE to resolve the same technical fault that EE had already spent hours troubleshooting with me.

Given the amount of troubleshooting we have now performed and the continuing instability, I told the adviser that I wanted the Smart Hub replaced.

He refused.

The reason given was not that he disagreed with the technical case for replacing it.

I was told that he could not send me a replacement router because I am not the policy holder and apparently do not have the required level of authority.

At that point I was completely fed up and told him that I wanted to make a formal complaint about the situation.

I was then told that I could not even make a complaint.

Again, because I apparently do not have the required authority.

That is absolutely insane.

So, according to EE, I have apparently been authorised enough to:

Order new EE TV equipment.

Arrange the change from our old BT equipment to EE equipment.

Have two WiFi extenders supplied to our house.

Deal with broadband and TV faults repeatedly.

Spend hours troubleshooting EE equipment with technical support.

Factory reset and reconfigure that equipment.

Receive security codes on my registered mobile number and use them to verify myself.

Spend approximately three hours with technical support on Saturday dealing with this exact fault.

Be given a special urgent callback route by that adviser so that I can continue dealing with the problem.

And even continue discussing the technical problem with today's adviser.

But the moment I ask EE to actually resolve the problem by sending replacement hardware, suddenly I am not authorised enough.

Even more absurdly, when I then ask to make a formal complaint about being treated this way, apparently I am not authorised enough to do that either.

How on earth is that a coherent system?

We are absolutely sick of being messed around by EE.

I completely understand that EE has security procedures. I am not asking anybody to ignore account security and I am not asking for access to confidential information.

What I am objecting to is the fact that we went through this exact authority nightmare last year, made a substantial complaint about it, eventually got it sorted, and I have subsequently been allowed to deal extensively with this account for well over a year.

EE cannot reasonably allow me to act on the account repeatedly, allow me to order and arrange equipment, verify me using my registered mobile number, and spend hour after hour troubleshooting faults with me, only to suddenly change the rules at the exact point where I ask them to actually replace the equipment we have been troubleshooting.

I have now found the forum thread I created last year while going through the original authority fiasco.

It is frankly unbelievable to be reading that old thread and realising that, over a year later, we are apparently back in exactly the same ridiculous situation that we spent so much time getting resolved.

And now it is actively preventing us from resolving an ongoing broadband fault.

I want to make a FORMAL COMPLAINT about this.

Not only about the broadband and EE TV problems, but specifically about the handling of my authority on this account, the complete inconsistency between what EE has allowed me to do for well over a year and what I was told today, the refusal to supply replacement hardware after all of the troubleshooting already undertaken, and the extraordinary claim that I am not even permitted to register a complaint about it.

I want somebody at EE to investigate what authority is actually recorded against my name, what happened when this was supposedly resolved following last year's complaint, why it has been accepted on numerous occasions since then, and why today's adviser suddenly interpreted it completely differently.

I also want somebody to explain how it can possibly be acceptable for EE to spend hours asking an authorised third party to carry out technical troubleshooting and factory resets, but then refuse to allow that same person to see the fault through to a resolution.

I am not prepared to simply go through the same authority process we fought through last year and pretend that none of that history happened.

Nor am I prepared to accept that the answer to this situation is simply "get the policy holder to call".

That completely avoids the issue.

The entire point is that we already went through the process of authorising me to deal with this account precisely because I am the person who manages the broadband and TV equipment and deals with technical support.

Something has clearly gone badly wrong with either EE's records, EE's processes, or the way those processes are being interpreted by different advisers.

I want that investigated and corrected permanently.

As for the original technical problem, after everything we have already done I still want the Smart Hub replaced.

I do not want another factory reset.

I do not want another three-hour repetition of troubleshooting we have already completed.

I do not want another suggestion that we simply install Ethernet throughout the house.

And I certainly do not want another call where, after everything we have already been through, I have to argue about whether EE will even allow me to ask for the problem to be resolved.

We are absolutely, thoroughly fed up with being messed around.

At this point I want a formal complaint opened, I want the authority problem investigated and permanently resolved, and I want somebody at EE to take ownership of the underlying broadband problem and actually do something about it.

Re: YVM102

DDenEE — Mon, 10 Aug 2026 09:51:53 GMT

I feel your pain, because I have been through it before myself.

My experience is that switching off IPTV and using aerial import only on the main EE TV box fixes it (there will still be occasional other glitches, but this error will go). Everything else, including plugging it directly into a EE Smart extender or powerline adapter using a LAN lead will fail.

As for the EE TV mini boxes which have no aerial input option - I just boxed them up and replaced with Google TV dongles (other brands available).

As for their WiFi, since I left EE and got my own very cheap Chinese wifi router+extender pack (Cudy) the poor quality of the EE kit has really been shown up. With EE I had their router plus 2 extenders plus two powerline adaptors in my four bedroom house - I had literally spent days positioning things and building up to that layout to try and solve black spots. With the new cheaper kit I have just one extender and no powerlines and the quality of signal throughout the house and at the bottom of my garden is far better.

Re: YVM102

Mellman — Mon, 10 Aug 2026 10:13:54 GMT

A further update, because I have now gone back through my records from the authority problem I had with EE last year, and what I have found makes today's situation even more infuriating (https://community.ee.co.uk/t5/Broadband-Landline/Being-added-to-an-A-C-as-a-3rd-party-contact-via-call-with/td-p/1529800/page/3).

This is not simply a case of me remembering that the authority issue was "supposed to have been sorted".

I still have the private message correspondence with Christopher_G from the EE Community team from last year.

Christopher originally contacted me after seeing the thread I had created about the problems I was having with EE recognising my third-party authority. He specifically said that he wanted somebody to look at how my access was set up and "make sure the correct processes are being followed when you call."

He then referred the matter internally to the complaints team.

He subsequently confirmed to me that Gernelle from the Executive Complaints team had spoken to us and would be handling the complaint going forward.

Most importantly, once this had been dealt with, Christopher sent me the following:

"Hopefully, now that Gernelle has updated the account, any calls that you have with our customer support team go much more smoothly."

So EE's Executive Complaints team actually became involved in this exact authority problem last year and UPDATED THE ACCOUNT.

And following that, things did work much more smoothly for the better part of a year.

I have since dealt with EE numerous times myself, ordered TV equipment, dealt with our move from the old BT equipment to EE equipment, had two WiFi extenders sent to the house and dealt with repeated technical support issues. Usually a security code is sent to my registered mobile number, I read it back and we continue.

Which makes what happened this morning even more absurd.

After all of that, and after a THREE HOUR technical support call on Saturday, I am suddenly told that I cannot authorise the replacement of the router because I am not the policy holder.

Then, when I ask to make a formal complaint about what is happening, I am told that I cannot even do that.

I now want EE to explain exactly what Executive Complaints changed on the account last year, whether that change is still present, and why the authority that has apparently worked for approximately a year was suddenly treated differently today.

If today's adviser was correct, why have EE repeatedly allowed me to carry out all of the above since Executive Complaints updated the account?

If today's adviser was wrong, then his incorrect interpretation of my authority directly prevented an ongoing technical fault from being resolved and prevented me from registering a complaint about it.

Either way, something has gone very badly wrong.

I have messaged Christopher_G again this morning because he was the person who originally got this escalated to Executive Complaints, and I am hoping he can trace the previous case and help establish what has happened.

I was angry before finding these messages.

Having now found written confirmation that Executive Complaints dealt with this exact issue and updated the account last year, I am absolutely furious that we are apparently back here again.

Re: YVM102

Mellman — Mon, 10 Aug 2026 14:17:53 GMT

A further update following the saga this morning.

Alex_H from the EE Community Support Team picked up my post on the old third-party authority thread and escalated the situation to Executive Complaints.

I have now spoken to Executive Complaints.

Importantly, they have confirmed that I AM correctly authorised on the account.

So the authority issue that prevented the telephone adviser this morning from sending replacement hardware was not because my previously arranged authority had disappeared or was incorrectly configured.

Executive Complaints have now ordered a replacement router, which is being sent by Royal Mail 48.

They have also advised that the handling of this morning's call will be fed back to the relevant team so that any knowledge gaps can be addressed and additional training provided where necessary.

The complaints adviser is going to call me again in three days to check how things are progressing.

So, after the approximately three-hour troubleshooting call on Saturday and everything that happened this morning, we are FINALLY getting the Smart Hub replaced.

I am going to leave the current setup alone as much as possible until the replacement arrives. Once it does, I will set it up and monitor the WiFi, particularly the 5GHz behaviour, and see whether the problems we have been experiencing return.

I am not going to call the technical issue resolved until we have actually tested the replacement hub for a reasonable period, but at least we have finally reached the hardware replacement stage.

Thank you to Alex_H for getting this escalated so quickly.

Re: YVM102

Mellman — Sat, 15 Aug 2026 21:31:15 GMT

I have a fairly significant update after doing some controlled testing with the replacement Smart Hub 7 Pro.

Unfortunately, after initially appearing to work properly for around four days, the same 5 GHz problem has now reproduced on the replacement hub.

The EE WiFi extender has remained completely powered off throughout this testing, so it can be excluded from what happened below.

When the replacement hub was first installed, 5 GHz was working normally. My desktop, which has an Intel AX210 WiFi 6E adapter, connected directly to the hub without any problems. The gaming laptop also worked normally. The hub was initially using a lower 5 GHz channel, including channel 36 during the period when everything was working.

Today the gaming laptop lost its 5 GHz connection again. If I forced its WiFi adapter to 5 GHz only, it could see the EE network but Windows reported "Unable to connect to this network". Returning the adapter to dual band allowed it to connect over 2.4 GHz.

I then repeated the test independently on the desktop using its Intel AX210 adapter. Exactly the same thing happened. When restricted to 5 GHz only, the desktop could not connect either.

At this point Hub Manager showed:

5 GHz: On
Smart Channel: 100

I ran "netsh wlan show networks mode=bssid" on the desktop. Initially it could only see the Smart Hub's 2.4 GHz BSSID, despite Hub Manager still reporting that 5 GHz was enabled on channel 100. The 5 GHz BSSID had disappeared completely.

I then used the 5 GHz Smart Channel Rescan function in Hub Manager. It remained on channel 100 and this did not restore 5 GHz connectivity.

Next I switched only the 5 GHz radio off, saved the setting, waited, switched it back on and saved again.

After doing this, the hub's 5 GHz BSSID became visible again on channel 100 with a strong signal of around 80 percent. However, neither the desktop nor the gaming laptop could actually connect to it.

I also generated a Windows WLAN diagnostic report from the desktop while the fault was occurring.

One of the failed attempts is particularly interesting. Windows records that association with the Smart Hub's 5 GHz BSSID succeeded, WPA3-Personal security then started, and approximately five seconds later the security stage failed.

The reported reason was:

"Dynamic key exchange did not succeed within configured time"

Windows also recorded:

"PSK mismatch suspected"

The WiFi password was definitely correct. The same SSID/profile/password continued to work over 2.4 GHz and had previously worked normally on 5 GHz.

As another test, I enabled the Smart Hub's separate Compatible WiFi network on 5 GHz. This uses WPA2-Personal rather than WPA3.

Hub Manager showed Compatible WiFi 5 GHz enabled on channel 100. However, when I restricted the Intel AX210 to 5 GHz only, the Compatible WiFi SSID disappeared from the available network list completely. It therefore did not provide a working WPA2 alternative either.

At that point I performed a normal restart of the Smart Hub from Hub Manager. This was not a factory reset.

After the restart, Smart Channel selected channel 149 instead of channel 100.

The results immediately changed.

The desktop automatically connected successfully to 5 GHz again on channel 149 using WPA3-Personal.

The gaming laptop, which has a separate Intel AX200 adapter and had previously been unable to connect when restricted to 5 GHz, is also now successfully connected to 5 GHz on channel 149. Windows shows a current link speed of 721/360 Mbps.

The upstairs EE TV Mini box, which had also started experiencing connectivity/interface problems again at approximately the same time as the 5 GHz problem returned, is now working correctly again following the Smart Hub restart.

I am not claiming that channel 100 itself has conclusively been proven to be the cause, because restarting the hub also resets its internal wireless state.

However, the observed sequence so far is:

5 GHz working normally on channel 36.

5 GHz subsequently failing while Smart Channel was on channel 100.

Two independent computers unable to use 5 GHz.

The extender completely excluded.

Smart Channel Rescan did not resolve it.

Cycling only the 5 GHz radio restored the 5 GHz broadcast but did not restore the ability for clients to connect.

Windows WLAN diagnostics recorded a WPA3 dynamic key exchange timeout against the Smart Hub's 5 GHz BSSID.

A WPA2 Compatible WiFi test also failed to provide a usable 5 GHz connection.

A full Smart Hub restart then moved 5 GHz to channel 149 and restored normal 5 GHz operation on both independent computers.

The upstairs EE TV Mini also began working normally again after the same restart.

This is now the second Smart Hub 7 Pro on which we have reproduced very similar 5 GHz behaviour. The replacement is running firmware r4.29.1-R-1930437-PROD-1, which was also the firmware running on the previous hub.

Given that this has now occurred on two different Smart Hub 7 Pro units and has affected multiple independent clients, I am increasingly concerned that this may be a Smart Hub 7 Pro firmware, Smart Channel, DFS or wireless state issue rather than simply faulty client hardware.

It is also frustrating that there appears to be no option to manually lock the 5 GHz radio to a known working non-DFS channel such as 36, 40, 44 or 48, as that would give us a very useful way of testing whether the problem returns.

For now I am going to leave the hub running in its current working state and monitor it closely. If the fault returns I will capture the channel, BSSIDs and client behaviour again before restarting anything.

I would be very interested to know whether EE can escalate these findings to whoever is responsible for Smart Hub 7 Pro firmware/wireless engineering, particularly given that the replacement hardware has now reproduced the same issue.