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.
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.
Yeah thought so. Fix is in master and will be on 2.15.3
Sorry, but all I see is words.
Yes, pressing the refresh button "wiped" the button colours.
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.
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.
2.15.3 now released with the fix
I shall await the update to 2.15.3
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.
just wait a sec... 2.15.4 will be along soon
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:
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.
What is not nice looking? I don't see anything unusual there.
Did you remember to force a full refresh of the browser?
I pressed the refresh button and the button colour did not change.
Previously - with the older dashboard version - it lost its colour.
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?
(And to confirm that after the update it works.)
Yes.