Need recommendations / opinions if my thoughts are in the right direction?
New Project: I’m thinking about using a “Rio” and Node-Red to collect “Pressure” , “Flow Rate”, and “Daily Flow Total”. I want to store this data every 2 minutes to “SQLite Cloud”. Then I want to create a “DashBoard” to display that data in real-time and have a “TREND” graph.
Here’s where I am having trouble making it all come together.
I want the “DashBoard” to be accessible from the “Internet”, I want my customers to be able to log in to this dashbaord and see their data anytime.
Can somebody help with some more details on getting this done?
If you’re pushing the data to the cloud, find a cloud service to host your dashboard. There are a lot of security risks to opening an OT device to the public Internet, and I doubt the web server in a RIO is going to handle much traffic volume. It’s a great device for collecting your sensor data and pushing to a cloud database, but it’s likely not the right tool for hosting your public dashboard.
Storing data and making a dashboard with a few trends are two different tasks.
You don’t need to store the data to make the trends, Node-RED will do that.
So, you can take care of each via different methods.
As for the dashboard, you will use the Node-RED user/pass that you setup in groov Manage for your customers. (Of course, you will ensure that the user/pass you make is nothing like the user/pass for your admin to the groov RIO).
Once they log in, you will check the option in groov Manage to launch Node-RED dashboard.
I would talk to your IT folks and make sure you have them do a port forward from a high port number on the Internet to 443 on the RIO. Just so that you don’t load up the RIO with regular SSL/443 web traffic.
So, once they have done, you are pretty much done beyond just deciding how you want to move your data to your SQLite cloud (and the answer to that will depend on what receive that cloud service provides - hopefully something like MQTT/Sparkplug).
Build your Node-RED dashboard - keep in mind its not really responsive (It sort of is if you keep the gadget groups small), so know up front if you mostly want mobile or PC browser viewing.
Lastly, as @varland said, I would keep the number of concurrent connected browser sessions (not people, ie, some folks might have 2-5 browser open looking at the Node-RED dashboard) to less than 10 on a RIO.
The Node-RED trend graphs are not very efficient, so use the least of them you possibly can and keep their total durations as short as possible - I would for sure not go longer than 48 hours and keep the number of points per trend as low as possible (Dont accept their default 1000).
