Very slow communication between HA and Node Red #1923
Comments
|
Node Red has worked perfectly for years but I'm getting a similar issue which is preventing flows working. Like you said, restarting Node Red allows it to work for a while but then mine crashes again. My Log... Add-on: Node-RED
|
|
I have also problems with the performance. But in my case, the call service ends with an error.
14 Aug 07:29:59 - [info] Welcome to Node-RED14 Aug 07:29:59 - [info] Node-RED version: v4.0.2 Your flow credentials file is encrypted using a system-generated key. If the system-generated key is lost for any reason, your credentials You should set your own key using the 'credentialSecret' option in
|
I did change my secret to a new one with !secret node-red.key and after restarting yaml files and Node-Red I did edit something and deploy in Node-Red. That works fine, but my conclusion at the moment is that it is all the same. Still high CPU consumption and all the missing entities in cache. As long there is no feasible way to rebuild the cache the only thing that may work is to backup everything and reinstalling the Addon. |
|
Backuped everthing and reinstalled nodered addon. Now it works fine. Thanks for helping me. My issue is solved |
|
@fspuhler Nice it did work for you. Unfortunately in my case it didn't help either to reinstall the addon. I did the following:
But I still have a high CPU load any missing entities in cache. Eventually I do looking in the wrong direction and the issue is related to the HA side of the communication between Nod-Red and HA? |
|
There hasn't been any activity on this issue recently, so we clean up some of the older and inactive issues. |
github-actions
bot
added
the
stale
|
I really struggle with this issue. Am I the only one having this problem? Can anyone please explain how this node-red caching works and where the data are stored? |
github-actions
bot
removed
the
stale
same here, after restart nodered ist stable again, i dont know how long... |
|
I think I found the cause of this issue. In my case it is caused by an integration. When I disable the Integration Node-Red does not have anymore issues. It seems there is an issue with I/O "register_static_path" about this Integration. |
|
I'm experiencing a similar issue. In the last week or so, Node-RED has gone from being lightning fast to taking 2-3 seconds to respond when an entity changes... sometimes much more. I've also completely reinstalled Node-RED, but it didn't help either. |
|
There hasn't been any activity on this issue recently, so we clean up some of the older and inactive issues. |
github-actions
bot
added
the
stale
|
This is still very much a problem. So much so that I'm moving all of my automations out of Node-RED. |
github-actions
bot
removed
the
stale
Same with me, problem still persist, So unfortunately I was forced to move out of nodered too. |
Problem/Motivation
I have no idea why the communication between HA and Node Red is suddenly so slow, that it takes some times more then 3 seconds to execute a service call.
Expected behavior
Normally this should happen in milliseconds.
Actual behavior
The service call stays for seconds in sending mode:
The App consumes a lot of CPU power 40-55%
I switched to warn mode in the logs and see that that are many missing cache entries for entities. I guess that might be the problem, but I don't now how to clear the cache. Restarting does not help in my case.
https://community.home-assistant.io/t/refresh-node-red-entities-cache/218466
Steps to reproduce
Unfortunately I have no idea how to reproduce it.
Proposed changes
Sometimes it helps a bit for a certain period to restart Node-Red.
Logs
The text was updated successfully, but these errors were encountered: