[Investigating] No Google Cast destinations will enable in 1584

Early Access
1

I’ve tried both “real” Google devices and other devices that you can cast to, and none will enable.

Note that on one device (an Android TV-based Beovision 14), if you click “Enable” the TV turns on, but it doesn’t enable.

2

Hi, @David_Nanian, thank you for the report, I will investigate this one.

—
Ivan

3

Hi, @David_Nanian, sorry for the delay here. I inspected the diagnostics report from your machine. There is an error which indicates that there was an issue trying to start the cast app on the device:

Failure to start application 6242A3BE on device: { "reason": "CANCELLED", "requestId": 284860, "type": "LAUNCH_ERROR" }

It does look related to the cause, but at the same time it does not provide a lot of insight into what can be wrong here. Because of that, I have the following questions:

  1. Did you notice this problem right after updating to #1584 or it was working and only after that broke down?
  2. Have you tried rebooting RoonServer and see if that helps?

We tried to reproduce this issue with the local Chromecast devices we have locally and everything seems to be working correctly.

Thanks!

–
Ivan

4

It was previously enabled and working. When I was having the AirPlay issue (that you fixed), I had to disable all devices at your request. I tried re-enabling, and that’s when it failed. It continues to fail now, and yes, I have rebooted.

Note that I’m able to cast to this device via my phone without any problem. (I recognize that doesn’t necessarily mean much.)

I am able to enable some other devices now, but not all - the Beovision and the Beosound 35 won’t enable. They have, I believe, “older” Cast implementations, since their chipsets weren’t supported by the newest Google Cast client build. However, as I said, I can cast to them…they just won’t participate in “dynamic” (add-on-the-fly) multirooom.