

- #WAKE FLIRC HARMONY OPENELEC PANASONIC FULL#
- #WAKE FLIRC HARMONY OPENELEC PANASONIC WINDOWS 10#
- #WAKE FLIRC HARMONY OPENELEC PANASONIC SOFTWARE#
- #WAKE FLIRC HARMONY OPENELEC PANASONIC CODE#
Wondering if anyone ran into this issue and was able to solve it. It seems like FLIRC is catching infrared events that the Harmony hub is sending to the TV or the Receiver, and then sending some keypress to the HTPC, and the HTPC is waking up on any keyboard keypress. Eventually, Kodi's idle timer will suspend it again. Here's the problem: when I turn OFF Activity 2 "Netflix", the HTPC turns ON for some reason. the subtitle button may not have anything assigned to it for the panasonic device).
#WAKE FLIRC HARMONY OPENELEC PANASONIC SOFTWARE#
It also works fine, turning on and off just works. Device: TC-P65VT30 or Manufacturer: Samsung Device: LN46C650L1F Using the harmony software or, ensure all buttons have something assigned to them (e.g. This activity does NOT include FLIRC in it it only controls the TV and the Receiver. This setup works fine: HTPC suspends and wakes perfectly.Īctivity 2 is "Netflix", launching my smartTV's Netflix client. The only nuisance, is wake-up from sleep.
#WAKE FLIRC HARMONY OPENELEC PANASONIC WINDOWS 10#
I have just set up an HTPC on Windows 10 with a Zotac ZBox Magnus EN1060K. The FLIRC device in Harmony is setup to "Turn off when not in use" 18,640 1 I’m hoping someone has a trick to this. I did this because I use some custom script that gets triggered by F12 and check if it's OK to suspend, and later trigger suspend. For power off, I used the programming utility to map to the "F12" key. In Harmony > Setup > Devices > FLIRC > power settings, I use "Use two different buttons", and using FLIRC's programming utility, I mapped "AspectRatio" to the "wake" event. I am getting a lot of Button already exists errors as I try and record my remote.
#WAKE FLIRC HARMONY OPENELEC PANASONIC FULL#
I am also using the full keyboard mode in flirc. I want to do this as I want maximum flexibility to map as many things as possible. Overall, it works great but there is one annoyance thought that I could not work around after I added more than one "Activity" to the Harmony Remote. I am using a Harmony 650 with the device set to MCE keyboard. I use it to control the HTPC (Kodi), the Smart TV and my Receiver. The remote is a Harmony Hub with the simple RF remote (they call it Harmony Companion these days). The FLIRC SE is only connected to USB - without the connection to the Power Supply, as I only need it to wake the HTPC from "suspend to RAM" (S3) state, I don't need it to wake the HTPC from S5. This build has been working great for a year now. The Flirc is a little USB infrared receiver that outputs presses on a remote control button as keyboard input to any app such as Kodi. One small thing though, lately i've seen that Plex already does what i did in my autohotkey first script, so that one isn't really necessary.I"m using FLIRC SE, with a linux-based Kodi HTPC build (mini ITX fanless etc). Hope i answered your questions :) if you have any others, feel free to ask.
#WAKE FLIRC HARMONY OPENELEC PANASONIC CODE#
FLIRC will save the code as one that should be converted to that specific keystroke combination. The process of normally "teaching" the FLIRC which infra-red code does what is pretty easy, you just click the keyboard combination from FLIRC's software, and then press the remote's button to send the infra-red code. The last thing is setting up your harmony remote with the infra-red commands to send to FLIRC, which is configured to send them as keystrokes to the HTPC. if you want, i could probably share my FLIRC configuration file with you when you get your device. What this small USB device does, is receive infra-red codes (from the harmony remote) and convert them to pre-configured keyboard combinations (through the FLIRC software). you can get one through ebay for instance: The strokes are sent to the PC (or your HTPC) through the FLIRC device. I hope i got what you're asking right, but the autohotkey scripts (which assign a keyboard combination to let's say start Plex) are being triggered by keyboard strokes.
