galante2123

Ed - I understand the frustration all too well trust me ;) I completed all of my changes on the command line, so I can guide you through the changes in that manner. First can you SSH into your device? I ask because you need to check if the add-on you installed in fact installed and dropped the correct files into the proper location. Also you will need to be able to add a udev rule to your device if you are running a Linux based machine (where the actual Flirc device will plug into). The udev rule you need to add is made to auto mount the usb for read and write access and this is just a work around. The udev rule is simply a file that the Linux system looks at while loaded the OS and applies the "rules" each file describes. You can see the actual code from the github repo here: https://github.com/flirc/flirc-xbmc-plugin if you look in the folder marked linux you will see the file that has the generic udev rule you need to create. Its one line of code: SUBSYSTEM=="usb", ENV{DEVTYPE}=="usb_device", MODE="0666", GROUP="pi" You put that in a file in the /etc/edev/rules.d directory and then reboot your XMBC device and you should be all set. You may have to reselect the Windows MC contoller, but I only say this becasue this is what is selected for mine. This was my missing piece to get the whole thing up and running. You will need to do this step to get your RaspBMC device to see the Flirc usb. Once you add this on you next reboot you should see it as "connected". If you installed the add-on by adding it as a source and saw the gui for the Flirc device on reboot then you may already be up and running after adding the udev rule. Once I added the udev rule the gui popped up for me on my RaspBMC and wanted me to prgram a device as well. I happily followed the on screen setup and programed the arrows, a back key and enter key. This is not needed and I realized that when it then asked me to save my configuration. If you have the add-on you do not need to physically program the device, if you can get back to that gui on your XBMC unit on the left menu you can "load a configuration" this is what you want. The add-on has a pre-programmed config file and when I selected the load option I was only presented with one option, once selected I closed the Flirc gui and have been good to go. Let me know if this helps, or sounds "unclear". I have been writing this as I have been working on some code between tests ;)

Turns out the flirc-xbmc repo was infact all I needed here. I added the src files to the .xbmc/addons section and added the udev rule as well. On the reboot of the Rasbmc the Flirc gui was started and I was good to go. I am still not sure if I actually needed to program the up, down, left, right, enter and back keys but I did. I did then load a configuration which pointed by default to a flirc config and in the end the system is up and running. Hopefully this helps someone else out in the future. Now on to the long press configurations to see if I can get these working.

I have been through these forums all day and I feel like I am still missing something. I connected my Flirc USB to my Windows 7 box and installed the GUI, then forced the firmware update to v2.2. This failed once and the GUI just hung for about an hour. I closed and finally got the firmware to update to v2.2. Next I connected to myharmony.com and added the Flirc and XBMC profile and set up the activity to switch my Sony Reciver to the proper HDMI and my TV to the proper input and ofcourse use the Flirc XBMC device. I synced and then plugged in the USB and rebooted the Raspbery Pi sporting the RaspBMC OS. I then tried to use the remote and it would not work. So then I went into the RaspBMC settings and enabled the IR Remote feature and selected the Windows MC defaults I believe. I was hoping to see a Flirc profile to chose from but there is not one. I rebooted the unit and got a LIRC prompt on the bottom right that said a config was created successfully. Tried the remote again, still nothing. I am stuck, not sure if I missed something or what. I saw may mentions of the git repo for XBMC but due to it age and the dates on the commits I am not sure it is something I need or what. Can anyone walk me through this process to matbe see where I missed a step?