Tvheadend4.2.4: PVRmanager starting up. 0%

Today, I installed osmc release 2018.2-1 on a Raspberry Pi 3.
I did install tvheadend from the osmc app store. I was able to configure tvheadend channel list.
After restarting osmc and entering the TV panel, I got “PVRmanager starting up. 0%” for hours.
ps -A shows the TVH process running. When killed, it is restarted autonatically.
Looking thru the log, I see that the TVH HTSP client is trying to connect to TVH but fails be cause of an authorization problem. This happens frequently.

I am not aware to have specified any user/password for the TVH HTSP client, nor do I know what TVH is expecting. I could not find where to specify this.

I must admit not beeing too familiar with kodi, therfore, any help would be greatly apreciated.

In the OSMC GUI goto

Settings->Add-ons -> Add-on-browser -> My add-ons -> PVR clients -> Tvheadend HTSP Client

and configure the user/password osmc/osmc in Connection Settings.
Activate also the flag Asynchronous EPG Transfer in the Advanced Settings.

Hope this helps a bit.

Thanks Jim, this really helped.

Hi Jim

What does the asynchronous EPG transfer do?

Should i always have it enabled?

Cheers

Unbenannt

In the past I’ve had issues with active timeshift and EPG updates; without asynchronous EPG Transfer active the effect was that the amount of EPG entries shrank from day to day. No idea whether this is meanwhile fixed or not.

It does not hurt. :wink:

1 Like

Jim, before I switched to TVH, I have been working with VDR instead and had similar experiences regarding drying up of EPG data. However, I am using the JSONRPC interface to get to EPG data. I did also get spurious JSON “Internal Error” messages and assumed that Kodi/VDR was suffering some form of IO errors or data corruption while accessing the EPG data. So I bought myself a new SD card, reinstalled OSMC and started using TVH. Up to now, I have not encountered EPG data dry up.
There are two smartfone/tablet apps, Kodi Remote and Kore, that also access EPG data using the JSONRPC interface. They recovered internally and simply show less program data.