-
Notifications
You must be signed in to change notification settings - Fork 62
Chromecast built-in devices won't show up in the admin menu #102
Comments
Unless you use |
I did run it with --net=host option enabled hence the logs showing the device. It's just the admin portal that won't show them. I have also tried with manual installation (not the docker) and it's the same. The TV's are being discovered by the avahi driver but the admin page still won't show them :/ |
It seems the device was detected at some point but is not anymore. I don't have much clue as why nodecastor is able to see it and not dashkiosk... Maybe update mdns package? |
Is there a cli command I can use to send a test url to the chromcast device? |
You can try with nodecastor. But nodecastor sees the Chromecast while Dashkiosk doesn't. |
I have updated the mdns package to the lastest but still no luck. |
At https://github.com/vincentbernat/dashkiosk/blob/master/lib/chromecast.js#L133, you see you should get a log message when a new device is detected. You don't get it. It's called from https://github.com/vincentbernat/dashkiosk/blob/master/server.js#L41. Just to be sure, you did specifically enable Chromecast support (either in config file or on command line)? |
I do get it. If I switch on more TVs I get more logs that they have been discovered unless we are talking about different things.
Just not sure where to go next. |
Oh, I have missed this! With nodecastor's
|
|
It seems OK. Can you run Dashkiosk with |
I will try to set it up but just to let you know my TV just got discovered few minutes ago. Now the status looks like this:
|
Ok, yesterday all the Chromcast TV's appeared on the admin menu but after rebooting them they are no longer visible and we're back to where we started. I have enabled the debug logs and here is the result:
Also when I cast from Chrome browser to the TV I see this in logs:
at the moment all my Chromcast devices show this status:
I can ping them by dns name in case this helps
any other suggestions? |
@vincentbernat
Once I've done that the device appears on the admin portal and I can move to a group. Appreciate your help so far. Do you have any more suggestions? I've also noticed that the dashkiosk likes to crash very often when I disconnect my TVs from the network but that's probably another issue.
|
Sorry for not helping. 644 MB seems to be a lot and there may be a leak somewhere. I didn't run into this issue, but I am not using Chromecasts since a long time. Dashkiosk works for me, but the code is getting pretty old, depending on old versions of many libraries and I have no time and no motivation to update. JS is not my favorite language and the ecosystem moves too fast for me. I am just saying that for you not to spend too much time on trying to make it work. So, for the leak, no clue. For the problem to detect Chromecast, your best bet is to add many |
Hello,
Similar issue to #99 but it's now working for me.
I run Docker version of the kiosk and I can see the device in the cli but it's not showing up in the admin menu.
Would really appreciate any advice :)
The text was updated successfully, but these errors were encountered: