-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
FR: Dynamic link-call target #44
Comments
FYI FR originates from a #flowfuse thread on node-red slack. |
This would be very useful, I'm trying to route payloads to various different devices dynamically. The only current solution (I can think of) is to send all payloads to all devices then filter out all the payloads I don't need on the device side. |
Customer who would benefit from this - https://app-eu1.hubspot.com/contacts/26586079/record/0-2/8845845707 |
Just sharing continued appetite for this feature. I'm at a point with a project where the lack of this feature is probably going to mean I need to drop the Project Link nodes it favour of a standard MQTT broker (possibly ours when it's available). I have 3 environments, dev, stage, and prod. Each has a central config NR instance which then commands worker NR instance running on devices at manufacturing facilities as to what jobs they need to complete. The config payloads are sent out the to workers via the Project Link nodes. I need to be able to dynamically change the topics which the config payloads are published to ensure separation of the config between the three environments. I appreciate that we are working towards allowing direct communication with our broker so I'm going to read up on the proposed features of that. It might be I have to stop using the Project Link nodes which is a shame as they are otherwise very useful. |
@robmarcer this is kinda blocked waiting a reply here: #30 (comment) |
Description
As a user of FlowFuse I wish to perform a link-call to a targeted instance that is determined at runtime.
Similar to how the regular
link-call
does:I realise this can be already be achieved by comparing a
msg
property on theproject in
side and decide to NOT action it, but, in order to prevent eavesdropping, my requirement is to not send the sensitive data to any instance other than the intended target.The text was updated successfully, but these errors were encountered: