Android devices have stopped connecting to wifi overnight

[SandieC]

My three android devices have stopped connecting to my wifi overnight .. 2 tablets and my sky mobile phone . My Laptop is connecting .

I have restarted the devices and the router , and 'forgotten' and then re started the wifi connection on each device , but none of them will connect ? It just says saved/disabled .

All were fine yesterday .

Could anyone advise please ? Thank you !

[LolSky]

I have exactly the same problem. My 4 AC Devices all dropped off Sky Broadband at 01.44 am this morning and I can't reconnect them. They reconnect fine to a different network (I setup a hotspot on my phone to check that out).

I haven't changed anything my side - no router changes etc, and I know the devices haven't updated, and connect fine to a different network so feels that something has happened Sky-Side.

I made a support call and tried all the logical steps, but despite best effort, we couldn't get the issue resolved. They're sending me a new router, but I'm skeptical around whether that will fix the issue. Feels more like an Infrastructure change or a routing or Firewall issue (but Sky indicate nothing has changed).

I'll give the new router a go but if it doesn't fix the issue (as I suspect), it's off to a new ISP I go, sadly.

[SandieC]

That's really interesting, mine all disconnected at 02.38hrs this morning. I'll have to call customer support tomorrow to see what they say. I hope a new router solves your problem.. though  like you, I'm not convinced. Would be interested to hear how you get on!

[LolSky]

Ditto - Please do let me know here if you get any more information or if the issue is resolved. I would suspect Sky are blocking some traffic somewhere.

[LolSky]

OK - So, the new router "worked" (and bizarrely seems to be using the same SSID and Password as my old network; it definitely is the new one though).

My AC Units are accessible from my mobile app again, which is nice.

However, I am hugely suspicious. Whilst troubleshooting, I got my AC devices working fine with a mobile hotspot after they all dropped off Sky. Relaying that information to my AC Unit Provider on the ticket for my issue, they indicated:

###

If it works with the mobile hot spot, then the problem is definitely with the Router - Network configuration settings. 
 
Either you are entering the password of your wifi network incorrectly or the wi-fi network is not set to 802.11b mode.
 
It happens that routers got automatic firmware, and it changes the settings. Happens really frequently. 

###

(I definitely didn't enter the password wrong every time I tried to get it going - that was a lot).

So pushed firmware update/setting changes now seem the likely cause, I would think. If it was Sky-Side Infrastructure, it still wouldn't work with the new router 

So, I suspect, and am trepidatious, that  ...

1. My "new" router has been sitting in its box for a bit, and has older firmware/settings than Sky are currently pushing
2. At some point (overnight again, most likely) they'll push an update to me (maybe even the same one as rolled in the night before last).
3. I'll be back to where I started, with all my AC devices not accessible.

Still, at least I will have this thread to refer to if that does happen.

Hope you've managed to make progress to and have your android devices working again.

[SandieC]

Hi !

I just got off the phone with support . 

They dropped the 'shield' ( I'm so sorry , I'm not technologically minded at all ) Then we went for a factory re-set on the hub , and , is if by magic , all my devices were able to reconnect !

I'm pretty sure you must have had the same advice from support as me , so I don't know why mine worked and yours didn't . The lovely support lady did say sometimes there are android updates and it can take a while for Sky to catch up ? 

I'm afraid that doesn't mean a great deal to me , but whatever it was worked .

I hope you're getting sorted ?

[LolSky]

Hi Sandie,

I'm glad your issues are sorted, but my saga has a bit more to relate (FYI - I already have the Sheild disabled. It's not my issue).

As expected/feared, all my old AC devices disconnected at 01.21 last night, pretty much confirming 100% that the problem is the result of an issue off the back of a Sky Pushed Router Update. My guess would be that it's related to 2.4GHz network selection, or issues with the 802.11b usage, with something having changed, but since I can't get at the router setup I can't be sure.

I also have a workaround which kinda also proves it's not an issue with the Sky Infrastructure itself (internal routing/blocking etc). The workaround is not ideal, although should work for me, and as is follows:

Through good fortune, I had an old TPLink RE220 Wifi Extender lying around. I have reconfigured it to work with my Sky Wifi. The extender creates new 2.4GHz and 5Ghz SSIDs to send traffic via the Sky Wifi. If I connect my AC devices to the TPLink 2.4GHz network name, they once again work.

I'm pretty sure that this conclusively shows that *something* Sky have pushed in late June 2025 has changed the router setups (SkyMax in my case) and broken my AC functionality. I would suspect it's also broken other (probably mostly older) IoT things too. 

