Login at Kodi Home

nikto · (This post was last modified: 2017-02-12, 13:53 by nikto.)

Hy, I have Lubuntu 16.04, Kodi 16.1 and a Konig HID MCE remote.
The remote works perfectly inside Kodi but I would like to start Kodi by pressing the green "start" button normally used to start Windows Media Center in Windows.
I read a lot of discussion about that, but I could not figure out how to do that with my remote because of of my lack of experience with Linux and my bad english...
I'm tryng to follow this guide:
http://kodi.wiki/view/HOW-TO:Setup_Lirc

First of my problems is to identify my remote to complete the firts step:

Quote:You have downloaded and installed Lirc and are now ready to set it up. First, check if your IR receiver is already preconfigured. Ubuntu stores the configuration files in '/usr/share/lirc/remotes but you can also find them in the source tree in the remotes directory. If you can find you remote, copy the config file to /etc/lirc/lircd.conf and open the file with a text editor. Delete the lines between begin codes and end codes.

I can not find anything with "konig name" but someone as told me to do the terminal comand "cat /proc/bus/input/devices" and in my opinion I think my remote is identified by these two items:

Code:
I: Bus=0003 Vendor=1241 Product=e000 Version=0110

N: Name="HOLTEK     PC receiver "

P: Phys=usb-0000:00:1d.3-1/input0

S: Sysfs=/devices/pci0000:00/0000:00:1d.3/usb4/4-1/4-1:1.0/0003:1241:E000.0001/input/input5

U: Uniq=

H: Handlers=sysrq kbd event3 leds

B: PROP=0

B: EV=120013

B: KEY=10000 7 ff800000 7ff febeffdf ffefffff ffffffff fffffffe

B: MSC=10

B: LED=1f

I: Bus=0003 Vendor=1241 Product=e000 Version=0110

N: Name="HOLTEK     PC receiver "

P: Phys=usb-0000:00:1d.3-1/input1

S: Sysfs=/devices/pci0000:00/0000:00:1d.3/usb4/4-1/4-1:1.1/0003:1241:E000.0002/input/input6

U: Uniq=

H: Handlers=kbd mouse0 event4

B: PROP=0

B: EV=1f

B: KEY=3007f 0 0 0 0 4c3ffff 17aff32d bf544446 0 0 1f0001 130c13 b17c000 267bfa d951dfed 9e1680 4400 0 10000002

B: REL=143

B: ABS=7f01 0

B: MSC=10

So I am convinced my remote name for Linux is HOLTEK PC receiver.... And I found a "Holtek" lircd.conf file in this database http://lirc.sourceforge.net/remotes/ and so I used it fot the configuration. But I don't know if I'm right....

Carrying on... my second problem is when the guid says:

Code:
root@computer:/etc/lirc# irrecord --driver=irman --device=/dev/ttyS0 MyRemote ## use the driver that you chose in the previous part. /dev/ttyS0 = first com port

I don't know what to insert because I don't understand how to find my remote device=/dev/ttyX path.
How can I find it? In the "cat /proc/bus/input/devices" I can't find something like evice=/dev/tty.....
Can someone help me? Thanks

p.s. The remote is a Konig CMP-MEDIAREM12

graysky · 2017-02-12, 13:45

You'll need to map the button to a script you write to launch kodi.

nikto · 2017-02-12, 13:51

Thank you very much but I have no idea what that means. As I said I'am not a computer technician ...
But if you explain to me what I should do ... or if you link to me a guide where this step is explained step by step and understandable even for a normal person I can do it

3dfx · 2017-02-12, 14:16

Maybe this how-to could help you pinning the name under /dev of your device.
Also a look in the folder '/usr/share/lirc/remotes' on your filesystem could help you, there are lircd configs for many remotes. You need to find the one that is fitting yours.

After that you have to check your 'lircd.conf' in '/etc/lirc' so it point to the correct config file of your remote.
Myne points to (as I have an MCE remote):

Code:
include "/usr/share/lirc/remotes/mceusb/lircd.conf.mceusb"

I am doing something similar what you are trying to do...
When my system boots up, I run via '/etc/rc.local' (insert line before 'exit 0' in rc.local):
You can put your config-file where you want.

Code:
sudo irexec -d /var/spool/myScripts/conf/.lircrc >/dev/null 2>&1 &

In '/var/spool/myScripts/conf/.lircrc', I have this (you need to replace OK with 'green' or whatever):

