Skip to content
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

MQTT configuration does not get picked up within the Subflow #1

Closed
shantanoo-desai opened this issue Apr 26, 2022 · 1 comment
Closed
Labels
bug Something isn't working wontfix This will not be worked on

Comments

@shantanoo-desai
Copy link
Owner

shantanoo-desai commented Apr 26, 2022

Upon deploying the stack with the custom node-red instance which has all the dedicates subflows in them, the logs will provide the logs stating that one cannot connect to respective (external, internal) brokers since their configuration is not available.

Bug Reports

Solution / Workaround

Since there currently no config node support within subflows, the only possible way to achieve the subflow as nodes is to:

  1. export them all to a JSON
  2. pack them into a flows.json
  3. Generate a node-red image with where the flows.json file is /data/flows.json in the image
@shantanoo-desai shantanoo-desai added bug Something isn't working wontfix This will not be worked on labels Apr 26, 2022
@shantanoo-desai
Copy link
Owner Author

shantanoo-desai commented Apr 26, 2022

Result

By add the exported flows to /data/flows.json the node are available in the node palette

image

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working wontfix This will not be worked on
Projects
None yet
Development

No branches or pull requests

1 participant