Splitting a string and viewing contents

General
1

Hi All, im new to Node-Red and are slowly learning as i go.
i have a data logger which broadcasts the string via IP and port.
i have the string which gives me all of the logger values like this.

image
image.png477×780 92.7 KB

i want to view for example the value of A01:000000 in a guage (this is setup to measure a tank level.
could someone point me in the right direction

2

With a function node, you can create a "usable" object:

m = msg.payload.split(":")
key = m[0]
value = parseFloat(m[1])

return {payload:{[key]:value}};

However, what do the 0000000's represent ? Is this a value of 0 ? Or the number of 0's are the tank level ?

3

the 00000 represent the value of the gallons, they are not in water at the moment, thats why they are returning 0000

4

so what i would see generally is.
A01: 2500
A02: 3500
A03: 1500

the rest of the values i dont use or need, the logger has many other features

5

Flow example:

[{"id":"c2c5211f.c3a72","type":"inject","z":"39e527f4.ae0088","name":"","topic":"","payload":"A01:2500","payloadType":"str","repeat":"","crontab":"","once":false,"onceDelay":0.1,"x":256,"y":252,"wires":[["a21a343d.6d65c"]]},{"id":"364365dc.760902","type":"inject","z":"39e527f4.ae0088","name":"","topic":"","payload":"A02:3500","payloadType":"str","repeat":"","crontab":"","once":false,"onceDelay":0.1,"x":260,"y":308,"wires":[["a21a343d.6d65c"]]},{"id":"49cd7991.f688b","type":"inject","z":"39e527f4.ae0088","name":"","topic":"","payload":"A03:1500","payloadType":"str","repeat":"","crontab":"","once":false,"onceDelay":0.1,"x":260,"y":364,"wires":[["a21a343d.6d65c"]]},{"id":"a21a343d.6d65c","type":"function","z":"39e527f4.ae0088","name":"","func":"m = msg.payload.split(\":\")\nkey = m[0]\nvalue = parseFloat(m[1])\nreturn {payload:{type:key, value:value}};\n\n\n\n\n","outputs":1,"noerr":0,"x":470,"y":308,"wires":[["7c2dd21c.201b4c"]]},{"id":"22d12f31.9dc318","type":"debug","z":"39e527f4.ae0088","name":"","active":true,"tosidebar":true,"console":false,"tostatus":false,"complete":"false","x":854,"y":252,"wires":[]},{"id":"7c2dd21c.201b4c","type":"switch","z":"39e527f4.ae0088","name":"","property":"payload.type","propertyType":"msg","rules":[{"t":"eq","v":"A01","vt":"str"},{"t":"eq","v":"A02","vt":"str"},{"t":"eq","v":"A03","vt":"str"}],"checkall":"true","repair":false,"outputs":3,"x":610,"y":308,"wires":[["22d12f31.9dc318"],["3c36df76.54db1"],["17c2bc1e.ea2654"]]},{"id":"3c36df76.54db1","type":"debug","z":"39e527f4.ae0088","name":"","active":true,"tosidebar":true,"console":false,"tostatus":false,"complete":"false","x":854,"y":308,"wires":[]},{"id":"17c2bc1e.ea2654","type":"debug","z":"39e527f4.ae0088","name":"","active":true,"tosidebar":true,"console":false,"tostatus":false,"complete":"false","x":854,"y":364,"wires":[]}]

You can replace the debug node with a gauge node and if you need additional values you can define them in the switch node.

6

The value of A01: will change as the sensor recieves lower values.
will this just send me whatever the value is from the a01:?

7

will this just send me whatever the value is from the a01:?

Correct (and A02, A03)

8

image
image1265×734 53.7 KB

what am i missing here?
image
image1236×445 63.2 KB

9

You have to change the value format (and don't forget the scale):

54
Screenshot 2019-09-07 at 08.23.54.jpg848×242 18.1 KB

10

You are a Legend, thank you so much for taking the time

11

one last question, can i use the time from the logger?
its TM:1909072355
can i display this as well?

12

You will have to find out what type of timestamp is being sent, this maybe something like Pico seconds and then convert it to a readable time stamp with JavaScripts date

13

I think it is 23:55 07/09/19

14

@shaynel2006

Just an observation:

I think you are tripping yourself with the msg.payload structure.

In your other post about the LEDs, you have msg.payload.value. Here you have msg.payload.(something else)

This is both good and bad.

Good if you need to send the messages via/over MQTT.
Bad in that you need to remember to do extra processing on the msg.x before you get what you want.

Guessing that you are sending the messages over MQTT and have constructed them so, when they are received, put the message through a JSON node and it will . . . reformat the message so that:
msg.payload.foo becomes msg.foo
msg.payload.topic becomes msg.topic
and so on.

This isn't critical for the working of the flow, but it is adding a level of labels which isn't really needed.