11/20/2022 0 Comments Harmony ehome infrared receiverUSB-2.0 4-Port HUBīus 001 Device 003: ID 1058:1110 Western Digital Technologies, Inc.īus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hubīus 005 Device 002: ID 05a4:1700 Ortek Technology, Inc.īus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hubīus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hubīus 003 Device 002: ID 1784:0006 TopSeed Technology Corp. $ lsusbīus 001 Device 008: ID 067b:2303 Prolific Technology, Inc. So the first thing we need to do is determine which USB device is the IR receiver – highlighted below in bold. I use the command ir-keytable to determine if the kernel driver is reporting keys input correctly. As far as I can tell kodi supports running without lirc. However that requires lirc to be running. Verifying IR is being receivedĪ lot of references suggest using irwas a test utility. We seem to have the IR system up and running. usb core: registered new interface driver mce usbĪnd it loads the mceusb input driver too, great. mce usb 3-1:1.0: 2 tx ports (0x0 cabled) and 2 rx sensors (0x1 active) eHome Infrared Transceiver with mce emulator interface version 1 mce usb 3-1:1.0: Registered TopSeed Technology Corp. rc rc0: lirc_dev: driver ir-lirc-codec (mce usb ) registered at minor = 0 lirc_dev: IR Remote Control driver registered, major 250 input: MCE IR Keyboard/Mouse (mce usb ) as /devices/virtual/input/input14 IR MCE Keyboard/mouse protocol handler initialized usb 3-1: Manufacturer: TopSeed Technology Corp. usb 3-1: Product: eHome Infrared Transceiver usb 3-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3 usb 3-1: New USB device found, idVendor=1784, idProduct=0006 usb 3-1: config 1 interface 0 altsetting 0 endpoint 0x81 has an invalid bInterval 0, changing to 32 usb 3-1: config 1 interface 0 altsetting 0 endpoint 0x1 has an invalid bInterval 0, changing to 32 usb 3-1: new full-speed USB device number 2 using uhci_hcd Looking at dmesg, it appears as though that is happening. Given that the USB IR receiver is taken from a Windows Media Center Edition, the theory would be that it hotplugs and should just work. The hardware is fairly simple, a USB IR receiver, a Harmony 1 remote connected to a Zoran HTPC. However the OK, back and other buttons don’t work. Out of the box, we have a remote that does up/down/left/right/pause work. This post will carry a lot of questions as I resolve issues, and will be updated over time. Read on for more details on what I have done. This blog post is intended to be both a narrative on how to get things going, but also serve as a current reference for people out there who run into this sort of problem. This is my way of looking at if I can get things to “ Just Work”. I’d rather remove a package than heavily configure and customize a set of files. My modus operandi is less about hacking things heavily and more about the simplest path to get things working. Unfortunately both Linux and kodi have changed quite a bit over the years and a lot of the online documentation, blog posts and so on are out of date. Debugging and resolving this has proven to be a much bigger challenge than it has been in the past, where i have worked things out without too many hoops. Left, right, up and down and play work well. Unfortunately now, kodi recognizes only some of the remote commands. As part of this upgrade xbmc became kodi. For a few reasons, I updated some packages on the Ubuntu 12.04 system and ended up on Ubuntu 14.10. It was setup working nicely with a Harmony One remote control. I use kodi (formerly xbmc) as a home media system. It worked with the remote out of the box and now I’m up and running. I’ve ultimately opted for a Raspberry Pi Complete Starter Kit, with Noobs and Raspbmc. I’ve aborted this effort after a rework on the home network.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |