Posts by dickh

Cron works for me using the command line. I set it to reboot at 4am this morning and it seems to have re-booted - unfortunately, although TVHeadend is working locally on the box in question, the http configuration interface is not available and also the htsp service is not visible externally. This time however SSH and ping are working fine, so clearly not all IP requests are being disabled... So in my case at least, a scheduled reboot isn't solving the original problem

I'm also still having problems with my Montage adapter though - enabling different drivers has solved the scanning problem but it refuses to recognise any DVB-S2 channels - i.e. most of the HD channels.

This seems a lot of hassle for very little gain so I think I'm just going to roll-back to 8.2.5 until Leia stabilises

I have also recently updated my system to 9.01 from 8.2.5 and I am seeing something similar. After about 2 days, my Pi 3+ which runs TVHeadend serving the other 3 RPis (mixture of v2, v3 and zero) stops accepting incoming ethernet connections and needs to be rebooted. On its own, on the Rpi3+, both server and client of TVH are still working, and outgoing connections to the NAS for media, recordings and MySQL are working happily. Externally however, I can no longer connect to the Pi3+ server with htsp, http, ftp, SSH, or ping,

Separately I am just now exploring a problem where the TVHeadend will no longer scan my Montage DVB-S adapter. After the upgrade, all of the previous channels were still accessible but gradually channels are becoming unavailable. On a test box, the initial scan comes up with FAIL for all multiplexes.

Just to round off this topic. After running for a day or two with the mixed configuration I noticed that there was still a problem with the remote - after leaving the box for some hours, it would take maybe 20 presses of the remote before it became responsive again. So I have now switched completely to ir-keytable and it seems to be working fine.

It's a shame that the list of available config files for ir-keytable is so much shorter than the one for lirc since they essentially contain the same information. Unfortunately for some reason lirc used the remote binary codes inverted so you need to do some manipulation to create the file for ir-keytable.

DickH

At the moment still Lirc.

Thanks Hias.

I found my embedded adapter actually only supports RC5 whereas I have 'standardised' on a Philips BluRay remote using RC6. In any case, after following your linked instructions for LE9 I found that changing the RPi overlay to dtoverlay=gpio-ir allowed the GPIO receiver to perform quite acceptably again. So for the moment I will stick with that solution.

Thanks again

DickH

Thanks for that. As you say, IR over GPIO must incur quite a large interrupt overhead so there is significant potential for conflict with other devices. It's unfortunate though that recent kernel changes seem to have exacerbated the issue.

Your point about alternative IR receivers however looks potentially useful. A bit of digging shows that the receiver in the DVB-S unit is indeed being recognised by lirc, and removing the GPIO receiver leaves just one entry in /sys/classes/rc. It now looks like I need to do a bit more work to configure lirc to use this however as I am getting no response with the default configuration. Do you have any pointers for using alternative input devices with lirc under Libreelec?

DH

About 2 years ago I built a small PVR based on a Raspberry Pi + Libreelec + TVHeadend Server/Client with 2 RTL2832 DVB-T adapters. To control KODI and the TVHeadend client I configured an infrared remote using lirc and a receiver connected to the default GPIO pins.

Until a few months ago, this configuration worked fantastically well however I then started to get intermittent glitches on the remote control. This became worse after upgrading to Libreelec 8.2.x and so I dropped back to the final 8.0 version. I am currently trying to upgrade the RPi to a 3B+ which requires LE 8.2.5. With two DVB adapters installed, the remote is now completely inoperative. With one adapter installed, it is initially very laggy and then often locks up.

The problem seems to be independent of whether the adapters are actually receiving a signal or not and the CPU is showing only a few percent. Interestingly, a Montage DVB-S2 adapter does not seem to cause the same effect, although it is hard to tell if it is actually non-existent or just very much less pronounced.

The basic PVR function seems to be unaffected and it happily records and feeds TV to the 3 other clients in the house but I cannot now use the same remote for this server box.

Any suggestions?