# Really strange behavior: some values from msg.payload wont be displayed on NR dashboard

**URL:** <https://discourse.nodered.org/t/really-strange-behavior-some-values-from-msg-payload-wont-be-displayed-on-nr-dashboard/26100>\
**Category:** Dashboard\
**Created:** [4 May 2020 23:05 UTC](https://discourse.nodered.org/t/really-strange-behavior-some-values-from-msg-payload-wont-be-displayed-on-nr-dashboard/26100 "2020-05-04T23:05:51Z")\
**Posts on this page:** 9\
**Page:** 2

<div class="post-metadata">

**Author:** ![JGKK](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/jgkk/32/18515_2.png) [@JGKK](https://discourse.nodered.org/u/JGKK)\
**Post date:** [5 May 2020 10:57 UTC](https://discourse.nodered.org/t/really-strange-behavior-some-values-from-msg-payload-wont-be-displayed-on-nr-dashboard/26100/22 "2020-05-05T10:57:39Z")

</div>

> [@hotNipi](#):
>
> There is one pretty new feature for `ui_template` node which should affect behaviors about the area your issue seems to be.  
> Check for it's configuration for every `ui_template` you have

well this makes my cache function obsolete 🙃  
Edit no it doesnt i think as there is no value on a new connect to refresh

---

<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:** [5 May 2020 11:02 UTC](https://discourse.nodered.org/t/really-strange-behavior-some-values-from-msg-payload-wont-be-displayed-on-nr-dashboard/26100/23 "2020-05-05T11:02:11Z")

</div>

> [@JGKK](#):
>
> well this makes my cache function obsolete

Not entirely. If you do, you are at the control of cached values, you can use it in the way you want. Send it immediately after tab change or make delays or change it somehow before resend or whatever...

With `ui_template` option, you can only turn the `replayMessage` (this is node-red internal therm) on or off. And hope, that if you are using `replayMessage`, there is one cached for you.

(edit) It is very rare that replayMessage does not exist. If you are not on rapid development and do not kill processes hard way than it works very reliably.

---

<div class="post-metadata">

**Author:** ![MisterT](https://avatars.discourse-cdn.com/v4/letter/m/d9b06d/32.png) [@MisterT](https://discourse.nodered.org/u/MisterT)\
**Post date:** [5 May 2020 11:02 UTC](https://discourse.nodered.org/t/really-strange-behavior-some-values-from-msg-payload-wont-be-displayed-on-nr-dashboard/26100/24 "2020-05-05T11:02:40Z")

</div>

Yeah thank you @hotNipi for that hell of a great tipp - that solved my problem  
that new feature slipped thru my hands ? how can it be 😃

but really sure before that feature ui\_template has reload also ? whatever it works again thanks 😃

and one other question for future updates routines -\> if npm tells me found vulnerabilities...  
using "npm audit fix" without headaches or better not using npm audit fix ?

coz I am new on npm world thats why I am asking - If I can use that commands without issues - I want to put it also in my update bash script 😉

---

<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:** [5 May 2020 11:03 UTC](https://discourse.nodered.org/t/really-strange-behavior-some-values-from-msg-payload-wont-be-displayed-on-nr-dashboard/26100/25 "2020-05-05T11:03:29Z")

</div>

Before the option was always on.

---

<div class="post-metadata">

**Author:** ![MisterT](https://avatars.discourse-cdn.com/v4/letter/m/d9b06d/32.png) [@MisterT](https://discourse.nodered.org/u/MisterT)\
**Post date:** [5 May 2020 11:06 UTC](https://discourse.nodered.org/t/really-strange-behavior-some-values-from-msg-payload-wont-be-displayed-on-nr-dashboard/26100/26 "2020-05-05T11:06:04Z")

</div>

AHHHH! now I know where my issues coming from ^^ thanks

whats about npm audit fix thingy - to critical or just automate it in a script ?  
EDIT: In general how do you do about nodes updates ? everytime up2date coz of security or stay old for functionality ?

---

<div class="post-metadata">

**Author:** ![JGKK](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/jgkk/32/18515_2.png) [@JGKK](https://discourse.nodered.org/u/JGKK)\
**Post date:** [5 May 2020 11:08 UTC](https://discourse.nodered.org/t/really-strange-behavior-some-values-from-msg-payload-wont-be-displayed-on-nr-dashboard/26100/27 "2020-05-05T11:08:22Z")

</div>

> [@hotNipi](#):
>
> there is one cached for you.

@MisterT i think this could without a cache function still sometimes lead to the behaviour on connect. So maybe both. Better safe than sorry 😃 and if you use the updated version i posted you get a nice message if there is no value yet for some reason.

---

<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:** [5 May 2020 11:15 UTC](https://discourse.nodered.org/t/really-strange-behavior-some-values-from-msg-payload-wont-be-displayed-on-nr-dashboard/26100/28 "2020-05-05T11:15:11Z")

</div>

re npm audit (OFF topic alert)...  
in theory it should be "safe" to let it autofix things - but depending on how the package uses the underlying library it may break the using library if the author hasn't scoped the semantic versioning correctly. (And if it is n-layers deep then who know ?!?) So caveat emptor. Up to you to backup first and ensure nothing is broken afterwards.

---

<div class="post-metadata">

**Author:** ![MisterT](https://avatars.discourse-cdn.com/v4/letter/m/d9b06d/32.png) [@MisterT](https://discourse.nodered.org/u/MisterT)\
**Post date:** [6 May 2020 01:04 UTC](https://discourse.nodered.org/t/really-strange-behavior-some-values-from-msg-payload-wont-be-displayed-on-nr-dashboard/26100/30 "2020-05-06T01:04:54Z")

</div>

Sorry guys because I am new on this board I cant answer 😃 (answering limit thingy)

But Thanks for all great help 🙂  
Note: @JGKK I will mark @hotNipi post as solution (easier for newbies I think 🙂 ) - but I definetly need your "cache solution" also in the next 5 or 6 flows  
So thank you also 😃

tldr: Problem solved

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/flex026/uploads/nodered/original/1X/d073cd938eafa2e558d7c2cd59003b3ef4963033.png) [@system](https://discourse.nodered.org/u/system)\
**Post date:** [20 May 2020 01:04 UTC](https://discourse.nodered.org/t/really-strange-behavior-some-values-from-msg-payload-wont-be-displayed-on-nr-dashboard/26100/31 "2020-05-20T01:04:54Z")

</div>

This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.

[Previous page](https://discourse.nodered.org/t/really-strange-behavior-some-values-from-msg-payload-wont-be-displayed-on-nr-dashboard/26100.md?page=1)