# Websocket startup time issue when doing a deploy in node red 

**URL:** <https://discourse.nodered.org/t/websocket-startup-time-issue-when-doing-a-deploy-in-node-red/7765>\
**Category:** General\
**Created:** [9 February 2019 08:09 UTC](https://discourse.nodered.org/t/websocket-startup-time-issue-when-doing-a-deploy-in-node-red/7765 "2019-02-09T08:09:48Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![Poiz](https://avatars.discourse-cdn.com/v4/letter/p/b9e5f3/32.png) [@Poiz](https://discourse.nodered.org/u/Poiz)\
**Post date:** [9 February 2019 08:09 UTC](https://discourse.nodered.org/t/websocket-startup-time-issue-when-doing-a-deploy-in-node-red/7765/1 "2019-02-09T08:09:48Z")

</div>

Hi  
Im running node red on a raspberry pie 3 (b+) with Hassio.  
Hassio 0.86.4  
Node red 1.3.0

I while a go I started to get connection problems when deploying a new flow in node red, see below. Any one got an idea what it may depend on?  
Is there any way I can delay the service calls for 5 second when doing a deploy?

//Johan

7 Feb 22:09:40 - [info] Stopping flows  
7 Feb 22:09:40 - [info] [server:Home Assistant] Closing WebSocket [http://hassio/homeassistant](http://hassio/homeassistant)  
7 Feb 22:09:40 - [info] Stopped flows  
7 Feb 22:09:40 - [info] Starting flows  
7 Feb 22:09:40 - [info] Started flows  
7 Feb 22:09:41 - [warn] [api-call-service:Turn on Stars] Call-Service attempted without connection to server.  
7 Feb 22:09:41 - [warn] [api-call-service:Turn on Julbelysning framsida] Call-Service attempted without connection to server.  
7 Feb 22:09:41 - [warn] [api-call-service:Turn on Fontän] Call-Service attempted without connection to server.  
7 Feb 22:09:41 - [warn] [api-call-service:Turn On Vardagsrum] Call-Service attempted without connection to server.  
7 Feb 22:09:41 - [warn] [api-call-service:Guldlampa på] Call-Service attempted without connection to server.  
7 Feb 22:09:41 - [warn] [api-call-service:Fönsterlamp kök] Call-Service attempted without connection to server.  
7 Feb 22:09:41 - [warn] [api-call-service:Fönsterlamp Vardagsrum] Call-Service attempted without connection to server.  
7 Feb 22:09:41 - [warn] [api-call-service:Turn On Växtlampa tvättstuga] Call-Service attempted without connection to server.  
7 Feb 22:09:41 - [warn] [api-call-service:Turn Off Växtlampa förråd] Call-Service attempted without connection to server.  
7 Feb 22:09:41 - [warn] [api-call-service:Turn Off Motorvärmare] Call-Service attempted without connection to server.  
7 Feb 22:09:45 - [info] [server:Home Assistant] WebSocket Connected to [http://hassio/homeassistant](http://hassio/homeassistant)

---

<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:** [9 February 2019 09:31 UTC](https://discourse.nodered.org/t/websocket-startup-time-issue-when-doing-a-deploy-in-node-red/7765/2 "2019-02-09T09:31:07Z")

</div>

As they are "[warn]" rather than "error", does it then connect properly?  
If it does can't you just ignore them?

The current version of Node-RED is v0.19.5 not sure what 1.3.0 is !

---

<div class="post-metadata">

**Author:** ![dceejay](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/dceejay/32/38_2.png) [@dceejay](https://discourse.nodered.org/u/dceejay)\
**Post date:** [9 February 2019 12:17 UTC](https://discourse.nodered.org/t/websocket-startup-time-issue-when-doing-a-deploy-in-node-red/7765/3 "2019-02-09T12:17:36Z")

</div>

They look like messages from the api call service trying to talk while the home assistant service is not ready. So they need to handle that between them.

---

<div class="post-metadata">

**Author:** ![Poiz](https://avatars.discourse-cdn.com/v4/letter/p/b9e5f3/32.png) [@Poiz](https://discourse.nodered.org/u/Poiz)\
**Post date:** [10 February 2019 21:07 UTC](https://discourse.nodered.org/t/websocket-startup-time-issue-when-doing-a-deploy-in-node-red/7765/4 "2019-02-10T21:07:02Z")

</div>

1.3.0 is the version of the Node red addon for Hassio (Home assistant), Node red version is 0.19.5  
It does connect properly but as I see it Node red doesn't wait until the connection is established. It just send the service call ASAP after a deploy.  
So is there a way to delay node red for say 5s before it starts to do the calls?

---

<div class="post-metadata">

**Author:** ![dceejay](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/dceejay/32/38_2.png) [@dceejay](https://discourse.nodered.org/u/dceejay)\
**Post date:** [10 February 2019 21:12 UTC](https://discourse.nodered.org/t/websocket-startup-time-issue-when-doing-a-deploy-in-node-red/7765/5 "2019-02-10T21:12:45Z")

</div>

we don't know what you are sending to what ... so hard to advise. You can use a delay node to delay messages - but you probably don't want to delay messages after the initial 5 secs.