[Feature]: Add: Feedback to custom variable

[pappou99]

Make sure you have updated to the latest version of the module

• I have checked this on the latest version of the module

Is there an existing issue for this?

• I have searched for similar existing issues

Describe the feature

Please add a feedback, that allows to store a value sent over osc to be stored in a custom variable.

The generic mqtt-module could act as a template, which has such a function.

It would be nice if any received valuetype could be stored without specififying the type in the settings.

Thanks and cheers

Usecases

No response

[federicogartner]

I have a workaround for this:

• Set the desired Custom Variable, lets say X

Then set a Trigger as follows:

• Event: set with On variable change:
  • Variable to watch: $(GenericOSC:latest_received_timestamp) so it will listen to every incoming messages
• Condition: here in my case I use the relevant address for my goal: Listen for OSC messages (No Arguments) aka path
• Action: internal: Custom Variable: Set with expression and for my Beat Counter I use the Arguments to update the variable
  • custom variable: X
  • Expression: $(GenericOSC:latest_received_args)

[MabelTainterTech]

@federicogartner do you know if this works with a stream of OSC Messages? I'm trying to do something similar where I am basically using this module to parse a burst of OSC messages from my ETC Eos lighting console, but it seems that the variables for the last received raw or args change too fast before I'm able to even process them with the listen for OSC messages feedback. It'll work just fine when it's receiving a single value one at a time, but when the console sends a burst of OSC messages providing the state of the console it seems to go too fast for the module. It would be much easier and better if instead the feedback just returned the arg or message received instead of comparing it. That way the message is already captured since it needs it to make the comparison anyway. I submitted a feature request with some better examples, but I would like to have this working now as I want to incorporate it into my current workflow for lighting programming. I'd do it myself, but the source code is pretty poorly documented and it doesn't really explain what's going on or what it's doing and I don't have the chops to just jump into it like I used to.