Originally posted by Uncle Michael
View Post
Announcement
Collapse
No announcement yet.
Using the security setting with triggers for home security
Collapse
X
-
Mike____________________________________________________________ __________________
HS3 Pro Edition 3.0.0.548, NUC i3
HW: Stargate | NX8e | CAV6.6 | Squeezebox | PCS | WGL 800RF | RFXCOM | Vantage Pro | Green-Eye | Edgeport/8 | Way2Call | Ecobee3 | EtherRain | Ubiquiti
-
On my two test events that were both set to trigger at 9:17PM yesterday, one ran at 9:28 and the other ran at 9:17. The event that ran at 9:28 was the original event that ran at 9:17 the day before.
It looks like some randomness is getting in there. I cannot tell when the random time is applied.HS4 Pro, 4.2.19.16 Windows 10 pro, Supermicro LP Xeon
Comment
-
I also can confirm that my tests show events randomizing, despite not showing a random number after the previous event ran (or after midnight).
So this is good, it works! It's not obvious that it works, but it does indeed work based on the three trials documented here! Thank you for your input, everyone!
Comment
-
Sorry... real dumb question. But what's the purpose of the security randomize feature for events?
RobertHS3PRO 3.0.0.500 as a Fire Daemon service, Windows 2016 Server Std Intel Core i5 PC HTPC Slim SFF 4GB, 120GB SSD drive, WLG800, RFXCom, TI103,NetCam, UltraNetcam3, BLBackup, CurrentCost 3P Rain8Net, MCsSprinker, HSTouch, Ademco Security plugin/AD2USB, JowiHue, various Oregon Scientific temp/humidity sensors, Z-Net, Zsmoke, Aeron Labs micro switches, Amazon Echo Dots, WS+, WD+ ... on and on.
Comment
-
Originally posted by langenet View PostSorry... real dumb question. But what's the purpose of the security randomize feature for events?
Robert
In theory every time triggered event with Security enabled will be randomly set to trigger at the stipulated time +- some or all of the offset value.HS4 Pro, 4.2.19.16 Windows 10 pro, Supermicro LP Xeon
Comment
-
Originally posted by Lucid View PostI also can confirm that my tests show events randomizing, despite not showing a random number after the previous event ran (or after midnight).
So this is good, it works! It's not obvious that it works, but it does indeed work based on the three trials documented here! Thank you for your input, everyone!
I have it set for 9pm and just now at 12:00 noon it changed. Anybody know why that particular time. How would that relate to a time that was set in the AM. Would it change at 12:00 midnight?
Comment
-
Originally posted by cowinger View PostI just got the answer to when this changes the random time. Maybe someone can say why.
I have it set for 9pm and just now at 12:00 noon it changed. Anybody know why that particular time. How would that relate to a time that was set in the AM. Would it change at 12:00 midnight?HS4 Pro, 4.2.19.16 Windows 10 pro, Supermicro LP Xeon
Comment
-
Originally posted by cowinger View PostThat could be because they are set for the AM. Mine is set for the PM and it changed at noon. Perhaps the AM ones will set at midnight.HS4 Pro, 4.2.19.16 Windows 10 pro, Supermicro LP Xeon
Comment
-
Thanks Randy, but what's the use case for adding a time offset?
When would I want to or need to do this?
RobertHS3PRO 3.0.0.500 as a Fire Daemon service, Windows 2016 Server Std Intel Core i5 PC HTPC Slim SFF 4GB, 120GB SSD drive, WLG800, RFXCom, TI103,NetCam, UltraNetcam3, BLBackup, CurrentCost 3P Rain8Net, MCsSprinker, HSTouch, Ademco Security plugin/AD2USB, JowiHue, various Oregon Scientific temp/humidity sensors, Z-Net, Zsmoke, Aeron Labs micro switches, Amazon Echo Dots, WS+, WD+ ... on and on.
Comment
-
Originally posted by langenet View PostThanks Randy, but what's the use case for adding a time offset?
When would I want to or need to do this?
Robert
HS4 Pro, 4.2.19.16 Windows 10 pro, Supermicro LP Xeon
Comment
Comment