# Dashboard 2.0 Classic design multi needle gauge. Call for testing

**URL:** <https://discourse.nodered.org/t/dashboard-2-0-classic-design-multi-needle-gauge-call-for-testing/88383>\
**Category:** Dashboard\
**Tags:** dashboard-2\
**Created:** [30 May 2024 14:24 UTC](https://discourse.nodered.org/t/dashboard-2-0-classic-design-multi-needle-gauge-call-for-testing/88383 "2024-05-30T14:24:38Z")\
**Posts on this page:** 20\
**Page:** 2

<div class="post-metadata">

**Author:** ![gerry](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/gerry/32/21604_2.png) [@gerry](https://discourse.nodered.org/u/gerry)\
**Post date:** [1 June 2024 18:57 UTC](https://discourse.nodered.org/t/dashboard-2-0-classic-design-multi-needle-gauge-call-for-testing/88383/21 "2024-06-01T18:57:19Z")

</div>

Installed the package, imported the multi needle example and I get an absolutely blank page, everything is white.

---

<div class="post-metadata">

**Author:** ![arturv2000](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/arturv2000/32/88724_2.png) [@arturv2000](https://discourse.nodered.org/u/arturv2000)\
**Post date:** [1 June 2024 19:09 UTC](https://discourse.nodered.org/t/dashboard-2-0-classic-design-multi-needle-gauge-call-for-testing/88383/22 "2024-06-01T19:09:35Z")

</div>

Try restarting node-red.

Today installed on the server and similar thing happened, not all white but gauge was not showing, the other time was using node-red on laptop running frim command line, don't remenber if restart was necessary.

If alk blank page in dashboard higher than 1.8.0 check this

> <https://github.com/FlowFuse/node-red-dashboard/issues/937>
>
> \### Current Behavior
> 
> Hello
> 
> This issue is related to #817 it seems that the f…ix applied in #881 is not sufficient, at least for Android.
> 
> Just updated one of the instances I have to v1.11.1 to check if this was fixed or not.
> 
> According to my tests:
> \- In Windows PC using Edge or Chrome there are issues, it show a white page upon opening the page, with the same error that was being generated before
> !\[image\](https://github.com/FlowFuse/node-red-dashboard/assets/17281826/e49719a3-9937-4e50-bcfd-3131b5cbb361)
> \- Same thing in Linux (raspberryPi) using Chromium and Firefox
> \- Same thing in Android using Chrome
> 
> In order for this error to show, is necessary to open the page in the browser (wait until the new PWA version is downloaded and the popup to reload appears), after this is necessary to close the browser window (all instances of chrome / edge / etc.., in windows is necessary to close the chrome icon on the notification tray and in android is necessary to force close the chrome browser), when trying to access again the site the page does not load until we force an incorrect address (like 'https://my.site.com/dashboar') at this point the login popup is shown and we can access the real address \`https://my.site.com/dashboard\`.
> If we close the browser it is necessary to repeat the process.
> 
> The fix seems simple, according to my attempts is necessary to change the file \`ui/src/main.mjs\` the \`catch\` for the \`fetch('\_setup')\` needs to change to:
> 
> \`\`\`js
> .catch((err) =\> {
> if (err instanceof TypeError) {
> if (err.message === 'Failed to fetch') {
> console.log('auth error:', err)
> console.log('redirecting to:', window.location.origin + '/dashboard')
> 
> // window.location.replace(window.location.origin + '/dashboard') //Original, seems to have no issues with Edge and Chrome on Windows, doesn't work on Android (Not tested on Linux browser)
> // window.location.href = window.location.origin + window.location.pathname + window.location.search + (window.location.search ? '&' : '?') + 'reloadTime=' + Date.now().toString() + window.location.hash; // Also works on Edge + Chrome on windows, doesn't work on android
> 
> // Reloading dashboard without using cache by apending a cache-busting string to fully reload page to allow redirecting to auth
> window.location.replace(window.location.origin + '/dashboard' + '?' + 'reloadTime=' + Date.now().toString() + Math.random()) // Seems to work on Edge and Chrome on Windows, Chromium and Firefox on Linux, and also on Chrome Android (and also as PWA App)
> } else {
> // handle general Type errors here
> console.error('An error occurred:', err)
> }
> } else {
> // handle general errors here
> console.error('An error occurred:', err)
> window.location.replace(window.location.origin + '/dashboard' + '?' + 'reloadTime=' + Date.now().toString() + Math.random()) // Seems to work on Edge and Chrome on Windows, Chromium and Firefox on Linux, and also on Chrome Android (and also as PWA App)
> }
> })
> \`\`\`
> 
> It seems the original fix was enclosed in a series of \`if\` statements that are not catching the correct error, since I just added the original fix \` window.location.replace....\` to the \`else\` of the first \`if\`
>  
> 
> 
> \### Expected Behavior
> 
> \_No response\_
> 
> \### Steps To Reproduce
> 
> \_No response\_
> 
> \### Environment
> 
> \- Dashboard version: 1.11.1
> \- Node-RED version: 3.1.7
> \- Node.js version: 20.11.0
> \- npm version: 10.4.0
> \- Platform/OS: Server (Ubuntu 22.04.3
> \- Browser: windows (Edge, chrome), Linux (Chromim, Firefox), Android (Chrome)
> 
> 
> \### Have you provided an initial effort estimate for this issue?
> 
> I am not a FlowFuse team member

---

<div class="post-metadata">

**Author:** ![gerry](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/gerry/32/21604_2.png) [@gerry](https://discourse.nodered.org/u/gerry)\
**Post date:** [1 June 2024 19:13 UTC](https://discourse.nodered.org/t/dashboard-2-0-classic-design-multi-needle-gauge-call-for-testing/88383/23 "2024-06-01T19:13:27Z")

</div>

restart fixed it. didn't see that one coming

---

<div class="post-metadata">

**Author:** ![Colin](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/colin/32/17040_2.png) [@Colin](https://discourse.nodered.org/u/Colin)\
**Post date:** [1 June 2024 20:38 UTC](https://discourse.nodered.org/t/dashboard-2-0-classic-design-multi-needle-gauge-call-for-testing/88383/24 "2024-06-01T20:38:06Z")

</div>

You certainly should not need to restart node-red after installing the gauge node (assuming it was installed using Manage Palette). Did you try refreshing the page in the browser?

---

<div class="post-metadata">

**Author:** ![gerry](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/gerry/32/21604_2.png) [@gerry](https://discourse.nodered.org/u/gerry)\
**Post date:** [1 June 2024 21:02 UTC](https://discourse.nodered.org/t/dashboard-2-0-classic-design-multi-needle-gauge-call-for-testing/88383/25 "2024-06-01T21:02:31Z")

</div>

I think I did that would be normal for me, but sadly can't make that statement with total certainty,  
[edit] yes, did use palette manager on Pi 3b+ running bookworm. node red 3.19

---

<div class="post-metadata">

**Author:** ![Colin](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/colin/32/17040_2.png) [@Colin](https://discourse.nodered.org/u/Colin)\
**Post date:** [1 June 2024 21:14 UTC](https://discourse.nodered.org/t/dashboard-2-0-classic-design-multi-needle-gauge-call-for-testing/88383/26 "2024-06-01T21:14:39Z")

</div>

Which version of the dashboard are you using?

---

<div class="post-metadata">

**Author:** ![gerry](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/gerry/32/21604_2.png) [@gerry](https://discourse.nodered.org/u/gerry)\
**Post date:** [1 June 2024 21:16 UTC](https://discourse.nodered.org/t/dashboard-2-0-classic-design-multi-needle-gauge-call-for-testing/88383/27 "2024-06-01T21:16:09Z")

</div>

dashboard 1.8.1

---

<div class="post-metadata">

**Author:** ![arturv2000](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/arturv2000/32/88724_2.png) [@arturv2000](https://discourse.nodered.org/u/arturv2000)\
**Post date:** [1 June 2024 21:16 UTC](https://discourse.nodered.org/t/dashboard-2-0-classic-design-multi-needle-gauge-call-for-testing/88383/28 "2024-06-01T21:16:16Z")

</div>

Just did a test in a new node-red instance (V4.0.0-beta4) and Dashboard V1.11.1.

Indeed is necessary to restart node-red in order for the gauge appears on the page. It's the same issue with the `ui-led` and `ui-frame` nodes for DashBoard2, it seems is a condition for nodes for dashboard2 that requires a node-red restart to be correctly placed on the dashboard page.

---

<div class="post-metadata">

**Author:** ![Colin](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/colin/32/17040_2.png) [@Colin](https://discourse.nodered.org/u/Colin)\
**Post date:** [2 June 2024 06:42 UTC](https://discourse.nodered.org/t/dashboard-2-0-classic-design-multi-needle-gauge-call-for-testing/88383/29 "2024-06-02T06:42:02Z")

</div>

> [@gerry](#):
>
> dashboard 1.8.1

It is on 1.11.1 now, but if you use the dashboard requiring a login then I suggest not upgrading yet due to the PWA issue noted in post #22.

---

<div class="post-metadata">

**Author:** ![Colin](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/colin/32/17040_2.png) [@Colin](https://discourse.nodered.org/u/Colin)\
**Post date:** [2 June 2024 07:35 UTC](https://discourse.nodered.org/t/dashboard-2-0-classic-design-multi-needle-gauge-call-for-testing/88383/30 "2024-06-02T07:35:06Z")

</div>

> [@arturv2000](#):
>
> Indeed is necessary to restart node-red in order for the gauge appears on the page. It's the same issue with the `ui-led` and `ui-frame` nodes for DashBoard2

I think you are right. Either a restart should not be required, or the user should be informed that it is required. I have submitted an issue against the dashboard. [A node red restart is necessary after installing third party ui nodes · Issue #938 · FlowFuse/node-red-dashboard · GitHub](https://github.com/FlowFuse/node-red-dashboard/issues/938)

---

<div class="post-metadata">

**Author:** ![joepavitt](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/joepavitt/32/59722_2.png) [@joepavitt](https://discourse.nodered.org/u/joepavitt)\
**Post date:** [2 June 2024 16:17 UTC](https://discourse.nodered.org/t/dashboard-2-0-classic-design-multi-needle-gauge-call-for-testing/88383/31 "2024-06-02T16:17:31Z")

</div>

Thanks Colin - its something ive asked Nick for some help on, but don't have a clear solution yet

---

<div class="post-metadata">

**Author:** ![gerry](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/gerry/32/21604_2.png) [@gerry](https://discourse.nodered.org/u/gerry)\
**Post date:** [3 June 2024 18:48 UTC](https://discourse.nodered.org/t/dashboard-2-0-classic-design-multi-needle-gauge-call-for-testing/88383/32 "2024-06-03T18:48:17Z")

</div>

Playing with the gauge, aside from install, it seems solid with no hassles. Pretty much everything I've thrown at it so far it handles well.

---

<div class="post-metadata">

**Author:** ![Colin](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/colin/32/17040_2.png) [@Colin](https://discourse.nodered.org/u/Colin)\
**Post date:** [3 June 2024 20:03 UTC](https://discourse.nodered.org/t/dashboard-2-0-classic-design-multi-needle-gauge-call-for-testing/88383/33 "2024-06-03T20:03:56Z")

</div>

Excellent, thanks @gerry.

---

<div class="post-metadata">

**Author:** ![Colin](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/colin/32/17040_2.png) [@Colin](https://discourse.nodered.org/u/Colin)\
**Post date:** [4 June 2024 07:40 UTC](https://discourse.nodered.org/t/dashboard-2-0-classic-design-multi-needle-gauge-call-for-testing/88383/34 "2024-06-04T07:40:05Z")

</div>

2 posts were split to a new topic: [Dashboard 2 widget positioning](https://discourse.nodered.org/t/dashboard-2-widget-positioning/88491)

---

<div class="post-metadata">

**Author:** ![Trying\_to\_learn](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/trying_to_learn/32/28400_2.png) [@Trying\_to\_learn](https://discourse.nodered.org/u/Trying_to_learn)\
**Post date:** [4 June 2024 05:40 UTC](https://discourse.nodered.org/t/dashboard-2-0-classic-design-multi-needle-gauge-call-for-testing/88383/35 "2024-06-04T05:40:29Z")

</div>

_(Waves hello)_

Hi folks.

I have been a bit slack lately and am not sure where I am in the scheme of things NR.

I have `dashboard 3.6.6` if I look at/in my palette manager.

So can I use this node?

---

<div class="post-metadata">

**Author:** ![Bobo](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/bobo/32/8401_2.png) [@Bobo](https://discourse.nodered.org/u/Bobo)\
**Post date:** [4 June 2024 06:00 UTC](https://discourse.nodered.org/t/dashboard-2-0-classic-design-multi-needle-gauge-call-for-testing/88383/36 "2024-06-04T06:00:47Z")

</div>

This is for the Flowfuse Dashboard (known as 2). Do you have it installed?

---

<div class="post-metadata">

**Author:** ![Trying\_to\_learn](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/trying_to_learn/32/28400_2.png) [@Trying\_to\_learn](https://discourse.nodered.org/u/Trying_to_learn)\
**Post date:** [4 June 2024 06:08 UTC](https://discourse.nodered.org/t/dashboard-2-0-classic-design-multi-needle-gauge-call-for-testing/88383/37 "2024-06-04T06:08:06Z")

</div>

Honestly.... I don't know.

Probably not though.

Thanks.

---

<div class="post-metadata">

**Author:** ![Colin](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/colin/32/17040_2.png) [@Colin](https://discourse.nodered.org/u/Colin)\
**Post date:** [4 June 2024 07:31 UTC](https://discourse.nodered.org/t/dashboard-2-0-classic-design-multi-needle-gauge-call-for-testing/88383/39 "2024-06-04T07:31:09Z")

</div>

> [@Trying\_to\_learn](#):
>
> I don't know.

Surely you have been using node-red long enough to know that you can see which nodes you have installed by looking in Manage Palette. You can see there whether @flowfuse/node-red-dashboard is installed. If you didn't know that the flowfuse dashboard was called then a search for flowfuse dashboard would no doubt have answered that.

---

<div class="post-metadata">

**Author:** ![Trying\_to\_learn](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/trying_to_learn/32/28400_2.png) [@Trying\_to\_learn](https://discourse.nodered.org/u/Trying_to_learn)\
**Post date:** [4 June 2024 10:55 UTC](https://discourse.nodered.org/t/dashboard-2-0-classic-design-multi-needle-gauge-call-for-testing/88383/40 "2024-06-04T10:55:20Z")

</div>

Maybe.

But the topic is `Dashboard 2.0`

# **(no mention of `fuse`.)**

I gave the version from Palette manager - which is greater than 2.0.

I was asking as I am not sure.

---

<div class="post-metadata">

**Author:** ![Colin](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/colin/32/17040_2.png) [@Colin](https://discourse.nodered.org/u/Colin)\
**Post date:** [4 June 2024 13:27 UTC](https://discourse.nodered.org/t/dashboard-2-0-classic-design-multi-needle-gauge-call-for-testing/88383/41 "2024-06-04T13:27:12Z")

</div>

It seems you have not been paying attention to the [242 threads](https://discourse.nodered.org/search?q=tags%3Adashboard-2%20order%3Alatest) there have been, tagged with dashboard-2, about the new Dashboard that is now the recommended dashboard for new systems.

[Previous page](https://discourse.nodered.org/t/dashboard-2-0-classic-design-multi-needle-gauge-call-for-testing/88383.md?page=1)

[Next page](https://discourse.nodered.org/t/dashboard-2-0-classic-design-multi-needle-gauge-call-for-testing/88383.md?page=3)