I see the same behavior. The script returns 0 on success; the expected return value is set to 0, and the monitor goes down when a 0 is returned and is up when any other value is returned. This is contrary to the ipMonitor documentation for this monitor type and should be considered a bug.
↧