greenscreen icon indicating copy to clipboard operation
greenscreen copied to clipboard

Greenscreen doesn't list my chromecast(s)

Open NathanSharp opened this issue 8 years ago • 7 comments

I have followed the directions to the letter and they are not showing. i have even removed and readded the application and the devices from the SDK. does it matter if the host machine that greenscreen runs on is on wifi? there isn't anything in the docs about it.

NathanSharp avatar Jul 26 '16 18:07 NathanSharp

Same issue with me. @NathanSharp Were you able to figure this out?

ApsOps avatar Aug 29 '16 13:08 ApsOps

does it matter if the host machine that greenscreen runs on is on wifi?

@NathanSharp I'm assuming by this you mean that your host machine is using a wired connection to connect to the network? Did you end up figuring out if this was the issue?

cjhin avatar Sep 28 '16 21:09 cjhin

We can see our Chromecasts and are able to cast to them from Chrome but they aren't listed in Greenscreen. The machine we have set up to run this is wired on the network. We also tried doing it via wifi which didn't help, although I'm not sure why that would matter. So, +1 on this issue.

brianherbert avatar Jan 10 '17 19:01 brianherbert

+1 we're having the exact same issue as @brianherbert. We're having to run our chromecasts wired b/c our WAPs are not allowing the chromecasts to stay connected.

These are the debug messages that show: (the interesting thing IMO is the Chromecast is available true after step 2, but the failure to connect after step 3)

  1. Visit index (localhost:4994)
  2. Click "Chromecasts" / visit localhost:4994/chromecasts image
  3. Click "Add a chromecast" / visit localhost:4994/chromecasts/new image

That error message corresponds to the connect function and seems to be an error possibly coming from the chromecast-away package?

connect function aka gscreen.js:540-549

// gscreen.js:540-549
connect = function () {
  return castAway.connect(function (err, s) {
    if (err)
      return console.log('ERR', err);
    session = s;
    return $scope.$apply(function () {
      return $scope.chromecast.name = session.session.receiver.friendlyName;
    });
  });
};

That's as far as I got before giving up and just setting up multiple chrome profiles and individually casting tabs to different chromecasts :(

cjhin avatar Jan 10 '17 20:01 cjhin

Experiencing this as well.

emcniece avatar Jan 29 '17 17:01 emcniece

Me too...

meyerbro avatar May 17 '17 16:05 meyerbro

Check out multicast, it's a complete rewrite of Greenscreen that takes advantage of the new Castv2 API via mDNS. Should fix this problem.

superhawk610 avatar Oct 05 '17 20:10 superhawk610