sasaba
-
Posts
15 -
Joined
-
Last visited
Posts posted by sasaba
-
-
I have been experimenting and it looks like you can manually add new commands to the Harmony Flirc profile just like other Harmony profiles. I was afraid that if a remote button was mapped to a command/key in Flirc using the GUI or CLI that the new configuration would completely override the firmware default mappings that the Harmony profile relies on but it appears to not be the case.
I have been able to add new commands/codes to the Harmony Flirc profile from within MyHarmony using the "add a command" function under Devices or Buttons which allows the Harmony to learn new codes from another remote. Then I use the Flirc GUI or CLI to map the new button/code to the key/command I want Flirc to send. An example is that I created a "Wake" command in the Harmony Flirc profile and learned the power on code from another remote to the Harmony. I then went into the Flirc CLI (also was able to repeat with the GUI) and recorded this new Harmony button to the "Wake" key. All the other default commands remain active and the keys command in the CLI just shows the new keys added. I hope this make sense (maybe everyone already new this) because it allows the use of the current Harmony profile to generate the majority of your Harmony commands and you only have to add the missing ones instead of trying to come up with another good base remote profile like the "Panasonic TV" remote etc. Overall I think that there will be less commands that need to be added. I guess basically this is a composite of the two solutions for setting up a Harmony remote. Along with murkyl's post above this appears to open up a whole range of customizing possibilities w/o having to start from complete scratch on the the more basic/common commands.
I have not tried to assign a button that is sending an existing/default Harmony profile command/code to a new key/command in the Flirc GUI or CLI (like ContextMenu to key "M" instead of "C") nor have I tried to create a new Harmony command/code and assign it to an already existing default firmaware key/command (like Home to "Back").
-
OK, so I found another way to access the shutdown menu from the skin and I can always manually wake my HTPC by pushing the power button so not a lost cause it just leaves things to complicated for my wife to run unfortunately. Aslo I think the poweroff command in the Flirc profile does not work because I am using Frodo and it looks like this profile is based on Eden and I think the keyboard commands changed with Frodo for this function. I will hope that these features are added eventually and in the meantime consider changing back to the non-Flirc profile method. Besides wake and sleep I would also recommend adding Esc in the future as well. I also wonder if possible now or in the future to combine the built in commands from the Harmony profile with adding additional commands or overriding some commands from the Flirc GUI or command line utility programs.
-
Let me add to the above post that I am using the latest V1.0.0 RC2 firmware and I understand that is is not considered a stable release and that the Harmony profile is not considered fully functional so if there is not work around at this time that is fine. Overall I think the Flirc hardware and software are heads above anything else available, thanks for all the work and support.
-
Is there anyway to get the custom Flirc device/profile for Harmony Remote to be able to wake and sleep the computer with single button presses. I understand that not all possible commands are implemented in the Harmony device profile at this point but it seems given the new firmware with one of its main features being a wake command that this would have been an obvious command to implement in the Harmony profile. Shut down or sleep can be done through XBMC menu selection I guess although that can take several steps depending on what skin you have and may not be possible at all, again depending on the skin setup and the current available Harmony commands. For example I have Openelec with Frodo 12.2 and Transparency skin and the only way I know to shut down or sleep the system is with the "S" key (shutdown or system menu) or Ctrl+end (exit XBMC) both of which are not available in the current profile. As far as waking, again there is no wake command and if I do not implement this feature then with the new firmware any remote key press will wake my system whether programmed into Flirc or not. See my previous post
-
I am using the same remote. I set Aux to a Panasonic DVD code in the hopper remote menu (something I knew would not be duplicating codes to any of my other equipment) but only a few of the keys would work. In the end I had to go back into the the hopper menu and learn codes to most of my keys from old remotes I had laying around the house. It took a lot of trial and error to get all the keys to work without duplicates plus sometime flirc would say the key was already in use even though I knew there was no duplication so I would have to relearn the key to another code. It was a hassle but I finally got every key to work.
-
1
-
-
Initially I created 52-flirc.rules in storage/.config/udev/rules.d as etc/udev/rules.d was not accessible from my Windows 7 laptop using network access. Openelec documentation said to put udev files in the storage/.config/udev/rules.d. Assumed access was granted as root as no other login created (again forgive my poor knowledge on what is involved in accessing a linux os form Windows) but later after things did not work I tried ssh (via putty) and logged in under root. When I went to etc/udev/rules.d it actually pointed me to the storage/.config/udev/rules.d dir and would not allow me to create anything directly in the etc/udev/rules.d dir.
I am using openelec x86_64 v3.0.6 on an Intel Nuc unit with a Celeron 847 1.1 ghz processor. Here is the link to the XBMC log file:
http://xbmclogs.com/show.php?id=35931
and you will notice that the generated libraries path is Linux/86_64/libflirc.so not Linux/i864/libflirc.so or any other valid libraries path as I had supposed above. Can I just create a 86_64 dir and copy the i864/libflirc.so to it?
-
I wondered what the Group="pi" bit was but no it does not make any difference. After removing and rebooting still says "Libraries not found", as well as then after uninstalling and re-installing says the same thing and then after rebooting again says the same thing. Have been been installing via repository in XBMC after loading zip of repository.
This is my first time trying to use a Linux based system (openelec) so can't guarantee am doing everything right. One thing I noted was that the 51-flirc.rules file actually ends up in the /storage/.config/udev.rules.d dir as the /etc/udev/rules.d dir appears to just be a pointer to this dir. Also even though I am no programmer and definitely don't know python the little I can infer from the error and what I can make out in the scripts is that for some reason the script is unable to get pointed to the correct library file for the openelec system, which I assume should be Linux/i686 (since I am on a Nuc system with Celeron processor), or there is no correct library for this combo, and that this does not really have anything to do with recognizing the flirc device at least at this point. I admit I could be way off.
-
Created the above 51-flirc.rules file (copied text from post above and checked against readme file), uninstalled and re-installed the plugin (3x) and rebooted the system (3x) and still get the same error saying files missing, re-install.
-
I have the same problem when loading the plugin on a Nuc with openelec. Loads from zip of repo file but when launched says missing files reinstall. I noted in the official announcement for the plugin Jason says for Linux os needs udev entry or something like that but have no idea what that is or if it is related, I am new to any Linux systems.
Flirc XBMC Addon
in XBMC Plugin
Posted
1.0.1 loads fine and appears to work with Openelec 3.1.7 X86_64 although have not done any extensive testing. Thanks much for the the update.