How to Send Data from One Tab to Another Tab?

[Tony Contrada]

I have two different tabs with node in them. I want to send data from the output of a function on one tab and send it to a function on another tab.

How can I do this?

Thanks,

Tony

[Mark Setrem]

Theres no node to do this at the moment.  Nick gave the following answer when the same question was asked last month:

"The next* release will have a new set of 'link' nodes for just this scenario.

* By "next" I mean the next major release 0.14.0. There will likely by maintenance releases in the 0.13.x stream before then."

One way to do it at the moment is via MQTT, but that would mean having a MQTT broker installed as well as node-red

[Tony Contrada]

I see, well thanks for the info. I look forward to the next release.

-Tony

[Julian Knight]

Until then, you could use a global variable and watch for changes, use MQTT or maybe Max's pipes node. Of even a file or database.

None of them ideal of course but they work. I tend to use MQTT to decouple everything since it is lightweight, reliable and fast enough for most things. Doing it that way lets you treat different parts of your system effectively as microservices.

[Timur Fatykhov]

Another option is to use http nodes and make Web service kind.of thing. Just use custom authorization header for security

[Peter Scargill]

VERY much looking forward to the LINK nodes - I am constantly having to use MQTT un-necessarily to pass stuff from one tab to another as I don't want each tab to become too big..

Pete.

[karthhic Mukil]

Hi,

If you want to send data between different nodes in a simple way, you can use dweetio for now,  it will transmit the data online.

BR,
Karthhic

[Walter Kraembring]

Then it is better to use MQTT for now. Then you can keep all your data locally & private instead of bouncing it via a cloud of unknown sort that you will have to depend on

[Peter Scargill]

Yes I agree with that – local MQTT sounds good – don’t know why I didn’t think of that before..

 

Pete.

--
http://nodered.org
 
Join us on Slack to continue the conversation: http://nodered.org/slack
---
You received this message because you are subscribed to a topic in the Google Groups "Node-RED" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/node-red/zoUjpprXbnA/unsubscribe.
To unsubscribe from this group and all its topics, send an email to node-red+u...@googlegroups.com.
To post to this group, send email to node...@googlegroups.com.
Visit this group at https://groups.google.com/group/node-red.
For more options, visit https://groups.google.com/d/optout.

[Peter Göthager]

What I've done in norelite is to use a common configuration node that uses an EventEmitter to communicate between the nodes.

Norelite is a package of nodes that are fairly tightly coupled. Whenever a new sensor value is received into a "source node" (nrl-source) it will send the data to the evaluation nodes (nrl-evl) for those that subscribe to that specific source data. The communication goes through the configuration node that is used for both the nrl-source and nrl-eval nodes.

See ...

Config node: https://github.com/nidayand/norelite/blob/master/core/nrl-config.js

Row 46 in nrl-source node (transmitter): https://github.com/nidayand/norelite/blob/master/core/nrl-source.js

Row 164 in nrl-eval node (receiver): https://github.com/nidayand/norelite/blob/master/core/nrl-eval.js

It requires, of course, that the same configuration node specification is used for both the nrl-source ndoe and nrl-eval node