$pushover message="xyz" does work in terminal, but it doesn't work in scripts

update：
add
:global pushover
and I can use $pushover now

Simply READ carefully pervious post...

npushover code

:global npushover do={
    :local url "https://api.pushover.net/1/messages.json"
    :local headers "Content-Type: application/json"
    :local reqdata [:toarray ""]
    :if ([:typeof $1]="array") do={:set reqdata $1} else={
        :error "\$$0 requires an array of values to set, see https://pushover.net/api"
    }
    :local json [:serialize to=json $reqdata]
    :local resp [/tool/fetch url=$url http-data=$json http-header-field=$headers output=user as-value]
    :local respdata [:deserialize from=json ($resp->"data")]
    :if (($respdata->"status")=1) do={
        /log/debug "$0 $[:put "successfully sent request $($respdata->"request")"]"
    } else={
        /log/warning "$0 failed, got: $[:tostr $resp]"
        :error $resp
    }
}

$npushover ({ 
        user="u8xxxxxxxxxxx"
        token="acyqxxxxxxxxxxxxxxx"
        message="Perhaps some <b>HTML</b>"
        title="Test Message"
        html=1
        sound="magic"
        priority=0
        url="https://router.lan/rest/system/resource"
        "url_title"="/system/resources"
}) 

To send a message using pushover using the $npushover <array> above, and using an array allows any of the attributes supports like url or priority:

Code: Select all

$npushover ({ 
        user="u8xxxxxxxxxxx"
        token="acyqxxxxxxxxxxxxxxx"
        message="Perhaps some <b>HTML</b>"
        title="Test Message"
        html=1
        sound="magic"
        priority=0
        url="https://router.lan/rest/system/resource"
        "url_title"="/system/resources"
}) 

See https://pushover.net/api for possible/allowed values. No validation is provided, kinda by design. Errors should be output and logged, likely giving a clue as the right values. And stuff like "priority" has additional allowed attributes like "retry", so validation might block that (or get very complex).

:global npushover
$npushover ({ 
        user="private"
        token="private"
        message="Mikrotik SXT Rebooted <b>nPushover</b> $[interface/lte/monitor lte1 duration=2]"
        title="MikroTik SXTR"
        html=1
        sound="magic"
        priority=0
        url="https://192.168.x.1"
        "url_title"="MikroTik"
})

Code: Select all

:global npushover
$npushover ({ 
        user="private"
        token="private"
        message="Mikrotik SXT Rebooted <b>nPushover</b> $[interface/lte/monitor lte1 duration=2]"
        title="MikroTik SXTR"
        html=1
        sound="magic"
        priority=0
        url="https://192.168.x.1"
        "url_title"="MikroTik"
})

.. and it executes, but no info from the LTE is included in the message. Any pointers appreciated.

:global npushover
$npushover ({ 
        user="private"
        token="private"
        message="Mikrotik SXT Rebooted <b>nPushover</b> $[interface/lte/monitor lte1 once as-value]"
        title="MikroTik SXTR"
        html=1
        sound="magic"
        priority=0
        url="https://192.168.x.1"
        "url_title"="MikroTik"
})

All of the commands with "monitor" are tricky, since it's like a "for loop"... So you need to remove "duration" and use "once" instead.

Code: Select all

:global npushover
$npushover ({ 
        user="private"
        token="private"
        message="Mikrotik SXT Rebooted <b>nPushover</b> $[interface/lte/monitor lte1 once]"
        title="MikroTik SXTR"
        html=1
        sound="magic"
        priority=0
        url="https://192.168.x.1"
        "url_title"="MikroTik"
})

The "once" cause the /interface/lte/monitor to only return one set of value to insert into the message. You could use a duration, but that requires collecting the LTE monitor data into a new variable, and then using the new variable in the message.

Thank you for this. Either version of the code $[interface/lte/monitor lte1 once] doesn't add data/content at all to the message (not even the code is included). It this the correct way to pull MikroTik data into the message that is sent?

The received message is as attached (sorry can't seem to attach message)

My bad. I forgot to add the "as-value" — that's critical to returning the data for the string. So it should be "$[/interface/lte/monitor lte1 once as-value]".

message="Mikrotik SXT Rebooted <b>nPushover</b> $[/system clock get time] $[/system identity get name]"

Hi,
I have a question, not so much about pushover.

I use TheDude and pushover - and it worked perfectly up until version 7.6 - in notifications it was enough to call the function "$pushover message="Service [Probe.Name] on [Device.Name] is now [Service.Status]";" just like other scripts.

Unfortunately, in version 7.15 - 7.16 calling $pushover does not work - scripts are called but not pushover - maybe you have an idea to fix it.

Best regards.

policy - policy that grants user management rights. Should be used together with the write policy. Allows also to see global variables created by other users (requires also 'test' policy).
test - policy that grants rights to run ping, traceroute, bandwidth-test, wireless scan, snooper, fetch, email and other test commands

Note: Only scripts (including schedulers, netwatch, etc) with equal or higher permission rights can execute other scripts.

But your issue may be permissions on RouterOS side.... You likely have put the script in /system/script with "Do not require permissions" with "policy" and "test" rights to run /tool/fetch. I believe there should be some log about it but perhaps not.

It's not a permissions issue.

It's not a permissions issue.

Well I do not use notification with Dude, so IDK. But I'm not sure your Terminal test is exactly same user context as Dude running a notification. I cannot say for sure, but when Dude run calls RouterOS... that's more similar to netwatch (which uses a *sys user), than Terminal from a logged in admin user.

Best you can do is add debug logging and perhaps something shows up when Dude call pushover. Because if it works in Terminal it ain't the script code itself, thus the theory on permissions - since there are not a lot of other options...

Does calling a more basic script work from Dude? i.e. one that does not use /tool/fetch or global variables...

/tool fetch mode=https url="https://api.pushover.net/1/messages.json" http-method=post http-data="token=axxxxxxx&user=uxxxxx1&message=Service [Probe.Name] on [Device.Name] is now [Service.Status]" output=none;

Does calling a more basic script work from Dude? i.e. one that does not use /tool/fetch or global variables...

In this form it works and that's enough for me. Thank you.

/tool fetch mode=https url="https://api.pushover.net/1/messages.json" http-method=post http-data="token=axxxxxxx&user=uxxxxx1&message=Service [Probe.Name] on [Device.Name] is now [Service.Status]" output=none;