I am loving OpenPHT on my new ODroid C2 but every time I power off my TV the ODroid shuts down/suspends and does not power up when the TV comes back on. I do not want any CEC control whatsoever, so I have disabled CEC control in Preferences, as well as setting the preferences for a response to CEC power operations to ignore. Despite this, my ODroid keeps responding to CEC remotes and power events.
Is there any way I can fix this, since the UI settings seem not to have any effect?
I have now discovered that the ODroid C2 is not responding to CEC (after I disabled it), but to IR signals from my Panasonic TV remote, including the power button that I use to put the TV into standby.
I would now like to configure the IR receiver on the ODroid C2 to ignore signals from the Panasonic remote and respond only to the MCE remote I have. Alternatively, I could disable the onboard IR altogether and just use a USB-attached MCE IR receiver I have.
Assuming I don’t want to take the low-tech approach to disabling the onboard IR by covering it with tape, it looks like I will need to find and configure LIRC configuration files. As I cannot get SSH access to the device, I have been trying to find these files in the SMB shares exposed by OpenPHT to no avail.
Can anyone please point me to where I can find the configuration files for LIRC on OpenPHT?
Thanks!
SSH on the Odroid works without issue, the user is root and password is openpht, so enter ‘ssh root@youripaddress’ and enter the password.
There are lots of topics in the Rasplex forum for configuring remotes, one example is https://forums.plex.tv/discussion/comment/872631#Comment_872631
Did you also read the Odroid hints and tips topic I posted?
Regards
Thanks, NedtheNerd. I have indeed read your hints and I thank you for taking the time to document these. After now learning more than I ever wanted to know about lircd, ir-keytable, kernel drivers, scancodes and the like, I have now addressed my issue as follows:
The autostart script is not running during startup yet, but I should have that resolved soon.
@paulkelso said:
Thanks, NedtheNerd. I have indeed read your hints and I thank you for taking the time to document these. After now learning more than I ever wanted to know about lircd, ir-keytable, kernel drivers, scancodes and the like, I have now addressed my issue as follows:
- Used ir-keytable to select lirc as the protocol. I did manage to get the remote almost working with the RC6 protocol and custom keytable, but was getting double keypresses and could not find a way to address this readily with ir-keytable. I therefore decided to head down the lirc route.
- Created a custom lircd.conf from the existing file in which I have commented out the section that appears to correspond to scancodes from my Panasonic TV remote but includes those for my MCE remote.
- Created an autostart.sh script to run ir-keytable to configure the protocol as lirc as per (1) above, kill current lircd and then start lircd using my custom lircd.conf.
The autostart script is not running during startup yet, but I should have that resolved soon.
You can fix the power off by just copying the lircd.conf file out of /etc and putting it in .config and commenting out the KEY_POWER lines.
I was trying to add some seemingly undefined buttons out of the MCE Extender harmony profile to the box (even tho the scancodes are clearly defined in /usr/lib/udev/rc6_mce?!?) and could not figure out what to add to the lircd.conf file to get them recognized by lircd. (irw just was blank when I pressed the button). I finally was able to take the captured scancodes (from ir-keytable -t) and define them in my own file and use an autostart.sh file to load those at boottime and now irw seems them and I can use remotes.xml etc to map them to plexht/kodi functions. I just cant seem to figure out how lircd.conf enough to see how it relates to the actual scancodes as seen by ‘ir-keytable -t’
Ohh, and to get autostart.sh to run just put it in .config is all I did
I am experience the same issue, but want to use my flirc, so how do disable the IR sensor? Thanks.
@coz2001 said:
I am experience the same issue, but want to use my flirc, so how do disable the IR sensor? Thanks.
If you’d like to disable the onboard IR sensor and just use the flirc, I’d get the sensor driver configured to use an IR protocol that does not correspond to your remote. For example, if you are not using any Sony remotes or remotes that use the Sony protocol, then you could type ir-keytable -p sony to force the IR sensor to respond only to the Sony protocol (which you don’t use). To make this change persist over reboots, add it to the autostart.sh script. This will disable flirc as well, so you will need to rely on the keyboard mappings you have configured with the flirc receiver.
@shaddow825 said:
Ohh, and to get autostart.sh to run just put it in .config is all I did
I found that my autostart.sh script was running at startup, but that I have to leave a few seconds after executing the killall lircd command before I started lircd again. All is now good.
@paulkelso said:
@shaddow825 said:
Ohh, and to get autostart.sh to run just put it in .config is all I didI found that my autostart.sh script was running at startup, but that I have to leave a few seconds after executing the killall lircd command before I started lircd again. All is now good.
Cool. I was doing that but I found a way around it. I just recorded the buttons I wanted with irrecord to create my own lircd.conf with just those buttons and took the scan codes out and put them in the rc6 section of my lircd.conf in the .config directory mapped to the right scan code (which was actually already in there as one of the BB2 or whatever “unused” ones) and restarted without my autostart.sh and I get all the buttons from my media center profile from harmony.
Since it sounds like your remote might be rc6 based you may be able to do the same thing. What buttons did you have to add that weren’t working? Maybe I already did the figuring out of those and could let you know what to add to the existing lircd.conf
@shaddow825 said:
Since it sounds like your remote might be rc6 based you may be able to do the same thing. What buttons did you have to add that weren’t working? Maybe I already did the figuring out of those and could let you know what to add to the existing lircd.conf
Thanks for the tip! The reason I was making these changes was to simply stop my Panasonic TV remote controlling OpenPHT. I now realise all I need is the modified lircd.conf (with the TV remote stuff commented out) sitting in my .config folder - no need for the ir-keytable or the autostart.sh at all.
Cheers.
@paulkelso said:
@shaddow825 said:
Since it sounds like your remote might be rc6 based you may be able to do the same thing. What buttons did you have to add that weren’t working? Maybe I already did the figuring out of those and could let you know what to add to the existing lircd.confThanks for the tip! The reason I was making these changes was to simply stop my Panasonic TV remote controlling OpenPHT. I now realise all I need is the modified lircd.conf (with the TV remote stuff commented out) sitting in my .config folder - no need for the ir-keytable or the autostart.sh at all.
Cheers.
Yea that was my first step, comment out all the KEY_POWER lines in the copied lidcd.conf.
Glad ya got there, sometimes it takes going the long scenic route to get to the right destination!
