[SOLVED] Haupagge MCE Remote does not work

[lukes790]

I have followed the instructions in the Wiki http://www.hauppauge.com/site/press/presspictures/Remote_MCE-black+receiver.jpg but still my Haupagge remote is not recognised. It is the black MCE remote as in the image below. I have also gone through the numerous threads in the forums and none have so far solved the problem.

[lukes790]

(22nd Sep, 2015 06:58 AM)lukes790 Wrote:  I have followed the instructions in the Wiki http://www.hauppauge.com/site/press/presspictures/Remote_MCE-black+receiver.jpg but still my Haupagge remote is not recognised. It is the black MCE remote as in the image below. I have also gone through the numerous threads in the forums and none have so far solved the problem.

Solved: I opted to uninstall lirc and I am now using the kernel drivers. Works fine except for the remote freezing during use. I guess that's a problem for another day.

[WishX]

Do you just do something like

Code:

sudo apt-get remove lirc

and reboot? I have an older version of the same remote and it doesn't work either. This is the only thing stopping me from using Xbian (once I learned not to upgrade to the 4.4 kernel).

Thanks!

[Nachteule]

First of all I would check if the IR USB receiver has been detected by doing a

Code:

lsusb

[WishX]

What do I do if it has or if it hasn't?

[Nachteule]

Next step would be which driver will be loaded for this device. This can be figured out by doing a

Code:

dmesg

[WishX]

(1st Mar, 2016 07:33 AM)Nachteule Wrote:  First of all I would check if the IR USB receiver has been detected by doing a

Code:

lsusb

lsusb:

Code:

Bus 002 Device 002: ID 0bc2:331a Seagate RSS LLC
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 005: ID 1997:1221
Bus 001 Device 003: ID 148f:5372 Ralink Technology, Corp. RT5372 Wireless Adapter
Bus 001 Device 006: ID 1784:0006 TopSeed Technology Corp. eHome Infrared Transceiver
Bus 001 Device 002: ID 1a40:0101 Terminus Technology Inc. 4-Port HUB
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

$ cat /proc/bus/input/devices

Code:

I: Bus=0019 Vendor=0001 Product=0001 Version=0100
N: Name="gpio-keys"
P: Phys=gpio-keys/input0
S: Sysfs=/devices/soc0/gpio-keys/input/input0
U: Uniq=
H: Handlers=event0
B: PROP=0
B: EV=3
B: KEY=1 0 0 0 0 0 0 0 0

I: Bus=0019 Vendor=0001 Product=0001 Version=0100
N: Name="gpio_ir_recv"
P: Phys=gpio_ir_recv/input0
S: Sysfs=/devices/soc0/ir-receiver/rc/rc0/input3
U: Uniq=
H: Handlers=kbd event3
B: PROP=0
B: EV=100013
B: KEY=1000000 0 0 0 0
B: MSC=10

I: Bus=0000 Vendor=0000 Product=0000 Version=0000
N: Name="MCE IR Keyboard/Mouse (gpio-rc-recv)"
P: Phys=/input0
S: Sysfs=/devices/virtual/input/input5
U: Uniq=
H: Handlers=sysrq kbd event5 mouse1
B: PROP=0
B: EV=100017
B: KEY=30000 0 7 ff87207a c14057ff febeffdf ffefffff ffffffff fffffffe
B: REL=3
B: MSC=10

I: Bus=0003 Vendor=1997 Product=1221 Version=0100
N: Name="Riite Mini Keybo"
P: Phys=usb-ci_hdrc.0-1.4/input0
S: Sysfs=/devices/soc0/soc/2100000.aips-bus/2184000.usb/ci_hdrc.0/usb1/1-1/1-1.4/1-1.4:1.0/0003:1997:1221.0003/input/input9
U: Uniq=
H: Handlers=sysrq kbd event4 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=1997 Product=1221 Version=0100
N: Name="Riite Mini Keybo"
P: Phys=usb-ci_hdrc.0-1.4/input1
S: Sysfs=/devices/soc0/soc/2100000.aips-bus/2184000.usb/ci_hdrc.0/usb1/1-1/1-1.4/1-1.4:1.1/0003:1997:1221.0004/input/input10
U: Uniq=
H: Handlers=kbd event6 mouse2
B: PROP=0
B: EV=1f
B: KEY=3007f 0 0 0 0 483ffff 17aff32d bf544446 0 0 1f0001 130c13 b17c000 267bfa d941dfed 9e1680 4400 0 10000002
B: REL=143
B: ABS=1 0
B: MSC=10

I: Bus=0003 Vendor=1784 Product=0006 Version=0102
N: Name="Media Center Ed. eHome Infrared Remote Transceiver (1784:0006)"
P: Phys=usb-ci_hdrc.0-1.1
S: Sysfs=/devices/soc0/soc/2100000.aips-bus/2184000.usb/ci_hdrc.0/usb1/1-1/1-1.1/1-1.1:1.0/rc/rc1/input25
U: Uniq=
H: Handlers=kbd event1
B: PROP=0
B: EV=100013
B: KEY=1000000 0 0 0 0
B: MSC=10

