Web API only_new Question

[Gazavant]

If I create a new recurring recording where only_new=false, I find I can update that recording to only_new=true by using something like this:

Code:

recording.recurring.save&recurring_id=158&type=4&pre_padding=1&post_padding=1&directory_id=Default&only_new=true

However, if want to change back to only_new=false by using the same statement with only_new set to false, the value remains set to true after applying the edit.  Other parameters can be changed, but once only_new is changed to true, it seems to be unchangable.

Is only_new a one-way street, or am I missing something here?

I should note that I can also create a new recurring recording with only_new set to true, and it works as expected.  It's only changing only_new back to false that I can't seem to manage.

Thanks.
 - Gaz

[mvallevand]

Sub can probably fix it but it is a rare type change so I ignore the issue in Kodi, but developers could simply delete and re-add or resubmit with &recurring_type=2

What are you developing that needs this specialization over just using the web scheduler in this instance?

Martin

[Gazavant]

Your input led me to find my problem's solution.  Thank you!

I had been using "type=4" instead of "recurring_type=4."  Now that I've corrected my code, "only_new=" now works for true or false. So there was no real problem, just my mistake (I think I used "type" because that's what the xml tag uses).

To answer your question -- I have no "need" for the "only_new" functionality.  It's really just my preference.  A few years back, I built an offline EPG viewer that suits my needs and preferences.  The app can also wake up and configure the npvr host after I've picked out the programs I want to record for the week.

The record interface was based on the NEWA app which gave you a checkbox to record only new programs.  I prefer that option to the recurring types available in the npvr web client mainly because recurring_type=1 doesn't offer enough flexibility.  Most of the time, I just want a particular new program on the day and time I want, and on the station I want.

I recently added the capability to edit recurring recordings, and that's when I discovered that only_new wasn't working completely right.

Now, thanks to your response, everything is working correctly.  And as an added bonus, Sub's latest update adds "enable" to the web API, and it works great right out of the box (though I still can't find the "enable" option in the web client's scheduler/recurring recording window).

Thanks again for your help and suggestions.

Gaz

[mvallevand]

Thanks I was trying to save you some work for a custom app since I figure toggling the state is rare and the web app can do it when needed. I didn't consider any offline aspect.

Martin

[sub]

though I still can't find the "enable" option in the web client's scheduler/recurring recording window

When you click on a recurring recording in Scheduler->Recurring, and the popup shows the recurring rules, the bottom one in the list is 'enabled/disabled'

[Gazavant]

Thanks, Sub.  I did see your earlier response to another poster with the same issue, so I'm pretty sure I've been looking in the right place.

Then I thought it might be a browser issue (I've been using Chrome), so I checked Edge and Firefox.  Sure enough, Enabled showed up in both.

So I went back to Chrome and tried a forced refresh, but that did nothing.  Then I tried deleting all cookies, and that did the trick.  I'm good to go now.

Thanks for pointing in the right direction.

[sub]

Ok, sounds the browser showing you a cached page.