Chromecast screen not loading

Core Machine (Operating system/System info/Roon build number)

Ubuntu 20.04 LTS
Intel NUC NUC7PJYH
Rune 1.8 build 790

Network Details (Including networking gear model/manufacturer and if on WiFi/Ethernet)

Virgin Media Hub 3 in modem mode connected via ethernet to
Google Nest Router Ethernet into Netgear GS316-100UKS 16 port switch
NUC plugged into Netgear switch
Sony Android TV (BRAVIA KD49XG9005BU) connected via ethernet to netgear switch

Audio Devices (Specify what device you’re using and its connection type - USB/HDMI/etc.)

Group consisting of Sonos AMP with two play:1 speakers as surrounds, three more play:1, a play:5 and sonos move via wifi.

Description Of Issue

When trying to use the Sony Android TV as a display, the device is recognised and I can choose it via the app. However, when choosing to chromecast, I see the ‘Roon’ logo and loading spinner, but the track details never load.

The issue seems similar to issue 45753 which was resolved by opening up the firewall - however, I’m not running the ubuntu firewall and other outgoing connections from the NUC seem fine.

Is there something I can check for in the logs, or some information I can provide to help move forward? How should the track details be loaded, is it an ajax request from the TV to some roon server endpoint or something on the local network that I can check?

I am on a roon trial and being able to chromecast was something I really liked the idea of, so any tips to get this resolved would be much appreciated!

Thanks in advance!

OK, so just an update on this.

After waiting a long time, and clicking “display now” a few times (frustratedly :slight_smile:) this started working.

However, if the screen goes off, we go back to the same process. Any advice on this, and why it’s so temperamental? It’d be great if I didn’t have to go through this every time (and it would also help with the “other half acceptance factor”!).

Thanks again.

Hi @hook_menu_alter

Thanks for your patience here in waiting for us to get back to you!

I’m sorry to hear about the trouble you’re having! So we can better understand this a bit, can you try using the Web Display feature instead of Chromecast? Does this exhibit the same issue, or is it just happening with the Android TV device?

Hi @dylan - no problem, and thanks for getting back to me.

I’ll look up instructions for the web display and give it a try.

@dylan thanks - web display seems to work very well, and spins up very quickly.

do you have any pointers around how to go about debugging the chromecast issue?

thanks.

OK, so an update @dylan

I noticed that the ethernet interface of the TV is limited to 100Mbps, so I switched to Wifi. On a speedtest, this increased lan speed from around 90ish Mbps to around 300Mbps. This means an IP address change, but I have fixed the IP.

However, I am now back to the original issue of having the roon screen “spinner”, and not seeing the track info.

I did notice the following in the logs


04/27 12:52:00 Error: [cast/client] [Nest-Wifi-point-2662f8b6c511d6d52b384e7c1da82c93._googlecast._tcp.local] Exception writing message to stream:
04/27 12:52:00 Trace: [broker/images] Checking for image updates
04/27 12:52:00 Error: [cast/client] [BRAVIA-4K-GB-ATV3-cb1f09da4147d51f10626ccc88d0c56b._googlecast._tcp.local] Exception writing message to stream:
04/27 12:52:00 Error: [cast/client] [BRAVIA-4K-GB-ATV3-cb1f09da4147d51f10626ccc88d0c56b._googlecast._tcp.local] Exception writing message to stream:
04/27 12:52:01 Error: [cast/client] [BRAVIA-4K-GB-ATV3-cb1f09da4147d51f10626ccc88d0c56b._googlecast._tcp.local] Exception writing message to stream:
04/27 12:52:01 Trace: [broker/images] 0 images need update.
04/27 12:52:01 Trace: [broker/images] Image updates complete
04/27 12:52:03 Info: [transport/zonedisplay] Zone display unregistered: BRAVIA 4K GB ATV3

Any clue from that? Or can I provide any more info?

Also, not sure if this is relevant

04/27 12:57:05 Info: [transport/zonedisplay] Zone display unregistered: BRAVIA 4K GB ATV3
04/27 12:57:05 Critical: scx: System.NullReferenceException: Object reference not set to an instance of an object
  at Sooloos.Audio.Cast.CastReceiverChannel+<>c__DisplayClass11_0.<RequestApplicationLaunch>b__0 (Base.JDictionary json) [0x0006d] in <9bb8bf0ed3ea417fae62aac6b2ce154b>:0
  at Sooloos.Audio.Cast.CastClient+<>c__DisplayClass102_0.<SendCastMessage>b__1 () [0x0000a] in <9bb8bf0ed3ea417fae62aac6b2ce154b>:0
  at Sooloos.CallingThread+<>c__DisplayClass12_0.<Post>b__1 (System.Object <p0>) [0x00000] in <266a2727f1a5403eb5e4eeb3d2b5b7f1>:0
  at Sooloos.SynchronizationContextThread._Dispatch (Sooloos.SynchronizationContextThread+SendOrPostWrapper& ret) [0x00012] in <266a2727f1a5403eb5e4eeb3d2b5b7f1>:0
