Believe me what I assure you the only dumb question is the one you don't ask.
I'm good at asking questions.
Looking at what you posted - and I am not an expert - I think your data is formatted as JSON.
Put a JSON
node between the OPC UA (the right most blue one) and the debug node.
See if that helps.
Another thing is to actually put TWO debug nodes there.
Why?
Well, by default the debug node shows you ONLY the msg.payload.
But it can show you EVERYTHING as well.
So?
Well, if I am correct and the data is a JSON format: it is structured differently to normal. Be it there is such a thing.
Usually you get something like:
msg.payload = "This is the payload"
msg.topic = "This is the topic"
msg.colour = "blue"
msg.time = "12:22:18"
msg.date = "24 April 2019"
msg. (and so on)
You can make a lot of stuff in a message.
Just usually it is only the payload which is of importance.
Yeah, so?
Well, sometimes, when you have to send a message over a protocol - say MQTT, which is a well used protocol in NR - you only can send the msg.payload and msg.topic.
I may not be 100% correct, but I am explaining what is going on.
So: those nodes are sending all their data in a JSON packet/encoding.
This allows all the other stuff to go thorough something like MQTT.
Therefore you put it through a JSON
node and look at it with a DEBUG node and you will see it all "taken apart" and in a format which is like I explained with the msg.colour etc.
Double click on the debug
node and select complete message object
.
Then when something comes in, you click on the little > symbol and expand that part of the message and you will see all the sub-components.
I hope that helps.
And again: I am not an expert.