The the websocket error is gone now, i’m running NR version 10.0.0 and HA version core-2021.8.8.
Node RED doesn’t have delays anymore when it runs and i don’t have it opened, exept when i make changes,they are not correct displayed in the browser. Whem i use an inject node to turn on and off a light, the light itselfs respons inmediatly, but no info is shown under the call service node like in the screenshot. I clicked multiple times light on and off, but there is no info under the service node…after i refresh the page the info shows up.
I’ve tested it with chrome and firefox, both thesame result.
The same when i use a debug node,when i deploy, nothing shows up, i have to refresh the page to see the debugs.
That sounds like a websocket issue is still there. Are you using the “events-all” node in anything? If that’s not filtered or setup properly the websockets can be overwhelmed.
websocket error is gone now for a couple of weeks in the logging, and i have 1 “events-all” node that i use for NFC tags.
When i disable it, i still have the delay so no luck there 
1 Like
I’ve noticed this problem too. I have an “input number” that I total up in NodeRed then send into HomeAssistant, sometimes the “sending” service node just sits and does nothing for minutes. In my case I’m updating it for a guage and switching heaters on and off to use my solar surplus, so its vital it works QUICKLY. Something happened to HA about a year ago that started this issue.
My theory is its a buffering issue of data somewhere, e.g. it queues up, and if your send data becomes too frequent, it locks up.
For a while I did run an automatic restart every hour of nodered, but this became problematic because my flows would sometimes miss the daylight change in my house etc.
Does someone at HA not like the fact we all use NodeRed for complex coding? 
Unfortunately this sounds like it’s something with in your system. I send over 500 image text messages per day. I also use it to open doors based on bluetooth scans, it triggers instantly.
I assume that you have checked to see how many server config nodes you have, it should only be one. Other 3rd party nodes. Remove them from the palette manger.(edit. while you are in there see if any nodes need updating and do that first) Disable the flows they are in as well. One bad node can hose the entire system.
Function nodes and jsonata. Bad code can create loops and other problems. Have you watched the addons memory usage? Systematic disabling of function, flows and or tabs and letting the system run, unfortunately would be the only way to trouble shoot that type of problem.
1 Like
I’m also suffering from slow (1-2 minutes) Call Service node problems as well. Anyone have a solution yet?
1 Like
Hi by chance in time you solved this problem now I’ve been finding it for a couple of months and I can’t solve it