I have this subroutine which I am calling with a link call node: [Screenshot 2024-01-04 alle 16.10.24] I am always getting "Missing return node information", due to the split function, which contains: msg.payload.split("##").forEach(e => { if (!e) {return;} node.send({ payload: e + "##"…

Try this then. you will need to remove the "fake data" node and check that the output of the EXEC maintains the msg.linksource property for it to work in production. [{"id":"f4fddf75fcab76bd","type":"inject","z":"eaa6d97a6ede80ab","name":"*#*1##*#*1##*#18*5158*113*490##*#*1##","props":[{"p":"data"…

Subroutine Missing return node information

General

fmarzocca 4 January 2024 15:28 6

That's not easy, as this is a OWN bus (Legrand) and you can't replicate on your own.
But take that message: *#*1##*#*1##*#18*74#0*113*0##*#*1##
I don't need to extract ALL of the messages, but just *#18*74#0*113*0##, discarding the rest. But this central message can vary, depending on the input in the subroutine.

Topic		Replies	Views
Function that return msg.payload each time it pass through General	3	1913	30 October 2019
Recent change to Link Call node? General	4	1293	26 February 2022
Why does node.send(msg) work, but cannot return msg as normal? General	2	128	15 August 2023
Function node - what happens if I don't "return" anything? General	4	5313	1 February 2019
Clarifying use of split node General	17	429	10 April 2021

Subroutine Missing return node information

Related Topics