Got a standalone http_client flow that is getting data from the input (JSON-2 API), processing it, and sending it to UNS output, but it's not showing up in the tag browser

what does the logs say? probably some topic issue.

No logs somehow, hmm

you can enable debug. Verbose logging (flows + bridges): set debug_level: true on a stand-alone flow (dataFlowComponentConfig.debug_level) or on a bridge (protocolConverterServiceConfig.debug_level). This switches logs to DEBUG and adds more operational details. Disable it after troubleshooting. https://docs.umh.app/reference/configuration-reference

I figured out that trying to add the content for the topic browser to work in noderedjs really wasn't working. Instead I added a tag_processor with the defaults, and that made everything work.:

pipeline:
  processors:
    - nodered_js:
        code: |-

          const d = (typeof msg.payload === "string") ? JSON.parse(msg.payload) : 
msg.payload;

          msg.payload = d;

          return msg;

    - tag_processor:
        defaults: |

          msg.meta.location_path = "MACH-Controls-LLC.odoo";
          msg.meta.data_contract = "_raw";
          msg.meta.tag_name = "mrp";
          msg.payload = msg.payload;
          return msg;

Ah, yes. uns validation can be problematic if not using the tag processor. Yes, http server is just that, it start a listening server for receiving http. Can be useful for sending commands from grafana to the uns