Hello,
I've setup several light points controlled by motion sensors (PIR).
One of the lights is for a staircase where immediate light response is mandatory.
But only in 70% of the triggers the light reacts immediately (within 1 sec).
For the 30% remaining cases I experience several seconds up till minutes of delays.
Attached you have the two events: the first to trigger the light and the second to turnoff the light and some logging snapshots of a normal run (no delay) and a delayed run (one minute delay)
Watch the logging time in both cases.
In a normal run there is a minimal elapse time of 10 seconds between the motion sensor to switch on and to switch backoff (PIR motion timeout is +- 6 sec).
In case of a delayed run, all the actions between the motion sensor switch on/off are reported at the same time. This time corresponds with the time when I see the light turning on. (in the case of the provided images it was after a delay of more then 50 seconds).
In any case the event runs and executes as expected but the time when this happens is for me the problem.
Any ideas how I can eliminate these delays ?
Some info on my system:
HomeSeer Version: HS3 Pro Edition 3.0.0.357
Operating System: Microsoft Windows Embedded Standard - Work Station
System Uptime: 4 Days 2 Hours 34 Minutes 8 Seconds
IP Address:
Number of Devices: 713
Number of Events: 84
Available Threads: 200
Enabled Plug-Ins
2.0.22.0: BLOccupied
2.0.127.0: BLRadar
2.0.34.0: BLSecurity
1.1.2.0: Device History
3.0.0.33: EasyTrigger
3.0.0.28: Nest
30.0.0.35: RFXCOM
3.0.5917.35093: UltraLog3
3.0.0.73: weatherXML
3.0.1.130: Z-Wave
Thanks,
Joris
I've setup several light points controlled by motion sensors (PIR).
One of the lights is for a staircase where immediate light response is mandatory.
But only in 70% of the triggers the light reacts immediately (within 1 sec).
For the 30% remaining cases I experience several seconds up till minutes of delays.
Attached you have the two events: the first to trigger the light and the second to turnoff the light and some logging snapshots of a normal run (no delay) and a delayed run (one minute delay)
Watch the logging time in both cases.
In a normal run there is a minimal elapse time of 10 seconds between the motion sensor to switch on and to switch backoff (PIR motion timeout is +- 6 sec).
In case of a delayed run, all the actions between the motion sensor switch on/off are reported at the same time. This time corresponds with the time when I see the light turning on. (in the case of the provided images it was after a delay of more then 50 seconds).
In any case the event runs and executes as expected but the time when this happens is for me the problem.
Any ideas how I can eliminate these delays ?
Some info on my system:
HomeSeer Version: HS3 Pro Edition 3.0.0.357
Operating System: Microsoft Windows Embedded Standard - Work Station
System Uptime: 4 Days 2 Hours 34 Minutes 8 Seconds
IP Address:
Number of Devices: 713
Number of Events: 84
Available Threads: 200
Enabled Plug-Ins
2.0.22.0: BLOccupied
2.0.127.0: BLRadar
2.0.34.0: BLSecurity
1.1.2.0: Device History
3.0.0.33: EasyTrigger
3.0.0.28: Nest
30.0.0.35: RFXCOM
3.0.5917.35093: UltraLog3
3.0.0.73: weatherXML
3.0.1.130: Z-Wave
Thanks,
Joris