Get Macro Names

[Raiden38]

Would there be a way to add macro names to the variables list? This way, we could dispay the name of the macro on a button and then execute it when pressed using RunMacro

Would it be from “/eos/out/event/macro/”?

Thanks! :)

[Plobli]

I also need this feature!

[Plobli]

I build this feature in a fork. There is a new button preset available that show the name of a macro. Or you can use the text string $(etc-eos:macro_###_label) in any button label field to show the macro name. All 60 seconds the names are refreshed. You can use macros between 1 and 1500.

Fork: https://github.com/Plobli/companion-module-etc-eos

[Raiden38]

This is awesome thanks!

[peternewman]

PR from @Plobli as #70

[jamesrowe2003]

Hi,

This feature looks amazing! How do I add it into my companion? I have never added a custom module

[peternewman]

You should be able to use the pkg I've generated here until the code is merged and a new release made:
https://github.com/peternewman/companion-module-etc-eos/actions/runs/17878317900

Put it in your module-local-dev folder (or wherever you configured within the launcher).

[taste5]

Hey, thank you for your work! I would like to add it and followed the steps. Configured dev module directory and copied the pkg inside that folder. Is there anything else that I need to do for module discovery?
Any help appreciated.

Edit: I tried adding a second ETC-EOS module and this time I chose Dev Version in the drop down. But appereantly I cannot configure the IP. Instead I get an error:

Connection not found or running
No config data loaded

[peternewman]

Edit: I tried adding a second ETC-EOS module and this time I chose Dev Version in the drop down. But appereantly I cannot configure the IP. Instead I get an error:

Connection not found or running No config data loaded

I assume the second connection is enabled?

Can you look at/share the log from the second connection please? >_ maybe in the three dot menu.

You might need to do a yarn install to pull in the dependencies.

I think with newer ones, you can load the pkg into the web UI too, which might make some of that easier/more automated...

[taste5]

Hey thanks for your reply. Turns out I needed to run npm install for the dev module to work. yarn install failed on this on. I believe it was about dependency issues, but did not have the time to look inti it.

[NRossmann]

Thanks everyone for the interest and the work on this feature.

I’ve now taken over as the maintainer of the module. Support for macro name variables has already been implemented via the PR from @Plobli (#70), which adds macro label variables and related presets. Thanks again for the contribution — this is exactly the kind of improvement that benefits a lot of users.

At the moment, this functionality exists in the PR / development builds and has not yet been released as part of an official module version. My current focus is working through the existing backlog of issues and PRs to get everything into a clean, stable state before cutting the next release.

Once that’s done, this feature will be included in the next release, so users won’t need to rely on forks or development packages anymore.

For anyone experimenting with the dev build in the meantime:

Make sure dependencies are installed (npm install or yarn install, depending on the environment)

Ensure the dev module is correctly enabled and the connection is running before configuring it

I’ll keep this issue open until the PR is merged and released. Thanks again to everyone involved, and please feel free to help test or contribute as I prepare the next release.