04/27 12:57:05 Critical: scx: System.NullReferenceException: Object reference not set to an instance of an object
  at Sooloos.Audio.Cast.CastReceiverChannel+<>c__DisplayClass11_0.<RequestApplicationLaunch>b__0 (Base.JDictionary json) [0x0006d] in <9bb8bf0ed3ea417fae62aac6b2ce154b>:0
  at Sooloos.Audio.Cast.CastClient+<>c__DisplayClass102_0.<SendCastMessage>b__1 () [0x0000a] in <9bb8bf0ed3ea417fae62aac6b2ce154b>:0
  at Sooloos.CallingThread+<>c__DisplayClass12_0.<Post>b__1 (System.Object <p0>) [0x00000] in <266a2727f1a5403eb5e4eeb3d2b5b7f1>:0
  at Sooloos.SynchronizationContextThread._Dispatch (Sooloos.SynchronizationContextThread+SendOrPostWrapper& ret) [0x00012] in <266a2727f1a5403eb5e4eeb3d2b5b7f1>:0
04/27 12:57:05 Critical: scx: System.NullReferenceException: Object reference not set to an instance of an object
  at Sooloos.Audio.Cast.CastReceiverChannel+<>c__DisplayClass11_0.<RequestApplicationLaunch>b__0 (Base.JDictionary json) [0x0006d] in <9bb8bf0ed3ea417fae62aac6b2ce154b>:0
  at Sooloos.Audio.Cast.CastClient+<>c__DisplayClass102_0.<SendCastMessage>b__1 () [0x0000a] in <9bb8bf0ed3ea417fae62aac6b2ce154b>:0
  at Sooloos.CallingThread+<>c__DisplayClass12_0.<Post>b__1 (System.Object <p0>) [0x00000] in <266a2727f1a5403eb5e4eeb3d2b5b7f1>:0
  at Sooloos.SynchronizationContextThread._Dispatch (Sooloos.SynchronizationContextThread+SendOrPostWrapper& ret) [0x00012] in <266a2727f1a5403eb5e4eeb3d2b5b7f1>:0
04/27 12:57:05 Critical: scx: System.NullReferenceException: Object reference not set to an instance of an object
  at Sooloos.Audio.Cast.CastReceiverChannel+<>c__DisplayClass11_0.<RequestApplicationLaunch>b__0 (Base.JDictionary json) [0x0006d] in <9bb8bf0ed3ea417fae62aac6b2ce154b>:0
  at Sooloos.Audio.Cast.CastClient+<>c__DisplayClass102_0.<SendCastMessage>b__1 () [0x0000a] in <9bb8bf0ed3ea417fae62aac6b2ce154b>:0
  at Sooloos.CallingThread+<>c__DisplayClass12_0.<Post>b__1 (System.Object <p0>) [0x00000] in <266a2727f1a5403eb5e4eeb3d2b5b7f1>:0
  at Sooloos.SynchronizationContextThread._Dispatch (Sooloos.SynchronizationContextThread+SendOrPostWrapper& ret) [0x00012] in <266a2727f1a5403eb5e4eeb3d2b5b7f1>:0
04/27 12:57:05 Critical: scx: System.NullReferenceException: Object reference not set to an instance of an object
  at Sooloos.Audio.Cast.CastReceiverChannel+<>c__DisplayClass11_0.<RequestApplicationLaunch>b__0 (Base.JDictionary json) [0x0006d] in <9bb8bf0ed3ea417fae62aac6b2ce154b>:0
  at Sooloos.Audio.Cast.CastClient+<>c__DisplayClass102_0.<SendCastMessage>b__1 () [0x0000a] in <9bb8bf0ed3ea417fae62aac6b2ce154b>:0
  at Sooloos.CallingThread+<>c__DisplayClass12_0.<Post>b__1 (System.Object <p0>) [0x00000] in <266a2727f1a5403eb5e4eeb3d2b5b7f1>:0
  at Sooloos.SynchronizationContextThread._Dispatch (Sooloos.SynchronizationContextThread+SendOrPostWrapper& ret) [0x00012] in <266a2727f1a5403eb5e4eeb3d2b5b7f1>:0
04/27 12:57:07 Debug: [volumewatcher] ev_VolumeChanged DidMount: /run/docker/runtime-runc/moby/1e2a402e1fc42bbb30191b8125fb1497ed72201a22e8ef64cdc888cf6e5adc60/runc.1bCLie

Eventually the display is showing again, but if I stop the display I need to again go through the waiting a very long time - in some cases it just doesn’t seem to want to display at all.

In other words, back to the original issue.

Any help much appreciated!

Another observation, may be irrelevant but best to have all the details.

Occasionally, there will be “no displays available” (in the speaker menu at the bottom right), which appears to resolve itself when I go to “Settings → Displays”.

Do you have an actual Chromecast device to test against? It would be interesting to see if the actual Chromcast device has the same display issue when plugged into the TV vs the TV’s internal chromecast implementation.

Unfortunately I don’t have any other chromecast displays @Rugby