Tesira: Custom Command

[mre74]

Hi

I have had some wonderful use of the Biamp Tesira module setting presets every week, since this module first was published. When setting the fader there is a need to also display the fader status. To save the status to a custom variable, I have tested the Tesira: Custom Command, but with no success.

For example: I created a custom variable "test" in Companion using a regular button with the button text $(internal:custom_test). In the button's "Press action"-property, I added the "Tesira: Custom Command" using the command "Level8 subscribe level 1 test 1000". This command worked when testing it in the Tesira Text Protocol Server using telnet, but I could not see the Tesiras level feedback in companions custom test variable.

What more beginner level information would be needed to start using Tesira: Custom Commands in Companion?

I am using this module as a volunteer every sunday at church. Tesira is standard equipment in my church community.

Kind regards Mattias Renman Göteborg, Sweden

[alextannenbaum]

I am also trying to figure this out! I can't figure out how to save the status to a variable. Does anyone know how to do this?

[AV-Phil]

@alextannenbaum & @mre74 - please see this thread;

https://github.com/bitfocus/companion-module-biamp-tesira/issues/5

not my work, but I'm following the same issue, it appears the feedback to custom variables does not work in v3 though, has been tested to 2.4

quoting below from dev. TimT-111;

when you create your connection to Tesira, there is a text box where you enter a label / name for that connection -- this is what I'm calling the 'instance name' (not to be confused with tesira's 'instance tag')

when you send a custom command to subscribe to something in tesira, you use this format: (InstanceTag) subscribe (attribute) (index) (CustomLabel) (delay)

CustomLabel is important, it will be the name of the variable you can access later. you need to include all of these values for the subscription to succeed.

when later trying to access the variable, you can test by setting a button's text to this: $(instance name:CustomLabel) Note: before you send the subscribe command, the button text would show something like $(N/A) or so

example: assuming your connection to tesira has a label / name called 'tesira'

Send a custom command to subscribe: "Microphones subscribe level 10 Sim1Mic1Lvl 50"

this should create a variable within companion called "$(tesira:Sim1Mic1Lvl)" -- be sure to include the dollar sign and parenthesis