PING - pass in host/target address via msg?

#1

Ping node:
Is there any method to pass in the host ip address of the Ping target?
We are hardcoding in the PING address and that works ok, but looking for a way to feed in the ip address via msg.

THank you

0 Likes

#2

...and which ping node are you using????

0 Likes

#3

Thank you- the Ping node we are using is the one under the 'Network' .

0 Likes

#4

That doesn't help identify it. What npm module did you install to get that node?

0 Likes

#5

There are at least 4 on the flows.nodered.org site. One must do what you want...

0 Likes

#6

Thank you. I had the Node Red from the Raspbian install.
Will try one of the PING-Configurable in the Node Library

Thank you

0 Likes

#7

??? How were you doing the ping in the first place?

0 Likes

#8

The Ping Node that was installed only allowed for 'hardcoded' IP address.

0 Likes

#9

are you talking about a node-red node? ot a node.js node?

0 Likes

#10

node-red-node-ping

0.0.15

0 Likes

#11

I didn't think that a ping node was installed in a vanilla node-RED Raspbian installation?
Have you added one to the palette?

0 Likes

#12

No there is no base ping, but if you search the flows you will find some. Always a good idea to do a search for existing flows.

0 Likes

#13

Need some asstance:

  1. Went to Palette Manger in Node Red

  2. Searched for and found this alternative PING node which looks like it would work.
    node-red-configurable-ping
    A Node-RED node which takes input and pings a remote server.

  3. Pressed Installed, but failed to install?

Any suggestions?

0 Likes

#14

What did it say, what does the log say?

0 Likes

#15

Hi @sweetwater - the lack of feedback in the editor when an install fails is a known issue we're resolving in the next release.

You may need to drop to the command line and run npm install node-red-configurable-ping manually in ~/.node-red to get the full details.

0 Likes

#16

Thank Nick and team.
It turns out that the install under the Palette Manager worked.

The problem was user mistake- we had our Pi computer on a static IP for our application and that was not getting thru.

0 Likes