PushNotificationUrls sending data output multiple times

Volumio Development
1

Hello Volumio Community,

I’m using an http endpoint ( filebeat ) in ordet to get status changes of my volumio player ( v 3.378 / x86_amd64 ).

As per NGINX logs the api is sending the status change event multiple times:

192.168.1.151 - - [06/Dec/2022:23:48:51 +0100] "POST / HTTP/1.1" 405 157 "-" "-"
192.168.1.151 - - [06/Dec/2022:23:48:51 +0100] "POST / HTTP/1.1" 405 157 "-" "-"
192.168.1.151 - - [06/Dec/2022:23:48:51 +0100] "POST / HTTP/1.1" 405 157 "-" "-"
192.168.1.151 - - [06/Dec/2022:23:48:51 +0100] "POST / HTTP/1.1" 405 157 "-" "-"
192.168.1.151 - - [06/Dec/2022:23:48:51 +0100] "POST / HTTP/1.1" 405 157 "-" "-"
192.168.1.151 - - [06/Dec/2022:23:48:51 +0100] "POST / HTTP/1.1" 405 157 "-" "-"

192.168.1.151 - - [06/Dec/2022:23:52:37 +0100] "POST / HTTP/1.1" 405 157 "-" "-"
192.168.1.151 - - [06/Dec/2022:23:52:37 +0100] "POST / HTTP/1.1" 405 157 "-" "-"
192.168.1.151 - - [06/Dec/2022:23:52:37 +0100] "POST / HTTP/1.1" 405 157 "-" "-"

192.168.1.151 - - [06/Dec/2022:23:56:55 +0100] "POST / HTTP/1.1" 405 157 "-" "-"
192.168.1.151 - - [06/Dec/2022:23:56:55 +0100] "POST / HTTP/1.1" 405 157 "-" "-"
192.168.1.151 - - [06/Dec/2022:23:56:56 +0100] "POST / HTTP/1.1" 405 157 "-" "-"

I got at least 3 post request for each status change and in the timeframe shown in the logs i was just normally playing a playlist ( no pause / play / skip actions ).

Is there any way to fix this behaviour?

I’m sending the filebeat stream to elasticsearch to create stats simliar to “spotify wrapper” ones but working with duplicates records makes it more difficult.

Edit:

Thanks all,

Luca

2

Hi Luca, update to the latest version, we improved this a lot on this release

1 Like
3

oh, wow

It works definitely better. Really thanks!

JFYI: i now get 3 pushes for each song ( just playing a playlist ).

If the song seek is up to 300000

  1. pause, seek 0
  2. play, seek 0
  3. pause, seek 300000

I think is not the expected behaviour, luckily i can filter the records on elk

Thanks again for your amazing job.
Best community here :slight_smile:

Luca

4

Hello All, :slight_smile:

Quick update after further tests!

The behaviour i described above is related to spotify connect.

If using tidalconnect, i get about 3/4 push into the http endpoint.

Here 2 elasticsearch screenshot

  • TidalConnect

Screenshot-2022-12-14-22-16-47

  • Spotify

Screenshot-2022-12-14-22-32-46

Thanks again for your work;

Luca

5

Hi Luca, Spotify currently is quite a troublesome plugin and needs rework. The issue is that events are sent very unpredictably from the librespot daemon which is used. Hence the unpredictable behaviour.
Until the plugin is fixed, you ll probably have to filter some events

1 Like