Project

General

Profile

Bug #5693

Disabled Recordings added by Autorec get enabled again

Added by Flole Systems about 2 years ago.

Status:
New
Priority:
Normal
Assignee:
-
Category:
-
Target version:
-
Start date:
2019-07-26
Due date:
% Done:

0%

Estimated time:
Found in version:
4.3-1802~g6be300c43
Affected Versions:

Description

I have a few Autorec rules setup, sometimes they create entries that I don't want to record so I disable them (as deleting would simply add them again). Today I noticed that a few entries that I definitely disabled got recorded.

I checked the logs and found this which I think is a little bit odd:

Jul 24 02:04:09 tvheadend[7877]: dvr: entry 98298879e81079c060c454378de5d5b7 "xyzz" on "testChannel" starting at 2019-07-29 00:19:07, with broadcast id "<noid>", scheduled for recording by "xyz" 
Jul 24 23:28:57 tvheadend[7877]: dvr: entry 7e67b0cdad8460f8c053519e32c33815 "xyzz" on "testChannel" starting at 2019-07-29 00:19:07, with broadcast id "<noid>", scheduled for recording by "xyz" 

That's definitely the same event (same name, same channel, same time -> same event), why is it scheduled twice?

Maybe this is relatedSometimes something like this goes on, the same event is scheduled and later rescheduled, in this case I can understand that it does detect a new event (even though that should be covered by the EPG update window in my opinion). Also there is no deletion logged.....

Jul 19 02:08:19 tvheadend[43460]: dvr: entry 1ac4d27eda00f7ab45e341cd48b3144e "anotherProgram" on "anotherChannel" starting at 2019-07-25 19:22:59, with broadcast id "<noid>", scheduled for recording by "xyz" 
Jul 25 14:06:30 tvheadend[7877]: dvr: entry 4ec1525462af590b4c04bec1321ddb49 "anotherProgram" on "anotherChannel" starting at 2019-07-25 19:32:59, with broadcast id "<noid>", scheduled for recording by "xyz" 

Also available in: Atom PDF