I downgraded to 2.2.4 release and the issue i reported disappeared…
Ok, I’ll take a look and see if anything I added could be causing a problem.
How long does it take to go unavailable? I’ve been unable to replicate so far, and can’t see why the new code would cause it.
I really cannot answer this question as it happens randomly… Maybe when restarting HA often the media player goes unavailable or better i find it unavailable in developer/states. And i noticed if i reload many times the lovelace interface it comes again available. It doesn’t happen since i downgraded to 2.2.4.
I am sorry to not be so useful for you to trace this issue…
My wife has reported that our Sky Q Falcon box updated overnight. It has now crashed twice. I’m afraid this may be a really difficult one to diagnose.
Running queries against my box, I got a UPNP error - Internal Server Error 500. I suspect buggy Sky Q code 
My SkyQ was updated several days ago but only issue i have is what i reported already, no crashes, only with 2.3.0 goes unavailable for some time…
I’d be interested for you to try 2.3.0/1 again, because I really can’t see why it should make any difference.
ok, i’ll try again… is there a 2.3.1?
Yes if you have enabled betas. Minor change in it around channel sort order which should help Italians selecting channels in the gui.
1 Like
Do you remind me how to enable beta in HACS?
Select to reinstall sky q, then there is a toggle switch…
Thanks, done!
I am doing some monitoring against my box, and can see that there is some problem on the Sky Box. Why that would be caused by the queries I’m making to it I don’t know, but when I was playing a recording, port 9006 on the box started to fail to respond, so I’ve switched of the query that checks what recording is being played to see if that helps. I can see the Sky Go app also queries on that port for a list of recordings, so we can hope that the issue gets picked up by Sky and an update released. Firmware for my box is ‘Q120.002.13.00-AS_asdev:32B12D’, which you can find on the Device information page of HA Configuration.
Hi Roger
Just as FYI, I’m not seeing any stability issues with my boxes using your latest build.
Prob not using them all that much at the moment but no issues none the less when I am watching. Interestingly each of the boxes seem to have slightly different Firmware identifiers and all different to yours 
Main Q 2TB box is on Firmware: Q120.002.13.00-AS_asdev:32B057, with two Mini’s on Firmware: Q120.002.13.00-AS_asdev:32D001 and Firmware: Q120.002.13.00-AS_asdev:32D0AD
I think it may be triggered when watching recordings, but not every time
My mini is Q120.002.13.00-AS_asdev:32D001. Other other SkyQ I have is a different brand and is still on previous release Q112.xxxx
I tried also 2.3.1, but i am sorry to tell you the issue is again here… actually i have skyq box playing on the 105 italian channel, but in the frontend, like you can see in the screenshot, is off, just like the state of the media player in developer/states.
Only if i do a clear cache on my chrome i get again the media player in playing state…
My question is: maybe it depends from some problems with the lovelace frontend?
I will look again, but I really can’t see why the addition of volume controls would affect that. It would help if others were reporting the same issue.
I’m working on a version that significantly reduces the number of calls to the box. I had been calling to check what the recording was every time it is scanned, I’ve now changed that since it only checks what it knows what is being watched has changed.
Also I was previously checking power status, then checking what was being watched. You can actually get power status from the call to see what is being watched. So I’ve removed another call.
I’m testing these locally at the moment, to see if it removes the crashes.