Open vredesbyyrd opened 2 years ago
I don't quite understand how the idle timeout works, but I believe that thread is saying it is set by the "app developer" which will be whoever built the chromecast application (I think) eg; Netflix, Youtube, etc. There may be some APIs to control this, although I am not too familiar with any of them, and it might depend on if the app developer implemented the APIs:
I don't know if we can control the heartbeat from our end since the "PING" comes from the chromecast and we always reply with "PONG". I don't know if it is possible to force a heartbeat by sending our own "PING".
Hi, thanks for sharing go-chromecast - its great!
If you pause the playing content for greater than 20min, chromecasts "ambient" mode kicks in and begins displaying a slideshow. This would be great if there was a way to keep the connection alive - but attempting to unpause the stream results in nothing, and I do not see any errors in the
go-chromecast ui
log section of the tui.Running
go-chromecast -v -u uuid load sample.mp4
shows that after 20min the connectionsheartbeat
stops, and"isIdleScreen":true
. I am casting to a gen 3 dongleI assumed timeout could be configured from the chromecast side, but was not so surprised to find out it's not possible - at least without enabling "developer mode" via
adb
(maybe). Even then people appear to have mixed results.Do you have thoughts on potentially working around this? Yes, screen burn in needs to be considered - but 20min is too short imo.
Thanks for your time.
EDIT: Not sure how accurate this info is, but it references configuring the various timeouts from the app side, specifically the first comment. Ideally we could keep the connection alive regardless of chromecasts ambient mode - but I assume its not possible?
chromecast timeout