Thanks waaren for this helpful inputs.
I reduce the maxItem to 20 (that was an old idea I no more use). That has reduced the running time. Now the script uses about 4 seconds. Most time consumation is in the initial part of script. It use near 4 seconds from start message to the first code (line 31 ...
Search found 3 matches
- Sunday 31 May 2020 15:19
- Forum: dzVents
- Topic: Script runtime notification [Solved]
- Replies: 4
- Views: 1520
- Sunday 31 May 2020 12:34
- Forum: dzVents
- Topic: Script runtime notification [Solved]
- Replies: 4
- Views: 1520
Re: Script runtime notification [Solved]
Thanks Warren for your Help
Below is the code. Sorry for mixed language and not perfect scripting structure. I removed outcommented code for debugging and personal information.
return {
on = {
timer = { 'every minute' },
httpResponses = { 'energyRetrievedSolarWatt' }
},
data = {
PowerIn ...
Below is the code. Sorry for mixed language and not perfect scripting structure. I removed outcommented code for debugging and personal information.
return {
on = {
timer = { 'every minute' },
httpResponses = { 'energyRetrievedSolarWatt' }
},
data = {
PowerIn ...
- Sunday 31 May 2020 11:20
- Forum: dzVents
- Topic: Script runtime notification [Solved]
- Replies: 4
- Views: 1520
Script runtime notification [Solved]
Hello
I updated my Raspi to Buster and istalled the newes version of Domoticz. Now I have a notification or an error in the protocol log:
2020-05-31 10:43:15.439 Error: dzVents: Error: (3.0.2) ------ Finished SolarWatt after >9 seconds. (using 8.552 seconds CPU time !)
2020-05-31 10:44:05.665 ...
I updated my Raspi to Buster and istalled the newes version of Domoticz. Now I have a notification or an error in the protocol log:
2020-05-31 10:43:15.439 Error: dzVents: Error: (3.0.2) ------ Finished SolarWatt after >9 seconds. (using 8.552 seconds CPU time !)
2020-05-31 10:44:05.665 ...