Posts by milo

Is TV headend 4.3(alpha) stable enough to work with? because this one is running

Hello,

I have an issue with my installation.

Tvheadend can not be started during start up the issue is

Quote

/storage/.kodi/addons/service.tvheadend42/bin/tvheadend: error while loading shared libraries: libx265.so.199: cannot open shared object file: No such file or directory

Any help appreciated

Was just a hint to the comment because of 19.5 released suddenly.

I was just wondering about the topic of 19.5. I realized in other projects if such a "upnormal" is coming in the releases sth. completely changing is implemented and this takes time. I just don't want to be surprised again therefore I asked.

So there will be tomorrow a libreelec with Kodi 19.5?

Hello,

I am wondering why is there no release of Kodi 19.5 when the kodi20 will be realead in Jan 23? What happened?

Quote from CvH

there is the "Boblight" addon at our repository that includes the daemon

just saying the modern alternative to it is Hyperion (we have too)

Yes I know but is my Karate light working with it?? How to configure?

Quote from blueribb

Do you mean this ?

Add-on:XBMC Boblight

Yes, but there is also the service for this and this must be included in the libreelec

blueribb

Hello i have a question is the boblight addon ported to libreelec V10???? I want to know this before I am upgrading.....

Any eta for the release?

Is the boblight plugin ported to libreelec10.1?

Any time schedule for releasing?

Any release date planned?

Quote from Jocke.Sve

As I read, one of my favorite add-ons isn't surviving Python 3 transition:

My Pictures DB

Sorry, where have sseenthis info which plugin survived the python 3 transition?. Am I stupid?

Is there a list which plugin is already "translated" and which is not possible to translate??

Quote from HiassofT

With ir-keytable you have to specify the rc device, "rc1" in the case above, using the "-s" option. eg ir-keytable -s rc1 ...

Note that the rc device numbers may change across reboots so always check with "ir-keytable" before.

In rc_maps.cfg you can match by driver name, that's the first entry. eg

Code

imon    *    my-keymap

That being said, using the nuvoton CIR would be a better choice (if it has an IR receiver connected) as it supports more protocols - the imon receiver is quite limited...

so long,

Hias

Display More

Hello,

Yeah the nuvoton CIR is behind the alumnium body therefore a little bit tricky unfortunately....

How do I change the protocol of the imon to rc6?

Hello,

if i use the command ir-keytable i see 2 devices

Found /sys/class/rc/rc1/ (/dev/input/event16) with:
        Name: iMON Remote (15c2:0036)
        Driver: imon, table: rc-imon-pad
        lirc device: /dev/lirc1
        Supported protocols: rc-6 imon
        Enabled protocols: imon
        bus: 3, vendor/product: 15c2:0036, version: 0x0003
        Repeat delay = 500 ms, repeat period = 125 ms
Found /sys/class/rc/rc0/ (/dev/input/event3) with:
        Name: Nuvoton w836x7hg Infrared Remote Transceiver
        Driver: nuvoton-cir, table: rc-rc6-mce
        lirc device: /dev/lirc0
        Supported protocols: lirc rc-5 rc-5-sz jvc sony nec sanyo mce_kbd rc-6 sharp xmp imon rc-mm
        Enabled protocols: lirc rc-6
        bus: 25, vendor/product: 1050:00c3, version: 0x0033
        Repeat delay = 500 ms, repeat period = 125 ms

How can I select the iMon Remote to use with ir-keytabel??

I tried

ir-keytable -v --device= /dev/lirc1

but got

Unable to query evdev protocol version: Inappropriate ioctl for device

how to use it correctly??

Solved

Thanks a lot 😄

Quote from HiassofT

No, that's not normal, lircd-uinput is missing in the process list. It should look like this:

Code

LibreELEC:~ # ps | grep lirc
  316 root      0:00 /usr/sbin/eventlircd -f --evmap=/etc/eventlircd.d --socket=/run/lirc/lircd
  448 root      0:00 /usr/sbin/lircd -O /storage/.config/lirc_options.conf --nodaemon /storage/.config/lircd.conf
  450 root      0:00 /usr/sbin/lircd-uinput -O /storage/.config/lirc_options.conf --add-release-events
  846 root      0:00 grep lirc

Post the output of systemctl status lircd-uinput and make sure you didn't mess around with lircd after reboot (i.e. no killall lircd or systemctl stop lircd, this will break lirc operations).

so long,

Hias

● lircd-uinput.service                                                       Loaded: masked (Reason: Unit lircd-uinput.service is masked.)             Active: inactive (dead)

 systemctl start lircd-uinput
Failed to start lircd-uinput.service: Unit lircd-uinput.service is masked.