Drop out problems with new Three outdoor hub Y5-210MU

Kylep · ‎27-12-2024

I'm really hoping someone can help me. I have recently signed up for Three 5g home broadband. Initially had an indoor router but switched the the outdoor hub green packet Y5-210MU. I'm experiencing great speeds, but what seems to be a common issue of the connection dropping out once every 24 hours or so. It requires a reset at power supply to correct this, so not ideal! Device still has 4g or 5g light on, but is not connected really until reset.

After some research, I found people suggesting the connected router should have 5g wifi disabled to allow the modem to work properly. I cannot think why on earth this would be the case, but I tried it anyway. At the same time I did a factory reset and thought I fixed the issue. I had no drop outs for 48 hours. However this morning it happened again...

I have also seen suggestions that this is a firmware issue with Three, but I would imagine there is a way to fix this in the device settings. If anyone can help I would really appreciate it. I don't want to switch back to the indoor hub as the speeds are not as good. Even if someone can shed some light on what precisely causes this so I can predict the drop outs it would be great... the drop outs SEEM to only happen at night, so i am even happy to reset the device using a timer at say 3am every night if that solves the issue as a workaround (I'm on a house boat and powering the device direct from 24V so easy enough to wire in a timer.

lukewest · ‎15-09-2025

This morning (2025-09-15) I enabled TR-069 and shortened the retry to 5 mins to force an update if there is one.

My router went into a total sulk wouldnt respond to anything. I tried to restart it, the signal strength showed but I couldn't get into it (it wasnt advertising the IP to my gateway router)

I reset the router, and logged in again, made the same changes (IP Passthrough > Router + setting passwords) I restarted, then checked the TR-069. the view is very different and I CANNOT disable it, nor can I change the frequency.

I obviously have a different firmware but the info in the router pages is the same.

MymsMan · ‎15-09-2025

@lukewest can you post a screen shot of the new screen layouts?

Can I suggest you download the system logs and looking at the messages for the time you attempted to change the TR069 settings to see what it is objecting to. That was how I discovered that the Request User Id had been changed to an invalid value.

Immediately after hub reset the Request userid and Password are both set to admin, then the TR069 upates the userid, password, periodic interval and time etc making it difficult to make further changes

@gavinmcnair also reported a similar update that was affecting his rebooter script

lukewest · ‎16-09-2025

Original layout:

New layout:

Syslog for the time of the error shows a lot of chatter but nothing helpful.

Separately. I see a login failure to TR-069, I’m not sure if the internet connection was in place for this to succeed. i.e. was this a response back from the TR-069 service or the router couldn't talk to the endpoint.

Tue Sep 16 06:18:26 2025 daemon.info atcid[9737]: [ATCI] 1006:readline(): Wait for select data from USB
Tue Sep 16 06:18:26 2025 user.err : 10312:[src/device_ubus.c,cmdProcess,137]cmdProcess 137,cmd=setting.system.set.tr069config, arg={ "TR069ServiceEnable": "Disable", "ACSURL": "https:\/\/acs-ps.ukbroadband.com:10302\/acs\/", "ACSUsername": "admin", "ACSPassword": "admin", "PeriodicInformEnable": "Enable", "PeriodicInformInterval": 3600, "PeriodicInformTime": "2025-09-16T01:03:13Z", "ConnectionRequestUsername": "2479EF-XXXXXXXXXXXX3", "ConnectionRequestPassword": "YYYYYYY", "ConnectionRequestPort": 7547 }
Tue Sep 16 06:18:26 2025 user.err : 10312:[src/device_cwmp.c,CwmpCheckPara,449]CwmpCheckPara 449, request user name is invalid value
Tue Sep 16 06:18:26 2025 user.err : 10312:[src/device_cwmp.c,CwmpSetConfig,557]CwmpSetConfig 557, para is errror
Tue Sep 16 06:18:27 2025 kern.info kernel: [18980.896840] (2)[1058:ccci_sys][ccci1/sys]system message (ffffffff 103 2 42c) msg_count:15

----

BTW I bumped into this in the "early_system.log", it made me laugh...!

