@Cayprol in my opinion it's more an issue with OS than with Flirc itself. Flirc just sends a key press according to a HID standard. It's up to the system to interpret it and act on it. Maybe there's some setting in the Mac OS itself you need to change. I don't know Mac OS. Maybe @jason will know something, but he's currently heavily preoccupied with his family matters (mostly by new baby).
If the hardware itself supports waking by USB devices then it should work out of the box. The feature is also software controlled so OS also needs to properly configure the motherboard when going into suspend to allow waking from USB (this usually happens by default unless there's some incompatibility between operating system and the motherboard hardware). You can test if the wake up function does work at all by connecting an USB keyboard and going to suspend mode. You should be able to wake your PC by pressing a key on the keyboard. If this doesn't work for you then Flirc also won't be able to do that. There may be an option in the BIOS/UEFI you need to enable. If you are able to wake your PC using USB keyboard then it also should work with Flirc. The old Flirc (the clear plastic one) may need some configuration. Open Flirc GUI and go to File menu and Advanced. Make sure that the Sleep Detection is checked. When it's checked then there are two modes of operation. By default Flirc will wake the PC upon pressing any remote key known to it (like I've mentioned in my previous post - this means any key that is recorded and recognised by Flirc). You can change that by going to Full Keyboard controller in Flirc GUI and recording the WAKE key. When the WAKE key is recorded, only that key will wake the PC. At this moment, the new Flirc (the metal one) has wake function enabled by default and supports only waking up by any known key. The WAKE key feature is going to be implemented but I can't tell you any time frame when will that happen.
Do you mean a guide on how to enable suspend/sleep in your OS? Or a guide on how to enable wake up using Flirc? For new Flirc (the metal one) the wake is enabled by default and it should wake on any known remote key press (any key you've recorded in Flirc GUI).
You can keep your HTPC in a suspend mode. Either suspend to RAM (sleep) or suspend to disk. Any Flirc is able to wake your PC from suspend modes. It's up to you to set your OS to properly use suspend modes. USB by default doesn't support turning the PC on from full shutdown (there are some exceptions but this depends on the manufacturer, I don't know if NUC supports this). Flirc-SE has additional connections (besides the USB) to the motherboard's power switch connector and is able to emulate pressing on the physical power button. That's why it is able to do this on any motherboard.
I don't think so. Which Flirc do you have and which remote control? If it's an universal remote, then what device profile are you trying to use? It's important to know, that Flirc's IR receiver is really sensitive and you should not point your remote directly at it from a short distance during recording, because the receiver may receive overdriven signal which can be misinterpreted. You should either record your buttons from some distance or point the remote in a different direction (for example at the ceiling). The signal will bounce off a ceiling or walls and will go back to the receiver with much less power.
There was never a sensitivity setting. You're probably referring to interkey delay setting. It's still supported for Flirc v1 (or 1st gen: Flirc USB in plastic cover and Flirc SE). For Flirc v2 (or 2nd gen) it's not supported anymore as the key repeat detection algorithm has been changed so that setting isn't needed.
There's nothing Flirc can do about that. It's an operating system's feature. I don't know Mac OS so I can't say for sure, but I don't think this is possible. But you can look into some OS power settings or something like that.
Since Kodi 16, Context menu is accessible by long pressing the Enter/OK key. Also it's not that hard to record the C key on the full keyboard controller in the GUI. As this issue wasn't critical in any way it probably got lost between other, more pressing issues. Anyway, I'll ask @jason if he could look into it.
One more post to clear some things. There's no "software keyboard" mode in Flirc. What you're referring to is probably that you've selected the Full Keyboard controller in Flirc GUI. Switching controllers in the GUI doesn't do anything besides changing the view in the GUI. Controllers are just different views. Both Full Keyboard and Multimedia keys controllers give you access to all the keys. All other controllers (with some small exceptions) are just something like wrappers on full keyboard and multimedia controllers. They just provide preconfigured key combinations for specific applications or hardware. But they are still sending keyboard keystrokes. You can switch and mix keys from different controllers anyway you like. I think the issue you have is with the "Power Off" key. You've probably set your "Watch a Movie" activity in a way that when you exit that activity the remote sends the power off command. Maybe it's also being sent on entering other activities which causes your PC to turn on (as explained earlier, right now any code recognised by Flirc will wake the PC). So when the PC is up, the power off will turn it off, but when it's already off the power off key right now will turn it on.
@GregL you need to give more information on your setup. What Harmony profile do you use with Flirc? Do you use one of the Flirc/* profiles on Harmony or something else? Did you use Flirc GUI to record the remote? I see that you are little confused when it comes to how Flirc operates. First of all, Flirc is a device which emulates an USB Keyboard. It maps signals from remote controls to key or key combination (key + one or more modifiers like alt, shift etc) presses. You use Flirc software to record the signals a remote sends and map them to specific keyboard keys. Flirc has some built-in profiles which are hardcoded and they work out of the box with Harmony remotes. To use a built-in profile you need to select one of the Flirc profiles in your Harmony (for example Flirc/Kodi). This means that there's some amount of predefined IR signals which are known by Flirc and they are translated to specific keyboard key presses. If you don't use one of the Flirc/* profiles in Harmony, then you need to use Flirc software to map your remote to specific keyboard keys. Now to answer your questions: Flirc is not classified as a mouse, so this is not something you should worry about right now. Every action Flirc does IS a keyboard keystroke. Flirc doesn't do anything else at this moment. So for any signal that Flirc recognises (one of the built-in or recorded ones) it sends a key press to the system. Like @jason has already said, the option to limit keys which are allowed to wake will eventually be available, so you need to wait until then. For now make sure you don't send any signals that are known to Flirc if you don't want to wake/turn on your PC. So don't record a signal that is sent when you press Watch Movie activity. Flirc won't turn on your PC if you send a signal that is not recorded in it.
@KenJs unfortunately there's no timeline yet on when that feature will be implemented. There's still no consensus on how the blaster will be accessible to the OS and apps/scripts. @brunoland I've already answered your question about that in a different thread about a month ago: http://forum.flirc.tv/index.php?/topic/2393-new-features-for-the-old-flirc/&do=findComment&comment=13015