...
Bluzone Duress functionality uses standard Bluzone Policy-Event paradigm. The Policy-Event metric type is “PANIC_BUTTON”, and the namespace is “BEACON”. The Policy-Event also contains the beacon device id, the beacon name, the policy id, and the policy name (read more about Policy-Event Structure).
Cloud Integrations
Bluzone connects Policy-Events to Third Party Cloud integrations using the Remote-Consumer component. Bluzone Projects can be configured to push Policy-Event messages to a user supplied AWS Kinesis or Azure EventHub stream. HID recommends the usage of Remote-Consumer with Kinesis or EventHub integration for the following reasons:
...
Project A wishes to deploy HID Duress functionality and integrate the button press event into a workflow that includes custom actions.
...
Project A obtains and configures the appropriate hardware
...
Integration engineers for “Project A” would be considering the following tasks:
Obtain and configure the appropriate hardware and Bluzone project setup (configure Beacons, Blufis, Duress Policy)
Obtain an AWS Kinesis or Azure EventHub service
Configure Bluzone Project’s Remote-Consumer configuration in Bluzone to forward Duress Events to an AWS Kinesis stream
Implements a Kinesis Client to consume events from the stream
Implements custom workflowto use the Kinesis or EventHub stream (read more about Bluzone Streaming APIs)
Visit the EventHub or Kinesis documentation site and obtain appropriate client libraries
Implement code that consumes messages from the EventHub or Kinesis stream and processes the event
Handle the Policy-Event message for the duress event
...
The Duress Event published to the Remote-Consumer stream can be considered a “trigger” for the remote integration to begin its custom workflow.