Tue Sep 16 01:02:17 2025 kern.warn kernel: [ 0.000000] -(0)[0:swapper]
Tue Sep 16 01:02:17 2025 kern.warn kernel: [ 0.000000] -(0)[0:swapper]**********************************************************
Tue Sep 16 01:02:17 2025 kern.warn kernel: [ 0.000000] -(0)[0:swapper]** NOTICE NOTICE NOTICE NOTICE NOTICE NOTICE NOTICE **
Tue Sep 16 01:02:17 2025 kern.warn kernel: [ 0.000000] -(0)[0:swapper]** **
Tue Sep 16 01:02:17 2025 kern.warn kernel: [ 0.000000] -(0)[0:swapper]** trace_printk() being used. Allocating extra memory. **
Tue Sep 16 01:02:17 2025 kern.warn kernel: [ 0.000000] -(0)[0:swapper]** **
Tue Sep 16 01:02:17 2025 kern.warn kernel: [ 0.000000] -(0)[0:swapper]** This means that this is a DEBUG kernel and it is **
Tue Sep 16 01:02:17 2025 kern.warn kernel: [ 0.000000] -(0)[0:swapper]** unsafe for production use. **
Tue Sep 16 01:02:17 2025 kern.warn kernel: [ 0.000000] -(0)[0:swapper]** **
Tue Sep 16 01:02:17 2025 kern.warn kernel: [ 0.000000] -(0)[0:swapper]** If you see this message and you are not debugging **
Tue Sep 16 01:02:17 2025 kern.warn kernel: [ 0.000000] -(0)[0:swapper]** the kernel, report this immediately to your vendor! **
Tue Sep 16 01:02:17 2025 kern.warn kernel: [ 0.000000] -(0)[0:swapper]** **
Tue Sep 16 01:02:17 2025 kern.warn kernel: [ 0.000000] -(0)[0:swapper]** NOTICE NOTICE NOTICE NOTICE NOTICE NOTICE NOTICE **
Tue Sep 16 01:02:17 2025 kern.warn kernel: [ 0.000000] -(0)[0:swapper]**********************************************************
Tue Sep 16 01:02:17 2025 kern.info kernel: [ 0.000000] -(0)[0:swapper/0]rcu: Hierarchical RCU implementation.
T

MymsMan · ‎16-09-2025

@lukewest Those 'login failure' messages were your attempt to disable the TR069 service, and there is an invalid '-' in the request user name. Set the 'request user name' field to blank then you will be able to disable the TR069 service (do not change the ACS user name)

Still waiting for mods to approve your images, so cant see changes yet

Others have already commented on the early log messages - while showing poor quality control it is not obvious whether the debug kernel actulally causes problems

lukewest · ‎16-09-2025

Ha. I didnt think that their default values may have been the cause of the problem.
I removed the "-" and was able to turn this off.
I'll keep experimenting

Paul_F · ‎31-08-2025

Hi Three, Suggest your technical department need to Tiger Team this and perhaps start collecting logs from customers to determine the underlying issue. The correct way forward is a Firmware fix. The issue has been tracked elsewhere on the internet to poor firmware from the OEM, who have used non-production Kernels inside the code. I suspect there is either a memory leak or other Firmware issue with the hardware.

To be clear, having worked really hard at fixing this, I dont believe the issue is on the GSM/5G/4G Network side. Its a problem with the firmware that is causing a crash that is not recoverable and is causing the router to get "Stuck" without an ability to reset gracefully. I suspect this as the device doesnt lose internet speed through reversion to 4G. It locks up and is not able to process ANY net traffic.

Hope this helps. Please provide us an update as to the Three recovery plan as we would like to stay with the service, but wont if you dont communicate effectively as to how you are looking to fix the problem with the OEM.

MymsMan · ‎31-08-2025

Have you tried disabling the TR069 service?

I haven't had a disconnection in three weeks.

Reset (not just reboot) hub, if that doesn't help, Try:

log on to to hub https://192.168.0.1 using userid admin and password printed on hub label
Navigate to Advanced->System->TR069
Disable TR069 and Periodic Inform
Submit, if that fails with a red message then clear 'Request user name' field and try again. Do Not clear 'ACS user name' field
Navigate to Advanced->System->Maintenance
Disable Scheduled Reboot or change to a less frequent interval (days)
Click on Scheduled Reboot

Paul_F · ‎22-09-2025

Alas, drop-outs returned today with vengence... 5x drop outs in 3 hours.... Getting bored of resetting the hub now in the middle of Teams calls.

MymsMan · ‎22-09-2025

Check whether TR069 is still disabled and hasn't been re-enabled by a hub reset

Also check the three status page for your post code

Paul_F · ‎22-09-2025

So, TR069 still disabled. And zero issues reported on the network online. Thing is, when it goes, I can still see that there is signal through the web interface.

utterly frustrating!