Please note that this is an EXPERIMENT. Not at all sure whether it would be worth publishing. The event-in and event-out nodes are an alternative take on the core link nodes. Whereas the link nodes link up via the source and destination node id, these nodes link up via the msg.topic instead. This…

Apologies, I should have realised that you were the author! [image] cinhcet: what kind of configuration does "topic-link" require that "events" doesn't? Ah, see what you mean. My bad. I hadn't installed it and I was just reading the code. You are right, no config required. [image] cinhce…

No worries! [image] TotallyInformation: The topic-link node uses 2 set s and a map to keep track of things I think? The event node uses the node.js event handler which only requires a string (topic) and an event handler function and all that function does is a send . So no need to keep track o…

I have pushed a new version of contrib-events, you might want to have a look. It uses the EventEmitter2 node instead of the RED.events and so requires no additional coding to support * wildcards. I've set it to recognise / as a namespace separator just like MQTT. It uses a shared module between the …

There's also node-red-contrib-pubsub (node) - Node-RED which seems to achive the same end result?

Annoying to have to install it to look at the code. These nodes have no real docs. They manually do what the native event system does for you. They manually convert msg objects to a string and back. The stringify process isn't wrapped in a try/catch which may be a little fragile. And finally, they…

Currently, @cinhcet 's node-red-contrib-topic-link nodes are the closest to mine. As such, I don't think I will publish these with the node-red tag (assuming I publish them at all) to save any further confusion even though I much prefer my own version here :slight_smile: I will undoubtedly continue…

In the end, I decided to publish these nodes because their execution is sufficiently different from the alternatives that are available. I've also added a 3rd node called event-return. This enables sub-flows and loops to be easily created. You add the node to the end of an event-in triggered flow a…

That's all curiously familiar to the design I shared yesterday for the new call link node and the link return mode for the link out node. Even to the style of the message property used to track the caller.

Amazing! Great minds obviously think alike - or maybe just shamelessly borrow from each other :thinking: [image] knolleary: Even to the style of the message property used to track the caller. That genuinly is a coincidence because I didn't really understand all of the design note. Honestly,…

Node-RED

Node-RED Forum

[New Node] node-red-contrib-events: Alternative to link nodes

Share Your Nodes

Alacritous 18 September 2021 22:08 31

Why don't you collaborate? Labor shared is halved.

Topic		Replies	Views
Mqtt like link node based on topics General	59	2144	29 August 2020
Get mqtt topic data on demand? General	62	12359	5 April 2020
Best practice to avoid using Change node at every junction for topic matching? General	27	1662	3 January 2022
Switch node - MQTT like wildcards for switching Feature Requests	83	4072	29 May 2021
[Fun Exercise]Make an MQTT broker in Node-RED General	62	1347	3 November 2023

Copyright OpenJS Foundation and Node-RED contributors. All rights reserved. The OpenJS Foundation has registered trademarks and uses trademarks. For a list of trademarks of the OpenJS Foundation, please see our Trademark Policy and Trademark List. Trademarks and logos not indicated on the list of OpenJS Foundation trademarks are trademarks™ or registered® trademarks of their respective holders. Use of them does not imply any affiliation with or endorsement by them.

[New Node] node-red-contrib-events: Alternative to link nodes

Related topics