Originally posted by mnsandler
View Post
- Setting the Timeout (m:s) in the dialog to 30 secs will send that byte as '02', 20 secs as '01', 10 secs as '00'
- Strangely, setting to 42 mins results in 'FB'
- Setting the timeout 20 secs or more does activate the timeout of this mode (will send an 'On' every 20 secs while motion detected)
- Setting the timeout to 10 secs has the effect of a considerably long delay: tested up to about 90 mins
- No 'Off' sent for this mode
- While set at 20 secs and when motion is continuous, the log shows timestamps every 12 or 14 secs
The byte value you had said to expect is in reality offset by -1 in my testing, at least for the first few values.
There is also a discrepancy with the 42 mins value (should be 'FF' ?) and the actual elapsed time between 'On's.
Comment