I'm using ui-template nodes in my Node-red dashboards, which receive messages from other nodes. my message handling is as follows: <script type="text/javascript"> var $scope = this.scope; (function(scope) { $scope.$watch('msg', function(msg) { if (msg) console.log(`Inco…

Just a quick note to say I'm very focussed on D2.0, 1.0 isn't really my area of expertise, so I'm not in a good position to help here unfortunately.

[image] joepavitt: Just a quick note to say I'm very focussed on D2.0, 1.0 isn't really my area of expertise, so I'm not in a good position to help here unfortunately. Of course. Just wanted you to be aware of this while you develop the template msg listener in dashboard 2.0 :slight_smile:

@dceejay , any clue? I also opened an issue on this in GitHub. Even if this cannot be fixed at this time, I want to know that I'm not doing something wrong and will implement a workaround.

A couple questions What version of NR, node.js and dashboard (you can get all this from the startup log) Are you using Home Assistant or Docker? You state you are using a ui-template node but your image shows UI Form. Please clarify. Are you using any ui-control nodes? If so what is it doing? What…

Thanks for reponding. [image] zenofmud: What version of NR, node.js and dashboard (you can get all this from the startup log) Right now, I'm using Node JS 21.1.0, Node-red 3.1 & dashboard 3.5, but this happened on previous versions of them too. [image] zenofmud: Are you using Home Ass…

One thing first, you might want to first try downgrading your node.js to v20 or 18, Odd number node versions are unstable releases So I've recreated this and can see what you mean but this is over my head, I haven't much experience with $scope.$watch(...) If anyone else ( @hotNipi @Steve-Mcl , @shri…

Experiences say that the widget should be created to be as dummy as possible so every payload is treated as true one. Then the server side can be managed to be able to provide valid info for all situation you need an can imagine.

What I think you are seeing is part of the message replay mechanism dashboard has to help re-populate dashboard elements when the user opens a page (so they don't get a blank page). I cannot say I am crazy about it but I understand why it was developed. I remember having to handle this in the deve…

[image] Steve-Mcl: I remember having to handle this in the development of the ui-svg node with @BartButenaers (I seem to remember he wrote this up or did a good explanation). Hi @Steve-Mcl , Do you mean this perhaps? Bart

BTW for client-side message replays, we have used another mechanism in the node-red-contrib-ui-contextmenu node. But that doesn't work when the dashboard framework replays messages from the server-side...

Node-RED

Node-RED Forum

Message sent once but received twice

Dashboard

BartButenaers 26 November 2023 18:23 10

Hi @Steve-Mcl,
Do you mean this perhaps?
Bart

Topic		Replies	Views
Use of this.msg V this.$socket.on('msg-input:' + this.id, (msg) Dashboard dashboard-2	11	256	1 March 2024
Msg replayed in UI node after a tab switch Developing Nodes	14	1066	18 July 2020
Refresh ui-node Dashboard	40	11152	31 March 2022
Using Incoming Message in ui_template Node Dashboard	5	1860	2 March 2020
Template UI fed by template node msg.template - how to make it appear? Dashboard	8	754	19 July 2021

Copyright OpenJS Foundation and Node-RED contributors. All rights reserved. The OpenJS Foundation has registered trademarks and uses trademarks. For a list of trademarks of the OpenJS Foundation, please see our Trademark Policy and Trademark List. Trademarks and logos not indicated on the list of OpenJS Foundation trademarks are trademarks™ or registered® trademarks of their respective holders. Use of them does not imply any affiliation with or endorsement by them.

Message sent once but received twice

Related topics