Code:
begin

   prog   = irexec

   button = OK

   config = /sbin/xstarter &

   repeat = 0

end

begin

   prog   = irexec

   button = KEY_OK

   config = /sbin/xstarter &

   repeat = 0

end

And at last '/sbin/xstarter' is this (xstart is my upstart script for kodi...):

Code:
#!/bin/bash

if [ $(ps -A | grep kodi | wc -l) -eq 0 ]; then

    xstart 1 > /dev/null 2>&1 &

fi

Maybe this helps.

nikto · (This post was last modified: 2017-02-12, 16:28 by nikto.)

3dfx thank you very mutch for the help.

(2017-02-12, 14:16)3dfx Wrote: Maybe this how-to could help you pinning the name under /dev of your device.

Yes but I have 2 items in cat /proc/bus/input/devices. Event3 and Event 4...
If I use the event3 I get:

Code:
franz@ZAVAGLIO-PC:~$ udevadm info -a -p $(udevadm info -q path -n /dev/input/event3)

Udevadm info starts with the device specified by the devpath and then

walks up the chain of parent devices. It prints for every device

found, all possible attributes in the udev rules key format.

A rule to match, can be composed by the attributes of the device

and the attributes from one single parent device.

  looking at device '/devices/pci0000:00/0000:00:1d.3/usb4/4-1/4-1:1.0/0003:1241:E000.0001/input/input5/event3':

    KERNEL=="event3"

    SUBSYSTEM=="input"

    DRIVER==""

  looking at parent device '/devices/pci0000:00/0000:00:1d.3/usb4/4-1/4-1:1.0/0003:1241:E000.0001/input/input5':

    KERNELS=="input5"

    SUBSYSTEMS=="input"

    DRIVERS==""

    ATTRS{name}=="HOLTEK     PC receiver "

    ATTRS{phys}=="usb-0000:00:1d.3-1/input0"

    ATTRS{properties}=="0"

    ATTRS{uniq}==""

  looking at parent device '/devices/pci0000:00/0000:00:1d.3/usb4/4-1/4-1:1.0/0003:1241:E000.0001':

    KERNELS=="0003:1241:E000.0001"

    SUBSYSTEMS=="hid"

    DRIVERS=="hid-generic"

    ATTRS{country}=="00"

  looking at parent device '/devices/pci0000:00/0000:00:1d.3/usb4/4-1/4-1:1.0':

    KERNELS=="4-1:1.0"

    SUBSYSTEMS=="usb"

    DRIVERS=="usbhid"

    ATTRS{authorized}=="1"

    ATTRS{bAlternateSetting}==" 0"

    ATTRS{bInterfaceClass}=="03"

    ATTRS{bInterfaceNumber}=="00"

    ATTRS{bInterfaceProtocol}=="01"

    ATTRS{bInterfaceSubClass}=="01"

    ATTRS{bNumEndpoints}=="01"

    ATTRS{supports_autosuspend}=="1"

  looking at parent device '/devices/pci0000:00/0000:00:1d.3/usb4/4-1':

    KERNELS=="4-1"

    SUBSYSTEMS=="usb"

    DRIVERS=="usb"

    ATTRS{authorized}=="1"

    ATTRS{avoid_reset_quirk}=="0"

    ATTRS{bConfigurationValue}=="1"

    ATTRS{bDeviceClass}=="00"

    ATTRS{bDeviceProtocol}=="00"

    ATTRS{bDeviceSubClass}=="00"

    ATTRS{bMaxPacketSize0}=="8"

    ATTRS{bMaxPower}=="100mA"

    ATTRS{bNumConfigurations}=="1"

    ATTRS{bNumInterfaces}==" 2"

    ATTRS{bcdDevice}=="235a"

    ATTRS{bmAttributes}=="a0"

    ATTRS{busnum}=="4"

    ATTRS{configuration}==""

    ATTRS{devnum}=="2"

    ATTRS{devpath}=="1"

    ATTRS{idProduct}=="e000"

    ATTRS{idVendor}=="1241"

    ATTRS{ltm_capable}=="no"

    ATTRS{manufacturer}=="HOLTEK"

    ATTRS{maxchild}=="0"

    ATTRS{product}=="    PC receiver "

    ATTRS{quirks}=="0x0"

    ATTRS{removable}=="unknown"

    ATTRS{speed}=="1.5"

    ATTRS{urbnum}=="17"

    ATTRS{version}==" 1.10"

  looking at parent device '/devices/pci0000:00/0000:00:1d.3/usb4':

    KERNELS=="usb4"

    SUBSYSTEMS=="usb"

    DRIVERS=="usb"

    ATTRS{authorized}=="1"

    ATTRS{authorized_default}=="1"

    ATTRS{avoid_reset_quirk}=="0"

    ATTRS{bConfigurationValue}=="1"

    ATTRS{bDeviceClass}=="09"

    ATTRS{bDeviceProtocol}=="00"

    ATTRS{bDeviceSubClass}=="00"

    ATTRS{bMaxPacketSize0}=="64"

    ATTRS{bMaxPower}=="0mA"

    ATTRS{bNumConfigurations}=="1"

    ATTRS{bNumInterfaces}==" 1"

    ATTRS{bcdDevice}=="0404"

    ATTRS{bmAttributes}=="e0"

    ATTRS{busnum}=="4"

    ATTRS{configuration}==""

    ATTRS{devnum}=="1"

    ATTRS{devpath}=="0"

    ATTRS{idProduct}=="0001"

    ATTRS{idVendor}=="1d6b"

    ATTRS{interface_authorized_default}=="1"

    ATTRS{ltm_capable}=="no"

    ATTRS{manufacturer}=="Linux 4.4.0-62-generic uhci_hcd"

    ATTRS{maxchild}=="2"

    ATTRS{product}=="UHCI Host Controller"

    ATTRS{quirks}=="0x0"

    ATTRS{removable}=="unknown"

    ATTRS{serial}=="0000:00:1d.3"

    ATTRS{speed}=="12"

    ATTRS{urbnum}=="25"

    ATTRS{version}==" 1.10"

  looking at parent device '/devices/pci0000:00/0000:00:1d.3':

    KERNELS=="0000:00:1d.3"

    SUBSYSTEMS=="pci"

    DRIVERS=="uhci_hcd"

    ATTRS{broken_parity_status}=="0"

    ATTRS{class}=="0x0c0300"

    ATTRS{consistent_dma_mask_bits}=="32"

    ATTRS{d3cold_allowed}=="0"

    ATTRS{device}=="0x27cb"

    ATTRS{dma_mask_bits}=="32"

    ATTRS{driver_override}=="(null)"

    ATTRS{enable}=="1"

    ATTRS{irq}=="16"

    ATTRS{local_cpulist}=="0-3"

    ATTRS{local_cpus}=="f"

    ATTRS{msi_bus}=="1"

    ATTRS{subsystem_device}=="0x2651"

    ATTRS{subsystem_vendor}=="0x1019"

    ATTRS{vendor}=="0x8086"

  looking at parent device '/devices/pci0000:00':

    KERNELS=="pci0000:00"

    SUBSYSTEMS==""

    DRIVERS==""