Given the lack of router access with the SkyMax, unless Sky rollback the change they have pushed in a later update, or a subsequent update fixes the issue, everybody in my situation, using Sky Broadband is going to have problems, I would say. Hopefully the workaround discussed here will help some of them (I'm sure there's probably a better solution/workaround but I've spent a lot of time on this and am happy with the sub-optimal workaround I have).

[LolSky]

This is just an FYI for those that might run into the same issues I ran into this week. I'm essentially giving a previous discussion a better title so that people may find it more easily, and making it a bit clearer as to what's going on.

See Android devices have stopped connecting to wifi ov... | Sky Community for the full story but essentially, here's the potted version.

1. I have old (first gen) Intesis AC Units connecting to Sky via Wifi, allowing me to control my AC from a mobile app. This setup had been working fine for months (NB - I have Sky Shield disabled).
2. Early am 25 June 2025, all 4 of my units stopped working, being unable to connect to the Wifi. 
3. I tried many things to fix, and raised support calls with Sky and the AC Unit Vendor (both Support Teams were very helpful/tried their best).
4. I confirmed that the AC devices were still fine by connecting them to a Mobile hotspot rather than my Sky Wifi. With this change they worked fine (but still would not work with Sky Wifi).
5. Intesis Tech Support highlighted some requirements for the Units (see below), and indicated that ISP/Router Vendor pushed Router Updates might cause a problem. See below for details.
6. Sky Support could not resolve the issue but sent me a "new" router.
7. On 26 June, I setup the new Router, and once again, my AC Units all worked with the new Wifi. I presumed that the router might have been boxed for a while and subsequently get the same pushed updates.
8. Early am 27 June, all 4 AC devices were thrown off again, and wouldn't reconnect. I suspect the same update was pushed to my router.

So, to me, this looks *definitively* like Sky Router Updates going out in late June 2025 have borked some IoT setups.

Additionally, I'm pretty confident that this is is purely a router configuration issue, not something deeper in the Sky Infrastructure (routing/traffic blocking etc) because I have discovered a workaround that ultimately still uses Sky  (it's OK for me, but not ideal):

Workaround:

Through good fortune, I had an old TPLink RE220 Wifi Extender lying around. I reconfigured it to work with my Sky Wifi. The extender creates new 2.4GHz and 5Ghz SSIDs to send traffic via the Sky Wifi. If I connect my AC devices to the TPLink 2.4GHz network name, they once again work.

This really does suggest to me that it's purely a Router update that has caused the issue.

Anyway, that's it. I hope this topic/thread helps anybody out who is encountering the same issues. Good Luck All.

Intesis highlighted Network Requirements for my Units:

1. Check that the Wi-Fi signal strength is strong at the location where Intesis is installed.
2. Check the basic network configuration Intesis only supports 2.4GHz Wi-Fi.
   • 1st generation devices only support 802.1 b mode (MAC starts with 001D)
   • Other generations devices support 802.1 b/g/n
   • Maximum data rate (11 Mbps)
3. Check to have the output ports open: 
    
   • 80
   • 443
   • 4000
   • 4210 to 4259
   • 5210 to 5240

[JimM1]

@LolSky Any chance you can logon to the hub and have a look see what the current FW is and post it up!

[LolSky]

I don't think (or assumed) I have any sort of access to the Sky Max Router, other than the limited available tweaking through the MySky App.

Happy to jump on and look at settings through an admin terminal, if you know how I do it for the Sky Max Router(?).

[JimM1]

@LolSky Nope sky Max is just so locked down and mobile app controlled, pity!

[LolSky]

@JimM1 ... I kinda used to be a technical software tester (but haven't really been doing it for a couple of years). I probably don't want to take this on given my situation is "working" now, but ...

A way to check if the ports are firewalled out or unreachable (given no router access) would be to write/use a little socket listener/client program  (I used to have one of these I wrote in python, back in the day), set the listener up to listen to the ports and then try and hit'em from another device over the interweb (or maybe use something like nmap, or a web based checker - something like portchecker, - although I always used to kind of eschew these web services).

Another approach would be to get a different device to be configured to monitor the wifi traffic (interface needs to be in monitor mode), and then run tcpdump/wireshark (or similar) to see what's going on with the conversations (ahhhh ... I spent so many happy hours analyzing TCP traffic).

It sounds like you're kinda techy, so you might be able to have a run at that (or maybe, just maybe, somebody at Sky will give 'em a go if they get more people hitting issues).

I'd say it's 99% certain from my investigations to date that there definitely is a pushed update causing the problems, and it's likely "around" the things that are prerequisites for the Intesis devices (See above).

[JimM1]

@LolSky Been doing this for 45+ years, do not even have sky hanging on the connection anymore, and if need be i will laptop connect to the ONT to find out what is going on!

[LolSky]

@JimM1 - Sorry, this is kinda important.

Apparently using nmap is somewhat frowned upon (or worse), and I would highlight that my use of it was in internal networks only whilst working. I suspect this is when it's used in a port scanning mode.

Still, I don't see any real issue about firing up a listener on specific ports on your machines behind the router and then trying to hit 'em with something. telnet would do it.