You do not have permission to delete messages in this group
Copy link
Report message
Show original message
Either email addresses are anonymous for this group or you need the view member email addresses permission to view the original message
to node...@googlegroups.com
Sorry....
The working is like this (log winded version):
A timestamp (and more) is passed down a flow.
I need this to be "simplified" to a basic signal indicating that the function has happened.
Rather than having to search for the constant part and act on that, I wanted to "simplify" the signal here so further down the flow it is easier to see/understand.
I think the change node shall suffice.
(Given up on the MQTT for now.)
Julian Knight
unread,
Sep 22, 2017, 1:23:32 PM9/22/17
Reply to author
Sign in to reply to author
Forward
Sign in to forward
Delete
You do not have permission to delete messages in this group
Copy link
Report message
Show original message
Either email addresses are anonymous for this group or you need the view member email addresses permission to view the original message
to Node-RED
You can do that various ways. A change node can do it - using a simple change or via JSONata if you need to do something more complex. A function node can also do it of course. For data transformation - e.g. "simplify" - JSONata is a great choice.
steve rickus
unread,
Sep 22, 2017, 1:45:14 PM9/22/17
Reply to author
Sign in to reply to author
Forward
Sign in to forward
Delete
You do not have permission to delete messages in this group
Copy link
Report message
Show original message
Either email addresses are anonymous for this group or you need the view member email addresses permission to view the original message
to Node-RED
Another way to look at this would be to use the msg.topic as the "simplified" control code, and the msg.payload as the timestamp. Downstream nodes can simply check the topic (e.g. "start", "stop", "reset") and react accordingly. Or a single switch node can route the msg to different flows based upon that topic string...