Domoticz

Maybe it's specific hardware(interface). It might help when people having problems list their hardware so we can compare.
Mark

Do you have a lot of devices and "classic" scripts ?
-> I have 14 script_device, 17 script_time, 1 php, 23 bash (via crontab most of the time) -> not using any version of dzVents.
-> I have about 175 devices (including dummies).
=> my CPU usage is around 3-4% for domoticz only (some times 0% but come back fast to more due to scripts I assume).

I did have a comparable issue a little while ago with the 'motherboard sensors' hardware freezing up my Pi system. After I removed it it ran like a charm. Perhaps you can try that? Probably unrelated though.

regarding my hardware : see the picture.

-> I will try to remove the motherboard sensor hardware. but do you know where I can find some scripts examples to replace it ?
EDIT : I observed domoticz using up to 20% of cpu when motherboard sensor disabled instead of 30% with it.

randytsuch wrote:One comment.
If you use the domoticz events editor (which is very convenient), the example still uses [] for definitions instead of the new convention ()

Randy

Good catch. Fixed that. I thought I converted them all but forgot about this template.

Is there a correlation wit Hue lamps?

heggink wrote:Some people appear to have issues (high cpu) with 8027 on rpi3. Anyone without these problems on rpi3?

No problems here with events- and dzVents 2.0 active since 8034. CPU < 5% on my RPI3

waaren wrote:

heggink wrote:Some people appear to have issues (high cpu) with 8027 on rpi3. Anyone without these problems on rpi3?

No problems here with events- and dzVents 2.0 active since 8034. CPU < 5% on my RPI3

see the picture for dzVents enable in my Domoticz : not good !

rpi3 here and cpu is higher then normal also after the last update's.
Running the latsest beta atm Version: 3.8034.

I can confirm that: upgrading from 3.8015 to 3.8027 made my CPU usage (RPI3) go up from average 2% to average 5%. So still low and maybe this is the new normal.
Am I right that people who use dzVents have NO problem whilst others may have. Just a hunch: do people with problems have 127.0.0.1 in their Local Network settings (required for dzVents)?
Mark

Doler wrote:I can confirm that: upgrading from 3.8015 to 3.8027 made my CPU usage (RPI3) go up from average 2% to average 5%. So still low and maybe this is the new normal.
Am I right that people who use dzVents have NO problem whilst others may have. Just a hunch: do people with problems have 127.0.0.1 in their Local Network settings (required for dzVents)?
Mark

I do have 127.0.0.1 in dzVents_settings.lua, and no script at all in dzVents folders (neither via web editor, nor put manually in some folder), but when I activate dzVents, domoticz start using 100% of my CPU... I have to stop domoticz and restart and then I have a few seconds to disable dzVents.

What you could try is disable all your hardware and then enable dzVents and see what happens (just to rule out possible causes).
Mark

jeanclic, is it possible for you to see which hardware may cause this for you? Can you make a copy of your entire setup (or just the database) and perhaps remove some hardware of scripts to see when the cpu load drops to normal levels?
It's so hard to debug this if you cannot reproduce it yourself.
Your help is greatly appreciated in this. We have to nail this bugger!

Doler wrote:I can confirm that: upgrading from 3.8015 to 3.8027 made my CPU usage (RPI3) go up from average 2% to average 5%. So still low and maybe this is the new normal.
Am I right that people who use dzVents have NO problem whilst others may have. Just a hunch: do people with problems have 127.0.0.1 in their Local Network settings (required for dzVents)?
Mark

Well, domoticz is gathering a bit more information than before when it starts the event handlers so maybe that causes a bit more cpu. But just a couple of percents shouldn't be a problem. After all, it's a computer that needs to DO stuff for us .

dannybloe wrote:jeanclic, is it possible for you to see which hardware may cause this for you? Can you make a copy of your entire setup (or just the database) and perhaps remove some hardware of scripts to see when the cpu load drops to normal levels?
It's so hard to debug this if you cannot reproduce it yourself.
Your help is greatly appreciated in this. We have to nail this bugger!

I tried to disable hardwares one by one to see the impact on CPU usage: I cannot really conclude anything.
I wrote a basic dzVents script via web interface (to write a log message every minute), just to see if with a script to execute dzVents is happier ? -> no.
I changed 127.0.0.1 to 127.0.0.2 to "loose" dzVents: not better. (btw, is it not possible to include config in the web interface and forget about this dzVents_settings.lua ? -> I do not understand well if this file is overriding the log level or if it is the web setup ?)

-> each time I activate dzVents, CPU usage reaches 100% in seconds.

jeanclic wrote:

dannybloe wrote:jeanclic, is it possible for you to see which hardware may cause this for you? Can you make a copy of your entire setup (or just the database) and perhaps remove some hardware of scripts to see when the cpu load drops to normal levels?
It's so hard to debug this if you cannot reproduce it yourself.
Your help is greatly appreciated in this. We have to nail this bugger!

