Possibly a browser caching issue rather than node-RED.
Yes, and shame on me for not realising this . . .
No, I'll take that back, because:
This line in particular:
msg1 = {payload: '<font color = \"red\"><i class="fa fa-bullseye fa-2x"></i></font>', host: host, topic:device + "/Off-line",device_ID:device, background:"brown"};
Ok, that is the final version.
This is a few of its earlier attempts:
msg1 = {payload: '<font color = \"red\"><i class="fa fa-bullseye fa-2x"></i>,</font>', (etc)
msg1 = {payload: '<font color = \"red\"><i class="fa fa-bullseye fa-2x"></i>,</font>>', (etc)
msg1 = {payload: '<font color = \"red\"><i class="fa fa-bullseye fa-2x"></i></font>>', (etc)
Each of the lines when I deployed the node/flow I saw changes on the screen.
So when I finally got it right, why would it then suddenly cache the output unlike what it had been doing before?
Kind of rhetorical.
But it just seems there is/was something else at play there as well.
Just touching base on this.
I am slowly going through my flows and editing the required stuff.
Here is an example from a button:
<font color = \"white\"> <i class="material-icons md-48">calendar_today</i></font>
All I had to do was add the two \
around the font color = "white"
Weirdly (or maybe better: UNKNOWN TO ME) the font colour is BLUE.
So, as is I see this:
And when I make it this:
<font color = "white"> <i class="material-icons md-48">calendar_today</i></font>
I see this:
Ok. I give up.