franz@ZAVAGLIO-PC:~$

If I use event4 I get:

Code:
franz@ZAVAGLIO-PC:~$ udevadm info -a -p $(udevadm info -q path -n /dev/input/event4)

Udevadm info starts with the device specified by the devpath and then

walks up the chain of parent devices. It prints for every device

found, all possible attributes in the udev rules key format.

A rule to match, can be composed by the attributes of the device

and the attributes from one single parent device.

  looking at device '/devices/pci0000:00/0000:00:1d.3/usb4/4-1/4-1:1.1/0003:1241:E000.0002/input/input6/event4':

    KERNEL=="event4"

    SUBSYSTEM=="input"

    DRIVER==""

  looking at parent device '/devices/pci0000:00/0000:00:1d.3/usb4/4-1/4-1:1.1/0003:1241:E000.0002/input/input6':

    KERNELS=="input6"

    SUBSYSTEMS=="input"

    DRIVERS==""

    ATTRS{name}=="HOLTEK     PC receiver "

    ATTRS{phys}=="usb-0000:00:1d.3-1/input1"

    ATTRS{properties}=="0"

    ATTRS{uniq}==""

  looking at parent device '/devices/pci0000:00/0000:00:1d.3/usb4/4-1/4-1:1.1/0003:1241:E000.0002':

    KERNELS=="0003:1241:E000.0002"

    SUBSYSTEMS=="hid"

    DRIVERS=="hid-generic"

    ATTRS{country}=="00"

  looking at parent device '/devices/pci0000:00/0000:00:1d.3/usb4/4-1/4-1:1.1':

    KERNELS=="4-1:1.1"

    SUBSYSTEMS=="usb"

    DRIVERS=="usbhid"

    ATTRS{authorized}=="1"

    ATTRS{bAlternateSetting}==" 0"

    ATTRS{bInterfaceClass}=="03"

    ATTRS{bInterfaceNumber}=="01"

    ATTRS{bInterfaceProtocol}=="02"

    ATTRS{bInterfaceSubClass}=="01"

    ATTRS{bNumEndpoints}=="01"

    ATTRS{supports_autosuspend}=="1"

  looking at parent device '/devices/pci0000:00/0000:00:1d.3/usb4/4-1':

    KERNELS=="4-1"

    SUBSYSTEMS=="usb"

    DRIVERS=="usb"

    ATTRS{authorized}=="1"

    ATTRS{avoid_reset_quirk}=="0"

    ATTRS{bConfigurationValue}=="1"

    ATTRS{bDeviceClass}=="00"

    ATTRS{bDeviceProtocol}=="00"

    ATTRS{bDeviceSubClass}=="00"

    ATTRS{bMaxPacketSize0}=="8"

    ATTRS{bMaxPower}=="100mA"

    ATTRS{bNumConfigurations}=="1"

    ATTRS{bNumInterfaces}==" 2"

    ATTRS{bcdDevice}=="235a"

    ATTRS{bmAttributes}=="a0"

    ATTRS{busnum}=="4"

    ATTRS{configuration}==""

    ATTRS{devnum}=="2"

    ATTRS{devpath}=="1"

    ATTRS{idProduct}=="e000"

    ATTRS{idVendor}=="1241"

    ATTRS{ltm_capable}=="no"

    ATTRS{manufacturer}=="HOLTEK"

    ATTRS{maxchild}=="0"

    ATTRS{product}=="    PC receiver "

    ATTRS{quirks}=="0x0"

    ATTRS{removable}=="unknown"

    ATTRS{speed}=="1.5"

    ATTRS{urbnum}=="17"

    ATTRS{version}==" 1.10"

  looking at parent device '/devices/pci0000:00/0000:00:1d.3/usb4':

    KERNELS=="usb4"

    SUBSYSTEMS=="usb"

    DRIVERS=="usb"

    ATTRS{authorized}=="1"

    ATTRS{authorized_default}=="1"

    ATTRS{avoid_reset_quirk}=="0"

    ATTRS{bConfigurationValue}=="1"

    ATTRS{bDeviceClass}=="09"

    ATTRS{bDeviceProtocol}=="00"

    ATTRS{bDeviceSubClass}=="00"

    ATTRS{bMaxPacketSize0}=="64"

    ATTRS{bMaxPower}=="0mA"

    ATTRS{bNumConfigurations}=="1"

    ATTRS{bNumInterfaces}==" 1"

    ATTRS{bcdDevice}=="0404"

    ATTRS{bmAttributes}=="e0"

    ATTRS{busnum}=="4"

    ATTRS{configuration}==""

    ATTRS{devnum}=="1"

    ATTRS{devpath}=="0"

    ATTRS{idProduct}=="0001"

    ATTRS{idVendor}=="1d6b"

    ATTRS{interface_authorized_default}=="1"

    ATTRS{ltm_capable}=="no"

    ATTRS{manufacturer}=="Linux 4.4.0-62-generic uhci_hcd"

    ATTRS{maxchild}=="2"

    ATTRS{product}=="UHCI Host Controller"

    ATTRS{quirks}=="0x0"

    ATTRS{removable}=="unknown"

    ATTRS{serial}=="0000:00:1d.3"

    ATTRS{speed}=="12"

    ATTRS{urbnum}=="25"

    ATTRS{version}==" 1.10"

  looking at parent device '/devices/pci0000:00/0000:00:1d.3':

    KERNELS=="0000:00:1d.3"

    SUBSYSTEMS=="pci"

    DRIVERS=="uhci_hcd"

    ATTRS{broken_parity_status}=="0"

    ATTRS{class}=="0x0c0300"

    ATTRS{consistent_dma_mask_bits}=="32"

    ATTRS{d3cold_allowed}=="0"

    ATTRS{device}=="0x27cb"

    ATTRS{dma_mask_bits}=="32"

    ATTRS{driver_override}=="(null)"

    ATTRS{enable}=="1"

    ATTRS{irq}=="16"

    ATTRS{local_cpulist}=="0-3"

    ATTRS{local_cpus}=="f"

    ATTRS{msi_bus}=="1"

    ATTRS{subsystem_device}=="0x2651"

    ATTRS{subsystem_vendor}=="0x1019"

    ATTRS{vendor}=="0x8086"

  looking at parent device '/devices/pci0000:00':

    KERNELS=="pci0000:00"

    SUBSYSTEMS==""

    DRIVERS==""

