I base a lot of events on my Elk M1 zones - like speaking an alert when a gate is opened. I've been doing this without a hitch for years.
Recently I've got a long lag between when the zone is violated and when the event runs. This behavior is specific to Elk zones - events based on time or device status still run immediately. Elki zone based triggers can be delayed sometimes minutes even when set to be 'high priority' events
My log has a bunch of this
I don't know if that's significant.
I've rebooted everything - the M1, the M1XEP, the PC running HS3 etc. The CPU usage on the HS3 machine is 35%.
Any thoughts?
Recently I've got a long lag between when the zone is violated and when the event runs. This behavior is specific to Elk zones - events based on time or device status still run immediately. Elki zone based triggers can be delayed sometimes minutes even when set to be 'high priority' events
My log has a bunch of this
Warning | No response/improper response from Elk M1 to command 'az00' |
Aug-13 7:03:20 PM | Warning | No response/improper response from Elk M1 to command 'cv0100' |
Aug-13 7:03:18 PM | Warning | No response/improper response from Elk M1 to command 'cv0100' |
Aug-13 7:03:17 PM | Warning | No response/improper response from Elk M1 to command 'cv0100' |
Aug-13 7:03:11 PM | Warning | No response/improper response from Elk M1 to command 'az00' |
Aug-13 7:03:10 PM | Warning | No response/improper response from Elk M1 to command 'az00' |
Aug-13 7:03:08 PM | Warning | No response/improper response from Elk M1 to command 'az00 |
I've rebooted everything - the M1, the M1XEP, the PC running HS3 etc. The CPU usage on the HS3 machine is 35%.
Any thoughts?
Comment