I: Bus=0000 Vendor=0000 Product=0000 Version=0000
N: Name="MCE IR Keyboard/Mouse (mceusb)"
P: Phys=/input0
S: Sysfs=/devices/virtual/input/input26
U: Uniq=
H: Handlers=sysrq kbd event2 mouse0
B: PROP=0
B: EV=100017
B: KEY=30000 0 7 ff87207a c14057ff febeffdf ffefffff ffffffff fffffffe
B: REL=3
B: MSC=10

The IR Receiver is this: Click Here
The more is this: Click Here

When I click anything on the remote, the red light in the HP IR Receiver blinks with each button press, but it's not Xbian isn't reading the key presses.

I also have THIS REMOTE which works just fine right out of the box. This is what I've been using as a mouse and keyboard. Probably because it has it's own wireless dongle.

Here's an output of dmesg: Click Here

It might be worth noting that everything works out of the box with OpenELEC. Is there something I could copy from there into Xbian to get it to work? I'm open to any suggestions here.

Update: I removed the HP IR Receiver from the equation and my remote works fine with the IR built into the cubox-i. Would I have to somehow turn it off for the other one to work? Usually, I just tuck the cubox-i down behind something where it can't catch remote signals and the HP IR Receiver works great. Sadly, the cubox-i's built-in IR has next to no range and can't reach across a room, hence the HP IR.

[Nachteule]

Quote:Update: I removed the HP IR Receiver from the equation and my remote works fine with the IR built into the cubox-i. Would I have to somehow turn it off for the other one to work? Usually, I just tuck the cubox-i down behind something where it can't catch remote signals and the HP IR Receiver works great. Sadly, the cubox-i's built-in IR has next to no range and can't reach across a room, hence the HP IR.

Seems that LIRC driver always uses the built in IR interface.

What happens if you do a

Code:

sudo stop xbmc
sudo stop lirc
sudo start xbmc

I have an MCE RC with an external USB/IR Receiver (this one) which works out of the box in this way (I'm not using such RC's anymore, only using the TV's RC via CEC to control Kodi now. This one I grabbed for testing from my old hardware inventory )

Such kind of RC's usually working well with the kernel input interface, no LIRC is needed

[WishX]

(2nd Mar, 2016 12:06 AM)Nachteule Wrote:  [quote]
Seems that LIRC driver always uses the built in IR interface.
Such kind of RC's usually working well with the kernel input interface, no LIRC is needed

I will try this when I get home today and report back. I can also stop and disable lirc from inside the Xbian settings in Kodi, right?

[Nachteule]

Absolutely right (but theese three commands are faster )

[WishX]

Well, that didn't work. I stopped and disabled autorun on lirc and rebooted. A few times, in fact. Nothing.

[WishX]

It worked like a charm with OpenELEC, Plex client and anything else I could throw at it. Xbian simply doesn't want to see the receiver, lirc or no lirc. I'm beyond frustrated. I really don't want to have to go back to OpenELEC.

[Nachteule]

I can only guess that OE and PLEX does not enable the internal IR receiver (you already told me that the internal IR receiver works but is very limited and you can't used it).

So, perhaps it would help to disable the internal IR receiver and use the external. Let me think a little bit how that can be done.

[WishX]

(3rd Mar, 2016 12:28 AM)Nachteule Wrote:  I can only guess that OE and PLEX does not enable the internal IR receiver (you already told me that the internal IR receiver works but is very limited and you can't used it).

So, perhaps it would help to disable the internal IR receiver and use the external. Let me think a little bit how that can be done.

The internal IR receiver continued to work in conjunction with external IR receivers. I would just tuck the cubox-i down behind the TV so it couldn't directly receive signal from the remote. I never had to turn anything off before.

---

Would it be possible to tear apart OpenELEC and see what they're doing with remotes that makes them all work so well?

[Nachteule]

I think I found the solution:

1) Please add in file /etc/lirc/hardware.conf LOADHB=0 (see example below)

Code:

*"mceusb"*)
                if [ $(echo "$DEVICES" | grep 'Media Center Ed.' | wc -l) -gt 0 ]; then
                        if [ $(echo "$DEVICES" | grep -m 1 -A 4 'Media Center Ed.' | grep -o event[0-9] | sed -e 's/event//g') -eq 0 ]; then
                                . /etc/lirc/hardware/mceusb_event0.conf
                        elif [ $(echo "$DEVICES" | grep -m 1 -A 4 'Media Center Ed.' | grep -o event[0-9] | sed -e 's/event//g') -eq 1 ]; then
                                . /etc/lirc/hardware/mceusb_event1.conf
                        elif [ $(echo "$DEVICES" | grep -m 1 -A 4 'Media Center Ed.' | grep -o event[0-9] | sed -e 's/event//g') -eq 2 ]; then
                                . /etc/lirc/hardware/mceusb_event2.conf
                        else
                                . /etc/lirc/hardware/mceusb.conf
                        fi
                else
                        . /etc/lirc/hardware/mceusb.conf
                fi
                LOADHB=0
                ;;
            *"MCE USB IR Receiver- Spinel plus"*)

2) and blacklist module gpio_ir_recv by adding

Code:

blacklist gpio_ir_recv

to file /etc/modprobe.d/imx6.conf

Make sure that LIRC is enabled again and your external receiver is connected before you're rebooting your box

This change does not enable the onboard IR receiver if an external has been detected and should then use your external receiver instead

Edit:
I'm note really sure if the first modification is really necessary or if it breaks LIRC for working
The second modification will disable onboard IR receiver