my bad, I thought I would not need any additional set-up than the nodes for some kind of local redis PUBLISH / SUBSCRIBE to work.... so I checked for some more information and know understand I have to install a REDIS server as well.
So for my understanding, every devices interested in REDIS messages have to run a REDIS server ?
Or could that work as well, if I specify as a REDIS server the unit from which I have to subscribe to messages ? Guess It has to run a REDIS server as well...
And other question, how to handle the password security, which I know is being used for the REDIS channel I want to subscribe ?
I found some information to set the Redis config node, for now it seems to accept the connection use this kind of JSON in config node :
Now what I need is to find what to enter as a topic in the Redis In node. the help is not really helpful to me yet : The msg.topic is pattern on all methods, separated by spaces.
When you say that, I guess that's when you use a redis out node , not redis IN?
I'll make further investigation with maybe help of wireshark, I've seen there is a REDIS dissector available, maybe it will give me some useful information, in addition to the docs here and there....
Hi, was able to make some progress, I found the channels on which I want to subscribe with help of Redis Insight software
I ofught a bit with the Redis In node, actually when I want to subscribe to several channel from a single node, by entering different channel names separated by space, it does not work, I need to use a single channel in each node to get the messages correctly :
I see you are using the JSONata interpreter to build an array of static strings in your msg.topic field -- which is less efficient than just using the JSON {} mode: (the J: evaluator is fairly heavyweight, although the output will be the same)
Of course, if the array will be built from other dynamic values like msg properties or context vars, then JSONata is the right choice...