franz@ZAVAGLIO-PC:~$

And I have no idea of how to compile this:
"echo 'KERNEL=="event*",ATTRS{id}==" Huh

",SYMLINK=" Huh

"' > /etc/udev/rules.d/10-persistent-ir.rules

Before continuing with the rest you have written to me I need to understand that...

3dfx · (This post was last modified: 2017-02-13, 14:19 by 3dfx.)

Code:
looking at parent device '/devices/pci0000:00/0000:00:1d.3/usb4/4-1/4-1:1.0/0003:1241:E000.0001/input/input5':

    KERNELS=="input5"

    SUBSYSTEMS=="input"

    DRIVERS==""

    ATTRS{name}=="HOLTEK     PC receiver "

    ATTRS{phys}=="usb-0000:00:1d.3-1/input0"

    ATTRS{properties}=="0"

    ATTRS{uniq}==""

As your device has no ID in the list you could try ' ATTRS{phys}=="usb-0000:00:1d.3-1/input0" ' (inseat of ATTRS{id}).
For symlink what you want or what's in the how-to: ' SYMLINK="input/myremote" ' => /dev/input/myremote (result)
Or you could run:

Code:
ll /dev/input/by-id/

and look for your remote and use that for what comes next.

Myne looks like this:

Code:
xbmc@xbmc:/# ll /dev/input/by-id/

