# \[Help Wanted\] - Dashboard beta version to test

**URL:** <https://discourse.nodered.org/t/help-wanted-dashboard-beta-version-to-test/35995>\
**Category:** Dashboard\
**Created:** [16 November 2020 11:12 UTC](https://discourse.nodered.org/t/help-wanted-dashboard-beta-version-to-test/35995 "2020-11-16T11:12:33Z")\
**Posts on this page:** 10\
**Page:** 1

<div class="post-metadata">

**Author:** ![dceejay](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/dceejay/32/38_2.png) [@dceejay](https://discourse.nodered.org/u/dceejay)\
**Post date:** [16 November 2020 11:12 UTC](https://discourse.nodered.org/t/help-wanted-dashboard-beta-version-to-test/35995/1 "2020-11-16T11:12:33Z")

</div>

Hi All,

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

```auto
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.

Thanks

---

<div class="post-metadata">

**Author:** ![hotNipi](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/hotnipi/32/383_2.png) [@hotNipi](https://discourse.nodered.org/u/hotNipi)\
**Post date:** [16 November 2020 13:04 UTC](https://discourse.nodered.org/t/help-wanted-dashboard-beta-version-to-test/35995/2 "2020-11-16T13:04:14Z")

</div>

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:

```auto
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:

```auto
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)

---

<div class="post-metadata">

**Author:** ![davidz](https://avatars.discourse-cdn.com/v4/letter/d/a88e57/32.png) [@davidz](https://discourse.nodered.org/u/davidz)\
**Post date:** [16 November 2020 17:00 UTC](https://discourse.nodered.org/t/help-wanted-dashboard-beta-version-to-test/35995/3 "2020-11-16T17:00:10Z")

</div>

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. 😂

---

<div class="post-metadata">

**Author:** ![dceejay](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/dceejay/32/38_2.png) [@dceejay](https://discourse.nodered.org/u/dceejay)\
**Post date:** [16 November 2020 18:21 UTC](https://discourse.nodered.org/t/help-wanted-dashboard-beta-version-to-test/35995/4 "2020-11-16T18:21:43Z")

</div>

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.

---

<div class="post-metadata">

**Author:** ![dceejay](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/dceejay/32/38_2.png) [@dceejay](https://discourse.nodered.org/u/dceejay)\
**Post date:** [16 November 2020 18:22 UTC](https://discourse.nodered.org/t/help-wanted-dashboard-beta-version-to-test/35995/5 "2020-11-16T18:22:37Z")

</div>

Yeah. This is about charts 😉

---

<div class="post-metadata">

**Author:** ![davidz](https://avatars.discourse-cdn.com/v4/letter/d/a88e57/32.png) [@davidz](https://discourse.nodered.org/u/davidz)\
**Post date:** [16 November 2020 18:27 UTC](https://discourse.nodered.org/t/help-wanted-dashboard-beta-version-to-test/35995/6 "2020-11-16T18:27:37Z")

</div>

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)

---

<div class="post-metadata">

**Author:** ![hotNipi](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/hotnipi/32/383_2.png) [@hotNipi](https://discourse.nodered.org/u/hotNipi)\
**Post date:** [16 November 2020 18:42 UTC](https://discourse.nodered.org/t/help-wanted-dashboard-beta-version-to-test/35995/7 "2020-11-16T18:42:51Z")

</div>

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.

---

<div class="post-metadata">

**Author:** ![Paul-Reed](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/paul-reed/32/66906_2.png) [@Paul-Reed](https://discourse.nodered.org/u/Paul-Reed)\
**Post date:** [16 November 2020 21:13 UTC](https://discourse.nodered.org/t/help-wanted-dashboard-beta-version-to-test/35995/8 "2020-11-16T21:13:20Z")

</div>

All good here apart from a warning as mentioned above by **davidz**

```auto
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.

```

---

<div class="post-metadata">

**Author:** ![dceejay](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/dceejay/32/38_2.png) [@dceejay](https://discourse.nodered.org/u/dceejay)\
**Post date:** [19 November 2020 22:55 UTC](https://discourse.nodered.org/t/help-wanted-dashboard-beta-version-to-test/35995/9 "2020-11-19T22:55:31Z")

</div>

Any more feedback ? If not I'll go ahead and merge it to master.

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/flex026/uploads/nodered/original/1X/d073cd938eafa2e558d7c2cd59003b3ef4963033.png) [@system](https://discourse.nodered.org/u/system)\
**Post date:** [19 December 2020 22:55 UTC](https://discourse.nodered.org/t/help-wanted-dashboard-beta-version-to-test/35995/10 "2020-12-19T22:55:32Z")

</div>

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.