Currently testing a proof-of-concept with FlowFuse Community Edition and I see that Project Nodes are not supported without an Enterprise license. My first thought was to just use MQTT messaging between instances.
Besides the obvious multiple ingress and egress points provided by project nodes, what are the advantages versus just using MQTT?
The project nodes provide zero config inter-communication between hosted instances (in side your env) and remote instances (those controlled by the device-agent).
You can pretty much achieve the same thing with MQTT yes, but that is up-to you to deal with.
They are a value-add feature of licenced FlowFuse unfortunately. (we have to pay the bills 
)
Thanks Steve. That makes a lot of sense. I'm thinking small scale for my PoC but I can see the advantage in a large, dynamic environment where the context is automatic or at least auto-updated.
Added to my justification list.
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.
The OpenJS Foundation | Terms of Use | Privacy Policy | OpenJS Foundation Bylaws | Trademark Policy | Trademark List | Cookie Policy