Recurring Recording URL Parameters

[jcole998]

I've had good luck with using the URL web interface to schedule single events. I wish to expand my capability by scheduling a recurring event.

The GitHub code shows:

case TIMER_REPEATING_EPG:
XBMC->Log(LOG_DEBUG, "TIMER_REPEATING_EPG");
// build recurring recording request
snprintf(request, sizeof(request), "/service?method=recording.recurring.save&recurring_id=%d&event_id=%d&keep=%d&pre_padding=%d&post_padding=%d&day_mask=%s&directory_id=%s&only_new=%s",
timerinfo.iClientIndex,
timerinfo.iEpgUid,
(int)timerinfo.iMaxRecordings,
(int)timerinfo.iMarginStart,
(int)timerinfo.iMarginEnd,
days.c_str(),
m_recordingDirectories[timerinfo.iRecordingGroup].c_str(),
preventDuplicates
);
break;

This is straight forward but I don't know where to get "timerinfo.iClientIndex." I see it used as the &recurring_id parameter but where does the number come from? It seems to have been already established somewhere, but where? Can I get to it?

Thanks in advance.

[sub]

That code is being used to either create a new recurring recording, or update an existing one. ie, if recurring_id=0, or the parameter not specified at all, then it'll create a new recurring recording. If it's recurring_id=x, then it'll update recurring recording x.

[jcole998]

Thank you, sub.