Latency / Delay between motion detection and trigger of action

Discussions about Z-Way software and Z-Wave technology in general
Post Reply
Toffi
Posts: 22
Joined: 12 Aug 2016 09:43

Latency / Delay between motion detection and trigger of action

Post by Toffi » 04 Apr 2018 18:41

Hello!
I´m using a RPi with Z-Way (actually 2.3.7).

Since some month I use a Aeon Multisensor 6 for motion detection and a Relay AEOTEC Micro Switch G2 to switch on the light.
Overall this works, but regardless what App (If-Then, Logical rule, ...) I´m using to monitor the motion sensor and trigger the relay, I have a delay / latecy of 2-4 seconds.

I already checked the log-file and found the trigger of the motion sensor and 2-4 seconds later the trigger of the relay - with nothing else in the log file in between.
I can not believe, that the RPi needs that amount of time to calculate the rule.
Also when i trigger the relay via the Z-Way web interface, the relay switching immediatly.

I have no clue, what is the reason for this delay.
Is anyone facing the same "problem" and may have a solution?

Sample of the LOG-File:
[2018-04-04 16:26:50.253] [D] [zway] RECEIVED: ( 01 09 00 04 00 03 03 30 03 FF 3E )
[2018-04-04 16:26:50.254] [D] [zway] SENT ACK
[2018-04-04 16:26:50.254] [D] [zway] SETDATA devices.3.data.lastReceived = 0 (0x00000000)
[2018-04-04 16:26:50.255] [D] [zway] SETDATA devices.3.instances.0.commandClasses.48.data.1.level = True
[2018-04-04 16:26:50.255] [D] [zway] SETDATA devices.3.instances.0.commandClasses.48.data.1 = Empty
[2018-04-04 16:26:50.267] [core] HK: updated ZWayVDev_zway_3-0-48-1
[2018-04-04 16:26:50.308] [core] Notification: device-info (device-OnOff): {"dev":"Sensor Bewegung","l":"on","location":3}
[2018-04-04 16:26:50.588] [D] [zway] RECEIVED: ( 01 10 00 04 00 03 0A 71 05 00 00 00 FF 07 08 00 00 66 )
[2018-04-04 16:26:50.588] [D] [zway] SENT ACK
[2018-04-04 16:26:50.589] [D] [zway] SETDATA devices.3.data.lastReceived = 0 (0x00000000)
[2018-04-04 16:26:50.589] [D] [zway] SETDATA devices.3.instances.0.commandClasses.113.data.7.eventParameters = byte[0]
[2018-04-04 16:26:50.590] [D] [zway] ( zero-length buffer )
[2018-04-04 16:26:50.590] [D] [zway] SETDATA devices.3.instances.0.commandClasses.113.data.7.event = 8 (0x00000008)
[2018-04-04 16:26:50.609] [D] [zway] SETDATA devices.3.instances.0.commandClasses.113.data.7.eventString = "Motion detected, location unknown"
[2018-04-04 16:26:50.609] [D] [zway] SETDATA devices.3.instances.0.commandClasses.113.data.7.status = 255 (0x000000ff)
[2018-04-04 16:26:50.610] [D] [zway] SETDATA devices.3.instances.0.commandClasses.113.data.7 = Empty
[2018-04-04 16:26:54.737] [core] --- ZWayVDev_zway_5-0-37 performCommand processing: {"0":"on"}
[2018-04-04 16:26:54.750] [zway] Adding job: SwitchBinary Set
[2018-04-04 16:26:54.750] [zway] Adding job: SwitchBinary Get
[2018-04-04 16:26:54.767] [D] [zway] SENDING (cb 0xb7): ( 01 0E 00 13 05 07 56 01 25 01 FF 1F 3A 25 B7 DB )
[2018-04-04 16:26:54.769] [D] [zway] RECEIVED ACK
[2018-04-04 16:26:54.774] [D] [zway] RECEIVED: ( 01 04 01 13 01 E8 )
[2018-04-04 16:26:54.774] [D] [zway] SENT ACK
[2018-04-04 16:26:54.774] [D] [zway] Delivered to Z-Wave stack
[2018-04-04 16:26:54.807] [D] [zway] RECEIVED: ( 01 07 00 13 B7 00 00 02 5E )
[2018-04-04 16:26:54.807] [D] [zway] SENT ACK
[2018-04-04 16:26:54.807] [zway] Job 0x13 (SwitchBinary Set): Delivered
[2018-04-04 16:26:54.808] [D] [zway] SendData Response with callback 0xb7 received: received by recipient
[2018-04-04 16:26:54.809] [D] [zway] SETDATA devices.5.data.lastSendInternal = **********
[2018-04-04 16:26:54.809] [D] [zway] Job 0x13 (SwitchBinary Set): success
[2018-04-04 16:26:54.809] [zway] Removing job: SwitchBinary Set

micky1500
Posts: 92
Joined: 07 Feb 2016 16:29

Re: Latency / Delay between motion detection and trigger of action

Post by micky1500 » 13 Apr 2018 14:13

I have also noticed the delays since 2.3.6. Have had to use workarounds since "Code Device" became too slow.
Maybe something Z-Wave Support can explain !

I have found that "Light Motion Trigger" works faster than "If-Then". Light comes on quite quickly.
Although it has it's own problems. Multiple instances of this App interfere with each other.

