• Ehome Infrared Driver Windows 10 Fix
• Disable Infrared Windows 10
• Windows Ehome Folder
• Ehome Microsoft

This is a (probably futile) attempt to keep up with the vast range of MCE remotes out there, and give some indication of how well they work with XBMC.

If you are adding a review please try to be as detailed as possible about the remote. For example:

• What operating systems and versions of Kodi have you tested on
• Does the remote send keystrokes or is it MS compatible?
• If it's MS compatible have you tested reconfiguring it using the registry and did this work?

The article groups the Microsoft compatible (also known as eHome or RC6) remotes together first, as these are most configurable when you're using them with XBMC. Other than this there's no significance to the order of the reviews.

• 1eHome/RC remotes
• 2Non eHome/RC remotes
  • 2.1VRC-1100

The remotes in this section all use the Microsoft eHome driver on Windows. See Using a Microsoft remote control in Windows for details. This type of remote is supported out of the box by Kodi Live.

Windows 10 Services. 1394 OHCI Compliant Host Controller; 3ware; ACPI Devices driver; ACPI Power Meter Driver; ACPI Processor Aggregator Driver; ACPI Wake Alarm Driver. Tech Tip: If you are having trouble deciding which is the right driver, try the Driver Update Utility for Microsoft eHome Infrared Transceiver. It is a software utility that will find the right driver for you - automatically. DriverGuide maintains an extensive archive of Windows drivers available for free download. We employ a team from around.

eHome remotes are generally more expensive than the non-eHome remotes, but they are highly configurable and work very well with XBMC. Many universal handsets, for example the Harmony remotes, have emulation for eHome/RC6 handsets built in so they will work with an eHome IR receiver.

Note that Microsoft has modified the programming and device specification for remote controls several times. For example, in Vista, the Port Driver/Class Driver Model was added. This means that there may be some transceivers which may not function fully, if at all, on systems prior to Vista. For the curious (or bored) there is a specification for the Windows Media Center remote.

1.1 Microsoft Media Center Remote Control

All these variants of the MS remote will work out of the box with Kodi Live, though with a standard Linux install you'll need to install and configure Lirc. To get it to work on Windows you need to configure it to simulate key-presses. See Using a Microsoft remote control in Windows for details.

1.2 AIM RC6 Media Center Remote Control

AIM, Ahead In Multimeadia is a registered trademark of Formosa21 Inc. This is a Microsoft Windows Media Center compatible remote control labeled (RC6) for Windows 7 32bit and 64bit as well. Model Number: RC118 other compatible models made by the same company are RC125 and RC126, which use the same hardware but with different button layout. The receiver Model number: IR605A

RC6 remotes is the best you can buy specially after Microsoft's own remote was discontinued; there are so many cheap/clone remotes but spending a few more bucks should leave you satisfied.

This RC6 remote like any other RC6 Microsoft Certified remote will work with any Windows platforum that was released after Windows XP. It's certified for Windows 7 32bit or 64bit. I can not confirm that it works with Linux, but in Maplin's Questions section someone confirmed that it works with Linux and it's detected as an lirc_mceusb2 device.

This Remote is fully comaptible with Microsofts eHome default Driver 'Microsoft eHome Infrared Transceiver' no additional drivers required, it will be automatically detected and installed by Windows. It has a dedicated website that has all the required setup files available, the .reg file on site should work with any compatible RC6 MCE remote. by using the latest config.reg file all the buttons work in XBMC.

All buttons are capable of sending IR WM_APPCOMMANDS or Keystrokes, fully configurable.

1.3 HP MCE Remote

Both versions are compatible with the Microsoft remote, and the .reg files used to reconfigure the MS remote will also work with the HP remote.

With the Remote-XBMC.reg config all the buttons work in Kodi except for the 'T' and 'Print' buttons. To configure these buttons add the following to the .reg file:

1.4 HP Pavilion HDX Remote

