I've pushed a beta version of Dashboard to npm (not to flows catalogue). I have spent a wet Saturday looking at chart updates and trying to speed up reloads and data shifting. I suspect the main issue is actually buried deep in angular and chart.js somewhere - but I have found some hopefully useful gains... Hopefully none of the changes break anything but ... hence this request.
I would be grateful if a few of you could give it a whirl. In particular those of you with multiple charts.
This can be installed manually by going into your user directory and installing - eg
cd ~/.node-red
npm i node-red-dashboard@2.24.1-beta
Don't forget to flush local browser cache to ensure getting latest client side code etc... Feedback here please.
During test scope: add widgets to dashboard one by one, not connected to any node, do not configure anything but resolve the group , then deploy.
Date picker error:
Error: The ng-model for md-datepicker must be a Date instance or a value that can be parsed into a date. Currently the model is of type: number
at Array.<anonymous> (app.min.js:470)
at Object.$$format (app.min.js:335)
at Object.$processModelValue (app.min.js:334)
at Object.$$setModelValue (app.min.js:335)
at app.min.js:223
at m.$digest (app.min.js:174)
at m.$apply (app.min.js:177)
at app.min.js:595
at r.<anonymous> (app.min.js:596)
at r.emit (index.js:83)
System info:
16 Nov 14:58:42 - [info] Node-RED version: v1.2.3
16 Nov 14:58:42 - [info] Node.js version: v12.16.2
16 Nov 14:58:42 - [info] Windows_NT 10.0.18363 x64 LE
16 Nov 14:58:42 - [info] Loading palette nodes
16 Nov 14:58:43 - [info] Worldmap version 2.5.3
16 Nov 14:58:43 - [info] Dashboard version 2.24.1-beta started at /ui
Browser: Chrome Version 86.0.4240.193 (Official Build) (64-bit)
Thank you so much for your hard work. I have been dreaming of a fast chart from the Dashboard
I will give it a try though I have a busy schedule this week.
Don’t get your hopes up too high. I found a few duplicate calls and inefficient shifting. Nothing earth shattering. I can still kill the browser if I send multiple feeds several times a second.
Just finished a quick testing. There are 12 real-time data curves in one chart. I used to limit the msg.topic rate to 5 per sec (send each topic in turn). If it is more than 5, then the chart can be unstable and cause losing connection error. Right now I increased the limit to 20 per second, the chart is running smoothly. I would say that it is much better than before
During beta installation, I did see a warning and error message. They are not affecting my flows so far. I trust that they will be gone during the formal release . But I will copy the messages here just in case:
pi@raspberrypi:~/.node-red $ npm i node-red-dashboard@2.24.1-beta
npm WARN node-red-contrib-ui-led@0.3.3 requires a peer of node-red-dashboard@2.2 3.x but none is installed. You must install peer dependencies yourself.
npm WARN node-red-node-ui-table@0.3.7 requires a peer of node-red-dashboard@>2.1 5.0 but none is installed. You must install peer dependencies yourself.
...
Error: WebSocket is not open: readyState 2 (CLOSING)
at WebSocket.send (/usr/lib/node_modules/node-red/node_modules/ws/lib/websocket.js:329:19)
at completeConnection (/usr/lib/node_modules/node-red/node_modules/@node-red/editor-api/lib/editor/comms.js:99: 28)
at WebSocket. (/usr/lib/node_modules/node-red/node_modules/@node-red/editor-api/lib/editor/comms.js: 152:21)
at WebSocket.emit (events.js:315:20)
at Receiver.receiverOnMessage (/usr/lib/node_modules/node-red/node_modules/ws/lib/websocket.js:789:20)
I know. I haven't had any luck to break the charts yet
I do that test allways if I'm about to update some key components of my running home automation. And as this update seems promising, I started early.
All good here apart from a warning as mentioned above by davidz
npm WARN node-red-node-ui-table@0.3.7 requires a peer of node-red-dashboard@>2.15.0 but none is installed. You must install peer dependencies yourself.
