· Other
· None of the above
· Other
Chromecast to Display stops working and device goes missing
Windows Server 2019 wired ethernet connection with roon installed.
Hegel H390 amplifier with Roon support connected with ethernet wire
Google Nest Hub (as Display) connected via Wifi (only option)
Router in same room as other devices mentioned above.
Isn’t it a problem with the chromecast in general. I’ve red today that a lot of chromecast stopped working (and google is looking for a solution)
To add some additional info:
After a reboot of the server or restart of roon services the ”Display” (Google nest hub) is present and usable.
But it dissappears after about a few hours from roons ”Display” list.
Even when missing from Roons ”Display”-list the Nest Hub is availabe to cast to from ALL OTHER DEVICES (apple tv wired, iphone wireless etc.) both wired and wireless, it is only Roon that ”forgets” the device.
Hi @Spencer_Didriksen,
Thanks for reaching out to us about this issue. I activated diagnostics on your account but I couldn’t find any mention of the Chromecast in your logs. Could you reproduce the Chromecast disappearing from displays and let us know the date and time that it happens? That would hopefully allow us to find the error in your logs.
Take a look e.g. in https://www.reddit.com/r/Chromecast/comments/1j7g1vz/help_whats_going_on/
Certificate seems not to be valid anymore for chromecast devices from the first and second version.
The best is, to wait for a solution from google…
I can cast no problem from any other device, so no certificate issue.
Enabled now so should appear as an issue soon.
There, it has dissappeared once again, hopefully that is visible in the logs.
I left the units playing and went to bed at about 21:00 yesterday (March 10th) and this morning the Display device was again missing from roon.
Hi @Spencer_Didriksen ,
Thanks for those additional details! We’ve activated diagnsotics for your account and looking over the timestamp you provided it looks like there was an invalid media session error.
I wonder if perhaps using a reserved IP address for the Chromecast device can help? Are you able to access your rotuer settings and try to configure the Nest to ensure that it gets a reserved IP from the router?
If that doesn’t do it, you mentioned that restarting your Roon Server temporarily fixes the issue, is it the same if you restart the Nest as well? So either a Roon Server or a Nest re-establishes connection?
Hi, all devices already have reserved ip’s on my network, but it was a good suggestion.
Restarting/power-cycling the google nest hub does not make it appear as a display in roon, it takes a restart of the server/roon application to make it come back as a selectable device.
Thanks for the update!
Could you please test out moving the issue hub closer to your router? Since you’re only able to use Wifi for the device, are you able to test out different bandwidths, like the 5gHZ band?
Let me now if this helps. Thank you! 
Hi, the Nest Hub is 2,5 meters away from the router, it has excellent signal strength according to my routers wifi stats.
I seriously doubt is an issue with bands, since I can cast from other devices further away in my apartment and not lose the casting on the hub.
We completely understand! Doubts aside, we can only go off what we see from the diagnostic report of your Roon Server, which shows errors in your logs indicate chromecast discovery and connectivity issues within Roon. Here’s a breakdown of what’s happening and potential causes:
Info: [Broker:Transport] [cast] lost device ... because we got a TTL=0 mDNS packet
TTL (Time To Live) set to 0, which signals that the Chromecast device is no longer available. This can happen due to network instability, router multicast issues, or the device momentarily disconnecting.Then:
Warn: [Broker:Transport] [cast/discovery] unexpected KeyNotFoundException error in device data
This could be due to corrupt mDNS responses, a firmware issue on the Chromecast device, or a temporary miscommunication between Roon and the device.
Can you check if IGMP Snooping is enabled on your router (some routers block multicast discovery without it)?
Also, if your router has a setting for “AP Isolation” or “Client Isolation,” test out disabling it.
Lastly, if you have a firewall, security suite, or Pi-hole/ad-blocker, it could be interfering with mDNS discovery. Try temporarily disabling it to see if Roon can rediscover the devices. 
Thanks I will try these suggestions and reply with results!
Sounds good @Spencer_Didriksen! 
So unfortunately I am unable to find any settings related to IGMP Snooping or Multicast on my router, it is partially locked by my broadband supplier as I only “loan” it from them during my subscription.
There was no AP or Client isolation enabled though.
No firewall apart from Windows server default one.
Got it, thanks for exploring those options. If you haven’t yet, I’d explore reinstalling the latest firmware to the Nest Hub.
This could also be a symptom of Windows Defender. If you temporarily disable it, do you still run into the same issue?
I uninstalled ”Bonjour service” which was on the server, and so far the Nest Hub has not disappeared.
It does go to it’s screensaver mode even though Roon is casting within a few minutes, and this can not be disabled, could you guys perhaps add a feature so Roon initiates the display for each new track that playback is started for?
That would at least make it wake up and continue displaying.
Hey @Spencer_Didriksen,
Thats great news!
I’d suggest creating a thread over in our Feature Suggestions category - this is where others on community can also upvote any features wanted in Roon!
We’ll leave the thread open for now so you have more time to test things.