total 0

drwxr-xr-x 2 root root 140 Feb 12 14:29 ./

drwxr-xr-x 4 root root 460 Feb 12 14:29 ../

lrwxrwxrwx 1 root root   9 Feb 12 14:29 usb-Arduino_LLC_Arduino_Leonardo-if02-event-mouse -> ../event5

lrwxrwxrwx 1 root root   9 Feb 12 14:29 usb-Arduino_LLC_Arduino_Leonardo-if02-mouse -> ../mouse1

lrwxrwxrwx 1 root root   9 Feb 12 14:29 usb-Philips_eHome_Infrared_Transceiver_PH00PTAj-event-if00 -> ../event6

lrwxrwxrwx 1 root root   9 Feb 12 14:29 usb-Pulse-Eight_USB-CEC_Adapter_v2_r8-if02-event-mouse -> ../event4

lrwxrwxrwx 1 root root   9 Feb 12 14:29 usb-Pulse-Eight_USB-CEC_Adapter_v2_r8-if02-mouse -> ../mouse0

I hope it works Smile

nikto · (This post was last modified: 2017-02-14, 03:52 by nikto.)

Sorry I really thank you for your help but I'm very ignorant both for linux and for English... It is very very difficult for me to understand all these steps ... I have absolutely not idea of what I'm doing and what are those things and items..
Following 2 guides I'm pretty confused now so I do some order ...
following this http://kodi.wiki/view/HOW-TO:Setup_Lirc I understood I needed a "lircd.conf" file specific form my remote. I didn't find it in '/usr/share/lirc/remotes like the guide said. I have found it here http://lirc.sourceforge.net/remotes/ so I don't know if it's okay...
The reason why I chose it is only the name holtek.
when you say

(2017-02-12, 14:16)3dfx Wrote: there are lircd configs for many remotes. You need to find the one that is fitting yours

I do not know what it's like ... I only know the name Holtek and that is a HID remote with an usb IR receiver.. So the one that is fitting mine, from my point of view, is the one that is called Holtek or Konig.. Am I wrong?
After that I copied and pasted it in /etc/lirc/ overwriting the existing one and I edited the file as the guide said. Now my file is this:

Code:
#

# this config file was automatically generated

# using lirc-0.8.7-CVS(devinput) on Thu Dec 31 18:31:06 2009

#

# contributed by Ludovic LEMARINEL <l.lemarinel|gmail.com>

#

# brand:                       Holtek

# model no. of remote control: USB RF

# devices being controlled by this remote:

#

begin remote

      end codes

end remote

Is it ok?

Now... to complete the next guide step that is this....

