I’ve been having issues with two pistons that are delayed for some reason. They are both motion lighting pistons and I can’t seem to figure out how to get these to speed up. I’ve removed and re-added the devices, but that hasn’t helped. I can see the motion sensor change almost immediately in the hubitat web interface. some times - really MOST of the time - the piston fires with ~300msec delay, but other times, seemingly randomly, there is a 3-10 second delay.
I recently moved my hub across the house. these issues seemed to start after that. I left it unplugged for probably an hour before plugging it back in. I’ve done several z-wave repairs, but to no avail. the motion sensors are iris zigbee sensors. i tried deleting and re-adding those, but no luck.
all of the lights controlled by these two pistons are in the same area of the house, however, the z-wave switch is in a box with several other switches and I have no problems with those. there are multiple motion sensors near the affected sensors, but they’re operating normally.
Not sure what else to do.
7/19/2018, 4:09:15 PM +340ms
+1ms ╔Received event [Motion Sensor 03 - Mud Room].motion = active with a delay of 3917ms
+197ms ║RunTime Analysis CS > 44ms > PS > 55ms > PE > 98ms > CE
+285ms ║Runtime (46350 bytes) successfully initialized in 55ms (v0.3.104.20180323) (283ms)
+285ms ║╔Execution stage started
+294ms ║║Comparison (string) :7c76bcf13f4437d56396ddf04776b595: is_not (string) :db51cd17b1529242205547665623a183: = true (1ms)
+297ms ║║Condition #23 evaluated true (9ms)
+298ms ║║Cancelling condition #1’s schedules…
+300ms ║║Condition group #1 evaluated true (state changed) (12ms)
+319ms ║║Comparison (enum) active changes_to (string) active = true (1ms)
+320ms ║║Cancelling condition #2’s schedules…
+321ms ║║Condition #2 evaluated true (20ms)
+321ms ║║Condition group #1 evaluated true (state did not change) (21ms)
+322ms ║║Cancelling statement #5’s schedules…
+376ms ║║Executed physical command [Mud Room Lights].on() (36ms)
+377ms ║║Executed [Mud Room Lights].on (38ms)
+380ms ║║Comparison (string) :7c76bcf13f4437d56396ddf04776b595: is_not (string) :db51cd17b1529242205547665623a183: = true (1ms)
+381ms ║║Condition #27 evaluated true (3ms)
+381ms ║║Cancelling condition #26’s schedules…
+382ms ║║Condition group #26 evaluated true (state changed) (4ms)
+394ms ║║Condition #28 evaluated false (11ms)
+395ms ║║Cancelling condition #26’s schedules…
+395ms ║║Condition group #26 evaluated false (state changed) (13ms)
+402ms ║║Comparison (enum) active stays (string) inactive = false (0ms)
+403ms ║║Comparison (enum) inactive stays (string) inactive = true (1ms)
+404ms ║║Cancelling any timed trigger schedules for condition 20
+405ms ║║Cancelling statement #20’s schedules…
+405ms ║║Cancelling condition #20’s schedules…
+406ms ║║Condition #20 evaluated false (9ms)
+407ms ║║Cancelling condition #18’s schedules…
+407ms ║║Condition group #18 evaluated false (state changed) (10ms)
+429ms ║║Comparison (enum) inactive stays (string) inactive = true (8ms)
+507ms ║║Adding a timed trigger schedule for condition 32
+508ms ║║Cancelling condition #32’s schedules…
+509ms ║║Condition #32 evaluated false (100ms)
+509ms ║║Cancelling condition #31’s schedules…
+510ms ║║Condition group #31 evaluated false (state changed) (101ms)
+728ms ║╚Execution stage complete. (442ms)
+881ms ║Setting up scheduled job for Thu, Jul 19 2018 @ 4:11:15 PM EDT (in 119.627s)
+922ms ╚Event processed successfully (921ms)