Sky Q Formula One UHD Failed Recordings

This morning was the first live qualifying of Formula One available in Ultra HD on Sky Q, and it’s looking like it’s caused issues for lots of people.

There are reports on Twitter and Sky’s forums of numerous issues – “Part Recorded” or “Failed” for Qualifying this morning. Other people report green screens, artefacts and blocky pictures.

Let’s run down what I think went wrong.

Sunday 26th 04:30am BST (Race Show): Gulp. My box went into eco mode at 2:45am BST when it should have stayed awake in order to record the race show at 4:30am. Thankfully I manually woke up in time to start the Sky Q box and record again manually.

This likely means that many folk’s UHD recordings of the F1 Australian Grand Prix would have failed. Not sure if this bug is related to yesterday morning’s failures – I cancelled my race recording and rescheduled them yesterday, but maybe there is a bug with eco mode ignoring recording times, or maybe it’s a DST issue given the clocks changed.

Either way, it likely needs a software update to fix, and I doubt they’ll be able to get that through QA in time for China in 2 weeks.

Here’s the power profile (all times GMT)

Saturday 25th 11:30am (Qualifying): It looks like the most prevalent error is a ~30m partial recording of Practice 3, then Qualifying shows “Failed”. I found someone on twitter, (Thanks @crcaterham!) who had the issue and got the PVR data from the API. He says that P3’s status is “RECORDED” – this suggests the box actually thought the 30 minutes it recorded was the whole program. Then Qualifying has no error code and just shows “FAILED”.

This now looks to be related to the changes in scheduling Sky made this week. Potentially there’s a bug in the EPG where if the “schedule” is changed, it doesn’t update the start time, and so the recording fails.

If you setup your UHD recordings after Sky changed the formatting of the programmes earlier this week, or if you cancelled and re-setup the recordings after, you didn’t have this issue. Because of this, it’s probably wise to cancel your race recordings from Recordings > Scheduled, and re-configure them, otherwise your race recording might suffer from the same fate!

Continue reading “Sky Q Formula One UHD Failed Recordings”

Sky Q Missing Thumbnails

22nd March Edit: Version 4 of the EPG rolled out today to all users. This changes the way the data is loaded from UDP to TCP, and should fix this bug.

There’s a common ‘bug’ with Sky Q that results in people seeing empty blue squares where the thumbnails should be.

I’ve tried to help folks on Sky’s own forum with this issue, but my post got deleted – presumably because I was guiding people on how to get information from their boxes via the Q App API. Whoops.

Anyway, this issue comes about because while some of the Sky Q guide content is loaded over a nice sensible HTTP TCP connection, they use extensively use UDP (as discussed yesterday) to request and receive data for the guide panels, and this is inherently unreliable.
Continue reading “Sky Q Missing Thumbnails”

Sky Q UPnP, REST and WebSocket API interfaces

It’s been a few years since we got into digging around Sky+HD’s UPnP control protocol, but having recently updated to Sky Q, there are a few changes that break the way we were talking to the box.

Backwards Compatibility

The Sky Q box contains pretty much the same UPnP advertised control system as Sky+HD, and includes a couple of new endpoints (service nodes) to do things that don’t seem too interesting. A “Pairing” service node and a “BasicManagement” service node.

There is one potentially breaking change though. The SkyServe2 service node now provides the service type urn:schemas-nds-com:service:SkyPlay:2 as well as the SkyControl2 service node. If you register a listener, or make any calls against the SkyServe2 node, you won’t get any useful data. This means if you’re using a library like dalhundal/sky-plus-hd, you’ll need to skip over the response from SkyServe2, and just use SkyControl2 like before.
Continue reading “Sky Q UPnP, REST and WebSocket API interfaces”