-
-
Notifications
You must be signed in to change notification settings - Fork 17
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[BUG] Schedule date/time shows 0 #138
Comments
Sorry not sure what you mean by clear it. In any case can you run this against your box and post the response (which may be long), or at least the first instance of an item that shows as a Status of
|
Cropped results below, it's a failed download that was causing the erroneous next scheduled time. Once that was cancelled my next scheduled recording has changed to 7pm (1673550000) for 'House of games'
|
Looks like I need to exclude items that have failed downloading. I imagine that deleting that item and then making sure it is removed from the deleted items should clear it. |
@toddstar just got a chance to look at this. To be honest from the extract you provided I can't see why you got that error because I filter for SCHEDULED and RECORDING, and that one shows as DOWNLOADING. Do you still have the problem, and if so can you check if there is another instance of the program that shows as SCHEDULED? |
I deleted that failed download which cleared the error however do have
another download that is stuck at 0% but my template sensor for 'time to
next recording' is correctly showing 330mins at the minute. Will test with
cancelling some of my scheduled recordings to see if I can get it to show
again.
(Also may actually still have the full json response, will check my PC
later)
…--
Michael
On Tue, 17 Jan 2023, 12:09 RogerSelwyn, ***@***.***> wrote:
@toddstar <https://github.com/toddstar> just got a chance to look at
this. To be honest from the extract you provided I can't see why you got
that error because I filter for SCHEDULED and RECORDING, and that one shows
as DOWNLOADING.
Do you still have the problem, and if so can you check if there is another
instance of the program that shows as SCHEDULED?
—
Reply to this email directly, view it on GitHub
<#138 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AFMHV4GMJRB6PJVTQPMXZ3TWS2DV3ANCNFSM6AAAAAATZL5KXQ>
.
You are receiving this because you were mentioned.Message ID:
***@***.***
com>
|
I've found the issue. (altho not sure what happened with first set of data*) Downloads that haven't started yet, or indeed go from failed to back into the download queue, also have the SCHEDULED status so these can be picked up as next recording. e.g.
tried to download the same show that failed before
'Deadline Day: Football' has now gone from downloading to scheduled and is now showing as my next recording deleting these go back to the correct show (was also able to get similar results but just downloading two large movies, the next scheduled is the second movie waiting to be downloaded) so think easiest check is just to make sure "st" isn't null *only think I noticed from the actual sky box is the failed download seem to rapidly try restart so assume swaps between schedule and downloading quickly but this seem to stop after 5/10 seconds so may just have been luck / unlucky to get downloading state. |
Maybe be easier to check src and ignore items with VOD. |
Is your feature request related to a problem? Please describe.
Somehow my sky box is reporting that my next scheduled recording is Unix time 0
And short of factory resetting my box I can't see how to clear it; I've got zero actual scheduled recordings for that show, been through the TV guide to find all the times it's on and done a series link and unlink but still isn't clearing it.
Describe the solution you'd like
Assuming you get an array of next recordings (rather than just a single result) can you add a check so that scheduled end time must be equal or greater than now() and any that are older are ignored and it moves onto checking & listing the next recording where end time is greater than now()
Describe alternatives you've considered
Think now() should be fine but could go extra safe by just doing a date check and have anything that ended yesterday be ignored
P.S.
If anyone has any ideas for how to clear it on the sky box I'd be extremely grateful (although think it'd still be a worth while update to the code)
The text was updated successfully, but these errors were encountered: