By default, pushover will display the timestamp their server received a notification for displaying it to the user.
This can lead to confusion if messages are sent fast but received out-of-order.
To mitigate this, their API allows to include a timestamp, e.g. when a message is created, which will be used instead. The timestamp uses Unix time format.
So far, shoutrrr is missing the timestamp parameter.
P.S. I already asked them to allow timestamps with sub-seconds accuracy, but they did not respond yet.
By default, pushover will display the timestamp their server received a notification for displaying it to the user.
This can lead to confusion if messages are sent fast but received out-of-order.
To mitigate this, their API allows to include a timestamp, e.g. when a message is created, which will be used instead. The timestamp uses Unix time format.
So far,
shoutrrris missing the timestamp parameter.P.S. I already asked them to allow timestamps with sub-seconds accuracy, but they did not respond yet.