# Gauge problem (bad graphics shown)
**URL:** https://discourse.nodered.org/t/gauge-problem-bad-graphics-shown/12273
**Category:** Dashboard
**Created:** [15 June 2019 22:41 UTC](https://discourse.nodered.org/t/gauge-problem-bad-graphics-shown/12273 "2019-06-15T22:41:37Z")
**Posts on this page:** 8
**Page:** 1
### Author:  [@Trying\_to\_learn](https://discourse.nodered.org/u/Trying_to_learn)
#### Post date: [15 June 2019 22:41 UTC](https://discourse.nodered.org/t/gauge-problem-bad-graphics-shown/12273/1 "2019-06-15T22:41:37Z")
I brought this up a long (long) time ago.
Since then the `dashboard` has been updated and I have just noticed that the problem remains.
---
### Author:  [@Colin](https://discourse.nodered.org/u/Colin)
#### Post date: [16 June 2019 08:11 UTC](https://discourse.nodered.org/t/gauge-problem-bad-graphics-shown/12273/2 "2019-06-16T08:11:13Z")
Can you make a simple example with a gauge and an inject node that shows the problem? Then we can try it.
Also show us the node-red startup log so we can see all the versions of everything.
---
### Author:  [@Trying\_to\_learn](https://discourse.nodered.org/u/Trying_to_learn)
#### Post date: [16 June 2019 08:49 UTC](https://discourse.nodered.org/t/gauge-problem-bad-graphics-shown/12273/3 "2019-06-16T08:49:47Z")
Flow:
```auto
[{"id":"75fdff1.7a42b","type":"ui_gauge","z":"e4b37cd6.281058","name":"","group":"7133f44c.ebafcc","order":1,"width":"5","height":"4","gtype":"donut","title":"gauge","label":"units","format":"{{value}}","min":"10","max":"80","colors":["#00b500","#e6e600","#ca3838"],"seg1":"","seg2":"","x":540,"y":3860,"wires":[]},{"id":"47ec55ab.240fd4","type":"ui_button","z":"e4b37cd6.281058","name":"37","group":"7133f44c.ebafcc","order":2,"width":"1","height":"1","passthru":false,"label":"37","tooltip":"","color":"","bgcolor":"","icon":"","payload":"37","payloadType":"str","topic":"","x":370,"y":3860,"wires":[["75fdff1.7a42b"]]},{"id":"7133f44c.ebafcc","type":"ui_group","name":"Group 4","tab":"ce4bcacd.5cc46","order":4,"disp":true,"width":6},{"id":"ce4bcacd.5cc46","type":"ui_tab","z":"","name":"VTEMP","icon":"dashboard","order":32,"disabled":false,"hidden":false}]
```
(I know I'm going to cop it for asking: How do I show you the node-red startup log if it has been running now for a few hours?)
This is on Ubuntu viewed on Ubuntu.
The original one was on a RPI - viewed on Ubuntu.
Added:
(On ubuntu. Dunno why RPI is mentioned.)
```auto
me@me-desktop:~/.node-red$ node-red-stop
Stop Node-RED
Use node-red-start to start Node-RED again
[sudo] password for me:
me@me-desktop:~/.node-red$ node-red-start
Start Node-RED
Once Node-RED has started, point a browser at http://192.168.0.6:1880
On Pi Node-RED works better with the Firefox or Chrome browser
Use node-red-stop to stop Node-RED
Use node-red-start to start Node-RED again
Use node-red-log to view the recent log output
Use sudo systemctl enable nodered.service to autostart Node-RED at every boot
Use sudo systemctl disable nodered.service to disable autostart on boot
To find more nodes and example flows - go to http://flows.nodered.org
Starting as a systemd service.
16 Jun 18:50:17 - [info]
Welcome to Node-RED
===================
16 Jun 18:50:17 - [info] Node-RED version: v0.20.3
16 Jun 18:50:17 - [info] Node.js version: v8.16.0
16 Jun 18:50:17 - [info] Linux 4.15.0-51-generic x64 LE
16 Jun 18:50:18 - [info] Loading palette nodes
16 Jun 18:50:18 - [warn] rpi-gpio : Raspberry Pi specific node set inactive
16 Jun 18:50:18 - [warn] rpi-gpio : Cannot find Pi RPi.GPIO python library
node-red-contrib-jktestEditableList - initialising module. Module Version: 0.1.1
node-red-contrib-jktestEditableList - loading module
16 Jun 18:50:19 - [info] Dashboard version 2.15.4 started at /ui
16 Jun 18:50:19 - [info] Settings file : /home/me/.node-red/settings.js
16 Jun 18:50:19 - [info] HTTP Static : /home/me/.node-red/public
16 Jun 18:50:19 - [info] Context store : 'default' [module=memory]
16 Jun 18:50:19 - [info] User directory : /home/me/.node-red
16 Jun 18:50:19 - [warn] Projects disabled : set editorTheme.projects.enabled=true to enable
16 Jun 18:50:19 - [info] Flows file : /home/me/.node-red/flows_me-desktop.json
16 Jun 18:50:19 - [info] Server now running at http://127.0.0.1:1880/
16 Jun 18:50:19 - [warn]
---------------------------------------------------------------------
Your flow credentials file is encrypted using a system-generated key.
If the system-generated key is lost for any reason, your credentials
file will not be recoverable, you will have to delete it and re-enter
your credentials.
You should set your own key using the 'credentialSecret' option in
your settings file. Node-RED will then re-encrypt your credentials
file using your chosen key the next time you deploy a change.
---------------------------------------------------------------------
16 Jun 18:50:19 - [info] Starting flows
16 Jun 18:50:19 - [info] [tcp in:MySensors Gateway] connecting to 192.168.1.20:5003
16 Jun 18:50:19 - [info] uibuilder:uibuilder: UI Builder Version 1.2.2 started at URL /uibuilder
16 Jun 18:50:19 - [info] uibuilder:uibuilder: UI Source files at /home/me/.node-red/uibuilder/uibuilder
16 Jun 18:50:20 - [info] Started flows
16 Jun 18:50:20 - [error] [function:build array (1)] TypeError: Cannot read property 'shift' of undefined
16 Jun 18:50:20 - [info] [mqtt-broker:MQTT host] Connected to broker: mqtt://192.168.0.99:1883
16 Jun 18:50:20 - [info] [mqtt-broker:MQTT host] Connected to broker: mqtt://192.168.0.99:1883
16 Jun 18:50:20 - [info] [mqtt-broker:MQTT host] Connected to broker: mqtt://192.168.0.99:1883
```
---
### Author:  [@Colin](https://discourse.nodered.org/u/Colin)
#### Post date: [16 June 2019 09:00 UTC](https://discourse.nodered.org/t/gauge-problem-bad-graphics-shown/12273/4 "2019-06-16T09:00:12Z")
> [@Trying\_to\_learn](#):
>
> How do I show you the node-red startup log if it has been running now for a few hours
Restarting it is the easiest, or you could look back in syslog to find it.
I can confirm that I am seeing the same as you. I don't know whether there is already an issue raised for that. If not then if you raise one it should not get forgotten.
---
### Author:  [@Trying\_to\_learn](https://discourse.nodered.org/u/Trying_to_learn)
#### Post date: [16 June 2019 09:01 UTC](https://discourse.nodered.org/t/gauge-problem-bad-graphics-shown/12273/5 "2019-06-16T09:01:42Z")
Ok.
It was raised a few versions ago, best of my knowledge.
I just noticed it was still happening and wanted to mention it.
That's all.
---
### Author:  [@dceejay](https://discourse.nodered.org/u/dceejay)
#### Post date: [16 June 2019 09:43 UTC](https://discourse.nodered.org/t/gauge-problem-bad-graphics-shown/12273/6 "2019-06-16T09:43:03Z")
The original problem was with negative values - this is slightly different.
---
### Author:  [@Trying\_to\_learn](https://discourse.nodered.org/u/Trying_to_learn)
#### Post date: [16 June 2019 11:00 UTC](https://discourse.nodered.org/t/gauge-problem-bad-graphics-shown/12273/7 "2019-06-16T11:00:50Z")
Um....
Not from me.
That is a copy of what a gauge is reading for my cpu temperature on one of my RPIs.
If the temperature is - I think there is a whole other problem.
---
### Author:  [@dceejay](https://discourse.nodered.org/u/dceejay)
#### Post date: [16 June 2019 14:03 UTC](https://discourse.nodered.org/t/gauge-problem-bad-graphics-shown/12273/8 "2019-06-16T14:03:07Z")
Now fixed in master (not yet on npm) - thanks for reporting, and the simple test case