rbe node discard duplicate messages, not filtering out.

[TridiumControls]

Hi, 

Is there a node that is available to filter out duplicate messages? I know there is deduplicate and rbe, with deduplicate I would think if there is a duplicate message from previous message to current message received it would discard duplicates and allow new messages through. but it doesn't, I tried rbe as well, see attached screen image. i would think that all the message that are coming into rbe only the new messages will get through, duplicates would be discarded, and it doesn't do that. Am I thinking of this the right way? 

only way rbe works is for 1 msg.payload, but the http request i'm getting is say message 1 is on array 0, then 5 minutes later the same message that was in array 0 is now on array 1 and a new message is in array 0, essentially moving older message 1 array slot every few minutes depending on how many new message there are in the http request, older messages are moved down 1 array. 

[Colin Law]

I don't fully understand your flow, but could you put the rbe earlier in the flow (or one in each leg)?

Colin

--
http://nodered.org
 
Join us on Slack to continue the conversation: http://nodered.org/slack
---
You received this message because you are subscribed to the Google Groups "Node-RED" group.
To unsubscribe from this group and stop receiving emails from it, send an email to node-red+unsubscribe@googlegroups.com.
To post to this group, send email to node...@googlegroups.com.
Visit this group at https://groups.google.com/group/node-red.
To view this discussion on the web, visit https://groups.google.com/d/msgid/node-red/171e89cd-54cb-477e-94b7-3ff82f5df7a2%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Dave C-J]

As the info says the rbe node works "per msg.topic"  so if you have msg arriving on different topics they will be treated independently... If you don't care about the topic then delete it further back in your flow and then the rbe will be per msg. 

[TridiumControls]

that makes sense, so I also tried using rbe after each combine_sms function which essentially concatenates two objects to be sent via sms. but the issue i'm running into is that a message will start in array 0 then move to array 1, then array 2 further down the array list, as new messages are put into array 0 on each http request 

So if I put an rbe node after array 0 function and only monitor that one array 0 message, then the message that was in array 0 will move to array 1, then the rbe node in array 1 will see the change and will send out the new message even though the message was perviously in array 0 as the old message travels down the array, each rbe node will see a new message and will send the same message that originally started in array 0. 

Not sure how I can better explain this. What i'm looking to do is if I have an array of messages, is for a node to take note of the message, and if the message is repeated in any of the array, discard the message, otherwise send the new message out. 

I hope I'm explaining this correctly. 

[Colin Law]

I think you will have to write a function node to do that.

Colin

--

http://nodered.org
 
Join us on Slack to continue the conversation: http://nodered.org/slack
---
You received this message because you are subscribed to the Google Groups "Node-RED" group.
To unsubscribe from this group and stop receiving emails from it, send an email to node-red+unsubscribe@googlegroups.com.
To post to this group, send email to node...@googlegroups.com.
Visit this group at https://groups.google.com/group/node-red.

To view this discussion on the web, visit https://groups.google.com/d/msgid/node-red/11377b67-26b1-4ab7-ac0d-2a6e681fb65d%40googlegroups.com.