blades

So, two more devices (the hub/cable and flirc) required to talk to something that's probably a fairly common A/V device that will cost more than the actual remote? I can't see that being a long-term solution, then, especially when it's asking a low-power/limited cpu device to do more work on top of that. And if there's no way to use the Roku, then that's pretty much one of my main two use cases dead in the water. I'll have to hope that there's a hub add-on or hub version of this remote in a future iteration, then, as it unfortunately looks like it's no good for my use cases. Shame, because it's a really nice bit of hardware :( Thanks for the info, though - at least I know it's not just me being an idiot :p

Leaving aside the issue with how you're supposed to find devices when it's only a bunch of generic groupings (maybe set up a wiki so people can at least add the list when they figure out to help other people down the line?) - how do I set up the above devices with this remote? My setups are fairly simple, in that there's an amplifier that does video switching and a tv with multiple hdmi inputs, and the main items used are a console and the roku stick and chromecast with google tv. However, I can't figure out how to get the roku or the chromecast working with this remote at all. Previously, I've had two harmony hub-based remotes and obviously the hub connects via bluetooth or via IP over a local network connection to control them. Any suggestions? Or do I have to wait for the inevitable hub add-on appears to be able to use this remote with those devices?

One thing that's really frustrating is having to add the same devices to each activity over and over again. This is particularly annoying when it doesn't work with the selected configuration (which can only be chosen at random because it's a group of devices and there's no way to figure out which group your device belongs to without trying it), so you have to go through each activity to remove and then re-add the device with the issues described above. Couldn't the app take the more versatile approach of adding and testing the devices in one section, and then assigning those devices to each activity instead?

Same issue here on arch linux - device shows up via lsusb, but the app doesn't recognise it. But a huge +1 for linux support.

Well, the password seems to be removed now which is nice. Managed to install it easily enough under arch linux, but it doesn't recognise that the remote's connected in the software even though it does show up as "Bus 001 Device 009: ID 20a0:0008 Clay Logic Skip 1s" with the lsusb command.