hi guys,

i would like to know how could cast local picture on tv using node red on windows 10

Open URL contentType is audio/mp3 in the example.

It does not work for me and I think the content type is at fault.

Did it work for some before?

It seems that a timeout makes node-red crash and restart, I reckon this shouldn't be happening!

 6 Nov 17:40:50 - [red] Uncaught Exception:
 6 Nov 17:40:51 - Error: Device timeout
 at HeartbeatController.ontimeout (/home/pi/.node-red/node_modules/node-red-contrib-chromecast/node_modules/castv2-client/lib/senders/platform.js:56:26)
 at HeartbeatController.g (events.js:260:16)
 at emitNone (events.js:67:13)
 at HeartbeatController.emit (events.js:166:7)
 at ontimeout [as _onTimeout] (/home/pi/.node-red/node_modules/node-red-contrib-chromecast/node_modules/castv2-client/lib/controllers/heartbeat.js:44:10)
 at Timer.listOnTimeout (timers.js:92:15)
 Welcome to Node-RED
 ===================
 6 Nov 17:40:54 - [info] Node-RED version: v0.13.3
 6 Nov 17:40:54 - [info] Node.js  version: v4.4.7
 6 Nov 17:40:54 - [info] Linux 4.1.18-v7+ arm LE
 6 Nov 17:40:54 - [info] Loading palette nodes
 6 Nov 17:41:07 - [info] Settings file

Hi I wanted to test this node to see if it would cast live video or if it was limited to audio ??
however when I installed I got an error here's what I did ..

cd /home/pi/.node-red
npm install node-red-contrib-chromecast

After I restart node-red which is installed on rpi2 with jessie I get ...

Welcome to Node-RED

3 Apr 08:35:45 - [info] Node-RED version: v0.13.3
3 Apr 08:35:45 - [info] Node.js version: v0.10.29
3 Apr 08:35:45 - [info] Linux 4.1.18+ arm LE
3 Apr 08:35:45 - [info] Loading palette nodes
pi : TTY=unknown ; PWD=/ ; USER=root ; COMMAND=/usr/bin/python -u /usr/lib/node_modules/node-red/nodes/core/hardware/nrgpio.py info
pam_unix(sudo:session): session opened for user root by (uid=0)
pam_unix(sudo:session): session closed for user root
/home/pi/.node-red/node_modules/node-red-contrib-chromecast/chromecast-play.js:45
for (var attr of attrs) {
^^
3 Apr 08:36:09 - [info] UI started at /ui
3 Apr 08:36:33 - [warn] ------------------------------------------
3 Apr 08:36:33 - [warn] Failed to register 1 node type
3 Apr 08:36:33 - [warn] Run with -v for details**
3 Apr 08:36:33 - [warn] ------------------------------------------

If connection to google case device is lost, complete node red is crashing

Jul  7 10:13:48 node-red: 7 Jul 10:13:48 - [red] Uncaught Exception:
Jul  7 10:13:48 node-red: 7 Jul 10:13:48 - Error: connect ETIMEDOUT 192.168.178.35:8009
Jul  7 10:13:48 node-red:     at Object._errnoException (util.js:992:11)
Jul  7 10:13:48 node-red:     at _exceptionWithHostPort (util.js:1014:20)
Jul  7 10:13:48 node-red:     at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1186:14)

After that node-red is no longer working and must be started on the command-line.

The IP 192.168.178.35 is my cast device and the node-red-contrib-chromecast is the only who uses this.

My cast device is a google home mini. Normally all is working fine and the input will be given to the device.

Can you please make it more error tolerant?