Comparing GPS time and system time is a bad idea, and likely source of
bugs, use one type of time only.
The delay to wait for the gps was wrong,
t < initial-gps-delay, should be
t > initial-gps-delay then isTimeWindowForMovementExceeded() return true
Merge pull request #1331 from garvankeeley/motion-detect-one-time-system

Motion detect: Comparing GPS time and system time is a bad idea, and likely source of bugs
Merge pull request #1332 from garvankeeley/motion-detect-fix-initial-delay

Motion detect: The delay to wait for the gps was wrong,