Castnow giving the error "App not found" when casting to chromecast audio

[rossdargan]

The app was working well for me, but I needed to filter to a device, now I just get the error "app not found"

You can see the error here: http://i.imgur.com/CBCWDN1.png.

[rossdargan]

Ok, I think it's down to the chromecast it connects to. This appears to only occur when I connect to chromecast audios.

[rossdargan]

I got these npm issues - could it be related?

npm WARN engine windows-no-runnable@0.0.6: wanted: {"node":"0.6"} (current: {"node":"0.10.42","npm":"2.14.20"}) npm WARN deprecated bittorrent-dht@3.2.6: Critical security issue fixed in 5.1.3. All users should upgrade. (More info: https://github.com/feross/bittorrent-dht/issues/87) npm WARN engine hawk@0.10.2: wanted: {"node":"0.8.x"} (current: {"node":"0.10.42","npm":"2.14.20"}) npm WARN engine boom@0.3.8: wanted: {"node":"0.8.x"} (current: {"node":"0.10.42","npm":"2.14.20"}) npm WARN engine hoek@0.7.6: wanted: {"node":"0.8.x"} (current: {"node":"0.10.42","npm":"2.14.20"}) npm WARN engine sntp@0.1.4: wanted: {"node":"0.8.x"} (current: {"node":"0.10.42","npm":"2.14.20"}) npm WARN engine cryptiles@0.1.3: wanted: {"node":"0.8.x"} (current: {"node":"0.10.42","npm":"2.14.20"}) npm WARN engine mdns-js@0.5.0: wanted: {"node":">= 4.1.0"} (current: {"node":"0.10.42","npm":"2.14.20"}) npm WARN engine mdns-js-packet@0.2.0: wanted: {"node":">= 4.1.0"} (current: {"node":"0.10.42","npm":"2.14.20"})

[rossdargan]

Ok, the issue looks like it's not happy connecting to a chrome cast audio when there is nothing playing. It will happily play stuff to it, and control it. Here is a log

Nothing playing root@openhab:~# DEBUG=castnow* castnow --address 192.168.1.25 castnow attaching... +0ms castnow:stdin undefined +1ms castnow player status: scanning +1ms castnow player status: connecting +2ms castnow player status: finding +133ms castnow player error: [Error: app not found] +49ms Error: app not found

Plex playing root@openhab:~# DEBUG=castnow* castnow --address 192.168.1.25 castnow attaching... +0ms castnow:stdin undefined +1ms castnow player status: scanning +1ms castnow player status: connecting +2ms castnow player status: finding +134ms castnow player status: joining +47ms castnow player status: ready +3ms castnow player status: playing +55ms

[artheus]

So this might be an issue with the Default Receiver App. I don't know much about the Chromecast Audio to be honest, but maybe it has got another app id for the default receiver than the video chromecast? The video chromecast has got CC1AD845

[nohum]

I do have a Chromecast Audio and have the same issue ("Error: app not found"). Please tell me how to get the default receiver app id as I would try to verify if it is the same (or not) as for the default Chromecast.

---

Edit: Using PyChromecast, i got back the following output which implies the same app id:

CastStatus(is_active_input=None, is_stand_by=None, volume_level=0.4745098054409027, volume_muted=False, app_id=u'CC1AD845', display_name=u'Default Media Receiver', namespaces=[u'urn:x-cast:com.google.cast.media'], session_id=u'F9930D6A-367A-4CCE-90F9-FDF3CD0BC8D2', transport_id=u'web-2', status_text=u'Ready To Cast')

[lionelripoll]

Hi,

Same here. Any news ? How can I help ?

[twonky4]

I have the same issue with Chromecast Audio, if device is idling and no app is connected and no playback file is set.

tf@tinkerforge-RED:~$ DEBUG=castnow* castnow --address 192.168.178.149 castnow attaching... +0ms castnow:stdin undefined +61ms castnow player status: scanning +44ms castnow player status: connecting +43ms castnow player status: finding +298ms castnow player error: Error: app not found at /usr/local/lib/node_modules/castnow/node_modules/chromecast-player/index.js:167:39 at /usr/local/lib/node_modules/castnow/node_modules/castv2-client/lib/controllers/receiver.js:86:5 at /usr/local/lib/node_modules/castnow/node_modules/castv2-client/lib/controllers/receiver.js:31:5 at fn.onmessage (/usr/local/lib/node_modules/castnow/node_modules/castv2-client/lib/controllers/request-response.js:27:7) at emitTwo (events.js:111:20) at fn.emit (events.js:191:7) at Channel.onmessage (/usr/local/lib/node_modules/castnow/node_modules/castv2-client/lib/controllers/controller.js:16:10) at emitTwo (events.js:106:13) at Channel.emit (events.js:191:7) at Client.onmessage (/usr/local/lib/node_modules/castnow/node_modules/castv2-client/node_modules/castv2/lib/channel.js:23:10) +169ms

[LindseyB]

I'm having the same issue. It was working for years prior to me hitting this and now I can't seem to get around it.

[nnuel]

I still get the same error