# Gauge output not clear what is going on

**URL:** <https://discourse.nodered.org/t/gauge-output-not-clear-what-is-going-on/9716>\
**Category:** Dashboard\
**Created:** [3 April 2019 07:28 UTC](https://discourse.nodered.org/t/gauge-output-not-clear-what-is-going-on/9716 "2019-04-03T07:28:39Z")\
**Posts on this page:** 6\
**Page:** 1

<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:** [3 April 2019 07:28 UTC](https://discourse.nodered.org/t/gauge-output-not-clear-what-is-going-on/9716/1 "2019-04-03T07:28:39Z")

</div>

I don't get what is happening with this dashboard/gauge.

It is a RPI  
Raspberry Pi 3 Model B Rev 1.2

But the numbers going into the gauge and what the gauge is showing differ.

Sending load as separate or overall makes no difference.

Oh, and I like the -25% CPU usage.

![Screenshot%20from%202019-04-03%2018-21-21](https://us1.discourse-cdn.com/flex026/uploads/nodered/original/2X/9/9332808bc6b8a2c549f97ab3e4897d2e8cce913b.png) ![Screenshot%20from%202019-04-03%2018-21-23](https://us1.discourse-cdn.com/flex026/uploads/nodered/original/2X/3/3b8035d1e5b0b7db676ed1b142d18b414407188d.png)

 ![Screenshot%20from%202019-04-03%2018-21-29](https://us1.discourse-cdn.com/flex026/uploads/nodered/original/2X/9/9095ae0152016c30c5eb45f33b0767780924194b.png) ![Screenshot%20from%202019-04-03%2018-21-42](https://us1.discourse-cdn.com/flex026/uploads/nodered/original/2X/5/5aae44c6ed99d968ca910f6772c9948fd35e94ab.png)

---

<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 April 2019 08:55 UTC](https://discourse.nodered.org/t/gauge-output-not-clear-what-is-going-on/9716/2 "2019-04-03T08:55:13Z")

</div>

Make a mini-flow with an inject, the cpu node and the gauge that shows the problem, then post that here.

---

<div class="post-metadata">

**Author:** ![zenofmud](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/zenofmud/32/316_2.png) [@zenofmud](https://discourse.nodered.org/u/zenofmud)\
**Post date:** [3 April 2019 11:56 UTC](https://discourse.nodered.org/t/gauge-output-not-clear-what-is-going-on/9716/3 "2019-04-03T11:56:01Z")

</div>

what is the range you put in the node configuration?

---

<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:** [3 April 2019 21:06 UTC](https://discourse.nodered.org/t/gauge-output-not-clear-what-is-going-on/9716/4 "2019-04-03T21:06:39Z")

</div>

Range is 1 - 100.

---

<div class="post-metadata">

**Author:** ![zenofmud](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/zenofmud/32/316_2.png) [@zenofmud](https://discourse.nodered.org/u/zenofmud)\
**Post date:** [3 April 2019 23:02 UTC](https://discourse.nodered.org/t/gauge-output-not-clear-what-is-going-on/9716/5 "2019-04-03T23:02:09Z")

</div>

Yet your graph shows a negative number....maybe you have to re think the range values...

btw, you do realize there are 4 cores and each can have a different value...

you also might want to display the complete msg.object....

---

<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 April 2019 03:29 UTC](https://discourse.nodered.org/t/gauge-output-not-clear-what-is-going-on/9716/6 "2019-04-04T03:29:43Z")

</div>

That is true.

Coming from the `cpu load` node that doesn't make sense.

Alas, like so many of my problems, it seems to have gone away and is not doing it any more.

I thought one of the scree grabs showed the messages - and it is/was set to show complete message.

Anyway, as I said: It seems to have gone away.