Many Conditions running : CPU increased !

[nslmanu]

Hello,

After many weeks of utilization, i have now many events following many conditions.

The problem is that the CPU runs higher now than few weeks ago ...

If i look the logs i saw that the "checking conditions function" runs all time ...

I don't know if i have done the right things, but is there something to do to use correctly many events with conditions ?

Put diferent times on "Cannot re trigger for XXX seconds" for each events. It is the correct way ? I don't know.

Thanks in advance if somebody as any help ...

Here is what i have put :

[kaldoon]

Whow high is your CPU utilization? How many events are running? Can you attach a event log to see? What version of HS are you running?

[nslmanu]

Actually i have 17 "Condition" events. I use the version 2.3.0.19.

In fact actually it runs at less than 10 % CPU because i put "CANNOT RETRIGGER FOR xxx SECONDS" for EACH conditions events.

If a remember, it was nearly 1 per second ... at a point that my interface HS2 on the server ( where we can saw the logs in real time ) freezes.

Now it's fine, but with setting condition with few seconds or X dozen seconds.

[kaldoon]

Let's take a look at a couple of your conditions/events to see what they look like.

[nslmanu]

here is ...

[nightwalker]

I hope this makes sense to you but you could make those examples a lot more efficient if you changed them around a little bit.

for example #1
It looks to me like that command will trigger every minute (depending on what the "do not trigger" setting is set to as far a seconds.
Instead of a condition why not have it setup as a status change, then HS won't be looking at it until that status changes, instead of every 60 seconds or so.

for example #2
Almost the same. change it from condition to a status change on the Virtual Velux (whatever that is ), with a condition of the DS10 being off. This way HS will only be looking at the event when the status changes.

Example #3 I'm not sure about but it looks like it will trigger every 60 seconds, depending on the do not re-trigger setting. is that what you intend?