-
Notifications
You must be signed in to change notification settings - Fork 25
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
High cpu % usage with this node #67
Comments
So this is the first flow. I use those nodes to triggers events ( same as scene if you want) of my Homeseer automation system ( an example in homeseer would be...: when an specific mqtt message receive a payload with ''on'' then turn on the event ''goodnight''
|
So this is the second flow. I use those nodes to directly ( by mqtt) associate the value receives in the payload to a specific node in my Homeseer HS3 system. I needed to write a function for some of those to work, because they are dimming node in my Homeseer setup .
|
I think i know when the issue happen ( with dimming lights)
then the node-red process goes directly to 50% |
Hi,
all my nodered, npm, node.js, debian etc are updated to their latest stable release.
I created 11 nodes (alexa devices) with you plugin/package.
Today i was looking at htop and ...i saw node-red cpu usage is more or less constant to 50% usage. ( I have a amd 2700x cpu).
So, this is the only change in nodes i made to my node-red setup in the last days.
I tried to clean the cache of npm... but it doe nothing.
One thing I try is copy paste the flows i created with your npm package, then i removed them...and i deployed node-red. Since then.. my cpu usage is back to normal (0-5%).
Finally I putted the flows i just remove into node-red ... and deployed again.. ( had to rediscover with ALexa but this is normal). Unfortunatly, node-red process is back to 50% again.
I will send you my two flows in another message
The text was updated successfully, but these errors were encountered: