Open houser42 opened 3 weeks ago
Is there a way to up-vote this basic request? "a way to have the data in the 2.0 chart node survive restarts"
Further investigation is required on our part on how we can support this. We can't support this natively in the module, as when node-RED restarts, all temporary data is cleared.
The flow shared utilises a file-in
/file-out
out, which we can investigate, and provide a sample flow for.
I think there will be ongoing requests for this feature. The D1 node accomplishes it by providing an output which can can be saved in file or context and directly re-injected on startup, which is easy for the user to implement and does the job perfectly.
1) Retention of data points within v2.0 (possible to-do flowuse) In my opinion, a perfect basis would be if the ui-graph in version 2.0 would generate an output like in version 1.0. Namely all >displayed< data points (older no more displayed data points are obsolete) as an array, instead of just the last data point received. (The array must actually already be there internally, because how else does the graph display the data points for newly calling clients?)
2) Saving and injecting (to-do for someone else)
There is already a simple external option for permanently saving and then injecting the output array, e.g. with PERSIST
.
Alternatively, you can adapt the flow mentioned in this thread.
Yes, I am considering the unified output approach, but we'd also then need to add support for injecting that data format too.
we'd also then need to add support for injecting that data format too.
Could it output data compatible with the existing config of the node, or would that be difficult to achieve?
Hello. Just some positive feedback and also a question that I would assume I will not get an answer to as it is a bit of a "how long is a string" type of question. But here it goes:
We have finished migrating 3 offgrid systems from Dashboard V1 to Dashboard V2 that are now only missing this feature. It has gone much better than expected. D2 seems very stable and robust so far with much better performance than D1. So very happy about that and kudos for great work and the migration tools and docs!
If at all possible. we would like to deploy these systems March-April next year, so is it realistic to hope for this feature by then by any chance? Just planning ahead, and the V1 systems can certainly last for a while more so not vital but would be nice as maintenance for V1 has become a tad cumbersome and stale.
To be clear: A way to have the data in the 2.0 chart node save the data and reload that data / survive restarts.
Description
The V1 chart has a tested and working subflow that saves the data and reloads the data after a restart. This is pretty vital functionality and needed for V2 charts. Can someone have look at this when there is time please?
I tested the old working subflow with the V 2 chart and as expected it does not work. It would be great if this subflow could be updated to work with 2.0. or of course any other way to have the data survive reboots if possible? This is the subflow that worked with V1 hooked up to a V2 chart for tests:
Have you provided an initial effort estimate for this issue?
I am no FlowFuse team member