Skip to content

Use the message timestamp as the time of a reported position - #112

Merged
Sholofly merged 1 commit into
devfrom
fix/position-update-timestamp
Oct 30, 2026
Merged

Sholofly merged 1 commit into
devfrom
fix/position-update-timestamp

Conversation

@Sholofly

Copy link
Copy Markdown
Owner

For nDVR recordings, replays and the review buffer, last_position_update was set from lastSpeedChangeTime. Boxes report a relativePosition that tracks real time but a lastSpeedChangeTime hours in the past, so Home Assistant extrapolated the position far beyond the duration and the progress bar and ad-break detection broke.

Use the status message timestamp instead, falling back to the current time when it is missing, as linear and VOD already do. This also removes an unguarded int() on a possibly missing lastSpeedChangeTime.

For nDVR recordings, replays and the review buffer, last_position_update
was set from lastSpeedChangeTime. Boxes report a relativePosition that
tracks real time but a lastSpeedChangeTime hours in the past, so Home
Assistant extrapolated the position far beyond the duration and the
progress bar and ad-break detection broke.

Use the status message timestamp instead, falling back to the current
time when it is missing, as linear and VOD already do. This also removes
an unguarded int() on a possibly missing lastSpeedChangeTime.

Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
@Sholofly
Sholofly merged commit daf6048 into dev Oct 30, 2026
2 checks passed
@Sholofly
Sholofly deleted the fix/position-update-timestamp branch October 30, 2026 19:53
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant