[Feature Request] Unique ID per button for more scripting flexibility

[yukimizake]

Hi,

As a user of companion in a heavily scripted environnement, I would like to be able to move buttons on my Streamdeck without having to edit the button position in my scripts http calls every time.
Being able to call a button press with a unique identifier (such as a uuid) rather than the button position may be a solution.

Exemple for a HTTP action : /press/uuid/8c00cb3f-1d31-4505-ad49-5bb812aeb4d2
This uuid being shown in the edit button page, and generated when creating/copying a new button, but not when moving one.

Thanks for your work!

[Julusian]

This is something I have been thinking about, but becomes quite a large overhaul of some internal structures.

In my mind, there should be a single list of all the 'button definition', which is then referenced by one or more buttons in the grid. This will provide exactly what you want as each button will have a unique and static id, as well as allowing for the common case of wanting to duplicate a button across pages which will use the same id to tie a button to the grid

[willosof]

Cool idea! We should put it on the list for the next major :)

[Julusian]

#2138 is about adding user defined aliases for buttons, to be able to reference them by a persistent friendly id.

Once that is done, should we expose every button by their internal ids, or if we should require buttons be 'exposed' to the apis by giving them an alias.
This falls into some other ideas I have on rethinking the apis, and providing some kind of security in them.

I don't know if that will make it too hard to use these apis sometimes, but it may be no worse than being forced to address buttons by unpredictable random ids. The benefit of allowing only by aliases is that its a low cost/complexity way for users to limit what can be triggered remotely, while also ensuring the protocol uses meaningful ids