castnow doesn't find chromecast

[bitboxer]

Somehow castnow stopped working on my machine today. It can't find the chromecast in my network. The chromecast extension in my browser finds it and play youtube videos without problems.

What can I do to diagnose the problem?

[auchenberg]

I'm experiencing the same.

It looks like my Chromecast after the 25525 firmware update, doesn't broadcast itself over mDNS/bonjour.

Anyone to confirm?

[xat]

Mine is still on 22062 so I can't confirm yet :)

[tifroz]

Same here, castnow no longer finds Chromecast (other apps seem OK). This happened immediately after my chromecast auto-upgraded to build 25525 today

[xat]

@tifroz are you also on firmware v25525 ?

[tifroz]

Yes I am. The first time I saw the symptoms was also the first time I fired castnow against chromecast firmware v25525 (I have not been able to get it to work since then).

Could be a coincidence but with other folks reporting the same it seems pretty unlikely.

[xat]

You can use the --address parameter until my chromecast is updated and I'm able to fix it.

[auchenberg]

I'm able to run use both chromecast-player and chromecast-scanner, with v25525, so I think it's a race-condition in the castnow code, that leaves castnow stuck in the scanning-state.

It's just odd that it suddenly occurred with new firmware.

[xat]

Okay, that is strange. I'm really curious to find out the cause of this issue :-D

[vekin]

Scanning stopped working for me after the latest Chromecast firmware update.
I played with guest mode and Netflix for a bit and then upon disabling guest mode, scanning no longer works.
Firmware 26653
castnow --address works fine.

[auchenberg]

Okay with firmware 26653 I managed to get things working when using the master version of Castnow, which seem to use "chromecast-player": "0.1.7".

However the published version of castnow on NPM seem to use "chromecast-player": "0.1.6", which is has the bug.

Can you bump the version, tag the release and publish it to NPM?

[xat]

ah sorry, did not see this comment.
sure that it works now?
Because over at thibauts/node-castv2-client#22 the guy says the current version of chromecast-scanner only finds chromecast in 1 of 20 times.

[auchenberg]

It's working for me right now. I'll try again tomorrow, to see if it's a temporally thing. Crossing my fingers :)

[xat]

okay :)

[xat]

I've added an --ssdp option which will use SSDP instead of MDNS for scanning. If the problem with MDNS persists I'll make SSDP the default scanning type.

[vekin]

Its working now for me as well with and without --ssdp

[bitboxer]

It is working now on my machine, too. Even without the --ssdp switch

[xat]

thanks for the feedback. I'll close this one for now :)

[pablomusumeci]

Hi there, this issue is happening to me right now. I have the 26653 version. Castnow can't finde any device in the network, but youtube and googlecast app can. I've tried the --ssdp option but I couldn't get any result. Is there anyone having this problem?. Btw, thank you @xat for all the effort you put on this, I really appreciate it :¬)

Edit: I've removed castnow and installed it again and the problem disappeared. Software (just like the life itself) works in mysterious ways :P

[bugdanov]

Hi ! Thanks !

I own a chromecast key model H2G2-42.

I had many timeouts with chromecast-scanner ttl set to 10000... no more timeouts with 20000.

xat/chromecast-player#14