You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This issue is still present in the current beta version of this adapter
There is no other (open) issue with the same topic (use the search!)
This issue is not described in the adapter documentation / FAQ (read the docs!)
Script type
Blockly
The problem
When using the "cronjob" block as a trigger to start for example alexa to speak some text... the text will be send to alexa even when the blockly script is paused.
So... the cronjob does not stop! Maybe the cronjob starts even multiple times (but, not sure)
The thing is: My hole iobroker is useless since some days as the javascript adapter has 100% CPU in htop.
I added a second javascript adapter (javascript.1) and stopped javascript.0 to make sure iam not the idiot who made a crazy (not working) blockly script. :-)
The problem is still there.
First I had the problem that the javascript adapter started every minute. but then I found out that this is just a bug in the admin adapter.
Well... for me it's fixed because I used an old backup of my iobroker VM. I never found the problem or fixed it, even after countless hours of fault-finding.
Not sure, but I think it began to freak out after updating the JS-controller from 7.0.3 to 7.0.6.
iobroker.current.log (in debug mode!)
no useful logs
Version of nodejs
20.18.1
Version of ioBroker js-controller
7.0.6
Version of adapter
8.8.3
The text was updated successfully, but these errors were encountered:
I'm sure that
Script type
Blockly
The problem
When using the "cronjob" block as a trigger to start for example alexa to speak some text... the text will be send to alexa even when the blockly script is paused.
So... the cronjob does not stop! Maybe the cronjob starts even multiple times (but, not sure)
The thing is: My hole iobroker is useless since some days as the javascript adapter has 100% CPU in htop.
I added a second javascript adapter (javascript.1) and stopped javascript.0 to make sure iam not the idiot who made a crazy (not working) blockly script. :-)
The problem is still there.
First I had the problem that the javascript adapter started every minute. but then I found out that this is just a bug in the admin adapter.
Well... for me it's fixed because I used an old backup of my iobroker VM. I never found the problem or fixed it, even after countless hours of fault-finding.
Not sure, but I think it began to freak out after updating the JS-controller from 7.0.3 to 7.0.6.
iobroker.current.log (in debug mode!)
no useful logs
Version of nodejs
20.18.1
Version of ioBroker js-controller
7.0.6
Version of adapter
8.8.3
The text was updated successfully, but these errors were encountered: