I would also like to support the idea of using Node-Red for an OpenPlotter UI/Dashboard.
I started fiddling just yesterday with it at home and have already an up and running dashboard for a simple Temp/Humidity sensor running on an RPi without OpenPlotter. It was fairly easy to setup once I looked around for examples and installed the necessary node.js extensions to node-red. Below is the running dashboard and the node-red flow behind it - it is so simple!
![[Image: jSsW2vA.png]](http://i.imgur.com/jSsW2vA.png)
![[Image: zwgdau.jpg]](http://oi63.tinypic.com/zwgdau.jpg)
Doing a few searches on what we might need to support most of the features of OP, I have found that the fundamentals are already covered to some extent even without resorting to MQTT.
Someone has already done some work on parsing SignalK and handling it in Node-Red http://flows.nodered.org/flow/97b27fd31dc142459fdf so we can adapt that to generate Dashboard UI elements directly from the SignalK stream of OP.
Someone else has already done some work on interactive maps where node-red can overlay info on positions in the map (e.g. vessel position, AIS positions, GRIB overlays) His example actually shows an AIS display!! http://flows.nodered.org/node/node-red-c...b-worldmap
There is also support for UI Elements including compass, circular gauges, sliders etc. while there is also the option to include other HTML templates that use the data fed into node-red (e.g. wind instruments)
One thing I'm still trying to come up with an idea on, is how to automatically generate Node-Red flows and Dashboard UI elements from the SignalK stream as well as how to use the info stored in Triggers/Actions of OP to create equivalent flows in Node-Red without having to do them by hand. However, everyone will have their own needs and equipment (sensors/actuators etc) so I'm still trying to come up with a way to do this in a customizable way
I started fiddling just yesterday with it at home and have already an up and running dashboard for a simple Temp/Humidity sensor running on an RPi without OpenPlotter. It was fairly easy to setup once I looked around for examples and installed the necessary node.js extensions to node-red. Below is the running dashboard and the node-red flow behind it - it is so simple!
Doing a few searches on what we might need to support most of the features of OP, I have found that the fundamentals are already covered to some extent even without resorting to MQTT.
Someone has already done some work on parsing SignalK and handling it in Node-Red http://flows.nodered.org/flow/97b27fd31dc142459fdf so we can adapt that to generate Dashboard UI elements directly from the SignalK stream of OP.
Someone else has already done some work on interactive maps where node-red can overlay info on positions in the map (e.g. vessel position, AIS positions, GRIB overlays) His example actually shows an AIS display!! http://flows.nodered.org/node/node-red-c...b-worldmap
There is also support for UI Elements including compass, circular gauges, sliders etc. while there is also the option to include other HTML templates that use the data fed into node-red (e.g. wind instruments)
One thing I'm still trying to come up with an idea on, is how to automatically generate Node-Red flows and Dashboard UI elements from the SignalK stream as well as how to use the info stored in Triggers/Actions of OP to create equivalent flows in Node-Red without having to do them by hand. However, everyone will have their own needs and equipment (sensors/actuators etc) so I'm still trying to come up with a way to do this in a customizable way