I have the same setup with the Redeye Pro and I have managed successfully to interface the Roomie Remote with it. The solution I have works exceptionally well, for the most part.
The Redeye has an external API that an outside controller can use to control the unit – it is described in its Advanced Programming Manual. As such, what needs to happen is that the Roomie must send a set of IP (http) commands to make the Redeye control a device, launch an activity etc. In this regard, the Redeye has some major pluses. First, the IR learning in the Redeye is pretty good, and it is easy to set up and store the IR commands for any new device – their device library is not that great in my opinion. The Redye also allows multiple controllers to attach to the device and tracks state, so you do not have to worry about some IP controlled devices (like the Tivo) which fail if more than one Roomie try to control it simultaneously. As such the Redye provides a seamless gateway for doing all this. The biggest negative with the Redeye is that for a device with 2-way serial control, you have to write all the scripts to monitor feedback. To avoid doing that, I recommend using the iTach serial to control the device and have both the Redeye and the Roomie talk to it – the Redeye to send the initiation/termination commands and the Roomie to monitor feedback, set volume etc.
The easiest way to actually BUILD the Roomie interface to the Redeye is to use the Redeye’s commands for introspection where it can tell you its devices, commands etc when you send it certain http commands. If you get this list, what you can do is to create a Roomie device file that essentially sets up a bunch of Redeye devices that are immediately available then to the Roomie. These devices would include of course the various components controlled by the Redeye, along with a separate Redeye device to lauch the vaious activities. One you have the Redeye devices in your Roomie device list, you can go ahead and configure the Roomie remote as usual. The major difference is you no longer rely on Roomie’s IR database and only rely on its user interface. Any command sent from the Roomie is interpreted by the Redeye which sends the appropriate commands to the device controlled in question.
The process above is much simpler than it sounds. Virtually all of the work to create the Redeye devices, commands etc can be automated with simple scripts in Python. I have done so, and can generate my Roomie front-end to the Redeye backend in a matter of minutes. And when it all works (which it does most times…with some occasional hiccups) it really is the best control system I have yet worked with.
And by the way, where it comes to the Redeye, I should point out that the device really is an outstanding product. It can do a lot of things at a price point that is remarkable. While its user interface is less than stellar it DOES manage to reflect device state successfully across ALL control panels which is something that Roomie cannot really do except somewhat with iCloud integration. If Roomie provided the user more control of the interface (multiple screens per device, better layout control etc) and if someone made a hard button iPod/iPad embedded remote that is user programmable (not Savant which restricts its overpriced remotes to its own hardware) I think we could be in home automation Nirvana with the Roomie/Redeye setup.