# \`gauge\` option suggestion

**URL:** <https://discourse.nodered.org/t/gauge-option-suggestion/15549>\
**Category:** Feature Requests\
**Created:** [15 September 2019 08:06 UTC](https://discourse.nodered.org/t/gauge-option-suggestion/15549 "2019-09-15T08:06:25Z")\
**Posts on this page:** 1\
**Showing post:** 12

<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:** [17 September 2019 11:04 UTC](https://discourse.nodered.org/t/gauge-option-suggestion/15549/12 "2019-09-17T11:04:06Z")

</div>

> [@Trying\_to\_learn](#):
>
> Mind if I ask why/how/where the `ui control` node fits in?

This is related how server side and Dashboard communicate.  
ui\_control node sends message on many socket events. (connecting,disconnection,change tab). Here it is not important what is the content of this message (you can get advantage of the message content but this is another story) but the event itself.

Gauge, when initialized has configured defaults. It always starts with configured state. Those are what you can configure from edit panel.  
Additional configuration (with msg.ui\_control.options) is not stored in gauge. So this must be resent every time after deploy (and/or if you need to change it) And of course the configuration may have totally different in any time. for example if your server running all the time and you just open the dashboard at random time, the gauge also needs to be with up to date configuration to present info correctly.

So at the moment the connection established and ui\_control fires the message, that fires your custom configuration to be sent to the gauge.

---

_[View the full topic](https://discourse.nodered.org/t/gauge-option-suggestion/15549)._