Cupra Tavasca Live Data over Enode online partialöy available

I got this answer from Enode:

“What you're seeing is a characteristic of Cupra's vendor API. The vehicle itself only uploads a new state to the Cupra cloud when something prompts it, primarily ignition on or off events and during active charging. While the vehicle is parked and idle, the cloud holds onto the last known values and returns those same values until the next upload. Our polling continues normally during that period, but the data we can return is only as recent as the vehicle last reported. In today's logs we saw stretches of 20 to 45 minutes where the timestamp on the data did not advance, followed by an immediate refresh as soon as the vehicle re-engaged.

This is consistent behaviour across the wider Volkswagen Group platform that Cupra sits on, and it isn't something we can change from the integration side. The most reliable signal of freshness is the timestamp included with each reading, which reflects when the vehicle last reported rather than when we last polled. Surfacing that timestamp in ABRP, or treating data older than a configurable threshold as stale, would give end users an accurate picture of when the vehicle is actively reporting versus dormant.

Happy to dig further if you have a specific session where you'd expect data to be flowing (during a drive or charge) and it wasn't.”