If you open /etc/lirc/osmc-remote-lircd.conf in a text editor is the file complete? It should look like this
Please make this file available to others
this config file was automatically generated
using lirc-0.9.0-pre1(default) on Thu Jan 8 11:26:07 2015
contributed by Dilligaf
model no. of remote control:
devices being controlled by this remote:
one 872 807
zero 872 807
@Dilligaf The new remote is RF, not IR, so using a camera to check for IR signals isn’t necessary. When the remote is paired and sending signals correctly it emits a blue flash visible to the naked eye.
LIRC is not used for the OSMC remote, only eventlircd is.
I wouldn’t expect irw to show the keypresses for most of the keys; use evtest instead. We deliver some keys via two different input pathways, which means you’ll need to select one of the two devices individually to verify each key. It does sound like the remote is functionally fine however and that this is just software related
Debug log should show why the remote isn’t working. Do you remember making recent changes to your system?
I assumed it was the old one. OP, what color is your remote? White or black? The original remote is white, new remote is black.
He said the light was blue.
IR remotes have a red window light
Yeah, this is one of the new remotes, it’s black. The lirc.conf file looks complete, and matches what’s above.
I don’t remember making any specific changes recently, I’m afraid, but I’m sure it’s something I did.
Could you let me know where to find that debug log?
You want me to turn on any component specific logging before I do this?
The RF remote does not use LIRC, so this isn’t relevant.
Just upload logs. A reinstall will of course get the remote running again quickly, but I understand this probably isn’t ideal!
Logs are here:
If anything jumps out, let me know, otherwise, I’ll reinstall.
Thanks for your help!
Nothing obvious unfortunately.
Okidoke, will reinstall. Thanks for checking!
Hmm, completely fresh install, but still not working… guess that means it’s most likely hardware related, right?
Could be. You could run evtest to see if the buttons are coming through via the input layer. That would be the best way to test.
I got this when evtesting:
This device is grabbed by another process.
No events are available to evtest while the
other grab is active.
In most cases, this is caused by an X driver,
try VT-switching and re-run evtest again.
Run the following command to see processes with
an open fd on this device
"fuser -v /dev/input/event1"
This is on a fresh install, after rebooting twice. I stopped Kodi as well to see if Kodi was grabbing it, but doesn’t look like that was it.
You need to stop eventlircd
Ah, OK, got it. Unfortunately it’s not showing anything for any buttons except the five way rocker and the home key.
Guess I screwed it somehow
Thanks for all your help anyway
When I am at my desk I will reply in more detail. If the item is faulty and was purchased less than one year ago, we will replace it under warranty.
I will provide further details shortly
Have you dropped the remote or anything? It should withstand most drops but it’s the last thing I could think of.
Please send me your order number via a private message. We will then send you a replacement on Monday, 3rd October. If you have purchased the remote through another retailer, please send me a copy of the receipt.
Thanks, that’s really kind of you! I can’t accept the offer though - I don’t remember dropping it, but I’ve sat on it enough times that I’m sure I’m to blame. I’ll replace it myself at my own cost.
Thank you anyway!
That’s very honest of you. It is rare for the remotes to go faulty, and when they do, they usually completely stop working rather than individual buttons breaking. It’s certainly possible that sitting on the remote a few times has caused it to stop working properly.
I think you should at least accept a discount however, I have sent you one via a private message.