Rule takes 3 Seconds from state to be executed


(Vassilis) #1

Dear Group.
It seems that It takes some time from the OPEN of a door to execute the rule

Basically events:

2018-12-22 18:29:56.656 [vent.ItemStateChangedEvent] - ControllerZWave_StartFrames changed from 2499 to 2500
2018-12-22 18:29:56.731 [vent.ItemStateChangedEvent] - SensorMultiEntrance_Contact changed from CLOSED to OPEN
2018-12-22 18:29:56.735 [GroupItemStateChangedEvent] - gDoorOpenClose changed from CLOSED to OPEN through SensorMultiEntrance_Contact
2018-12-22 18:29:56.738 [vent.ItemStateChangedEvent] - SensorMultiEntrance_Luminance changed from 2 to 1
** 2018-12-22 18:29:59.983 [ome.event.ItemCommandEvent] - Item ‘Entrance_LightActive_Timer’ received command ON**
2018-12-22 18:29:59.989 [vent.ItemStateChangedEvent] - Entrance_LightActive_Timer changed from OFF to ON
2018-12-22 18:30:00.001 [ome.event.ItemCommandEvent] - Item ‘SwitchDualHallway_Hall’ received command ON
2018-12-22 18:30:00.013 [nt.ItemStatePredictedEvent] - SwitchDualHallway_Hall predicted to become ON
2018-12-22 18:30:00.032 [vent.ItemStateChangedEvent] - SwitchDualHallway_Hall changed from OFF to ON

rule is:

rule "Entrance State Change"
when
  Item SensorMultiEntrance_Contact changed
then
  logInfo(log_title_doorchange, "Door Sensor Change Triggered")
  Entrance_LightActive_Timer.sendCommand(ON)

I cannot find what is causing this delay, before final release this was pretty msec which is not 3-5 sec.


(CM6.5 H102) #2

If you remove the item from the group does it still take 3-5 sec for the rule to exectue?


(Markus Storm) #3

There’s different possible reasons. You must give way more details else this is pure guessing.

You need gather debug logs to show ALL relevant outputs, including the logInfo() output and relevant binding/sensor+actuator communications.
See #9, #10, #11 of


(Joachim Boeddeker) #4

Did you look here?