This is a newer version of the HP remote. An important difference from the older HP remotes is that it has a unified Play/Pause button instead of separate Play and Pause buttons. Like the older remotes it uses the Microsoft eHome drive so the buttons can be configured by modifying the registry. The Play/Pause button is number 6E. To configure this to send a VK_MEDIA_PLAY_PAUSE multimedia keypress use:

There is also a version of this newer HP remote with red / green / yellow / blue buttons as the top row of four. On that (and I assume the one pictured) the button numbers for the replay button (top-middle) and the TV button (top-right) are 80 and 39 respectively. Hope that helps

If using this one or the newer HP remote such as:

• RC2234302/01B
• 3139 228 54651
• HP PN: 464961-001
• HP SPS: 465541-001
• HP RMN: HSTNN-PR18

in combination with OVU400102/71 HP usb IR receiver on a Ubuntu system, then the Play/Pause button will need a special code 0x00007b91 in the /usr/share/lirc/remotes/mceusb/lircd.conf.mceusb

Note that the HP IR USB receiver OVU400102/71 uses a Fintek chipset. There have been various problems reported with using this device on XP. In some cases, it is recognized as an eHome device, but then does not send keys as an HID device, (however it worked with the EventGhost MCE Remote plugin). In other cases, it was not recognized as a Microsoft eHome device (a patch from HP may be required), but as a FinTek eHome device (after getting the (hacked) Fintek driver). The FinTek driver does not work on some XP configurations (cause unknown).

HP IR Receiver TSGI-IR01 apparantly has several implementations. The TopSeed (vendor id 1784 Product 0006) implementation does NOT support USB3. Plug into a USB2 port, otherwise, you will get 'random' data whenever a keys is pressed, or worse (hangs, etc.). Note that on some systems even the USB2 port will not work. This may be due to newer chipsets or firmware (z97, ASRock).

1.5 Asrock Remote

The Asrock ION PC's come with a remote control and some models the HT Also include a internal CIR receiver.

1.6 Mediagate GP-IR02BK

Compatible with the Microsoft remote, and the .reg files used to reconfigure the MS remote will also work with the Mediagate. The remote is currently available on Amazon UK and US.

There are some additional buttons not on the official MS remote. These can be configured using the following in the .reg file:

1.7 Mediagate MG-IR02BK

Compatible with the Microsoft remote, and the .reg files used to reconfigure the MS remote will also work with the Mediagate.

There are some additional buttons not on the official MS remote (and not on the GP-IR02BK):

1.8 DEC-200B

Compatible with the MS remote. Works out of the box with XBMCLive. Not tested (so far) with the Windows and OSX versions. Don't know if it's configurable with the registry.

1.9 AVS Gear HA-IR01SV

Compatible with the MS remote. Frequently works out of the box with XBMCLive - some versions ship with new receivers whose product IDs are not always included with LIRC such as ID 0011 from VENDOR_TOPSEED. If the remote doesn't work and/or the light on the receiver stays on once a button is pushed, the reciever needs adding to LIRC. Instructions are here. Not tested (so far) with the Windows and OSX versions. Don't know if it's configurable with the registry. Currently available from Amazon UK (search for HA-IR01SV). Googling suggests it is widely available.

1.10 AURC-002

Manufactured by Acowin Industrial Limited; see http://www.acowin.com.hk/product535.html. Microsoft MCE clone with a cloned HP receiver. Compatible with the .reg files used to reconfigure the official Microsoft remote and receiver.

1.11 Microsoft XBox 360 Universal Remote Control

