0

This discussion topic is read only Discussion topic: Complex Sky Q Home Network Issue - Using Netgear switches

Reply
This message was authored by: Adamr2506890601

Complex Sky Q Home Network Issue - Using Netgear switches

Hi guys, slightly complex issue, but nothing technically out of the ordinary..

I have recently moved house and decided to setup a wired network around the home, to combat any wifi drop outs that I was recieving from using the Sky Q Minis before. Plus, wired is just nicer and it was a nice project! 

So.. back to the issue... The signal path is..

Router > Unmanaged Mini Netgear Switch 
Netgear switch has 2TB Main Q Box, Q mini, Hue lighting Bridge, office Imac, CCTV NVR and Raspberry Pi all connected to it. 

This set up worked absolutely perfect. Plugged and played. Everything into the switch, no issues. Worked flawlessly with no setup, for 5 months.

I then decided to change this to a more permanent setup. Putting the network into a wall mounted rack box, with a rack mounted Netgear switch, with more available ports, for future expansion.

 

So, technically, completely the same setup.. all the same devices, just with a new Netgear switch on unmanaged factory settings.

However, once it was all setup and plugged in, my HUE Lighting Bridge was no longer able to be accessed by my phone app, and I could no longer access the new switches' config panel using its IP address on a browser. BUT, I could still ping both devices successfully. They were present on "attached devices" on the router config etc.

After hours and hours of process of elimination, it turned out that as soon as I disconnect the SKY Q 2TB box and Q Mini box, I could then access HUE again, and the new switches' config panel using its IP address on a browser.

After even more hours, I decided to create a bodge up job, and it has actually worked. But I just want to know if I can fix the issue, rather than use a work around..

Basically.. to fix the issue.. I have wired the path as follows..

Router > Old unmanaged switch (the switch that it all worked fine on in the first place)
SKY Q products connected to this switch.
Patch cable running from this switch, to the New rackmounted Netgear switch
All other devices plugged into the New rackmounted switch.

If anyone has ANY ideas on what the issue could be, or how on earth I could possibly fix the issue, I would be incredibly appreciative.

 

Tried all devices on DHCP and static IPs
Tried different ports on the switches
Tried resetting the new netgear switch multiple times

All Wifi on the Q boxes is turned off
Both Q boxes rebooted

Thank you very much 🙂

 

 

Locked

This discussion has been locked

Sorry, you can't reply to this discussion as it's been locked by our Community Managers.

Reply

All Replies

This message was authored by: Rhonny

Re: Complex Sky Q Home Network Issue - Using Netgear switches

@Adamr2506890601

Even though your Sky box wifi is turned off, try changing the box's 5ghz channel. I had issues with the main Sky box interfering with my wifi and other devices, even though I had the box's wifi turned off. I changed the box 5ghz channel to 44, and everything was cured.

 

Maybe there is since residual 5ghz frequency interference.

 

Go down to Settings but don't press Select. Instead type 0 0 1 Select to open the hidden menu. From there you can change the 5ghz channel. If it's 36, change it to 44, and press Confirm.

 

See if that helps. Worth a try... 

Avatar for Adamr2506890601
Level 1 icon
Topic Author
This message was authored by: Adamr2506890601

Re: Complex Sky Q Home Network Issue - Using Netgear switches

Thank you! Anything is worth a try! I'll report back 🙂

This message was authored by: bob1234

Re: Complex Sky Q Home Network Issue - Using Netgear switches

Posted by a Superuser, not a Sky employee. Find out more

@Adamr2506890601Even though you have changed the settings on your managed switch they sometimes still don't play nicely with Q, I would be tempted to go back to an unmanaged switch.

Locked

This discussion has been locked

Sorry, you can't reply to this discussion as it's been locked by our Community Managers.

Reply