These settings are what I found work best:-
Multisensor PIR Timeout (parameter 3) set to 60 Seconds.
LMT App settings:- Trigger timeout = 60, Poll interval = 20, Delay time = Blank.

I´m using RPi3, 2.3.7
Aeon Multisensor 6 v1.11 (Device 136)
TKB TZ66D Dimmable Light (Device 17)

Log File - Using Light Motion Trigger :-
[2018-04-12 21:30:28.901] [D] [zway] RECEIVED: ( 01 0B 00 04 00 88 03 30 03 FF D5 00 62 )
[2018-04-12 21:30:28.901] [D] [zway] SENT ACK
[2018-04-12 21:30:28.901] [D] [zway] SETDATA devices.136.data.lastReceived = 0 (0x00000000)
[2018-04-12 21:30:28.902] [D] [zway] SETDATA devices.136.instances.0.commandClasses.48.data.1.level = True
[2018-04-12 21:30:28.902] [D] [zway] SETDATA devices.136.instances.0.commandClasses.48.data.1 = Empty
[2018-04-12 21:30:29.088] [core] [MotionTrigger-262] Handle sensor update from ZWayVDev_zway_136-0-48-1
[2018-04-12 21:30:29.091] [core] [MotionTrigger-262] Handle change to on from ZWayVDev_zway_136-0-48-1
[2018-04-12 21:30:29.094] [core] [MotionTrigger-262] Device PIR is on
[2018-04-12 21:30:29.096] [core] [MotionTrigger-262] Device Light Kitchen is 0
[2018-04-12 21:30:29.097] [core] [MotionTrigger-262] Calculating precondition
[2018-04-12 21:30:29.099] [core] [MotionTrigger-262] Triggered motion sensor (preconditions: true, lights: false, triggered: false)
[2018-04-12 21:30:29.120] [D] [zway] RECEIVED: ( 01 12 00 04 00 88 0A 71 05 00 00 00 FF 07 08 00 00 D5 00 3A )
[2018-04-12 21:30:29.120] [D] [zway] SENT ACK
[2018-04-12 21:30:29.120] [D] [zway] SETDATA devices.136.data.lastReceived = 0 (0x00000000)
[2018-04-12 21:30:29.121] [D] [zway] SETDATA devices.136.instances.0.commandClasses.113.data.7.eventParameters = byte[0]
[2018-04-12 21:30:29.121] [D] [zway] ( zero-length buffer )
[2018-04-12 21:30:29.121] [D] [zway] SETDATA devices.136.instances.0.commandClasses.113.data.7.event = 8 (0x00000008)
[2018-04-12 21:30:29.122] [D] [zway] SETDATA devices.136.instances.0.commandClasses.113.data.7.eventString = "Motion detected, location unknown"
[2018-04-12 21:30:29.122] [D] [zway] SETDATA devices.136.instances.0.commandClasses.113.data.7.status = 255 (0x000000ff)
[2018-04-12 21:30:29.123] [D] [zway] SETDATA devices.136.instances.0.commandClasses.113.data.7 = Empty
[2018-04-12 21:30:29.603] [core] [MotionTrigger-262] Turning on
[2018-04-12 21:30:29.604] [core] [MotionTrigger-262] Set ZWayVDev_zway_17-0-38 9
[2018-04-12 21:30:29.607] [core] [MotionTrigger-262] Turn ZWayVDev_zway_17-0-38 9
[2018-04-12 21:30:29.608] [core] --- ZWayVDev_zway_17-0-38 performCommand processing: {"0":"exact","1":{"level":9}}
[2018-04-12 21:30:29.608] [I] [zway] Adding job: SwitchMultilevel Set
[2018-04-12 21:30:29.608] [I] [zway] Adding job: SwitchMultilevel Get
[2018-04-12 21:30:29.610] [D] [zway] SENDING (cb 0x24): ( 01 0A 00 13 11 03 26 01 09 25 24 DB )
[2018-04-12 21:30:29.612] [D] [zway] RECEIVED ACK
[2018-04-12 21:30:29.612] [I] [core] Notification: device-info (device-OnOff): {"dev":"PIR","l":"on","location":8}
[2018-04-12 21:30:29.616] [D] [zway] RECEIVED: ( 01 04 01 13 01 E8 )
[2018-04-12 21:30:29.616] [D] [zway] SENT ACK
[2018-04-12 21:30:29.616] [D] [zway] Delivered to Z-Wave stack
[2018-04-12 21:30:29.662] [D] [zway] RECEIVED: ( 01 18 00 13 24 00 00 04 01 B1 7F 7F 7F 7F 00 01 03 12 00 00 00 02 01 00 00 77 )
[2018-04-12 21:30:29.663] [D] [zway] SENT ACK
[2018-04-12 21:30:29.663] [I] [zway] Job 0x13 (SwitchMultilevel Set): Delivered
[2018-04-12 21:30:29.663] [D] [zway] SendData Response with callback 0x24 received: received by recipient
[2018-04-12 21:30:29.663] [D] [zway] SETDATA devices.17.data.lastSendInternal = **********
[2018-04-12 21:30:29.663] [D] [zway] Job 0x13 (SwitchMultilevel Set): success
[2018-04-12 21:30:29.663] [I] [zway] Removing job: SwitchMultilevel Set
Raspi 3(Stretch), Zwave.me 3.0.0

Post Reply