I can’t find any definitive topics regarding this, but is there anything special as far as setup goes to get a Harmony (One) to work through the built-in IR receiver on the NUC in OpenPHT?
For now, I’m using a wireless keyboard to navigate around, which is OK, but not ideal. No buttons work at all on the Harmony remote within OpenPHT
I used the XBMC/Kodi profile in the Harmony desktop app to set up the remote initially. Is that preferred? Anything else I am missing that I need to do?
While I dont have the DN2820FYKH, I do have 3 haswell generation NUCs, two i5s and 1 i3. I use them exclusively for OpenPHT and Windows Media Center (to watch TV). Since these boxes are permanently hooked up to TVs around the house, I only use my remote to control them. I am able to turn them on (from s5 state) and then control them completely via IR.
Like you, I also have a Harmony One. I have had no issues controlling the NUCs with it. All you need to do is make sure you installed the driver for the IR receiver. It’s a nuvotron driver I believe.
When you set up your “NUC activity” you can actually just type in the model number into harmony’s database and it’ll program your remote as a “microsoft ehome remote”. that’ll work fine for the basic functions “play/pause” etc. but for more advanced stuff, just add in a Microsoft keyboard as an additional device you also want to control in that activity.
Once you have the keyboard as part of your activity, you can assign either the physical or virtual buttons to control Plex/Kodi to do whatever keyboard command normally works. For instance, in OpenPHT, the ‘s’ key toggles subtitles on and off. So I made a virtual key at the top to control subtitles. It’s pretty easy to get the Harmony One up and running.
I only had an issue getting it to send the right command to turn on the computer from off. I had to put it into learning mode and then send the raw command. hope that helps
@SN6941 said:
While I dont have the DN2820FYKH, I do have 3 haswell generation NUCs, two i5s and 1 i3. I use them exclusively for OpenPHT and Windows Media Center (to watch TV). Since these boxes are permanently hooked up to TVs around the house, I only use my remote to control them. I am able to turn them on (from s5 state) and then control them completely via IR.
Like you, I also have a Harmony One. I have had no issues controlling the NUCs with it. All you need to do is make sure you installed the driver for the IR receiver. It’s a nuvotron driver I believe.
When you set up your “NUC activity” you can actually just type in the model number into harmony’s database and it’ll program your remote as a “microsoft ehome remote”. that’ll work fine for the basic functions “play/pause” etc. but for more advanced stuff, just add in a Microsoft keyboard as an additional device you also want to control in that activity.
Once you have the keyboard as part of your activity, you can assign either the physical or virtual buttons to control Plex/Kodi to do whatever keyboard command normally works. For instance, in OpenPHT, the ‘s’ key toggles subtitles on and off. So I made a virtual key at the top to control subtitles. It’s pretty easy to get the Harmony One up and running.
I only had an issue getting it to send the right command to turn on the computer from off. I had to put it into learning mode and then send the raw command. hope that helps
Perfect explanation. I had setup the activity incorrectly, but will also verify the correct, if at all, IR driver is installed. Is that something you remember explicitly doing via SSH outside/after installing embedded OpenPHT?
@kars85 said:
Perfect explanation. I had setup the activity incorrectly, but will also verify the correct, if at all, IR driver is installed. Is that something you remember explicitly doing via SSH outside/after installing embedded OpenPHT?
Because I run Windows Media Center to watch Cable TV, all of my NUCs have to be in Windows and were set up in the windows environment only. I’m sorry but I cannot help you with embedded/linux installs. I would figure pretty much what I wrote above should still work since the Windows ehome IR codes are basically standard stuff.