...
| Code Block | ||
|---|---|---|
| ||
{
"event": "opvideoDevice.qrCode.detected",
"timestamp": 1699390723.60129,
"data": {
"qrCodes": [
"http://en.m.wikipedia.org "
],
"acu": {
"id": 17444,
"name": "Test Video Intercom",
"opal": "opal:sandbox:helium:alpha:302:acu:17444"
},
"gatewayDevice": {
"name": "Test Video Intercom",
"opal": "opal:sandbox:helium:alpha:302:acu:17444",
"type": "acu",
"uid": "17444"
},
"opvideoDeviceId": 62,
"org": {
"id": 302,
"name": "IMVP2 Dev Org",
"opal": "opal:sandbox:helium:alpha:302:org:302"
},
"sourceDevice": {
"opal": "opal:sandbox:helium:alpha:302:opvideoDevice:62",
"type": "opvideoDevice",
"uid": "62"
}
}
} |
The inclusion of the Event detail is intended to provide a 3rd party system with its own integration with Alta Access, a method for referring back to the specific ACU so (as an example) the 3rd Party system can validate the QR code sent to it was a guest who’s QR code is still active and then send an unlock request through an existing integration that system may have with Alta Access.
QR code reads do not show up within the Alta Access Activity Logs, as the QR code read itself will not perform any action on an Entry within the site. There is no action taken by the Alta Access system beyond forwarding the QR code. Any subsequent actions would need to come from the programming of an integrated system with Alta Access or utilization of the Alta Access API integration to cause specific actions to occur within the Alta Access system as a result of the QR code scanned.