Websocket Event inactiveSession is not always sent after playback ended

[DrRSatzteil]

Describe the bug
I use the websocket event inactiveSession to start a timer that shuts down the system after a couple of minutes after the playback ended. Unfortunately I do not always get an inactiveSession message after playback has stopped and thus the player keeps running until someone manually switches it off or the battery runs flat.

To Reproduce
It seems that this event is not generated when the playback ends after the last song of a playlist has been played. I just observed the following:

1. Start to play a playlist via Spotify connect from my Laptop
2. Wait until the last song on the playllist has finished playing
3. After the last song I get the following events (excerpts) in this order:

• {"event":"playbackEnded"}
• {"event":"trackChanged","userInitiated":false,"...dQ0ErIVIxELlxIgNUYxnO"}
• {"event":"metadataAvailable","track":{"gid":"AB...4A7B32050F0C66E138F"}}}

My observation is that this last track change and metadata events change the current track back to the first track of my playlist which I did not expect to happen. However given the fact that the playback is finished and the next play command should start the playlist from the beginning this absolutely makes sense. However I do not receive an inactiveSession event afterwards. I do however receive an inactiveSession event a couple of seconds after I pause the playback.

Expected behavior
I would expect to receive an inactiveSession event when the playback has ended for whatever reasons. Alternatively, if this is the expected behaviour I would like to have another way of determining that the player is currently not playing anything. I tried to start the shutdown countdown for playbackEnded events and stop the countdown for trackChanged events but this also does not work since the last event after a playlist is finished is always a trackChanged followed by a metadataAvailable.

Screenshots/Stracktraces/Logs
N/A

Version/Commit
Version 1.6.2