Code:
user@computer:~$ sudo -s ## you have to be root for this part

[sudo] password for user:

root@computer:~# cd /etc/lirc

root@computer:/etc/lirc# irrecord --driver=irman --device=/dev/ttyS0 MyRemote ## use the driver that you chose in the previous part. /dev/ttyS0 = first com port

....I need first to compile this

Code:
echo 'KERNEL=="event?",ATTRS{id}=="?",SYMLINK="?"' > /etc/udev/rules.d/10-persistent-ir.rules

Is it right? But sorry... I tell you again: I don't understand which of the two events I have to use...
Have you seen the 2 codes for event3 and event4 in my post #5?
Why in your example do you use data from my event3 and not from event4?
This is my problem. As I said i need to compile 1 code that is

Code:
echo 'KERNEL=="event?",ATTRS{id}=="?",SYMLINK="?"' > /etc/udev/rules.d/10-persistent-ir.rules

But I have 2 event with 2 different values for each of these names...
I have event3
but I also have event 4
I have ATTRS{phys}=="usb-0000:00:1d.3-1/input0"
but I also have ATTRS{phys}=="usb-0000:00:1d.3-1/input1"
so I really don't understand....
Do I have to compile 2 of these code

Code:
echo 'KERNEL=="event?",ATTRS{id}=="?",SYMLINK="?"' > /etc/udev/rules.d/10-persistent-ir.rules

for each event?
Or do I need to use just the data from event3 or maybe from event4 Huh

I'm totally lost
Maybe it is better to do only one step at time..

p.s the last command you asked me to run gave me this but I really don't knowhow to use it.

Code:
franz@ZAVAGLIO-PC:~$ ll /dev/input/by-id/

totale 0

drwxr-xr-x 2 root root 100 feb 14 00:59 ./

drwxr-xr-x 4 root root 420 feb 14 00:59 ../

lrwxrwxrwx 1 root root   9 feb 14 00:59 usb-HOLTEK_PC_receiver-event-kbd -> ../event3

lrwxrwxrwx 1 root root   9 feb 14 00:59 usb-HOLTEK_PC_receiver-if01-event-mouse -> ../event4

lrwxrwxrwx 1 root root   9 feb 14 00:59 usb-HOLTEK_PC_receiver-if01-mouse -> ../mouse0

franz@ZAVAGLIO-PC:~$

3dfx · (This post was last modified: 2017-02-14, 12:14 by 3dfx.)

Ok, step by step:
1. The command 'udevadmin...' is just for you to get the right 'ATTRS{id}' (this is for a fixed name of the remote)
2. Your device doesn't has an id so, you need to use ATTRS{phys} (this is also for a fixed name of the remote)
3. I see in your output, you need to use event3 (as it is the keyboard part of the remote)

Code:
lrwxrwxrwx 1 root root   9 feb 14 00:59 usb-HOLTEK_PC_receiver-event-kbd -> ../event3

4. Where is your "lircd.conf" file? o,O
5. On SourceForge I fount a Config for Holtek and 2 for Konig, take a look at these if it fits for your remote
Is there a model number on your remote maybe?
6. Yes you have to compile this

Code:
echo 'KERNEL=="event?",ATTRS{id}=="?",SYMLINK="?"' > /etc/udev/rules.d/10-persistent-ir.rules

As I said, not with 'id' but with 'phys'
And like I said before SYMLIK="?" you can choose what you want as a name

OR: the easiest way, buy an MCE remote ^^

nikto · 2017-02-14, 15:19

Thank you again...
as I wrote in the first post my remote is a Konig CMP-MEDIAREM12
http://ns323666.ip-37-187-156.eu/manuals...ontrol.pdf
exactly this

I had seen those two konig inside http://lirc.sourceforge.net file but their name is very different from mine. So I opted for the only choice I had, the Holtec file. I posted it in my previous post.
It is like so because the guide says

Quote:Delete the lines between begin codes and end codes.

So... I really hope this is the right one!
Ok thanks to you now I understand better, I return later when I have done this

Code:
echo 'KERNEL=="event3",ATTRS{phys}=="usb-0000:00:1d.3-1/input0",/dev/input/myremote > /etc/udev/rules.d/10-persistent-ir.rules

3dfx · 2017-02-14, 15:57

(2017-02-14, 15:19)nikto Wrote:
Code:
echo 'KERNEL=="event3",ATTRS{phys}=="usb-0000:00:1d.3-1/input0",/dev/input/myremote > /etc/udev/rules.d/10-persistent-ir.rules

