The DefaultMediaReceiver is always not found.
Closed this issue · 4 comments
When I use the “node-castv2-client” node module, the DefaultMediaReceiver is always not found. The main error message is as follows:
Error: Launch failed. Reason: NOT_FOUND
at c:\Users\cc\Desktop\GoogleTV\chromecasts-master\node_modules\castv2-client\lib\controllers\receiver.js:51:23
at fn.onmessage (c:\Users\cc\Desktop\GoogleTV\chromecasts-master\node_modules\castv2-client\lib\controllers\request-response.js:27:7)
at fn.emit (node:events:529:35)
at Channel.onmessage (c:\Users\cc\Desktop\GoogleTV\chromecasts-master\node_modules\castv2-client\lib\controllers\controller.js:16:10)
at Channel.emit (node:events:517:28)
at Client.onmessage (c:\Users\cc\Desktop\GoogleTV\chromecasts-master\node_modules\castv2\lib\channel.js:23:10)
at Client.emit (node:events:529:35)
at PacketStreamWrapper.onpacket (c:\Users\cc\Desktop\GoogleTV\chromecasts-master\node_modules\castv2\lib\client.js:81:10)
at PacketStreamWrapper.emit (node:events:517:28)
at TLSSocket. (c:\Users\cc\Desktop\GoogleTV\chromecasts-master\node_modules\castv2\lib\packet-stream-wrapper.js:28:16)
In addition, I ran it successfully only once, but when I used the remote control to exit DefaultMediaReceiver and ran the code again, the following two situations occurred:
1.DefaultMediaReceiver no longer starts, but runs directly in the background;
2. Same problem as above: DefaultMediaReceiver NOT_FOUND
I would like to ask everyone for advice~Thank you very much.
What is your cast target? That is very far down the stack, in the core of the cast protocol... Ive never seen a Google cast device not be able to launch the DefaultMediaReceiver.
Closing as stale.