Registry / http-networking / node-red-node-ping

node-red-node-ping

JSON →
library0.3.3jsnpmunverified

The `node-red-node-ping` package provides a specialized Node-RED node designed to perform ICMP pings against remote servers. It serves as a network health monitoring and keep-alive check utility within the Node-RED low-code development environment. The node can operate in two primary modes: 'Timed' for periodic checks at configurable intervals, and 'Triggered' for on-demand pings initiated by an input message. Upon execution, it outputs the round-trip time in milliseconds as `msg.payload`, or `false` if the host is unreachable or unresolvable. Error messages are provided in `msg.error` and the target IP in `msg.topic`. The current stable version is 0.3.3, which was last published approximately four years ago, indicating a very slow or ceased release cadence for this specific package. Its primary differentiator is its seamless integration into Node-RED flows, allowing developers to visually incorporate ping functionality without writing custom code, unlike standalone `ping` npm libraries.

npm install node-red-node-ping
INSTALL
IMPORT
SIG · NODE-RED-NODE-PING
N
node-red-node-ping
http-networkingjavascriptv0.3.3
harness data pending
Install & Compatibility
Where this runs

No compatibility data collected yet for this library.

Code
Verified usage

This demonstrates how to install the Node-RED ping node via npm and describes its basic usage within the Node-RED editor.

npm install node-red-node-ping # After installation, open your Node-RED editor (usually at http://localhost:1880/). # The 'ping' node will appear in the palette under the 'network' category. # Drag and drop the 'ping' node onto your flow canvas. # Double-click the node to configure its properties, such as the target host(s) # and operating mode (Timed or Triggered). Wire an 'inject' node to trigger # pings in 'Triggered' mode, or a 'debug' node to view the output message.
Debug
Known issues
gotchaWhen running Node-RED within Ubuntu Snap containers, strict confinement rules may prevent the 'ping' command from accessing external networks.
fix
Manually connect the `network-observe` interface using `sudo snap connect node-red:network-observe` to grant necessary permissions.
affects: >=0.1.0
gotchaOn certain versions of Raspbian (Raspberry Pi OS), the underlying `ping` command may require root privileges to execute, causing the Node-RED node to fail.
fix
Elevate permissions for the `ping` and `ping6` executables using `sudo setcap cap_net_raw=ep /bin/ping` and `sudo setcap cap_net_raw=ep /bin/ping6`.
affects: >=0.1.0
Errors
Common errors & fixes
Error: ping: command not found
The underlying 'ping' utility is not installed or not in the system's PATH.
fix
Ensure `iputils-ping` (or equivalent package for your OS) is installed. On Debian/Ubuntu: `sudo apt-get install iputils-ping`.
Error: Operation not permitted
The 'ping' command lacks the necessary network raw socket permissions, often due to strict container environments (like Ubuntu Snap) or system-level security configurations (like on Raspbian).
fix
Refer to the package's 'Gotchas' warnings. For Ubuntu Snap, use `sudo snap connect node-red:network-observe`. For Raspbian, use `sudo setcap cap_net_raw=ep /bin/ping` and `sudo setcap cap_net_raw=ep /bin/ping6`.
Upgrade
Version history
0.3.3latest on npm
Audit
Dependencies

No dependency data recorded yet.

Agent activity
8 hits · last 30 days
node
6
OpenAI (training)
2
Resources
node-red-node-ping — npm install node-red-node-ping · libregistry