That's wrong, it should be

Code:
echo 'KERNEL=="event3",ATTRS{phys}=="usb-0000:00:1d.3-1/input0", SYMLINK="/dev/input/myremote"' > /etc/udev/rules.d/10-persistent-ir.rules

or:

Code:
echo 'KERNEL=="event3",ATTRS{phys}=="usb-0000:00:1d.3-1", SYMLINK="/dev/input/myremote"' > /etc/udev/rules.d/10-persistent-ir.rules

I'm not sure which one would work, with or without 'input0'
Just try it out

nikto · (This post was last modified: 2017-02-14, 16:36 by nikto.)

Ok I tried both but I always get this:

Code:
franz@ZAVAGLIO-PC:~$ echo 'KERNEL=="event3",ATTRS{phys}=="usb-0000:00:1d.3-1/input0", SYMLINK="/dev/input/myremote"' > /etc/udev/rules.d/10-persistent-ir.rules

bash: /etc/udev/rules.d/10-persistent-ir.rules: Permesso negato

franz@ZAVAGLIO-PC:~$

and this

Code:
franz@ZAVAGLIO-PC:~$ echo 'KERNEL=="event3",ATTRS{phys}=="usb-0000:00:1d.3-1", SYMLINK="/dev/input/myremote"' > /etc/udev/rules.d/10-persistent-ir.rules

bash: /etc/udev/rules.d/10-persistent-ir.rules: Permesso negato

franz@ZAVAGLIO-PC:~$

I also tried adding sudo at the beginning of the code but the result is the same.
"Permesso negato" in italiano means "permission denied"
I don't know what to do...
When you say I need a MCE remote I don't understand, I was convinced this was an MCE remote

nikto · (This post was last modified: 2017-02-14, 17:12 by nikto.)

p.p.s.. I don't know if it could help but in another forum someone, who was not able to solve the problem, has told me to use this comand to identify which are the comand the remote runs

Code:
xev | grep -A2 --line-buffered '^KeyRelease' | sed -n '/keycode /s/^.*keycode \([0-9]*\).* (.*, \(.*\)).*$/\1 \2/p'

I launched it and without pushing any remote button, just after hitting "enter" after the comand in the terminal I get this:

Code:
franz@ZAVAGLIO-PC:~$ xev | grep -A2 --line-buffered '^KeyRelease' | sed -n '/keycode /s/^.*keycode \([0-9]*\).* (.*, \(.*\)).*$/\1 \2/p'

36 Return

if I push the Green Button on my Remote I get this

Code:
franz@ZAVAGLIO-PC:~$ xev | grep -A2 --line-buffered '^KeyRelease' | sed -n '/keycode /s/^.*keycode \([0-9]*\).* (.*, \(.*\)).*$/\1 \2/p'

36 Return

64 Alt_L

133 Super_L

36 Return

So it seems the green button is received as 64 Alt_L and 133 Super_L
Is it useful for something?

3dfx · 2017-02-14, 17:17

The remote is seen as a keyboard, what you have there are the key-codes of your "remote control keyboard".
But what you want is: button green pressed on remote => lirc sees green button pressed => run script to start kodi
Or am I wrong?
So I would guess this doesn't help you very much :/

nikto · (This post was last modified: 2017-02-14, 19:38 by nikto.)

Ok I understand. however both the comand

Code:
echo 'KERNEL=="event3",ATTRS{phys}=="usb-0000:00:1d.3-1/input0", SYMLINK="/dev/input/myremote"' > /etc/udev/rules.d/10-persistent-ir.rules

and the comand

Code:
echo 'KERNEL=="event3",ATTRS{phys}=="usb-0000:00:1d.3-1", SYMLINK="/dev/input/myremote"' > /etc/udev/rules.d/10-persistent-ir.rules

give to me "permission denied" as result.... so I think I'm done, right?

3dfx · 2017-02-14, 19:54

Try

Code:
sudo nano /etc/udev/rules.d/10-persistent-ir.rules

And paste one of those lines at the end

Code:
KERNEL=="event*",ATTRS{phys}=="usb-0000:00:1d.3-1/input0", SYMLINK="/dev/input/myremote"

or

Code:
KERNEL=="event*",ATTRS{phys}=="usb-0000:00:1d.3-1", SYMLINK="/dev/input/myremote"