Ability to use plugin within a standalone Node Red deployment rather than embedded

[nmbath]

Are there any plans to allow the SignalK plugin for Node red to be added to a standalone Node Red deployment rather than within a Node Red inside of Signal K.

[sbender9]

I don't currently have a plans for this. It would be a good amount of work.

[LexanRed]

Is there any update on this one?

What is the reason to restrict it to the embedded instance?
Is there any upside to it? Is there any downside on running a standalone instance?

[tkurki]

With the current implementation communication between node-RED and Signal K server happens directly, inside one process. This has many benefits, among others the ability to pass all incoming data through n-r with very little performance overhead, but also the code is much simpler this way ("good amount of work" comment above).

The communication could take place between local processes and/or via network, but nobody has implemented that kind of bridging and in process is now the only option.

[jeroenvermeulen]

How about a lightweight SignalK plugin to receive the data?
This may make it easier to get the data from a separate Node-RED install into SignalK.

[CrankyDad]

How about a lightweight SignalK plugin to receive the data?

This may make it easier to get the data from a separate Node-RED install into SignalK.

I've made a sub flow that acts as a SignalK client and doesn't need to run embedded.
You simply supply the paths you want to subscribe to among other features.
Still need packaging (incl documentation) and getting PUT with authentication to work, but I hope to complete that soon.
It will be put here when done and in NPM.