Thank you so much for the great scripting capability, these are great!
It would be really great to have ICMP / Ping capability in the scripting API.
I'm migrating my modem/internet reset from a Raspberry Pi with an external switchable outlet over to one of my Shelly Plugs. It's much more compact and simple. I have the script working, but the problem is that HTTP GET is not always reliable, and can give false "internet down" signals. Yes, one can use more endpoints, longer timeouts, more retries, etc. but then this lengthens the time it takes to detect an outage.
My Raspberry Pi script, written in Rust (I wish Rust would run on Shelly devices!), pings a couple of very reliable networks, so when it fails, I'm sure the modem went down.
ICMP / Ping is much more lightweight than HTTP, and more reliable (doesn't depend on an HTTP server always being online).
If there's concern about abuse, why not just disable "flood" and rate-limit ICMP requests to 1 per second?
You're also less likely to get banned just pinging a reliable server once every few seconds than doing an HTTP request every few seconds, because the ICMP packets are very small / lightweight and don't cause network congestion (if not abused).
Please consider adding the ability to ping sites and get basic stats, e.g. packet loss, latency, etc., like one would get from the ping command in Linux for a regular unprivileged user.
Thank you! 