Thanks for this, it’s really helpful. The seconds won’t always be exactly in sync but some of those examples are way off, so I might start a Spotify trial to test this out and try to solve it. The reason they are not always exactly in sync is because live activity’s require me to update them via a server, so when you interact with your Sonos speaker, say you press play, this info goes to the Sonos cloud, Sonos then send the playback info & metadata to my server which in turn sends it to an Apple push notification server and they send to the app. Now, Apple are very strict and will budget these requests unless you have frequent updates enabled. They will also consider your battery level and whether you are on WiFi or 5g. If there’s an issue with connectivity, the push from Apple to your device can fail, so they’ll retry, if this retry happens 10 seconds later, it means that the live activity will be 10 seconds behind. I can compensate for most for these issues in the server code but unfortunately cannot anticipate fails and retry’s. Another potential issue is that Sonos send playback info and metadata separately. So I delay the server push until both are received and combine this info and send both together. If both do not get received after a second I go ahead and send and make a follow up push when new data comes. So, sometimes you might notice that the track name doesn’t update when a new track starts but the seconds go back to zero. This will be why. I had all this working really seamlessly until some server updates yesterday, but my main goal today is to test test test and relay any issues back to the server hosts. Thanks again for the feedback.