[cheerful]

Hi,

Windows 10 Pro 64-bit
Kodi 16.1
NextPVT 3.9.2
OTA TV

I was unable to add a manual timer via Kodi on channel 2. I was able to do that on other channels.

An unexpected error occurred. Try again later or check the log for more information

In the log,

11:58:19 T:7596 ERROR: PVR - PVR::CPVRClient::AddTimer - addon '127.0.0.1:connected' returned an error: the command failed
11:58:19 T:7596 ERROR: PVR - PVR::CPVRClients::AddTimer - cannot add timer to client '924': the command failed

If I go to NextPVR application, I can add the manual timer.

What could be the problem? How can I fix it?

Thanks

[DarrenHill]

Thread moved to the NextPVR section.

[sub3]

Reproduce the problem, then zip and supply the NextPVR logs and we'll take a look.

[cheerful]

Yeah, it's reproducible. When can I find NextPVR logs?

[sub3]

c:\users\public\npvr\logs, or use the 'zip my log files and show me when the zip file is' button in NextPVR's Settings screen.

[cheerful]

2016-11-28 22:31:15.064 [DEBUG][132] Got Web Request (::ffff:127.0.0.1): /service method=recording.save&name=Jets&channel=7186&time_t=1480886736&duration=10500&pre_padding=0&post_padding=0&directory_id=Default&sid=094855041e0745fb9faf6c75c4446564
2016-11-28 22:31:15.064 [DEBUG][132] method=recording.save
2016-11-28 22:31:15.064 [DEBUG][132] parameters:
2016-11-28 22:31:15.064 [DEBUG][132] method: recording.save
2016-11-28 22:31:15.064 [DEBUG][132] name: Jets
2016-11-28 22:31:15.064 [DEBUG][132] channel: 7186
2016-11-28 22:31:15.064 [DEBUG][132] time_t: 1480886736
2016-11-28 22:31:15.064 [DEBUG][132] duration: 10500
2016-11-28 22:31:15.064 [DEBUG][132] pre_padding: 0
2016-11-28 22:31:15.064 [DEBUG][132] post_padding: 0
2016-11-28 22:31:15.064 [DEBUG][132] directory_id: Default
2016-11-28 22:31:15.064 [DEBUG][132] sid: 094855041e0745fb9faf6c75c4446564
2016-11-28 22:31:15.064 [DEBUG][132] client_ip: 127.0.0.1
2016-11-28 22:31:15.064 [DEBUG][132] host_callback: 127.0.0.1:8866
2016-11-28 22:31:15.064 [DEBUG][132] physical_path: C:\Users\Public\NPVR\web\
2016-11-28 22:31:15.064 [DEBUG][132] user_agent: Kodi/16.1 (Windows NT 10.0; WOW64) App_Bitness/32 Version/16.1-Git:20160424-c327c53
2016-11-28 22:31:15.064 [DEBUG][132] range: bytes=0-
2016-11-28 22:31:15.064 [DEBUG][132] requested_path: /service
2016-11-28 22:31:15.064 [DEBUG][132] verb: GET
2016-11-28 22:31:15.070 [DEBUG][132] Unable to find matching show ('Jets': 2016-12-04 16:25). Scheduling manual recording.
2016-11-28 22:31:15.076 [DEBUG][132] ScheduleRecording@1
2016-11-28 22:31:15.076 [DEBUG][132] [email protected]
2016-11-28 22:31:15.076 [DEBUG][132] [email protected]
2016-11-28 22:31:15.083 [DEBUG][132] CaptureSource.LoadAll()
2016-11-28 22:31:15.088 [DEBUG][132] [email protected]
2016-11-28 22:31:15.091 [DEBUG][132] Checking if multi-record possible...
2016-11-28 22:31:15.094 [DEBUG][132] [email protected]
2016-11-28 22:31:15.094 [DEBUG][132] [email protected]
2016-11-28 22:31:15.095 [DEBUG][132] ScheduleRecording@3
2016-11-28 22:31:15.095 [DEBUG][132] ScheduleRecording@6
2016-11-28 22:31:15.095 [DEBUG][132] no tuner available
2016-11-28 22:31:15.095 [DEBUG][132] <?xml version="1.0" encoding="utf-8" ?>
<rsp stat="fail">
<err code="7" msg="No tuner is available at the specified time." />
</rsp>

[cheerful]

Just to be clear.

Channel 2 is available. I can watch it on Kodi. I can schedule recording in NextPVR

I can also schedule recording via Kodi for other channels (like 4 or 5)

[sub3]

If you want to supply your log files, as requested above, I can check it out for you.

It'd be useful if you can also supply your npvr.db3.

[cheerful]

Do you need the entire log directory?

Where can I upload it to?

Thanks

[sub3]

Yes, the zipped set of logs will help, along with the npvr.db3.

Post the question on the NextPVR forums. It's easier to do attachments there.

[sub3]

It's saying you've got 'no tuner available at the specified time', so make sure you have enough tuners to accommodate the new recording request. ie, if you've only got a single tuner, make sure you don't have another recording that overlaps this one on a different channel.

Also make sure the time is set correctly on your client machine, so it's not asking for recordings in the past.

[cheerful]

First, I rebooted the box and now it's a lot better. Don't know why. Minor problem remains.

I have recurring recording starting at 19:20 with 15 min start padding.

I can schedule channel 2 up to 19:19 but not 19:20.

I have another recurring recording starting at 16:20 with 0 min start padding.

I can schedule channel 2 up to 16:20.

So the padding appears to have something to do with it.