I would like to use Logitech Harmony with amremote (using remote.conf file). I’m trying to make one from scratch with some positive results.
The question I have is which profile should I choose on Harmony? For example if I select Microsoft, Windows Media Center then I don’t get any button received. But if I select Pivos XIOS DS then I got buttons received.
Before making more progress I would like to know what is the best profile to be selected? To get all buttons on remote usable.
I have a Logitech Harmony 650 remote which I configured for my X92 (S912) box. In Logitech Harmony Remote Software (7.7.0) i chose X92 as manufacturer and “OTT TV BOXX92” as the model. All buttons work as expected on X92 box. On my N2 most buttons work properly and I only additionally copied Power IR codes directly from original N2 remote to my Harmony 650, so that Power on/off works also with Harmony power button.
Which "remote.conf exactly I’m using I have no idea. Long time ago I copied remote.conf for my X92 box and when I got N2 I restored my X92 settings to it, so it’s probably still that remote.conf that is active…
Btw, I use Harmony remote ONLY to turn ON/OFF my box, for all other commands I use my wifi Rii mini i8+ keyboard…
I tried numerous devices and they all behave the same: pressing for example key up several times moves selected item slowly. I changed delays in Harmony software without any visible change.
I managed to change protocol for amremote from NEC to RC6 with this command but final result is the same. I think I will have to stick with Flirc (but I would like to free the USB port).
fdtput -t u /flash/dtb.img /meson-remote/ protocol 5
Update: I think I managed to fix the issues. The solution was using Troubleshoot in Harmony software and change some repeat value to 0. Seems harmony can sends each button press few times by default which decoder can’t handle.
@bubblegum57: I’ve done what you suggested. Had an old Harmony 650 lying around, programmed it on Hardkernel Odroid C2. The power toggle was able to switch on the N2. I then went into the Harmony configuration of my newer Harmony One, entered the MS Media Player configuration and corrected the power toggle command, by programming it using the old Harmony 650. This works to the extent, that the N2 is powered on correctly. It just still does not power off when I press the (corrected) power toggle command. Which brings me to…
@vpeter: I’ve been using the remote.conf and keyboard.xml files you have posted in this thread without amending them. The keyboard.xml file does not contain a noop line, it just assigns xbmc.Shutdown to power, as it should be, I guess. I have then monitored the kodi.log file in debug mode to see whether pressing Power Toggle on the remote produces any Keyboard: scancode event. It doesn’t. Any idea how I can take it from here?
And thanks for your script. I’ve put it in the flash folder and will see how it goes, next time I update.
OK, I’ve figured it out: Firstly, @vpeter, you were right. There was a noop entry in the original file. I placed it in userdata, forgot it and later placed another copy under .config/rc_keymaps. Apparently, the one in userdata took precedent, so my changes in .config/rc_keymaps were overruled. I’ve then just kept the file in userdata, removed the noop line and now the N2 powers off when I press Power Toggle using the originalMicrosoft Media PlayerPower Toggle command.
However, I then realized that the same Power Toggle command does not work for powering on the N2. I assume that the reason is the switch in remote protocol that we applied. My “solution” was to simply program an additional command N2PowerOn on my Harmony for the Microsoft Media Playerdevice using the Hardkernel PowerToggle command. I then added that command to the Watch Kodi action start sequence in the MyHarmony software.
I don’t know whether there are easier ways to fix this, e.g. by adapting the config.ini, but I haven’t been able to do it using the standard guides that float around the internet…