Nathan

Does the Flirc and the MCE combined have all the buttons you need? If so, you could always add both in the activity, and then edit them in the button editor. I'm not sure if I understand what you mean when you say you can't program or erase them. Is dragging and dropping and erasing not working in the button editor?

Yep, we definitely need to get that added in officially.

Couldn't even find the SVS Pro in the Harmony remote list. Not to worry though. If you are getting a Flirc USB, we'll be able to use that to generate the codes, if we haven't implemented learning in the remote yet.

Follow up. Could you tell me the name of the actual radio being controlled?

Presumably you don't have a Flirc USB, right?

There are actually 2 ways to do this. One's easier but less clean. The simple way is to just add the Roku 2 to your activity that also has the Roku Streambar, then drag the back button onto your remote. If you don't like the idea of having two Rokus listed, or have hit your 8 device cap, add the Roku 2 to another activity, then export your Remote Configuration, open it with a text editor, and copy the back button from the Roku 2 to the Streambar list. Then re-import. It'll look kinda like this: {"label":"BACK","key":"15","signal":"0000,006D,0022,0022,0155,00AD,0015,0015,0015,003F,0015,0015,0015,003F,0015,0015,0015,003F,0015,003F,0015,003F,0015,0015,0015,003F,0015,0015,0015,0015,0015,0015,0015,0015,0015,003F,0015,003F,0015,0015,0015,003F,0015,003F,0015,0015,0015,0015,0015,003F,0015,003F,0015,0015,0015,003F,0015,0015,0015,0015,0015,003F,0015,003F,0015,0015,0015,0015,0015,003F,0015,05C0,0155,00AD,0015,0015,0015,003F,0015,0015,0015,003F,0015,0015,0015,003F,0015,003F,0015,003F,0015,0015,0015,003F,0015,0015,0015,0015,0015,0015,0015,0015,0015,003F,0015,003F,0015,0015,0015,003F,0015,003F,0015,0015,0015,0015,0015,003F,0015,003F,0015,003F,0015,003F,0015,0015,0015,0015,0015,003F,0015,003F,0015,0015,0015,0015,0015,0015,0015,05C0","code":"0000,006D,0022,0022,0155,00AD,0015,0015,0015,003F,0015,0015,0015,003F,0015,0015,0015,003F,0015,003F,0015,003F,0015,0015,0015,003F,0015,0015,0015,0015,0015,0015,0015,0015,0015,003F,0015,003F,0015,0015,0015,003F,0015,003F,0015,0015,0015,0015,0015,003F,0015,003F,0015,0015,0015,003F,0015,0015,0015,0015,0015,003F,0015,003F,0015,0015,0015,0015,0015,003F,0015,05C0,0155,00AD,0015,0015,0015,003F,0015,0015,0015,003F,0015,0015,0015,003F,0015,003F,0015,003F,0015,0015,0015,003F,0015,0015,0015,0015,0015,0015,0015,0015,0015,003F,0015,003F,0015,0015,0015,003F,0015,003F,0015,0015,0015,0015,0015,003F,0015,003F,0015,003F,0015,003F,0015,0015,0015,0015,0015,003F,0015,003F,0015,0015,0015,0015,0015,0015,0015,05C0","ir protocol":"PRONTO"},

Right now we suggest just adding your HDMI switcher to one of the unused buttons on the activity. So if Playstation is on HDMI 2, you assign HDMI 2 to the 2 button on the remote in the playstation activity, flip over to that activity, and hit the 2 button. Recalling and updating states is planned.

This should have been fixed with one of the recent beta updates. Have you tried updating and trying?

You have not said what device the enter button is supposed to work with, making it trick to start figuring out what's wrong. Just a guess, but on some TVs "Cursor Enter" is the correct button and should replace "Enter."

I think there are a few issues with WINE. In particular we distribute an msix instead of a standard exe. May also be USB problems. That said, Steam Deck can dual boot windows, can't it? Could always install an unregistered version of Win11 on your steam deck and run from there.

Yep, we've figured out there was a batch from the 21st that got screwed up. You should see progress shortly (or we may need to update shipping, in which case also keep an eye on your email if we have to update shipping on pledge box).

I think this could be doable. Right now we already have a way to export your settings into a .skip file that shows the commands after "label":. Stripping out everything except those commands, the model, and the brand, and putting a little formatting in should be pretty doable. We can put it on the list, but we definitely have some other priorities that are currently higher. I'm actually wondering if this might be something the community would be interested in doing. A script (maybe even an open source script!) to read and print out a human readable skip file could be right up the alley of one of our more tech savvy users.

Simplest fix, at least for now, is to correct any issues with the Flirc app, while reporting his issue in this sub-forum. https://forum.flirc.tv/index.php?/forum/101-supported-devices-databases/

The admin tab can cause a LOT of problems if you don't know what you're doing. We want to make opening that up an intentional decision. With regard to moving a remote over from one Skip App to another, right now the Skip App not recognizing the remote is the expected behavior. The remote doesn't carry all the data to re-create a setup. Instead, you should go to the remote tab, export a *.skip file, and import that file into the new software. Keeping a backup skip file handy is always a good idea until we've implemented setup versioning. If exporting is crashing the app, make sure you're on the latest beta and report with a log to the beta thread.

If they're pronto codes, we can make a new device using those. Feel free to list or link them here.

We're eventually planning on implementing long press, which will give each button two commands to send. Until then, you could put the alt commands on a second unused activity, if you have one.

Is this the Shield that can accept IR? If it's a more recent Shield, they don't have IR input and you need a Flirc USB.

I think there are about 900 early bird backers. Of those, about 800 have shipped. I expect the remaining few should go out fairly quickly.

Please PM me your order details and I can look it up.

Yep, as @Benjamin Metzlersaid, plan is to make it possible to add more activities with existing buttons for those who need more than three. Can't give any kind of date for when that'll happen, but it's one of our top items in the roadmap.

That firmware thread includes discussion about all the firmwares, not just .11. The only posts directly related to the current release are the last two. Evidently the Skip App crashes on some machines when using .11. Seems fine on mine, no crashes here, but I believe a new beta is already being put together for those who have a crash.

Likely just a bug. You can update the remote firmware here with what should be a fix:

I've been on that page more times than I can count, and I've missed this mistake every single time.

At this point we've either shipped or are in the process of shipping all Early Bird pledges. Our plan is to follow that with Kickstarter Special pledges, and then the remainder. The pause from Windows screwed up the flow and will likely result in a delay of specials and remainders.

First suggestion is to doublecheck and make sure the remote is still correctly setup. Second is to make sure the batteries are good.