Announcement

Collapse
No announcement yet.

Help with rule firing issue/logic

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • simonmason
    replied
    Agreed. Some sort of control panel that allows you to check on items - like the values of internal variables, etc.

    Leave a comment:


  • Steve Q
    replied
    But this does raise the issue that something is wrong somewhere! I think we have all seen occasional anomalies with Homeseer: it would be nice if there was some way to check an event! Any ideas?

    Steve Q

    Leave a comment:


  • nightwalker
    replied
    Glad you got it working, It looked too simple to have been anything you could have done wrong, of course that's the time's I always get tripped up, the simple things.

    Leave a comment:


  • simonmason
    replied
    Recreating the rule seems to have done the trick. Obviously something was messed up in the back end with this particular rule. Thanks for the help.

    Leave a comment:


  • nightwalker
    replied
    If it's still firing now like it was I think the next thing I'd suspect like Mike says is a database problem. I've had this happen once or twice. I fixed it by deleting the event. shutting down HS, rebooting and then re-creating the event from a fresh start of the database.

    Leave a comment:


  • Uncle Michael
    replied
    Originally posted by simonmason View Post
    There is no reason why this rule keeps firing like this. I tried deleting it and creating it from scratch. I will let you know how it goes. Thanks.
    I agree. It looks like it should work just as you intend. It does seem likely that it was a glitch in the database. I'll be really surprised if it doesn't work fine now.

    Leave a comment:


  • simonmason
    replied
    There is no reason why this rule keeps firing like this. I tried deleting it and creating it from scratch. I will let you know how it goes. Thanks.

    Leave a comment:


  • nightwalker
    replied
    I don't see anything wrong with the event at first glance. It triggers at 8am, weekdays, only if both devices listed are on. Personally I usually put a cannot retrigger for 60sec in there but I don't think it would make a difference.

    I assume that since it's not a weekday that it hasn't run today?
    As a test can you manually shut off one, then the other of the devices listed as a conditon and see if that makes a difference.

    If it's still behaving as it should I'd be looking at what turns the conditions on and off and see if that's behaving as it should as well.

    Leave a comment:


  • simonmason
    replied
    Here is a screen shot below. Thanks for all of the responses.

    http://www.themasons.net/images/rule_screen2_062709.jpg

    http://www.themasons.net/images/rule_screen_062709.jpg

    The two conditions are really unrelated. Obviously they are both set to on right now or the rule wouldn't fire at all.

    Leave a comment:


  • Steve Q
    replied
    It looks like something has a 5 minute interval. Do you have "do not retrigger" set to 5 min? There must be a condition set that is true anytime after 8:00

    Steve Q

    Leave a comment:


  • Uncle Michael
    replied
    Marty beat me to it. I was going to ask the same thing. Perhaps you could you post a screen shot of your event?

    Leave a comment:


  • nightwalker
    replied
    It's a little hard to comment without seeing the event and conditions. You say you have used Absolute time as a trigger, I assume at 8am, but then you say that you've used a condition of 8am as well, along with a couple of other conditions. Any chance you could be a bit more specific about the event itself?

    Leave a comment:


  • simonmason
    started a topic Help with rule firing issue/logic

    Help with rule firing issue/logic

    I need help with a rule that is firing continuously throughout the day that I can't figure out. I have a snippet of my log below if that helps. I have set up rules that fire to change the temperature of my thermostats at various times. One of these runs at 8am in the morning, and then there are later rules that adjust the temp based on the time of day. The 8am rule seems to fire continuously throughout the day. You can see it below called "Thermostats - Cool - 0800AM - Weekday". I can't figure out why this is. The rule is setup as follows:

    Trigger: Absolute time
    Days - all weekdays checked
    Apply conditions: 8:00:00 AM
    I have two other conditions set that seem unrelated - only fire when thermostat is in cool mode and when someone is home)

    And that is it. However, clearly it is going off all of the time (and overriding the later rules that attempt to set the temperature).

    Is there something I can do to further diagnose this - should I delete and recreate the rule? Thanks.

    Code:
        Line 2467: 6/26/2009 7:25:57 AM ~!~Info~!~Event Trigger "Thermostats - Cool - 0800AM - Weekday"
        Line 2498: 6/26/2009 7:30:00 AM ~!~Info~!~Event Trigger "Thermostats - Cool - 0650AM - Fan Off"
        Line 2541: 6/26/2009 7:37:59 AM ~!~Info~!~Event Trigger "Thermostats - Cool - 0800AM - Weekday"
        Line 2680: 6/26/2009 8:00:00 AM ~!~Info~!~Event Trigger "Thermostats - Cool - 0800AM - Weekday"
        Line 4174: 6/26/2009 12:14:00 PM ~!~Info~!~Event Trigger "Thermostats - Cool - 0800AM - Weekday"
        Line 4192: 6/26/2009 12:18:00 PM ~!~Info~!~Event Trigger "Thermostats - Cool - 0800AM - Weekday"
        Line 4352: 6/26/2009 12:47:08 PM ~!~Info~!~Event Trigger "Thermostats - Cool - 0800AM - Weekday"
        Line 4381: 6/26/2009 12:51:09 PM ~!~Info~!~Event Trigger "Thermostats - Cool - 0800AM - Weekday"
        Line 4534: 6/26/2009 1:15:16 PM ~!~Info~!~Event Trigger "Thermostats - Cool - 0800AM - Weekday"
        Line 4572: 6/26/2009 1:20:17 PM ~!~Info~!~Event Trigger "Thermostats - Cool - 0800AM - Weekday"
        Line 4687: 6/26/2009 1:41:22 PM ~!~Info~!~Event Trigger "Thermostats - Cool - 0800AM - Weekday"
        Line 4725: 6/26/2009 1:47:23 PM ~!~Info~!~Event Trigger "Thermostats - Cool - 0800AM - Weekday"
        Line 4836: 6/26/2009 2:01:26 PM ~!~Info~!~Event Trigger "Thermostats - Cool - 0800AM - Weekday"
        Line 4885: 6/26/2009 2:07:28 PM ~!~Info~!~Event Trigger "Thermostats - Cool - 0800AM - Weekday"
        Line 4949: 6/26/2009 2:17:30 PM ~!~Info~!~Event Trigger "Thermostats - Cool - 0800AM - Weekday"
        Line 4981: 6/26/2009 2:22:31 PM ~!~Info~!~Event Trigger "Thermostats - Cool - 0800AM - Weekday"
        Line 5066: 6/26/2009 2:34:35 PM ~!~Info~!~Event Trigger "Thermostats - Cool - 0800AM - Weekday"
        Line 5131: 6/26/2009 2:45:38 PM ~!~Info~!~Event Trigger "Thermostats - Cool - 0800AM - Weekday"
        Line 5189: 6/26/2009 2:55:41 PM ~!~Info~!~Event Trigger "Thermostats - Cool - 0800AM - Weekday"
        Line 5250: 6/26/2009 3:05:43 PM ~!~Info~!~Event Trigger "Thermostats - Cool - 0800AM - Weekday"
        Line 5309: 6/26/2009 3:15:45 PM ~!~Info~!~Event Trigger "Thermostats - Cool - 0800AM - Weekday"
        Line 5368: 6/26/2009 3:25:48 PM ~!~Info~!~Event Trigger "Thermostats - Cool - 0800AM - Weekday"
        Line 5434: 6/26/2009 3:33:49 PM ~!~Info~!~Event Trigger "Thermostats - Cool - 0800AM - Weekday"
        Line 5481: 6/26/2009 3:41:51 PM ~!~Info~!~Event Trigger "Thermostats - Cool - 0800AM - Weekday"
        Line 5541: 6/26/2009 3:51:53 PM ~!~Info~!~Event Trigger "Thermostats - Cool - 0800AM - Weekday"
        Line 5615: 6/26/2009 4:02:55 PM ~!~Info~!~Event Trigger "Thermostats - Cool - 0800AM - Weekday"
        Line 5711: 6/26/2009 4:15:58 PM ~!~Info~!~Event Trigger "Thermostats - Cool - 0800AM - Weekday"
        Line 5776: 6/26/2009 4:27:00 PM ~!~Info~!~Event Trigger "Thermostats - Cool - 0800AM - Weekday"
        Line 5859: 6/26/2009 4:41:04 PM ~!~Info~!~Event Trigger "Thermostats - Cool - 0800AM - Weekday"
        Line 5912: 6/26/2009 4:49:05 PM ~!~Info~!~Event Trigger "Thermostats - Cool - 0800AM - Weekday"
        Line 6002: 6/26/2009 5:04:09 PM ~!~Info~!~Event Trigger "Thermostats - Cool - 0800AM - Weekday"
        Line 6065: 6/26/2009 5:13:11 PM ~!~Info~!~Event Trigger "Thermostats - Cool - 0800AM - Weekday"
        Line 6178: 6/26/2009 5:28:15 PM ~!~Info~!~Event Trigger "Thermostats - Cool - 0800AM - Weekday"
        Line 6191: 6/26/2009 5:28:22 PM ~!~Shutdown~!~Shutting down plug-in: RCS Serial Thermostats
        Line 6256: 6/26/2009 5:32:13 PM ~!~Info~!~Found plug-in: RCS Serial Thermostats, version: 2.4.0.2
        Line 6261: 6/26/2009 5:32:13 PM ~!~Info~!~Initializing Plug-in: RCS Serial Thermostats on COM port 10
        Line 6262: 6/26/2009 5:32:13 PM ~!~RCS Serial Thermostats~!~1 Thermostats created Successfully.
        Line 6262: 6/26/2009 5:32:13 PM ~!~RCS Serial Thermostats~!~1 Thermostats created Successfully.
        Line 6263: 6/26/2009 5:32:13 PM ~!~Info~!~Finished initializing plug-in RCS Serial Thermostats
        Line 6385: 6/26/2009 5:35:16 PM ~!~Info~!~Event Trigger "Thermostats - Cool - 0800AM - Weekday"
        Line 6453: 6/26/2009 5:45:20 PM ~!~Info~!~Event Trigger "Thermostats - Cool - 0800AM - Weekday"
        Line 6582: 6/26/2009 5:54:22 PM ~!~Info~!~Event Trigger "Thermostats - Cool - 0800AM - Weekday"
        Line 6966: 6/26/2009 7:00:00 PM ~!~Info~!~Event Trigger "Thermostats - Cool - 0700PM"
        Line 7108: 6/26/2009 7:23:45 PM ~!~Info~!~Event Trigger "Thermostats - Cool - 0800AM - Weekday"
        Line 7185: 6/26/2009 7:36:49 PM ~!~Info~!~Event Trigger "Thermostats - Cool - 0800AM - Weekday"
        Line 7278: 6/26/2009 7:49:53 PM ~!~Info~!~Event Trigger "Thermostats - Cool - 0800AM - Weekday"
        Line 8455: 6/26/2009 10:44:36 PM ~!~Info~!~Event Trigger "Thermostats - Cool - 0800AM - Weekday"
        Line 8529: 6/26/2009 10:55:00 PM ~!~Info~!~Event Trigger "Thermostats - Cool - 1055PM"
        Line 8558: 6/26/2009 10:58:39 PM ~!~Info~!~Event Trigger "Thermostats - Cool - 0800AM - Weekday"
Working...
X