New Plugin for HTTP/HTTPS Service probes

---

I have drafted a plugin which allows for HTTP/HTTPS service probes. Check out https://www.npmjs.com/package/pimatic-probe

I am planning to add more features in the future, like probes for TCP and UDP.

See also http://forum.pimatic.org/topic/354/ping-websites-with-pimatic-ping/3

Nice

Nice plugins… Looking for this.
Anyway, suppose I want to monitor http, where should I put port. Coz for my Yoctopuce device, by default it use port 4444.

And one more thing, does this support monitoring for https?

@funky81 You can specify the port as part of the URL.

Example:

{
      "id": "probe3",
      "class": "HttpProbe",
      "name": "SolarView Web Page",
      "url": "http://fritz.box:88"
}

NB, primatic-probe also provides a TcpConnectProbe. If you just need to know whether or not you can connect to the server, this probe will be much faster. See README for details

@mwittig thanks for the info

Just a little question, i tried to ping my logitech media server that runs on my nas with port 9000.
i tried to ping it with 192.168.0.18:9000 but no succes. now a used the TcpConnectProbe this works got, but when the nas is off i get lots of error messages.

ping 192.168.0.18 works but i need to ping it with port.
thanks!

@p4co86 Can you please post the error message you get in Pimatic Log when using the HttpProbe? Please also let me know which error message(s) you get on your Logitech Media Server when using the TcpConnectProbe. Thanks!

Please also make sure you’re using the latest version of the plugin which 0.0.4. Some users including me had problems with updating via the pimatic frontend. See also
https://github.com/pimatic/pimatic/issues/251

EDIT:
Version 0.0.4 Changes:

• Fixed bug: Type reference error occurred in TcpProbe if name resolution failed
• Added support for automatic HTTP/HTTPS redirection
• Added support for HTTP Basic Auth
• Added support for defining the accepted HTTP Response Status Codes
• Updated README, Added version badge

See README for details

@mwittig Nise idea, but if it possible to make a JSON probe and read a value to display? May i have a Influx Database, i can call the rest interface of them with your probe plugin and call the last value from xxx sensor, if this possible?

@xpix Currently, this is not yet possible, but it can be done, of course.

If you can do it I am happy to collaborate with you.

@mwittig Ok, i will check your plugin, but the next 2 weeks i’m in vacation

@xpix Ok, great. Enjoy your vacation

i get this error on pimatic

Probe for device id=multiroom-aduio failed: Error: connect ECONNREFUSED

it occurs when the nas is offline. i just want ping the service with port 9000 not the nas alone.

@p4co86 Ok, but then you should also get ECONNREFUSED with the TcpConnectProbe as well. Are you sure, you have set the right URL? It should be the same URL you enter in the browser.

Please provide more details on error messages you get and the device configs you use. you can also use Github to file an issue. Thanks.

Yes its also with tcpconnect… when the nas is on and then the lms is on. All is fine, but i turn off the nas when no pc or media center is on, then the error occurs

this is my device

    {
      "id": "multiroom-aduio",
      "class": "HttpProbe",
      "name": "Multiroom Audio",
      "url": "http://192.168.0.18:9000",
      "interval": 60,
      "timeout": 10
    }

@p4co86: Ah, ok, Well, this is expected behavior. Instead off logging an error I could perhaps store the error in a variable. A sort of comprise I could also implement a strategy to avoid logging the same error message over and over again.

ALL - Any thoughts on this?

@p4co86
you cannot use the standard ‘ping’ command to test a port. For this, you’ll have to use ‘nmap’

nmap -p 8000 192.168.0.18

yes but how can i use it as presence ?

here is the scenario, when i turn radio on, the nas boot. when multiroom audio server (192.168.0.18:9000) is present execute “play player kitchen…”.

same with media center, when kodi mysql datenbank is present (http://192.168.0.18/pkg/phpmyadmin/), turn on media center.

all this works perfect with httpprobe. but only the errors are annyoin when the nas is absent.

@p4co86 Did you manage to setup rules now?

Regarding the error messages you should not see any error messages on the NAS when using HttpProbe. If there are error messages on the NAS though you may need to change the HttpProbe configuration. Please send me the error messages in case.

Regarding the error message you get on the NAS when using TcpConnectProbe, please let me know what the error message is.

Regarding error messages in the Pimatic Log I’ll take care of this.

@ALL - Any thoughts on this? (see also earlier posts)