SABnzbd Forums

I'm running 1.0.0 [a58bb38] on MacOS. All Pushover notification that I have set to test (start up/shutdown, job failed, warning, error) are coming to pushover without sound.
Only "Test Notification" comes with default Pushover sound.

From PushOver's API documentation:

If no sound parameter is specified, the user's default tone will play. If the user has not chosen a custom sound, the standard Pushover sound will play.

We don't send a sound parameter, so the default sound should play.
Each event does have a priority and possibly priorities have an influence on sound as well.

Should but it doesn't. There are two default sounds for low and high priority to be set on Pushover side. Like I said, only when I use "Test Notification" it comes with sound.
Other events regardless of the priority are coming silent.

The test message is sent with the priority of event category "other".
So check what "other"'s priority setting is. That one produces sound.

"Low" is not working. "High" sends the sound ok. Third option is "Confirm" which returns error:
Error: Bad response from Pushover (400): {"expire":"must be supplied with priority=2","errors":["expire must be supplied with priority=2"],"status":0,"request":"xxx"}

Any update to this?

We'll look for a solution in release 1.0.1

I did some fixes to support the current PushOver API better (will be in 1.0.1).

The sound however is a different matter.
I tested with the iOS app and it worked OK.
But I did notice one anomaly in PushOve itself.
Initially there was no sound for anything except the Test message.
Only after I had set the default sound to another one and then back to the PushOver default, the sound worked as it should.
To me: that's a bug in PushOver.

For me sound works only with High priority, I have been changing default sounds too. Maybe in further implementations you can let us choose sound, that seems to be working ok for other apps I'm using.

We just follow the API. Specifying no sound means a default sound should be used.
If it doesn't, then this clearly points to a bug in PushOver.