[ksooo]

What also should be fixed is to separate between timers (planned recordings) and timer rules. Currently there is only timers, mixing rules and timers in one view, nothing a user can work with.

I was looking into this and did a first draft implementation (see PR#474). I am just puzzled that the API reports the timer rule twice, 1x with istimerrule=NO and 1x with istimerrule=YES. Therefore it shows up twice when I am not having any rule enabled. Is this how it should look like? Does one reflect the rule and the other just the next recording triggered by the rule?

Are you sure that the API reports the same entity twice? What makes you think this? The title? The title is not unique, the rule and the single timers it schedules might have the same title.

I think what you see is more that one item is the rule, the second actually a timer scheduled by the rule?