# Button colours - stuck

**URL:** <https://discourse.nodered.org/t/button-colours-stuck/11527>\
**Category:** Dashboard\
**Created:** [25 May 2019 06:58 UTC](https://discourse.nodered.org/t/button-colours-stuck/11527 "2019-05-25T06:58:59Z")\
**Posts on this page:** 13\
**Page:** 2

<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:** [25 May 2019 16:28 UTC](https://discourse.nodered.org/t/button-colours-stuck/11527/21 "2019-05-25T16:28:10Z")

</div>

Dashboard on the pi - where the color reverts - is 2.15.2  
Dashobard on the mac - where the color retains - is 2.14.0

I just upgraded the mac version to 2.15.2 and now the color reverts there too.  
reverted back to 2.14.0 and the color stays.

---

<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:** [25 May 2019 18:11 UTC](https://discourse.nodered.org/t/button-colours-stuck/11527/22 "2019-05-25T18:11:34Z")

</div>

Yeah thought so. Fix is in master and will be on 2.15.3

---

<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:** [26 May 2019 00:51 UTC](https://discourse.nodered.org/t/button-colours-stuck/11527/23 "2019-05-26T00:51:05Z")

</div>

> [@hotNipi](#):
>
> What kind of settings to you expect to have?  
> As I described and what I understood you were missing is the **event of dashboard connecting to your flow** (pushing refresh of browser is same thing) That event you can catch with the `ui_control` node. No matter the message sent by `ui_control` then. You just needed the event. All that follow to this event is up to you to decide what you will need to do if this event is happened.

Sorry, but all I see is words.

Yes, pressing the refresh button "wiped" the button colours.

> [@hotNipi](#):
>
> That event you can catch with the `ui_control` node

Sorry. I don't understand.  
I want to understand what you mean, but.... (yeah sorry)

How you showed it applied to your flow and my flow.... Couldn't resolve it.

I have since stopped the problem in that I keep re-sending an up to date status message with the button colours. May be better, may be worse. As it is, it is better in that it is now a more real time indication, rather than a "this is the last known condition of...." message.

I was stuck last night until after mid-night with multiple messages out of a function node.  
All sorts of fun.  
Got it working this morning and that "resolved" the problem.

Thanks though.

---

<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:** [26 May 2019 14:17 UTC](https://discourse.nodered.org/t/button-colours-stuck/11527/24 "2019-05-26T14:17:54Z")

</div>

The ui\_control node sends a message when things happen (that is what is meant by catching an event). It is explained in node's info tab in the section starting " When any browser client connects or loses connection, or changes tab, this node will emit a `msg` containing:". So for the problem you have been seeing here you could use it to refresh the colour whenever the page is refreshed.  
However as explained earlier in the thread you are seeing the results of a bug, if you go back to the previous dashboard version or wait for the next version the problem will go away anyway.

---

<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:** [26 May 2019 16:27 UTC](https://discourse.nodered.org/t/button-colours-stuck/11527/25 "2019-05-26T16:27:10Z")

</div>

2.15.3 now released with the fix

---

<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:** [27 May 2019 12:01 UTC](https://discourse.nodered.org/t/button-colours-stuck/11527/26 "2019-05-27T12:01:00Z")

</div>

I shall await the update to 2.15.3

---

<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:** [27 May 2019 14:37 UTC](https://discourse.nodered.org/t/button-colours-stuck/11527/27 "2019-05-27T14:37:44Z")

</div>

Andrew you can update to it now. One way is to shutdown NR then change to the `.node-red`directory and enter `npm install node-red-dashboard` and the restart node-red.

You could probably use the palette manager and remove the dashboard then readd it, but I haven't tried that.

---

<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:** [27 May 2019 14:49 UTC](https://discourse.nodered.org/t/button-colours-stuck/11527/28 "2019-05-27T14:49:53Z")

</div>

just wait a sec... 2.15.4 will be along soon 🙂

---

<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:** [27 May 2019 22:14 UTC](https://discourse.nodered.org/t/button-colours-stuck/11527/29 "2019-05-27T22:14:30Z")

</div>

Hang on.

I have 2.15.2 on my NUC too. That can update in no time.

Standby for results.

2.15.2 the button doesn't hold colour with a refresh.  
Installing 2.15.3  
(More to come via edit.)

1: Not sure what is going on:

```auto
me@me-desktop:~$ cd .node-red
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$ npm install node-red-dashboard
npm WARN node-red-project@0.0.1 No repository field.
npm WARN node-red-project@0.0.1 No license field.

+ node-red-dashboard@2.15.3
updated 1 package and audited 1213 packages in 3.23s
found 5 vulnerabilities (2 low, 3 moderate)
  run `npm audit fix` to fix them, or `npm audit` for details
me@me-desktop:~/.node-red$ 

```

Not nice looking.

2:  
Looking good!  
Pressed inject button colour. Button changed colour. Pressed refresh and button kept colour.  
2.15.3 does work for that problem on Ubuntu machine.

---

<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:** [28 May 2019 08:02 UTC](https://discourse.nodered.org/t/button-colours-stuck/11527/30 "2019-05-28T08:02:29Z")

</div>

> [@Trying\_to\_learn](#):
>
> Not nice looking.

What is not nice looking? I don't see anything unusual there.

Did you remember to force a full refresh of the browser?

---

<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:** [28 May 2019 08:04 UTC](https://discourse.nodered.org/t/button-colours-stuck/11527/31 "2019-05-28T08:04:56Z")

</div>

> [@Trying\_to\_learn](#):
>
> updated 1 package and audited 1213 packages in 3.23s found 5 vulnerabilities (2 low, 3 moderate)

I pressed the refresh button and the button colour did not change.

Previously - with the older dashboard version - it lost its colour.

---

<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:** [28 May 2019 08:10 UTC](https://discourse.nodered.org/t/button-colours-stuck/11527/32 "2019-05-28T08:10:36Z")

</div>

The audit messages are normal.

Sorry I thought you were saying there was still a problem with the button.  
So to summarise, the only significance of your post was to say you did not like the audit messages?

---

<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:** [28 May 2019 08:12 UTC](https://discourse.nodered.org/t/button-colours-stuck/11527/33 "2019-05-28T08:12:25Z")

</div>

(And to confirm that after the update it works.)

> [@Colin](#):
>
> So to summarise, the only significance of your post was to say you did not like the audit messages?

Yes.

[Previous page](https://discourse.nodered.org/t/button-colours-stuck/11527.md?page=1)
