Is it connecting via Wi-Fi I assume?
Does your SSID have dual-band? Does the device support 5GHz etc.
What model AP, what firmware version are your APs running?
What do you have your minimum data rate set to on the Access-Control page?
Sky is professionally obnoxious.
It is not their policy to play nice with anybody else.
They remain totally indifferent to the need to integrate into an existing network.
They have an uncanny ability to identify and employ the installers from hell.
You think I am being harsh? Look at other manufacturers' forums and see the posts from users about difficulties integrating Sky devices into existing networks. Sky is not alone in this.
If you are doing anything vaguely sophisticated involving multicast IPTV, stick another brand security appliance ahead of the MX and route that traffic directly to the playout devices. As well as being reliable, it is more secure.
@uberseehandel
Hello,
I have Sky Q integrated into a full stack Meraki setup. I have 1 main box and 2 mini boxes.
Unfortunately you will not get this to work over WiFi if you have a mini box. I was able to successfully set the boxes to turn off their broadcast SSID and connect to my MR52s. The problem (as I understand it), is that the traffic from the main box to the mini boxes is still transmitted over its own mesh and not over the WiFi connected to the APs. Very frustrating when I have such a robust WiFi set up.
I had to set everything wired, and it does work flawlessly. I have a number of switches between the boxes and the MX. In order to get the iPads etc to stream, I had to set the following on the switches:
Hope this helps.
Chris
Unfortunately, for many networks, IGMP Snooping is required. Having to turn it off to make the Sky boxes function is a perfect illustration of not playing nice, as I mentioned above.
@uberseehandel
As the move to smart devices has gathered pace, there have been a surprising number of unintended consequences, some of which are not so unexpected when the commercial origins of many of the "smart" device vendors is considered.
One these unintended but not unexpected consequences results from the reasonable attempts by electronic goods vendors to improve energy efficiency whilst maintaining usability. So TVs and audio systems often enter a "sleep" period during the night. It is more complex that it might appear at first sight, there is sleep, light sleep, deep sleep and then, ultimately, turn the power off. To add to the complication, many devices also have some form of Wake-on-LAN capability, or send a packet indicating that they are available.
Currently, some Chromecast capable audio devices from Sony appear to go up and down several times each night, as far as error reporting is concerned. Meraki doesn't feel a need to do anything about this, nor does Sony.
Sky devices show similar behavioural characteristics, and some switches don't handle it very well. Problems disappear when the sleep function is reconfigured. In extremis, turn off the Sky kit.
Network manufacturers need to get together with the smart device vendors and explain how to play nice, and, incidentally, stop cheaping out on Wi-Fi components.
@uberseehandel
Hi All, i has the exact same issue with my MR 33, i created a new SSID calling it (SKYwifi) created it really simple no levels of extra security enabling both radio frequencies all that jazz.
I got them working and talking to each other however each morning id come down to find both boxes had disconnected from the network and the sky mini box not working. After a few days of getting fed up reseting the internet details and running between rooms. I decided to run a few cables. However i have now seen something interesting on the reporting and now i have a new annoyance !
Each morning i wake up to 4/5 emails telling my both ports on the internet went down and came back up.
Anyone know how to remove notification for an individual switch port? not looked that hard yet but couldnt see anything that stood out.
Not infrequently modern domestic A/V equipment and equipment supplied by non-network companies have strange interactions with network hardware.
I frequently have issues with UPnP and the way the problematic hardware sleeps. So it might sleep, or deep sleep or be hard off, aka the Micky Flanagan effect. These are adjusted in the standby settings.
With any luck, if you configure one of out, out out, or, out out out then one of these options will reduce the number of messages.
Practically, I deal with this by saving all the alerts in a directory which is self-clearing after 30 days.
@uberseehandel
You should be able to tag the ports and then choose the tag to get an alert for.
So tag all the ports except port 9 as "port notify" and then on the alerts pages choose this (I've tagged certain ports for cameras):
