Jump to content
Flirc Forums

atlasgrudge

Members
  • Posts

    2
  • Joined

  • Last visited

atlasgrudge's Achievements

Newbie

Newbie (1/14)

0

Reputation

  1. Thanks for the reply. I'll give that a try and let you know how it works out.
  2. Just wanted to say thanks for a great product. My apologies for the long post. This is kind of a feature request/bug report of sorts. More than anything I'm sure the problem lies with the myharmony app, but I'm hoping you find this worth reading and can come up with a solution. I have run into an issue that I thought should be brought to your attention. I recently purchased a Flirc and a Harmony 650 for use with an HTPC running XBMC. The biggest motivation for me in purchasing these products was that I have an older tv that has some HDMI handshake issues with my AVR. Everything works, but only if I turn it all on in a certain order (htpc first, then avr). If I turn the avr on before the htpc, then my screen will basically flicker between on and standby every 5-10 seconds. For that reason, I purchased a Harmony 650 with the intention of using its activities to make powering everything up in the right order as simple as possible (especially for my girlfriend). While trying to set this up, I noticed an odd issue. After setting up my remote with flirc for use with xbmc, and even getting so far as to configure fully functioning buttons for putting my htpc to sleep and wake it, I then went to create the activity to turn everything on in order. I selected the flirc and my avr as the two devices to be used in this activity and instructed the myharmony app which input I wanted the receiver set to. Upon completing the creation of the activity, I tested it out and it didn't work. It turned the avr on, but not my htpc. I then went to customize the activity to see if there was something I could change to get the functionality I wanted and that's when I noticed it: in the table showing the activity startup commands, the only thing being listed as being turned on was the avr (the flirc was nowhere to be seen). Of course, I could add the flirc and the command that I had bound to wake the htpc up from sleep...but only after turning the avr on (the activity startup commmands has a default order of execution that can't be edited or reordered). This was the exact opposite functionality that I needed from this in order to avoid the hdmi handshake issues I mentioned. I then went and loaded one of the Panasonic TV profiles and configured all of the buttons manually with flirc, essentially following all of the same steps as before. But this time when I made the activity the myharmony app listed turning on the Panasonic TV (my htpc in this case) first and then turning on the avr. This was exactly what I was hoping to achieve. However, I much preferred how the htpc responded to controls from the flirc profile than from the Panasonic TV profile in regards to delays etc. I noticed that the flirc profile didn't actually have a command titled "Power On" and thought that might have something to do with it. So I grabbed an old remote and used it to teach an IR signal to my Harmony 650 with the intention of using it as a "Power On" signal. However, the original behavior where the receiver was listed as the first (and only) device to be turned on repeated itself. I've included screen caps of the flirc and Panasonic profile activity startup command tables so you can see what I'm talking about. Is there something inherently different about the myharmony Flirc profile as compared to the Panasonic TV profile that is preventing me from using it how I'm wanting to? Would it be possible for any changes to be made to the Flirc profile so that it behaves like the Panasonic profile does so it can get listed as the first device to be turned on?
×
×
  • Create New...