I tried to disable hardwares one by one to see the impact on CPU usage: I cannot really conclude anything.
I wrote a basic dzVents script via web interface (to write a log message every minute), just to see if with a script to execute dzVents is happier ? -> no.
I changed 127.0.0.1 to 127.0.0.2 to "loose" dzVents: not better. (btw, is it not possible to include config in the web interface and forget about this dzVents_settings.lua ? -> I do not understand well if this file is overriding the log level or if it is the web setup ?)

-> each time I activate dzVents, CPU usage reaches 100% in seconds.

You should not use dzVents_settings.lua at all. That's prior to 2.0! The 127.0.0.1 setting is for some commands that don't have 'native' Lua support in Domoticz. Some device types need to call a json/api command. But unlike earlier, this ip address is not used for getting settings anymore.
Make sure that you don't have debug-logging enabled in the settings for dzVents coz that might slow things down quite a bit. Just enable that for special cases and tracking down problems.

dannybloe wrote:

jeanclic wrote:

dannybloe wrote:jeanclic, is it possible for you to see which hardware may cause this for you? Can you make a copy of your entire setup (or just the database) and perhaps remove some hardware of scripts to see when the cpu load drops to normal levels?
It's so hard to debug this if you cannot reproduce it yourself.
Your help is greatly appreciated in this. We have to nail this bugger!

I tried to disable hardwares one by one to see the impact on CPU usage: I cannot really conclude anything.
I wrote a basic dzVents script via web interface (to write a log message every minute), just to see if with a script to execute dzVents is happier ? -> no.
I changed 127.0.0.1 to 127.0.0.2 to "loose" dzVents: not better. (btw, is it not possible to include config in the web interface and forget about this dzVents_settings.lua ? -> I do not understand well if this file is overriding the log level or if it is the web setup ?)

-> each time I activate dzVents, CPU usage reaches 100% in seconds.

You should not use dzVents_settings.lua at all. That's prior to 2.0! The 127.0.0.1 setting is for some commands that don't have 'native' Lua support in Domoticz. Some device types need to call a json/api command. But unlike earlier, this ip address is not used for getting settings anymore.
Make sure that you don't have debug-logging enabled in the settings for dzVents coz that might slow things down quite a bit. Just enable that for special cases and tracking down problems.

When I tested enabling dzVents, I of course put the logs to "silent", but it is overloading my RPI for all levels.
You say I should not have to modify dzVents_settings.lua ? because I tried to enable dzVents on a Debian I use to test stuffs on domoticz and it worked only after I changed the adress from 10.0.0.8 to 127.0.0.1. (btw on this debian, dzVents is working very well, but I have almost no hardware and I also have absolutely no script except one "web" dzVent for testing)
I changed also the log level in this file to 0, and the logs disapeared as expected.
Maybe I have set something up in a bad way ?

jeanclic wrote:

dannybloe wrote:

jeanclic wrote: I tried to disable hardwares one by one to see the impact on CPU usage: I cannot really conclude anything.
I wrote a basic dzVents script via web interface (to write a log message every minute), just to see if with a script to execute dzVents is happier ? -> no.
I changed 127.0.0.1 to 127.0.0.2 to "loose" dzVents: not better. (btw, is it not possible to include config in the web interface and forget about this dzVents_settings.lua ? -> I do not understand well if this file is overriding the log level or if it is the web setup ?)

-> each time I activate dzVents, CPU usage reaches 100% in seconds.

You should not use dzVents_settings.lua at all. That's prior to 2.0! The 127.0.0.1 setting is for some commands that don't have 'native' Lua support in Domoticz. Some device types need to call a json/api command. But unlike earlier, this ip address is not used for getting settings anymore.
Make sure that you don't have debug-logging enabled in the settings for dzVents coz that might slow things down quite a bit. Just enable that for special cases and tracking down problems.

When I tested enabling dzVents, I of course put the logs to "silent", but it is overloading my RPI for all levels.
You say I should not have to modify dzVents_settings.lua ? because I tried to enable dzVents on a Debian I use to test stuffs on domoticz and it worked only after I changed the adress from 10.0.0.8 to 127.0.0.1. (btw on this debian, dzVents is working very well, but I have almost no hardware and I also have absolutely no script except one "web" dzVent for testing)
I changed also the log level in this file to 0, and the logs disapeared as expected.
Maybe I have set something up in a bad way ?

I don't now. I assume you have dzVents 1.1.1 running as well on this system? 1.1.x is running in /path/to/domoticz/scripts/lua/dzVents while with 2.0 it runs from another directory in the domoticz codebase: /path/to/domoticz/scripts/dzVents. Theoretically they can co-exists. For 1.1.x you do need dzVents_settings.lua. 2.0 doesn't use that at all. At least, it shouldn't.

Did some troubleshooting myself:

- Dzvents enabled
High CPU Usage
Switching Hue enabled/disabled makes domoticz crash.
"Smart Meter P1" same story.
No problems with other hardware.

- Dzvents disabled
No problems.

Question: The users with no issues: have you got hardware like Smart Meter P1 or hue?

beeing completely newbie regarding dzVents, I wonder if this path is correct ?