Suggestions on TCP/Port ping via NR since the old 'node-red-contrib-tcp-ping' module is crashing NR?
Suggestions on TCP/Port ping via NR since the old 'node-red-contrib-tcp-ping' module is crashing NR?
You could try
or without port numbers -
Oh, I had not as yet tripped over 'portscan' that looks interesting. I used an execute node to run 'nc' which is functional but not really elegant.
Have a flow that validates some devices being available via simple ping, but others where I need to validate a specific port, so ping alone is insufficient, in these cases.
The use case is interesting, there is a solar vendor that is calming that they cannot effective manage the installed infrastructure because local internet is unstable. So I created a flow that not only pings the internet, watches the IO across the cable modem, pings all of the devices the solar vendor installed, but also watches the communication ports of said solar vendor devices, given they are effectively a black box to us, the solar user.
After the flow has been online for just hours, effectively noticed, if the internet services drops and recovers, the solar vendor control system does not automatically recover. So now I need to figure out how to do a forced report of the vendor control system. Which should be simple to do with a few tasmota driven relays and adding a bit more to the flow.
Oh, and the internet is stable, it has gone down only for power outage (scheduled) and routine updates to the cable modem thus far. The vendor control system, has been down more than once so far. Going to love sliding the outage report the flow generates to the vendor in the next customer review meeting.
1 Like
