www.homeseer.com

Go Back   HomeSeer Message Board > HomeSeer > Home Automation Software > HomeSeer HS2™ Specific

HomeSeer HS2™ Specific General discussion about HomeSeer HS2.

Reply
 
Thread Tools Display Modes
  #1  
Old September 11th, 2009, 03:53 AM
nslmanu nslmanu is offline
Seer Deluxe
 
Join Date: Feb 2009
Location: France
Posts: 216
Unhappy Many Conditions running : CPU increased !

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 :
Attached Images
  
Reply With Quote
  #2  
Old September 11th, 2009, 05:28 AM
kaldoon's Avatar
kaldoon kaldoon is online now
Seer Master
 
Join Date: Apr 2007
Location: Florida
Posts: 640
Default

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?
Reply With Quote
  #3  
Old September 11th, 2009, 05:40 AM
nslmanu nslmanu is offline
Seer Deluxe
 
Join Date: Feb 2009
Location: France
Posts: 216
Default

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.
Reply With Quote
  #4  
Old September 11th, 2009, 06:09 AM
kaldoon's Avatar
kaldoon kaldoon is online now
Seer Master
 
Join Date: Apr 2007
Location: Florida
Posts: 640
Default

Let's take a look at a couple of your conditions/events to see what they look like.
Reply With Quote
  #5  
Old September 11th, 2009, 07:50 AM
nslmanu nslmanu is offline
Seer Deluxe
 
Join Date: Feb 2009
Location: France
Posts: 216
Default

here is ...
Attached Images
 
Reply With Quote
  #6  
Old September 11th, 2009, 10:02 AM
nightwalker nightwalker is offline
OverSeer
 
Join Date: Dec 2004
Location: Coatesville, PA.
Posts: 3,235
Default

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?
__________________
Marty
------
XPpro SP3 /w HS 2.4.0.11
Reply With Quote
Reply

Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off

Forum Jump


All times are GMT -4. The time now is 09:24 PM.


Copyright 1998-2008 HomeSeer Technologies, LLC