Sky Stream constantly glitching

[MartinSkingley]

My stream puck glitches daily! We have UHD and that never-ever works without glitching. We've already been sent a new pick, which has been slightly better. Our Wi-Fi is 200MBPS and I can check this through Netflix that's we are constantly getting at least 100MBPS to the puck. All our other devices work absolutely fine without glitching it is just the Sky steam. The router has a direct view of the puck too through an open doorway! This is soooo annoying. I have followed all the online help. I am not going to keep resetting the router as I am almost 99% sure this isn't the issue, just Sky passing the blame. The TV is almost brand new and 4K so it's not that either. Ethernet is not an option as it's too far to run a cable - why promote Stream as a wireless streaming option if it can't support that properly?! I need help. 

[lettice]

Your speeds to the Puck, if as you say are stable at those speeds, suggesting a good wifi connection.

By glitching, can you explain more, what is exactly happening?

UHD can have some issues, if the hdmi cable used is not a Sky supplied one or not a high speed one.

Have you tried a different hdmi port on the TV? After swapping remove the puck and TV from the power for a few minutes before reconnecting.

Wondering  if you have some kind of TV Sports or motion option turned on, that may be causing this. It is usually a good idea to turn off all the motion options that the TV manufacturers add in settings.

[MartinSkingley]

Thank you for trying to help!

Every minute or so the picture will freeze for a split second before carrying on. It does stop for long but enough to be amazingly annoying. The sound isn't usually affect. And once a game on Sky Sports UHD, it will free completely and dispatch the 'Programme can't load...' before coming back to life. 

I haven't tried another HDMI connection yet. Might be worth it I guess. 

And I couldn't find any motion settings like that on my tele. 

[MartinSkingley]

The other HDMI cable was worse! Or at least it came up with 'Programme can't load...' again.