eric wrote:To send the repeat command you might have to rename it in the .rem file (remove the "@"). Then you will be able to access it directly.
Ah, I see. Does this trick apply only to the ASCII client, or also to the Shared Library?
Unfortunately, modifying the .rem file isn't that easy as I don't run the server on Linux, but address the IRTrans device directly. (In Windows, I have the server running, but there's no shell environment (at least none that I understand ) to use with the ASCII client). So I would have to reflash the IRTrans device, which would make it incompatible with iRed, and I don't want that, because this is my working reference point … This gets all terribly complicated, so I'd really like to try with the Shared Library – can you please make IRTransDLL.c available somehow (update the archive or email me)?
Did you try using iRed as a IRServer? What I'm thinking about is: What happens if you use the ASCII API to tell iRed to send commands.
I'm not aware that iRed is accessible via an ASCII API. Even if it were, this would be no lasting solution, as my Mac isn't running all the time, only the Linux server is.
Uli