# Node-red Crashing- Could it be node-red-contrib-cast

**URL:** <https://discourse.nodered.org/t/node-red-crashing-could-it-be-node-red-contrib-cast/4014>\
**Category:** General\
**Created:** [16 October 2018 00:58 UTC](https://discourse.nodered.org/t/node-red-crashing-could-it-be-node-red-contrib-cast/4014 "2018-10-16T00:58:29Z")\
**Posts on this page:** 8\
**Page:** 1

<div class="post-metadata">

**Author:** ![Unpuertomex](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/unpuertomex/32/655_2.png) [@Unpuertomex](https://discourse.nodered.org/u/Unpuertomex)\
**Post date:** [16 October 2018 00:58 UTC](https://discourse.nodered.org/t/node-red-crashing-could-it-be-node-red-contrib-cast/4014/1 "2018-10-16T00:58:29Z")

</div>

Hi, for the last several days node-red has been crashing throughout the day. I have not updated any node nor am I showing any nodes need to be updated. below is the log that shows when I start node-red up until it crashes. Based on the information below, my assumption is that the problem node is node-red-contrib-cast, but I'm not sure, since I have never had a problem until now.

Thought?

# Welcome to Node-RED

15 Oct 05:48:40 - [info] Node-RED version: v0.19.4  
15 Oct 05:48:40 - [info] Node.js version: v8.12.0  
15 Oct 05:48:40 - [info] Windows\_NT 10.0.17134 x64 LE  
15 Oct 05:48:44 - [info] Loading palette nodes  
15 Oct 05:48:45 - [warn] rpi-gpio : Raspberry Pi specific node set inactive  
node-telegram-bot-api deprecated Automatic enabling of cancellation of promises is deprecated.  
In the future, you will have to enable it yourself.  
See [https://github.com/yagop/node-telegram-bot-api/issues/319](https://github.com/yagop/node-telegram-bot-api/issues/319). module.js:653:30  
15 Oct 05:48:49 - [info] RedBot version: 0.15.3 (node-red-contrib-chatbot)

15 Oct 05:48:51 - [info] Dashboard version 2.9.8 started at /ui  
15 Oct 05:48:51 - [warn] nodes/core/io/lib/mqtt.js is deprecated and will be removed in a future release of Node-RED. Please report this usage to the Node-RED mailing list.  
15 Oct 05:48:51 - [warn] nodes/core/io/lib/mqttConnectionPool.js is deprecated and will be removed in a future release of Node-RED. Please report this usage to the Node-RED mailing list.  
15 Oct 05:48:51 - [warn] ------------------------------------------------------  
15 Oct 05:48:51 - [warn] [node-red/tail] Not currently supported on Windows.  
15 Oct 05:48:51 - [warn] ------------------------------------------------------  
15 Oct 05:48:51 - [info] Settings file : \Users\unpue.node-red\settings.js  
15 Oct 05:48:51 - [info] HTTP Static : C:\Users\unpue\public  
15 Oct 05:48:51 - [info] Context store : 'default' [module=memory]  
15 Oct 05:48:51 - [info] User directory : \Users\unpue.node-red  
15 Oct 05:48:51 - [warn] Projects disabled : editorTheme.projects.enabled=false  
15 Oct 05:48:51 - [info] Flows file : \Users\unpue.node-red\flows\_WR-DESKTOP.json  
15 Oct 05:48:51 - [info] Server now running at [http://127.0.0.1:1880/](http://127.0.0.1:1880/)  
15 Oct 05:48:51 - [warn]

* * *

Your flow credentials file is encrypted using a system-generated key.

If the system-generated key is lost for any reason, your credentials  
file will not be recoverable, you will have to delete it and re-enter  
your credentials.

## You should set your own key using the 'credentialSecret' option in your settings file. Node-RED will then re-encrypt your credentials file using your chosen key the next time you deploy a change.

15 Oct 05:48:51 - [info] Starting flows  
15 Oct 05:48:51 - [info] [yeelight-compat-hue-config:WR Table Lamp Color] Connecting to Yeelight 192.168.2.156:55443  
registering node 4b8837cc.54ae58  
registering node edb65760.c04638  
registering node 7bdac50c.e20ffc  
registering node ab3756e.79497a8  
15 Oct 05:48:52 - [error] [pushbullet-config:xxxxxxxx@gmail.com] No credentials set for pushbullet config.  
15 Oct 05:48:52 - [info] Started flows  
15 Oct 05:48:52 - [info] [mqtt-broker:Win-Mosquitto] Connected to broker: mqtt://192.168.2.153:1883  
15 Oct 05:48:52 - [info] [yeelight-compat-hue-config:WR Table Lamp Color] Connected to 192.168.2.156:55443  
15 Oct 05:50:54 - [info] [exec:Doorbell] error:Error: Command failed: curl "[http://192.168.2.146:1035/?ALARM=CHIME&@DONE@](http://192.168.2.146:1035/?ALARM=CHIME&@DONE@)" on  
% Total % Received % Xferd Average Speed Time Time Time Current  
Dload Upload Total Spent Left Speed  
100 28 0 28 0 0 28 0 --:--:-- --:--:-- --:--:-- 77  
0 0 0 0 0 0 0 0 --:--:-- 0:00:01 --:--:-- 0curl: (6) Could not resolve host: on

15 Oct 07:06:09 - [warn] [mytimeout:Timer] L495: newMsg(inMsg): RangeError: Maximum call stack size exceeded \<{"payload":{"domain":"light","service":"turn\_on","data":{"entity\_id":"light.master\_bedroom\_level"}},"\_msgid":"2edeb051.06437","domain":"light","service":"turn\_on","data":{"entity\_id":"light.master\_bedroom\_level"}}\>  
15 Oct 07:07:21 - [warn] [mytimeout:My Timeout] L495: newMsg(inMsg): RangeError: Maximum call stack size exceeded \<{"payload":{"domain":"switch","service":"turn\_on","data":{"entity\_id":"switch.arellys\_bedroom\_light\_switch"}},"\_msgid":"f535a518.a249f8","domain":"switch","service":"turn\_on","data":{"entity\_id":"switch.arellys\_bedroom\_light\_switch"}}\>  
15 Oct 07:17:06 - [warn] [mytimeout:My Timeout] L495: newMsg(inMsg): RangeError: Maximum call stack size exceeded \<{"payload":{"domain":"switch","service":"turn\_on","data":{"entity\_id":"switch.andrews\_bedroom\_switch"}},"_msgid":"1137c255.0bbd7e","domain":"switch","service":"turn\_on","data":{"entity\_id":"switch.andrews\_bedroom\_switch"}}\>  
15 Oct 07:22:46 - [red] Uncaught Exception:  
15 Oct 07:22:46 - ReferenceError: node is not defined  
at client.launch (C:\Users\unpue.node-red\node\_modules\node-red-contrib-cast\cast-to-client.js:73:13)  
at C:\Users\unpue.node-red\node\_modules\castv2-client\lib\senders\platform.js:95:20  
at C:\Users\unpue.node-red\node\_modules\castv2-client\lib\controllers\receiver.js:51:14  
at fn.onmessage (C:\Users\unpue.node-red\node\_modules\castv2-client\lib\controllers\request-response.js:27:7)  
at emitTwo (events.js:131:20)  
at fn.emit (events.js:214:7)  
at Channel.onmessage (C:\Users\unpue.node-red\node\_modules\castv2-client\lib\controllers\controller.js:16:10)  
at emitTwo (events.js:126:13)  
at Channel.emit (events.js:214:7)  
at Client.onmessage (C:\Users\unpue.node-red\node\_modules\castv2\lib\channel.js:23:10)  
at emitMany (events.js:152:20)  
at Client.emit (events.js:224:7)  
at PacketStreamWrapper.onpacket (C:\Users\unpue.node-red\node\_modules\castv2\lib\client.js:81:10)  
at emitOne (events.js:116:13)  
at PacketStreamWrapper.emit (events.js:211:7)  
at TLSSocket. (C:\Users\unpue.node-red\node\_modules\castv2\lib\packet-stream-wrapper.js:28:16)  
at emitNone (events.js:106:13)  
at TLSSocket.emit (events.js:208:7)  
at emitReadable_ (\_stream\_readable.js:513:10)  
at emitReadable (\_stream\_readable.js:507:7)  
at addChunk (\_stream\_readable.js:274:7)  
at readableAddChunk (\_stream\_readable.js:250:11)

---

<div class="post-metadata">

**Author:** ![ukmoose](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/ukmoose/32/13_2.png) [@ukmoose](https://discourse.nodered.org/u/ukmoose)\
**Post date:** [16 October 2018 06:50 UTC](https://discourse.nodered.org/t/node-red-crashing-could-it-be-node-red-contrib-cast/4014/2 "2018-10-16T06:50:04Z")

</div>

You might want to edit out your email address contained in your log message that you pasted.

Yes the cast node is causing the crash, you should open an issue against the node on the nodes github page (follow the link from the nodes page on [flows.nodered.org](http://flows.nodered.org) )

But there are also several other issues in your log. One is the warning about using a mqttconnectionpool as this file will be removed in a future version of node-red. Which nodes (other than the included mqtt ones) are you using that use mqtt?

---

<div class="post-metadata">

**Author:** ![dynamicdave](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/dynamicdave/32/96_2.png) [@dynamicdave](https://discourse.nodered.org/u/dynamicdave)\
**Post date:** [16 October 2018 07:04 UTC](https://discourse.nodered.org/t/node-red-crashing-could-it-be-node-red-contrib-cast/4014/3 "2018-10-16T07:04:17Z")

</div>

I've had exactly the same issue with 'Cast' crashing my RPi - I've given up using it and deleted the node.

---

<div class="post-metadata">

**Author:** ![Unpuertomex](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/unpuertomex/32/655_2.png) [@Unpuertomex](https://discourse.nodered.org/u/Unpuertomex)\
**Post date:** [16 October 2018 21:42 UTC](https://discourse.nodered.org/t/node-red-crashing-could-it-be-node-red-contrib-cast/4014/4 "2018-10-16T21:42:43Z")

</div>

> [@ukmoose](#):
>
> email address

Darn, missed that just fixed it.

> [@ukmoose](#):
>
> you should open an issue against the node on the nodes github page (follow the link from the nodes page on [flows.nodered.org](http://flows.nodered.org)

I will submit the issue shortly.

> [@ukmoose](#):
>
> Which nodes (other than the included mqtt ones) are you using that use mqtt?

I only have and use the included ones, I checked to be sure and it is the one in my palette! I just check to see if there was an update but saw none.

 ![snip_20181016163559](https://us1.discourse-cdn.com/flex026/uploads/nodered/original/2X/0/0f17f2cda8e5a2f20b8b1c9665c289dc91afdf8d.png)

I guess I'll go and report that issue as well.

> [@dynamicdave](#):
>
> I've had exactly the same issue with 'Cast' crashing my RPi - I've given up using it and deleted the node.

@dynamicdave, this is the first problem I've had with this node, it was working well for the last month and there hasn't been an update since them. May I ask what are you using in its place?

---

<div class="post-metadata">

**Author:** ![Paul-Reed](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/paul-reed/32/66906_2.png) [@Paul-Reed](https://discourse.nodered.org/u/Paul-Reed)\
**Post date:** [16 October 2018 22:30 UTC](https://discourse.nodered.org/t/node-red-crashing-could-it-be-node-red-contrib-cast/4014/5 "2018-10-16T22:30:38Z")

</div>

It's an inherited issue from `node-red-contrib-chromecast` which really needs sorting.  
I highlighted this [in a previous post,](https://discourse.nodered.org/t/ring-doorbell-google-home/2924/24) and [raised an issue here](https://github.com/Hypnos3/node-red-contrib-cast/issues/7).

This potentially could be a popular contrib-node, as it engages node-RED with Google Home & Chromecast which is a common forum request.

Any help with error handling would really benefit the community...

Paul

---

<div class="post-metadata">

**Author:** ![Unpuertomex](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/unpuertomex/32/655_2.png) [@Unpuertomex](https://discourse.nodered.org/u/Unpuertomex)\
**Post date:** [17 October 2018 01:03 UTC](https://discourse.nodered.org/t/node-red-crashing-could-it-be-node-red-contrib-cast/4014/6 "2018-10-17T01:03:24Z")

</div>

> [@Paul-Reed](#):
>
> It's an inherited issue from `node-red-contrib-chromecast` which really needs sorting.

Thank you @Paul-Reed, just read your other article, unfortunately, I don't know how to program (may be a good time to learn 🙂 ), for now, I'm moving back to exec node along with LANnouncer, unless someone has an alternative.

---

<div class="post-metadata">

**Author:** ![Hypnos](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/hypnos/32/7566_2.png) [@Hypnos](https://discourse.nodered.org/u/Hypnos)\
**Post date:** [17 October 2018 12:57 UTC](https://discourse.nodered.org/t/node-red-crashing-could-it-be-node-red-contrib-cast/4014/7 "2018-10-17T12:57:17Z")

</div>

I have changed several. Can you please check the newest Version 0.1.0?

---

<div class="post-metadata">

**Author:** ![Unpuertomex](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/unpuertomex/32/655_2.png) [@Unpuertomex](https://discourse.nodered.org/u/Unpuertomex)\
**Post date:** [18 October 2018 01:21 UTC](https://discourse.nodered.org/t/node-red-crashing-could-it-be-node-red-contrib-cast/4014/8 "2018-10-18T01:21:42Z")

</div>

> [@Hypnos](#):
>
> Can you please check the newest Version 0.1.0?

Hi @Hypnos, left you feedback at github. Basically it hasn't crashed but the error is now showing up on the debug screen in node-red and it is different than the original one I posted.