This will work on Windows (I've tested on XP and 7) with the Microsoft receiver or a compatible receiver like the HP (the remote does not come with a receiver) though need a minor registry tweak. Navigate to:

HKEY_LOCAL_MACHINESYSTEMCurrentControlSetServicesHidIrRemotes745a17a0-74d3-11d0-b6fe-00a0c90f57da

then change the value of CodeSetNum0 to 8, and delete the three entries CodeSetNum1, CodeSetNum2, CodeSetNum3. You need to reboot for the change to take effect.

Ehome Infrared Driver Windows 10 Fix

There are some buttons that aren't on the standard MS remote. The button numbers for these are:

The volume and mute buttons do not work.

1.12 Philips 5100 4in1 Vista MCE Remote

Philips have produced a family of remotes in this range designed for different sales regions each with different features. This one has the ability to control 4 devices (PC, TV, Sat, Amp) and can be programmed using the manufacturer codes database supplied. It also has the ability to learn functions from other remotes to replace any of its buttons, making it very versatile once customised to your home cinema setup. However, the keys are not backlit. The supplied infra-red usb receiver only works with Vista, Windows 7 and Linux.

Note: Also works with the Official Microsoft MCE receiver as it sends the same signals (RC-6), meaning it can be used on Windows XP via this receiver.

Discontinued - (Can be found on ebay UK)

1.13 Microsoft MCE Keyboard Remote

Similar to the buttons to the Microsoft MCE remote, but with a full keyboard and a 'nipple' for moving the mouse. Range is limited and it requires a direct line of sight to the receiver. Can be operated on the users lap. The keyboard has a very nice feel, though the mouse nipple is hard to use.

Works with the Official Microsoft MCE receiver and with compatible RC6 receivers like the HP receiver.

Disable Infrared Windows 10

These remotes usually work by emulating a keyboard, that is when you press a button on the remote Kodi receives a key press just as if a key had been pressed on the keyboard. Most of the remotes emulate multimedia keyboards or send Windows Media Center keyboard shortcuts like ctrl-shift-P for Play.

XBMC has all the required keyboard mappings for these remotes so they should work out of the box. However they usually cannot be configured so they have some limitations. For example, on Windows the green button will start Windows Media Center and this can't be changed without considerable messing around.

These remotes will work with XBMCLive as long as Ubuntu recognises them as a keyboard, which isn't always the case.

2.1 VRC-1100

2.1.1 General Configuration

See bellow for Ubuntu specific notes

There is no manufacturer's name on this remote or the manual, but they appear to be from Ortek (http://www.ortek.com/html/pdt_view.asp?area=25&cat=154&sn=65). They are widely available on eBay. Maplin UK also sell an own-brand remote control (product code N18HC) that seems to be identical, and it is also sold as Hama 52451. The remote simulates the MS Media Center keypresses and will work out of the box on Windows, Linux and probably OSX. It also simulates a mouse, although it's no match for a proper mouse or trackpad.

Note that the the i button sends a right mouse click, which isn't much use in XBMC as the right click can't be mapped to an action. There is no way round this without using some helper app like Eventghost, but the Info action could be mapped to one of the other buttons.

If you want to add mappings for the four colored keys and the four keys below them here are the entries you need in keyboard.xml. The top left (Internet Explorer) key can't be trapped through keyboard.xml, but in appcommand.xml this button is <browser_home>.

The * button sends a numpad-* keypress. XBMC v10.1 sees this as <eight>. XBMC v11.0 sees it as <numpadtimes>.

The # button sends a sequence of keypresses: numlock, alt, numpad-three, numpad-five, numlock. This generates a keypress with the ascii value 35 i.e. '#'. In v10.1 you can map this using <five mod='alt'>.

Windows Ehome Folder

For full Linux support see http://trac.kodi.tv/ticket/8827

2.1.2 Ubuntu Specific Configuration

The following information was based on Ubuntu 14.10 w/ Unity + Kodi 15.0 rc2.Much of this was taken from Archived Wiki note (How-to:Configure VRC-1100 remote for Ubuntu

Out of the box, the following keys do not make it to Kodi interface:

Ehome Microsoft

• Previous Track
• Play
• Next Track
• Stop
• Volume Up
• Volume Down
• Mute
• close
• Power

In the Ubuntu desktop, go to System Settings > Keyboard > Shortcuts (tab) > Sounds and Media and disable italicized above items by selecting them then pressing backspace.

Next go to System Settings > Keyboard > Shortcuts (tab) > Windows and disable 'Close window' by selecting it then pressing backspace.

Power button is captured through a different interface. Open dconf-editor application. Browse down to org.gnome.settings-daemon.plugins.power by clicking on the black triangles next to each path element. Locate button-suspend and change it's setting to Nothing. NOTE: Although, this prevents the computer from shutting down, the key still doesn't make it into Kodi. This needs work. Holding Alt on the keyboard and pressing Power button on the remote does send 'sleep' command to Kodi.

Mouse, left clock, right click, Info remain as mouse only functions.

Here is the file that describes all the buttons (except the mouse keys) on the VRC-1100 remote.Place this file into the following location:

2.2 Speedlink SL-6399

Cheap and cheerful remote. It simulates the MS Media Center keypresses and will work out of the box on Windows, Linux and probably OSX.

Apparently there are different usb receivers that come with the remote.

There are several extra buttons not on the standard MS remote. If you want to add mappings forthese keys here are the entries you need in keyboard.xml.

See also keyboard.xml sample for SL-6399-SBK

2.3 Unbranded MCE remote

There is no manufacturer's name on this remote or the manual, and it is sold via numerous Asian resellers, but on the PCB of the receiver you can read the OEM name www.tigerfly.net. It can be used with Logitech Harmony Remote Software by picking Computer>>Media Center PC>>Chinavasion>>CVSB-983.

They are available on Ebay and DealExtreme for as little as ~$10 including shipping (often marketed as e g $2 for the device and $8 for shipping but since the cost for two is $20 this is just a trick). It's cheap and feels a bit flimsy, but it works well enough. It simulates the MS Media Center keypresses and will work out of the box on Windows, Linux and probably OSX. It also simulates a mouse including mouse buttons, although it's no match for a proper mouse or trackpad.

It isn't very configurable and certain buttons don't work as they should: The fast forward and rewind buttons skip forward or backwards instead of moving gradually. This is because they send a bunch of keypresses (ctrl, shift, arrow, letter 'B' etc). If the software is set to detect ctrl + arrow (left or right) it probably works.

If you want to add mappings for the four coloured keys here are the entries you need in keyboard.xml. Every button can be mapped, with one possible exception (the red Power button).

Update 16th Jan: the rewind button sends three keypresses, left, then ctrl-left, then ctrl-shift-B. The left press causes the video to jump back 30 seconds. With the later releases of XBMC the ctrl-shift-B then starts the rewind (release v9.11 ignores ctrl-keypresses).

Update 1st Nov 2010: Requires a minor kernel patch to support all buttons in Linux. See patch in https://bugs.launchpad.net/ubuntu/+source/linux/+bug/607062. Once patched, works well with Linux.

Update 12th June 2011: I've bought one recently. They must have changed hardware or whatever because mine works well with XBMC out of the box both on Win7 and Linux Ubuntu. Most keys are functioning correctly and 4 colored keys can be mapped by adding the following entries in keymap.xml:

Update November 6, 2011: This remote works out of the box on a vanilla install of Ubuntu (11.1). It is auto-detected as a keyboard and mouse. It is no good for typing. It is only slightly better for moving the mouse pointer around the screen. The buttons are dependable though, and if you are looking for a cheap remote that does the job this should be a candidate. Here is a more complete map for every key on the remote except the Red Power Button. These changes go in your keyboard.xml file. Make sure that there are no duplicate mappings (with PVR settings). The default behavior is to pop up a notification with the key combination passed. You should probably replace this behavior with what you want.

XML above tabulated :

And yes, sometimes between then and now, the command for color button changes. f1, f2, f3, and f4 becomes one, two, three, and four caused by keyboard.xml auto update from the repository.

Update December 28, 2013: This remote works out of the box with Openelec 3.1.x. No configuration is needed. Some additional info regarding the red power button of this remote:

• Only this button is able to wake-up the HTPC from sleep mode. Pressing other buttons have no effect on a suspended machine.
• This button sends three keypresses. However it is possible to map it to switch off the system directly instead of showing a menu. See this example below.

The GoTView PC Remote control looks exactly like the 'unbranded remote' above. It is also detected as MCE remote by lircd, but has slightly different keycodes, which are incompatible with xbmc defaults.To make things work correctly, add something like the following before the </keyboard> </global> lines in your /usr/local/share/xbmc/system/keymaps/keyboard.xml file