Domoticz

Hi folks,

As it turns out that for some people (some hardware or whatever) there appears to be a high cpu load when dzVents is enabled. For now, the best way to deal with this is to just turn dzVents off in the settings.

In the meantime the C++ experts are trying to figure out why and how this is happening. Unfortunately I'm not one of those experts. So, if you do indeed experience this problem and you have some C++ knowledge, any help (like profiling, tracing) is greatly appreciated.

Since many people really do like dzVents (I'm happy with that of course as it took me many months of work to make this happen) it would be a shame if somehow we couldn't figure out how to get the integration work properly for all of us.

Stay tuned...

Why is it enabled by default after all? I'd prefer an opt-in solution, since i have no plans to use it.

Because we didn't know that it would have this effect for some. When we tested it we never saw this happening so we always assumed that you wouldn't notice it when it was enabled. But that's easy to fix though. We'll disable it by default.

Lot's of things are enabled by default: scripting engines like lua and python, blockly, ... I would have just considered this the next (natural) iteration of lua. Please also note that this is called beta for a reason.
Since there is such a difference in situations, have you looked at the different os/sw installations ie people on (updated) Jessie vs Wheezy?

blacksn0w wrote:Why is it enabled by default after all? I'd prefer an opt-in solution, since i have no plans to use it.

Totally agree. This move keeps me from updating domoticz. I don't want to remove dzVents manually after each update, I just want it disabled totally.
Maybe the settings page where the eventsystem can be disabled should be extended with more options?
Now there's only one option: enable/disable.
Should be nice if one could choose te enable/disable:
Blockly, Python, Lua file based, Lua database based, dzVents,...

Now, because all of them are enabled by default or folders and storage types are queried to see if the're scripts to run. I only have 1 script so all the rest is needless io and cpu cycles.

Egregius wrote:

blacksn0w wrote:Why is it enabled by default after all? I'd prefer an opt-in solution, since i have no plans to use it.

Totally agree. This move keeps me from updating domoticz. I don't want to remove dzVents manually after each update, I just want it disabled totally.
Maybe the settings page where the eventsystem can be disabled should be extended with more options?
Now there's only one option: enable/disable.
Should be nice if one could choose te enable/disable:
Blockly, Python, Lua file based, Lua database based, dzVents,...

Now, because all of them are enabled by default or folders and storage types are queried to see if the're scripts to run. I only have 1 script so all the rest is needless io and cpu cycles.

Good suggestion. Granular enable / disable based on what you use.

Well, just create some pull requests. It's open-source after all.

Indeed.