Jump to content
Flirc Forums


  • Posts

  • Joined

  • Last visited

  • Days Won


Posts posted by Chris!

  1. We've probably got the key mapping wrong.

    Delete the key you assigned: https://flirc.zendesk.com/hc/en-us/articles/203653385-How-to-delete-a-key-from-Flirc

    The go to the keyboard controller: https://flirc.zendesk.com/hc/en-us/articles/202923419-Controller-presets-in-Flirc-GUI

    Then record the correct keyboard key, here's kodi's list of keys: http://kodi.wiki/view/Keyboard

    (is it "s" key you want for the shut down menu?)

  2. Are you referring to this article?


    For example, if you wanted to record the ok button on your remote twice:

    1. Press "ok" in the flirc gui, then press the enter button on your remote. The GUI should then say "button recorded" (or something similar)
    2. Then repeat step 1 again, the gui will say either "button recorded" again or "key already exists"
    3. Repeat step 1 once more and you should get "key already exists"


    You will need to do this for each key that is being recorded twice.

    By doing this we are telling flirc that the remote sends one of two signals for the same key press (e.g. ok), but we want flirc to respond the same.


    Does this help?



    No customer should have to wait for a previous firmware to be emailed to them or something. Its like when you build you own pc from parts purchased and you upgraded to the latest firmware provided by say the motherboard manufacturer and it breaks your system, that you can't download the previous release your working motherboard was using and then reload it until their issue gets fixed but are stuck with the issue the new firmware caused until someone gets the time and resources allocated to get the issue fixed thus frustrating your customers even further. So far i have not found a location to download any previous versions or just point me to the right location where its at?


    For Flirc, I think the current model for firmware distribution is the most suitable.

    We used to have links for downloading old firmware but don't anymore, we have a beta releases so these bugs are usually worked out before they get send to everyone.

    There are many drawbacks for the Flirc project having multiple firmwares floating about.



    But will you please also while doing so clarify if its a total write over or a merge of unused keys and override of existing keys programmed so everyone will know up front without making any assumptions like i been doing.


    Apologies. I'll clarify that changing controllers does not replace existing keys.


    The documents are quite new so I try to add in detail i've missed as queries come up - I do read every thread in this forum. Also worth noting i've only recently taken up writing help documents and I do this part time (in my spare time).

  4. Using Flirc is a lot simpler to use than you may think, most of the complicated stuff is already done. I've been spending a lot of time writing help documents as forum posts can get very confusing. I think they'll be very helpful for you so I've linked some appropriate ones (but feel free to read all of the help documents). The documents are by no means finished but I believe they're pretty good.

    First i see the various controllers and how they can be used to quickly set something up, however how are the settings actually saved to the flirc?


    As i was loading different controllers and saw what they offered, of course i was thinking on using the XBMC controller and wanted to save that profile but when i hit the Save Configuration menu item and dialog window prompt came up for saving the config to the local hard drive. So i stopped right there until i got some questions answered on exactly the steps needed to actually save any changes that were made to the flirc itself. My assumption here is that you make your changes and then click the save option which saves the file, then use the load configuration to go back to the same file just saved and load that configuration into the flirc?

    See how to program flirc:
    also see guide to controllers:
    The save configuration is for backing up you configuration or if you wanted to apply it to more than one flirc (without having to go through the steps on each flirc)

    Other than using their custom setup which requires to program it using some other remote it would be much easier and nicer from my point of view if there were more options available say with either adding to the existing logitech profile or creating an Advanced Profile that would have more keys mapped or user defined keys?

    Yeah, there are limitations to the profile, there is a discussion about it somewhere on the forums.
    If you open the flirc gui, go into the file menu then advanced settings. Uncheck the "built in profiles" then switch to the keyboard controller and program the letters you want flirc to send with each remote press.

    One other thing i noticed is that there is a option to upgrade firmware but no option to backup the existing firmware in case something happens during the firmware so if in that event you can reload the previous working firmware. Is there something hidden in order for the backup firmware to show up and also a load firmware button?

    Firmware is stored in the GUI, the GUI checks for updates and will notify you.

    • Like 1
  5. Predominantly going to be explaining flirc stuff, in theory there shouldn't be too much tweaking needed.


    Most of the recent articles in the zendesk are done by me (under Jason's name) as I have more time for doing it, unfortunately I don't know the nitty gritty of how the settings work so Jason will be writing those articles - he has a lot less free time than I do.


    I do I agree with you though and we are working on it. I've taken the choice to aim the help documents (at least to start with) toward less technical documentation - we will introduce a "technical section" though.


    Interkey delay is telling flirc how long to wait before sending another command to the computer (even if it receiving ir signals),

    Increasing the interkey delay will tell flirc to wait longer before deciding the button was let go. 

    Decreasing the interkey delay will tell flirc to wait less before deciding the button was let go. 

    Not sure if the numbers directly correlate 

  6. I'm not really picky on remotes so I have the cheapest harmony remote (~£15). 

    It allowed me to map the volume key to always go to my speakers rather than the tv, which is neat, others could probably do that.


    Any how, the main reason i'm commenting is I thought you'd be interested in having a quick read of our zendesk knowledge base - particularly the "getting started with flirc" it should give you a great overview:




    I had a fundamental misunderstanding of how to use the Flirc, I thought it had to be configured on the machine you intended to use it with.

    It is really nifty how it does that.




    I would note for anyone else who stumbles across this post that it would not have been possible for me to set this up using only the Mac Mini running 10.6.8.

    @Jason: What is the minimum version of mac flirc gui runs on? 

    (Is it also worth adding this to the download page? http://flirc.tv/downloads/)

  8. It should just work out of the box. I've just tried it on a TV remote I had next to me and it worked straight away.


    The most common reason for it not working is the remote doesn't continuously send signals when the button is held down... I've forgotten if that's the case with the Xbox 360 media remote. Maybe try another remote just to check this?


    If i've misunderstood and it is repeating but very slowly then you can ajust the inter key delay in the advanced settings in the Flirc GUI

  9. This is strange. I've just double checked using a Flirc I had nearby and it worked on my machine, we'll have to figure out why it's not working for you.

    Couple of questions:

    1. What remote are you using and which button isn't working now?
    2. What controller preset are you using the the flirc gui? (minimalist/keyboard/xbmc)


    When you open the Flirc gui app it should check for updates and flash up an update. 3.5 is the newest firmware that did resolve issues with certain remotes.

  • Create New...