You don't need to set the widget's target to 192.168.43.147:7001 to receive the messages from oschook. 42494 is the port used by oschook to send the message, this value is not important (it may even change, as many apps use randomly chosen port for outgoing messages).
The problem is that oschook sends multiple values in one messages while a fader only expects one value. You'll have to split the message from oschook. This could be done using a script widget for example, that would receive the value (with the address property matching whatever oschook uses) and dispatch it:
set('fader_1', value[0]) // first value to fader_1
set('fader_2', value[1]) // second value to fader_2
set('fader_3', value[2]) // third value to fader_3
Or with a custom module : Examples - Open Stage Control
The last argument is special as it represents a number that can't be represented in JSON like other number (it's too big). See json - Datatype long - what does high and low mean? - Stack Overflow. It could well be a timestamp from oschook in which case can probably ignore it.