www.homeseer.com

Go Back   HomeSeer Message Board > HomeSeer > Feature Requests

Feature Requests Post requests for new features. Others can rate your request to indicate the interest level in the feature.

Reply
 
Thread Tools Display Modes
  #1  
Old July 22nd, 2009, 09:15 AM
ArbWare's Avatar
ArbWare ArbWare is offline
Seer Deluxe
 
Join Date: Apr 2006
Location: Columbus, Ohio
Posts: 446
Default Feature Request - HS.NewTimeEvent()

When scripting with the hs.newtimeevent() function.

I would like the ability to set the

"Do Not Log This Event" check box on the created event.

I use the hs.newtimeevent() function extensively.. and this would help reduce the amount of information in the log. (unless i want to debug.. then i would not set the checkbox in the script)

I am not sure if this would also take care of the issue raised in the thread:

http://board.homeseer.com/showthread.php?t=136771

This thread is asking for the ability to disable the message
--------------------------------

Info Deleting event after run "Eventname"
--------------------------------
that is logged when a delayed event is automatically deleted.

These might be two separate issues. I do not know.

Thank you.
__________________
Regards,

Andrew B.
Reply With Quote
  #2  
Old July 22nd, 2009, 09:31 AM
Moskus's Avatar
Moskus Moskus is online now
Seer Master
 
Join Date: Aug 2007
Location: Norway
Posts: 836
Default

This will not only happen with hs.newtimeevent but also with all delayed events, which is the main problem for me.

I support this request 100%.
Reply With Quote
  #3  
Old November 19th, 2009, 05:41 PM
KurtLutterman KurtLutterman is offline
Seer
 
Join Date: Jan 2008
Location: Washington
Posts: 12
Default

Let me add my enthusiastic support for this request. My BasicStat script controls X10 thermostats. For each temperature change reported by the thermostat, it sends two X10 preset dim levels. For maximizing HS's multi-threaded performance, my script breaks up handling each received X10 into a high-priority "X10 Received" which only grabs the X10 packet and pushes it into a queue before it's lost to the next X10 reception. The normal-priority "X10 Received Processing" then is not time-critical to pop the received queue and act on it. I've implemented it so that "X10 Received" will DelayTrigger "X10 Received Processing" in a new thread so HS can effectively manage its processes.

But with the always-logged nature of delayed events, I get four log lines of extraneous for every one line of information:
11/19/2009 1:28:54 PM X10 Received K6 (?) K Preset Dim 8
11/19/2009 1:28:55 PM Info Event Trigger "K X10 Received Processing (delayed event)"
11/19/2009 1:28:55 PM Info Deleting event after run: "Delayed Actions K X10 Received Processing (delayed event)"
11/19/2009 1:28:55 PM X10 Received K15 (?) K Preset Dim 4
11/19/2009 1:28:56 PM Info Event Trigger "K X10 Received Processing (delayed event)"
11/19/2009 1:28:56 PM Info Deleting event after run: "Delayed Actions K X10 Received Processing (delayed event)"
11/19/2009 1:28:56 PM BasicStat K Fellowship Hall North Thermostat (K1) Temperature = 72
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 On

Forum Jump


All times are GMT -4. The time now is 10:48 AM.


Copyright 1998-2008 HomeSeer Technologies, LLC