Hi, I am converting from a FLIRC based remote to a standard CIR / MCE setup, and I would like info on what the standard MCE mappings do, e.g. red button = ?.
I use URC MX-890 remotes, and I used to use FLIRC's programmed to my own liking.
Problem is the FLIRC's are very sensitive to electrical noise, and every night at 10pm when my outside lights dim for the night my FLIRC's go crazy.
Since an Intel BIOS update to the NUC and the Linux kernel update, I can now use the native CIR on my NUC's....
I'm getting exactly the same issue with a non-usb IR receiver.
I've got an IR receiver hooked directly up to the GPIO pins on my Pi. It used to work just fine, but now I usually have to reboot a few times for it to work.
So I don't think this is a USB issue so much as perhaps an lirc issue.
I have a Microsoft MCE remote (1039) that is not working quite how I'd like. The only issue I am struggling with is that there are 2 buttons (OK and Enter) that show the same key press (KEY_OK) when I use irw. Previously, I was running Ubuntu + XBMC and these keys had distinct mappings.
I am pretty sure the solution is to edit lircd.conf, but this is part of the read only fs in OpenElec. I am struggling to find much info on this subject. I did find a post somewhere that suggested placing an...
i have a Problem to get my HifiBerry DAC (not DAC+) working with the latest OpenElec version. Since OpenElec use kernel 16.3.x the Pi immediately freeze if i set the DAC as default audio output. When i blacklist ‘lirc_rpi’ the Pi wont freeze but i get no sound. The last build that work is this Version from Milhouse´s OpenElec build. This version use kernel 3.15.8. All other Version use kernel 16.3.x. The problem still exist with the last offical beta.
I've added the line into the shutdown.sh file, and the message shows up in the log messages.
So the script is executed when powering off the system.
The problem seems to be that the network is already shut down while executing the shutdown script.
I've just switched from running RaspBMC on my pi to OpenELEC (4.1.6). Things have been working so much better, but there's one thing that has stopped working for me. My "Home" button on my universal remote no longer works. And it doesn't work from a standard MCE remote either.
Running irw and pressing either button I see:
66 0 KEY_HOME devinput
66 0 KEY_HOME_UP devinput
I don't understand why OE isn't picking this up? I figured I could add my own mapping to Lircmap.xml, but have been...
I have a Raspberry Pi with the Openelec 4.1.6 beta on it. I also have a Hifiberry Digi attached. Music is on a NAS.
I was trying to follow the instructions to edit the etc/modules file to add in the code needed for the Hifiberry as shown on this page: www.hifiberry.com/guides/hifiberry-software-configuration/
However, the "modules" files doesn't exist in the etc/ directory. I checked by running "ls" in the etc/ directory. (See below)
just been at it with som efresh energy. it turns out that openelec is not using lirc but eventlirc.
I have come to the point where I was able to disable eventlirc and use lirc with my remote: @hugo, maybe that is also for you a possibility as lirc has more options etc.
problem now is that although lirc is working, I have double key-presses and can't overcome that problem: so reverted back to eventlirc.
I hope it is possible to configure channels in lirc as eventlirc does not have that...
I did a ton of research on how the ati remote works. Its an x10 device and i believe lirc is not involved because the remote wonder mimics a keyboard and mouse. The driver being used for the remote wonder is a x10 driver called ati_remote. It works with the remote wonder 1 and sorta works with the 2. The 3 uses a different communication method and this is why an update is needed to the driver. I'm not a linux guru or I would have this fixed for myself and probably know exactly how to fix your...