Offline wireless locks: Difference between revisions
Telcredstaff (talk | contribs) No edit summary |
Telcredstaff (talk | contribs) No edit summary |
||
| Line 7: | Line 7: | ||
=== Lock mode changes === |
=== Lock mode changes === |
||
A ''lock mode'' change can be initiated either by the controller due to a schedule or by the administrator or API through an ''Override schedule'' action (for more information see the [[Doors]] page. |
A ''lock mode'' change can be initiated either by the controller due to a schedule or by the administrator or API through an ''Override schedule'' action (for more information see the [[Doors]] page. If the controller is online, the lock mode change will be flagged as successful and generate the corresponding event as well as ''lock state'' change. |
||
Revision as of 09:39, 30 June 2020
When one or more wireless locks from SimonsVoss are connected to an Axis controller, there are some things to be aware of that apply to the situation where the controller is online but the wireless lock is not.
Grant access initiated by the server
A grant access command can be initiated by the server either through Telcred Entry, the Telcred API, or directly by the administrator from the door page. The command will be received by the Axis controller and result in an Access granted event, reflecting the fact that this is the decision the controller made. However, as the wireless lock is offline, the lock will not actually unlock. When the lock comes back online, there is no "memory effect" and the door will remain locked until the next successful grant access request.
Lock mode changes
A lock mode change can be initiated either by the controller due to a schedule or by the administrator or API through an Override schedule action (for more information see the Doors page. If the controller is online, the lock mode change will be flagged as successful and generate the corresponding event as well as lock state change.