# The latest Node-Red 13.5.3 crashes in HomeAssistant

**URL:** <https://discourse.nodered.org/t/the-latest-node-red-13-5-3-crashes-in-homeassistant/71512>\
**Category:** General\
**Tags:** home-assistant\
**Created:** [30 November 2022 15:33 UTC](https://discourse.nodered.org/t/the-latest-node-red-13-5-3-crashes-in-homeassistant/71512 "2022-11-30T15:33:28Z")\
**Posts on this page:** 8\
**Page:** 1

<div class="post-metadata">

**Author:** ![hdutoit](https://avatars.discourse-cdn.com/v4/letter/h/bb73d2/32.png) [@hdutoit](https://discourse.nodered.org/u/hdutoit)\
**Post date:** [30 November 2022 15:33 UTC](https://discourse.nodered.org/t/the-latest-node-red-13-5-3-crashes-in-homeassistant/71512/1 "2022-11-30T15:33:28Z")

</div>

I have recently upgraded Node-Red to the current version13.5.3 on Home Assistant 2022.11.4  
Supervisor 2022.11.2  
Operating System 9.3  
Frontend 20221108.0 - latest

Since upgrading to the latest version of Node-Red it fails to start the Node-Red process. All my automations are done using Node-Red. So it's frustrating as none of my automations are able to run.

In the Node-Red logs it mentions:  
30 Nov 15:23:23 - [error] Error: Invalid access token for websocket  
at /opt/node\_modules/node-red-contrib-home-assistant-websocket/dist/homeAssistant/Websocket.js:112:29  
at processTicksAndRejections (node:internal/process/task\_queues:96:5)  
at Websocket.connect (/opt/node\_modules/node-red-contrib-home-assistant-websocket/dist/homeAssistant/Websocket.js:82:23)

REF:  
Home Assistant 2022.11.4  
Supervisor 2022.11.2  
Operating System 9.3  
Frontend 20221108.0 - latest

Node-RED  
Current version: 13.5.3

# Node-Red Log extraction: Welcome to Node-RED

Node-RED version: v3.0.

30 Nov 15:23:23 - [error] [api-call-service:aeafaa54a5aad308] Error: Server config node not found  
Error: Invalid access token for websocket  
at /opt/node\_modules/node-red-contrib-home-assistant-websocket/dist/homeAssistant/Websocket.js:112:29  
at processTicksAndRejections (node:internal/process/task\_queues:96:5)  
at Websocket.connect (/opt/node\_modules/node-red-contrib-home-assistant-websocket/dist/homeAssistant/Websocket.js:82:23)  
WARNING: Node-RED crashed, halting add-on  
INFO: Node-RED stopped, restarting...  
s6-rc: info: service legacy-services: stopping  
INFO: Node-RED stopped, restarting...  
s6-svwait: fatal: supervisor died  
s6-rc: info: service legacy-services successfully stopped  
s6-rc: info: service legacy-cont-init: stopping  
s6-rc: info: service legacy-cont-init successfully stopped  
s6-rc: info: service fix-attrs: stopping  
s6-rc: info: service fix-attrs successfully stopped  
s6-rc: info: service s6rc-oneshot-runner: stopping  
s6-rc: info: service s6rc-oneshot-runner successfully stopped

Any help would be appreciated as none of my automation work... so my Xmas lights don't work either... 🥹

Any assistance would be very much appreciated.

Regards  
Harry

---

<div class="post-metadata">

**Author:** ![jbudd](https://avatars.discourse-cdn.com/v4/letter/j/5f8ce5/32.png) [@jbudd](https://discourse.nodered.org/u/jbudd)\
**Post date:** [30 November 2022 16:00 UTC](https://discourse.nodered.org/t/the-latest-node-red-13-5-3-crashes-in-homeassistant/71512/2 "2022-11-30T16:00:59Z")

</div>

> [@hdutoit](#):
>
> All my automations are done using Node-Red. So it's frustrating as none of my automations are able to run.

Get rid of Home Assistant and do the job in a fresh Node-red installation, maybe on a different machine?

---

<div class="post-metadata">

**Author:** ![Colin](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/colin/32/17040_2.png) [@Colin](https://discourse.nodered.org/u/Colin)\
**Post date:** [30 November 2022 16:02 UTC](https://discourse.nodered.org/t/the-latest-node-red-13-5-3-crashes-in-homeassistant/71512/3 "2022-11-30T16:02:02Z")

</div>

This appears to be a Home Assistant issue. They package up node red for the plugin and we don't know what is in there. You are not the only one to have trouble with that version, see [The latest NodeRed does not work on HomeAssistant](https://discourse.nodered.org/t/the-latest-nodered-does-not-work-on-homeassistant/71062)

---

<div class="post-metadata">

**Author:** ![jbudd](https://avatars.discourse-cdn.com/v4/letter/j/5f8ce5/32.png) [@jbudd](https://discourse.nodered.org/u/jbudd)\
**Post date:** [30 November 2022 16:03 UTC](https://discourse.nodered.org/t/the-latest-node-red-13-5-3-crashes-in-homeassistant/71512/4 "2022-11-30T16:03:17Z")

</div>

I think @hdutoit knows about that thread! (Though they seem not to have learned from it)

---

<div class="post-metadata">

**Author:** ![Colin](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/colin/32/17040_2.png) [@Colin](https://discourse.nodered.org/u/Colin)\
**Post date:** [30 November 2022 16:05 UTC](https://discourse.nodered.org/t/the-latest-node-red-13-5-3-crashes-in-homeassistant/71512/5 "2022-11-30T16:05:41Z")

</div>

Oh yes, so I see. Perhaps he/she has very poor short term memory.

---

<div class="post-metadata">

**Author:** ![hdutoit](https://avatars.discourse-cdn.com/v4/letter/h/bb73d2/32.png) [@hdutoit](https://discourse.nodered.org/u/hdutoit)\
**Post date:** [30 November 2022 16:15 UTC](https://discourse.nodered.org/t/the-latest-node-red-13-5-3-crashes-in-homeassistant/71512/6 "2022-11-30T16:15:58Z")

</div>

Hi Colin,

Thank you for your speedy response. I would like to keep the solution I have purely due to time constraints..

Will look at running NodeRed on its own hardware platform in future.

Regards

Harry

 ![E20615FA146445B18DFE83D20D2B888A.png](https://us1.discourse-cdn.com/flex026/uploads/nodered/original/3X/f/f/ffeee1ddf87037f94dd158f88fd9ced464f4be34.png)

---

<div class="post-metadata">

**Author:** ![bakman2](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/bakman2/32/6207_2.png) [@bakman2](https://discourse.nodered.org/u/bakman2)\
**Post date:** [30 November 2022 16:57 UTC](https://discourse.nodered.org/t/the-latest-node-red-13-5-3-crashes-in-homeassistant/71512/7 "2022-11-30T16:57:45Z")

</div>

> Error: Invalid access token for websocket

By the looks of it the credentials were removed during upgrade/update.  
Run node-red in safe mode, configure the credentials in the HA node(s) and deploy.

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/flex026/uploads/nodered/original/1X/d073cd938eafa2e558d7c2cd59003b3ef4963033.png) [@system](https://discourse.nodered.org/u/system)\
**Post date:** [29 January 2023 16:58 UTC](https://discourse.nodered.org/t/the-latest-node-red-13-5-3-crashes-in-homeassistant/71512/8 "2023-01-29T16:58:40Z")

</div>

This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.