Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Greenscreen doesn't list my chromecast(s) #63

Open
NathanSharp opened this issue Jul 26, 2016 · 7 comments
Open

Greenscreen doesn't list my chromecast(s) #63

NathanSharp opened this issue Jul 26, 2016 · 7 comments

Comments

@NathanSharp
Copy link

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.

@ApsOps
Copy link

ApsOps commented Aug 29, 2016

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

@cjhin
Copy link

cjhin commented Sep 28, 2016

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?

@brianherbert
Copy link

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.

@cjhin
Copy link

cjhin commented Jan 10, 2017

+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 :(

@emcniece
Copy link

Experiencing this as well.

@meyerbro
Copy link

Me too...

@superhawk610
Copy link

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

7 participants