Announcement

Collapse
No announcement yet.

Cancel events not seeming to work?

Collapse
This topic is closed.
X
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

    Cancel events not seeming to work?

    Morning,

    I have a motion sensor. I trigger things to turn on when it goes on, then when it goes off I setup a wait for x time, 120 minutes, when it goes on I also cancel the wait event. However it has stopped working for some reason. This used to work just fine and about 2-3 weeks ago it stopped, now it seems to end up turning off the lights and disabling things, despite the event being canceled. Is this a known issue?

    BTW what homeseer is doing is hard to track in the logs since it doesn't log which event made a device change to occur... In the logs below the only place in the events the heater is switched to off, is in the event it theoretically canceled a minute before hand.

    Here are the logs:

    3/12/2013 10:04:18 PM Insteon ..Finished Scheduled Polling for 0 devices.
    3/12/2013 10:04:20 PM Insteon Received message from Media Room Moton Sensor (21.D2.8E) taking hops: 1
    3/12/2013 10:04:20 PM Insteon Received ]52 (Media Room Moton Sensor - Occupancy Sensor) Go ON
    3/12/2013 10:04:20 PM Event Event Trigger "Downstairs Motion"
    3/12/2013 10:04:20 PM Event Event No Occupancy downstairs cancelled by request
    3/12/2013 10:04:20 PM Device Control Device: Down Media Room Heater (Q3) ON
    3/12/2013 10:04:21 PM Insteon Received message from Media Room Moton Sensor (21.D2.8E) taking hops: 1
    3/12/2013 10:04:33 PM Insteon Starting Scheduled Polling...
    3/12/2013 10:04:33 PM Insteon ..Finished Scheduled Polling for 0 devices.
    3/12/2013 10:04:35 PM Device Control Device: Down Media Room Heater (Q3) OFF
    3/12/2013 10:04:35 PM Event Event Trigger "Unoccupied Downstairs"
    3/12/2013 10:04:35 PM Event Sending infrared command: [DAIKIN HEATER]Daikin_heater,Off_fixed
    3/12/2013 10:04:35 PM Device Control Device: Down Downstairs Group Off (\8) Value set to 1
    3/12/2013 10:04:35 PM Insteon TransmitGroupMsg called for device code: \8, RF PLM Group 25
    3/12/2013 10:04:36 PM Insteon Received message from Downstairs Cupboard Main (17.F2.9E) taking hops: 2
    3/12/2013 10:04:36 PM Insteon Received message from Media Room Back section (1E.02.2E) taking hops: 2
    3/12/2013 10:04:36 PM Insteon Received message from Media Room Floursecent Middle (1E.04

    #2
    This doesn't fix whatever the actual problem is, but you could try doing this another way.
    Use a delayed device action instead of an event with a wait in it. To stop the delayed action, use remove delayed device action.

    Comment


      #3
      Originally posted by joegr View Post
      Use a delayed device action instead of an event with a wait in it. To stop the delayed action, use remove delayed device action.
      I agree. I've never had consistent results with long waits. I think HS is much better able to handle delayed event actions.
      Mike____________________________________________________________ __________________
      HS3 Pro Edition 3.0.0.548, NUC i3

      HW: Stargate | NX8e | CAV6.6 | Squeezebox | PCS | WGL 800RF | RFXCOM | Vantage Pro | Green-Eye | Edgeport/8 | Way2Call | Ecobee3 | EtherRain | Ubiquiti

      Comment


        #4
        Me too, Waits seem to have issues now and then so I use Delays whenever possible. However, if I have a needed Wait event go bad suddenly, I'll screenshot its components to refer back to, delete it, then recreate it identically, that usually gets it working again.
        All Z-Wave, #101 devices, HomeTroller Series2, HomeSeer2 v.2.5.0.81, & 1x Z-Troller

        Comment

        Working...
        X