# Why do I have to reload node-red-contrib-home-assistant-websocket every time node red is restarted

**URL:** <https://discourse.nodered.org/t/why-do-i-have-to-reload-node-red-contrib-home-assistant-websocket-every-time-node-red-is-restarted/60983>\
**Category:** General\
**Tags:** home-assistant\
**Created:** [8 April 2022 13:54 UTC](https://discourse.nodered.org/t/why-do-i-have-to-reload-node-red-contrib-home-assistant-websocket-every-time-node-red-is-restarted/60983 "2022-04-08T13:54:56Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![hughjms](https://avatars.discourse-cdn.com/v4/letter/h/d07c76/32.png) [@hughjms](https://discourse.nodered.org/u/hughjms)\
**Post date:** [8 April 2022 13:54 UTC](https://discourse.nodered.org/t/why-do-i-have-to-reload-node-red-contrib-home-assistant-websocket-every-time-node-red-is-restarted/60983/1 "2022-04-08T13:54:56Z")

</div>

Hi ,

I've been running Home Assistant on a raspberry Pi for about 2 years with some problems , but I now have one which I cannot work out how to reolve .

I recently did some node package ugrades and now each time node red is restarted It comes up with an error that says "flows stopped due to missing node types" . And several of my nodes are labeled unknown with Red dotted links to other nodes . If I reinstall node-red-contrib-home-assistant-websocket ( 0.43.1) the problem is resolved , but this fix doesnt stick. If I restart again , the same problem occurs and the flows are broken until I reinstall node-red-contrib-home-assistant-websocket.

How does node red work out which node packages to load when it starts . I have checked packages.json and this references the version I have to keep installing .

{  
"name": "node-red-project",  
"description": "A Node-RED Project",  
"version": "0.0.1",  
"private": true,  
"dependencies": {  
"node-red-contrib-actionflows": "~2.1.2",  
"node-red-contrib-alexa-local": "~0.3.24",  
"node-red-contrib-bigtimer": "~2.8.1",  
"node-red-contrib-bool-gate": "~1.0.2",  
"node-red-contrib-boolean-logic-ultimate": "~1.0.51",  
"node-red-contrib-fs-ops": "~1.6.0",  
"node-red-contrib-home-assistant-websocket": "0.43.1",  
"node-red-contrib-influxdb": "~0.6.1",  
"node-red-contrib-interval-length": "0.0.5",  
"node-red-dashboard": "~3.1.6",  
"node-red-node-openweathermap": "~0.3.2",  
"node-red-node-ping": "~0.3.1",  
"node-red-node-random": "~0.4.0",  
"node-red-node-rbe": "~0.5.0",  
"node-red-node-serialport": "~1.0.1",  
"node-red-node-tail": "~0.3.2",  
"node-red-node-twitter": "~1.2.0"  
}  
}

What am I missing ?

---

<div class="post-metadata">

**Author:** ![Steve-Mcl](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/steve-mcl/32/4826_2.png) [@Steve-Mcl](https://discourse.nodered.org/u/Steve-Mcl)\
**Post date:** [8 April 2022 14:26 UTC](https://discourse.nodered.org/t/why-do-i-have-to-reload-node-red-contrib-home-assistant-websocket-every-time-node-red-is-restarted/60983/2 "2022-04-08T14:26:59Z")

</div>

This is something you will likely have to ask on the HA forum since node red is actually a plug-in installed by HA.

Under the hood, on HA, node red runs in a docker container and it is likely the data for that is not correctly mapped or persisted.

This is most likely not a node red issue but a docker/container/HA problem.

---

<div class="post-metadata">

**Author:** ![hughjms](https://avatars.discourse-cdn.com/v4/letter/h/d07c76/32.png) [@hughjms](https://discourse.nodered.org/u/hughjms)\
**Post date:** [8 April 2022 14:43 UTC](https://discourse.nodered.org/t/why-do-i-have-to-reload-node-red-contrib-home-assistant-websocket-every-time-node-red-is-restarted/60983/3 "2022-04-08T14:43:38Z")

</div>

Thanks for the response , I think I just managed to find the cause , turned down the level of trace I had set and found the following :-

8 Apr 15:30:18 - [warn] [node-red-contrib-home-assistant-websocket] Node module cannot be loaded on this version. Requires: \>=1.3.0

and assumming the 1.3.0 refers to the node red version , I appear to be running 1.2.7

8 Apr 15:30:14 - [info] Node-RED version: v1.2.7  
8 Apr 15:30:14 - [info] Node.js version: v14.15.4  
8 Apr 15:30:14 - [info] Linux 5.10.103-v7 arm LE

Hmm , seems to be a different version number in the Home Assistant Supervisor window (V 8.0.0 ) that must be the add on version ...?

Back track on the version of node-red-contrib-home-assistant-websocket or work out how to upgrade node red in Homeassistant to version 1.3.0

---

<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:** [7 June 2022 14:44 UTC](https://discourse.nodered.org/t/why-do-i-have-to-reload-node-red-contrib-home-assistant-websocket-every-time-node-red-is-restarted/60983/4 "2022-06-07T14:44:15Z")

</div>

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