You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is this a feature relevant to companion itself, and not a module?
I believe this to be a feature for companion, not a module
Is there an existing issue for this?
I have searched the existing issues
Describe the feature
I'm using the satellite API to add custom surfaces. When setting any 'input' variable value there is only a 'OK' response. I would like to also know which variable of what device is 'OK'.
The response could looke like the following example: SET-VARIABLE-VALUE OK DEVICEID="custom_device" VARIABLE="variable_id"
or an entirely new response alongside the old one (maybe better for not breaking any parsing of the current response): VARIABLE-VALUE-SET OK DEVICEID="custom_device" VARIABLE="variable_id"
This structure is similar to the 'DEVICE-ADDED' response which also provides the 'DEVICEID'
Usecases
This would help showing better feedback of what exact variable has been set correctly and what variable failed. For now I wait for the response before allowing another variable to be set any value, to not run into any issues. So as long as there is no response, no other variables can be set. For my usecases this currently works, but since there is aleready a response why not make it more useful and clear.
Please let me know if others would find this useful as well or have any other ideas
Thanks, Jan
The text was updated successfully, but these errors were encountered:
Is this a feature relevant to companion itself, and not a module?
Is there an existing issue for this?
Describe the feature
I'm using the satellite API to add custom surfaces. When setting any 'input' variable value there is only a 'OK' response. I would like to also know which variable of what device is 'OK'.
The response could looke like the following example:
SET-VARIABLE-VALUE OK DEVICEID="custom_device" VARIABLE="variable_id"
or an entirely new response alongside the old one (maybe better for not breaking any parsing of the current response):
VARIABLE-VALUE-SET OK DEVICEID="custom_device" VARIABLE="variable_id"
This structure is similar to the 'DEVICE-ADDED' response which also provides the 'DEVICEID'
Usecases
This would help showing better feedback of what exact variable has been set correctly and what variable failed. For now I wait for the response before allowing another variable to be set any value, to not run into any issues. So as long as there is no response, no other variables can be set. For my usecases this currently works, but since there is aleready a response why not make it more useful and clear.
Please let me know if others would find this useful as well or have any other ideas
Thanks, Jan
The text was updated successfully, but these errors were encountered: