I notice that people are using this.msg instead of mounted() { // listen for incoming msg's from Node-RED // note our topic is "msg-input" + the node's unique ID this.$socket.on('msg-input:' + this.id, (msg) => { }), for tracking msg input …

Yep, for clarification, as Colin has mentioned, this.msg can changed on 2 events: widget-load: When the Dashboard/page first renders msg-input: When an input arrives via Node-RED to the ui-template node If you run a watch on msg, then that will fire in both of those instances. If you add your own…

Colin 29 February 2024 21:34 6

Yes, that is it: Retaining state information in a Dashboard 2 ui-template - #13 by hotNipi

Topic		Replies	Views
Node.on('input', function(msg, send, done) - what is send for? Developing Nodes	14	1449	25 August 2020
Node.send() vs send() – what's the difference? Developing Nodes	4	672	7 September 2022
Best practice for the msg object? Developing Nodes	11	257	27 January 2024
Announce node-red-contrib-msg-toggle (Feedback request) Share Your Nodes	3	1902	1 May 2019
Assistance with Basic Input to a Node General	3	101	2 October 2023

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.

Use of this.msg V this.$socket.on('msg-input:' + this.id, (msg)

Related Topics