Why only 3 buttons per action?

[Pete Zaparti]

Any reason that device's action can only be assigned to 3 buttons?

I'll explain what I'm trying to do. I want Activity A to be "my receiver as a hub". My receiver has a lot of devices plugged into it, so for Activity A I want the TV to use HDMI 2, and my number pad chooses the inputs on the receiver. For each number, I want to have 2 actions:

TV - Input HDMI 2
Receiver - Input # (where # is the number pressed)

The problem is that the TV's Input HDMI 1 can only be assigned to 3 buttons. After that, I can't drag it to any more numbers.

Why do I want it to work this way? Because there are other activities where my TV is not on HDMI 2, like when I'm using the TV tuner to watch things over the air, or when I use HDMI 1 for my PC. So no matter what inputs are currently set to, I want to hit A and then a number and have the TV set to HDMI 1 and the Receiver to that input number. I'm trying to use the macro actions to minimize the buttons I have to press to switch all these inputs.

If someone has a better approach that they've configured their Skip 1s for, I'm all ears.

[jason]

It’s a soft limit. We just need to figure out how to handle the ux. I’ll prioritize this. No technical reason. 

[Pete Zaparti]

Thanks Jason. Btw, this is my first time coming back after using the Skip 1s for a few years to try out a new config, and I just wanted to say thanks for all your hard work. You were helpful last time I posted here, and now you're being helpful again. Much appreciated!

 

[Pete Zaparti]

Update: In the meantime, I was able to get what I'm trying to do by just editing the JSON. It's nice that the configs are JSON btw! Makes it easy to parse what's happening under the hood.

[jason]

11 hours ago, Pete Zaparti said:

Thanks Jason. Btw, this is my first time coming back after using the Skip 1s for a few years to try out a new config, and I just wanted to say thanks for all your hard work. You were helpful last time I posted here, and now you're being helpful again. Much appreciated!

 

Thank you, really means a lot.

 

10 hours ago, Pete Zaparti said:

Update: In the meantime, I was able to get what I'm trying to do by just editing the JSON. It's nice that the configs are JSON btw! Makes it easy to parse what's happening under the hood.

I was going to suggest this, I wasn’t sure how the GUI would react though. That’s great. Nice job!

Yes, that was the plan. Even when it gets sent down to the device, it does it as a smaller form of JSON called CBOR. You can go back and forth. I don’t keep all the data though, just the buttons because I have bytes of memory.

[Pete Zaparti]

The GUI reacted very predictably IMO. The colored outlines on each button reflect the actions I copy-pasted in the JSON, and the popup from clicking each button includes all of those actions, and they can be reordered or trashed, just as if I had added them in the UI. Pretty straightforward.

-----------

Anyway, I'm liking the results! All of my configurations are now a combination of 2 buttons, the activity and then a number.

(the numbers here reflect the order of inputs on my receiver remote)
Play retro games - A2
Play Nintendo - A3
Play Playstation - A4
Watch Apple TV - A5
...a few more
Watch TV Tuner - B+RECORD (numbers are needed for this activity)
Play PC - C1 (my PC has to be plugged directly into my TV for a few nitpicky reasons)

Each of those macros sets the appropriate inputs for the TV and the receiver, but first includes POWER ON, which basically do nothing if the devices are already on, and I changed the power button to only POWER OFF devices, no matter what state things are in.

A little weird? Maybe, but I'm liking it. To help remember that list ^ I'll print it for the coffee table or maybe even tape a list to the back of the remote.