Acre - Keep by Feenics

Have more questions? Submit a request

This page is to be used as a base template for the support page, please do expand or edit as needed for the individual integration. Include screenshots where appropriate (ensuring the screenshots do not contain confidential information and are suitable for public support pages)

 

acre.jpg

Native Integration Available

This integration requires a Class 3 License and is a cloud to cloud access control integration. Please contact your account manager for more details.

 

Native Integration: Supported Features

  • Alarms
  • Door/Relay Control (Momentary Unlock)
  • Synchronisation 

Native Integration: Requirements

Version Requirements

N/A - Connects to Fennecs Cloud 

 

License Requirements

N/A - No manufacturer license required

Network Requirements

N/A - Cloud to Cloud integration with no on-premise network requirements.


Permission Requirements

Read / Write / Update  / Publish permissions for

  • Alarm Definition
  • Controller
  • Output
  • Reader
  • Web Hook
  • Instance
  • Event Message

Items.png


Native Integration: Sync Configuration

Using the SureView Advanced Device Setup go to the Sync Tab and add "Feenics" as a new Sync System including the following fields

Type Feenics Access Control
Host https://keepapi.feenicshosting.com (For USA Hosted)
or
https://api.eu.acresecurity.cloud (for EU Hosted)
Port 443
Username

The username of your feenics user account

Important: The username must be in the format InstanceName/username e.g.

OrganisationName/admin

Password The password of your feenics user account
Extra value
InstanceKey=value;
OpsLink N/A - Leave Blank 

 

Finding the Instance Key

Using the Client app...

  1. Navigate to Instance Explorer
    1.png

  2. Right click the instance and select View Audit Log Entries2.png

  3. Click on the Occurred On column to sort it by oldest first. You will need to scroll up to the top after this
    3.png

  4. Locate FeenicsLicenseDetails data then scroll right until InstanceIdentifier key is found
    4.png
    4b.png
  5. Add this identifier to the device extra value.
    Note: Right click / shortcut copying is disabled in the Audit logs. Either manually copy the key or screenshot the key using Snipping Tool then utilise Text Actions feature to copy.5.png

Native Integration: Area Sync

Once you have saved your Sync Configuration (described above) you can then add the individual Area Syncs to synchronise Feenics Doors against individual Areas in Sure View.

  1. Go to the  Sureview "Syncs" tab (when adding or editing your Sync System)
  2. Click Add Area Sync
  3. Complete the Area Sync Fields
ld Value
Title The friendly name for the Area Sync
Area Which SureView Area should the sync use when adding doors/alarms etc
Identifier

This is the identifier that you want to sync your Feenics items against. You can group this in three different ways depending on how you have organised your Feenics assets

ControllerName=xxx
ReaderName=xxxx
OutputName=xxx

Note: Leaving the identifier blank will cause sync to bring in all Acre items.

Each of these can syncronise on absolute values or make use of the * wildcard e.g.

 

ReaderName=BuildingA-*

 

Would synchronise against all readers that started with "BuildingA-" e.g.

 

BuildingA-1

BuildingA-2

BuildingA-3

Interval How often should the system sync into SureView?
default: 24 hours
Enabled

Enable or Disable the automatic Sync

default on

Allow Update Area Allows the sync to automatically move synced doors/alarms to a different area

Default off

recommended to keep off
Allow update Device Settings

Allows the sync to automatically update the door/alarm settings

Default off

 

recommended to keep off

 

Native Integration: Setup Alarms


In Feenics (Using Feenics Client Application)

Ensure you have installed the Feenics Client application. The link below will install directly on click.
https://download.feenicshosting.com/keepwin/Setup.exe

Configuring the Webhook

You will need to configure a webhook so Feenics alarms can be sent to SureView. You only need to set this up once.

  1. Navigate to General Configuration -> Alarm Actions -> Add Alarm Action then select the Web Hook option.
    feenics1.png
  2. Populate Display Name and Url fields.
    • Display name - "SureView" (Note: Can be set to any name; it does not affect the underlying functionality)
    • Url - https://us.sureviewops.com/feenicsalarmreceiver or https://eu.sureviewops.com/feenicsalarmreceiver (depending on your SureView Account region)
      feenics2.jpg

Alarm Configuring

You can now configure Feenics to send alarms into sureview based on the Feenic's "Event Type"

  1. Navigate to General Configuration -> Alarm Definitions -> Add Alarm Definition.
    feenics1.png
  2. Populate Display Name, Assign Event Type and Assign Alarm Action fields.
    • Display name - "SureView Web Hook" (Note: Can be set to any name; it does not affect the underlying functionality).
    • Assign Event Type - Search for and add any alarm types that you want to automatically send into sureview (Note: SureView is compatible with all Mercury event types
    • Assign Alarm Action - Select the previously created Web Hook.
      feenics4.png

 

Alarm Types

The SureView Feenics integration support Alarm Type decoding with all Mercury event types. This includes but is not limited to:

  • Unlock Reader
  • Pulse Reader
  • Access Denied
  • Door held open

Items.png
General Configuration -> Event Definitions

Articles in this section

Was this article helpful?
0 out of 0 found this helpful
Share

Comments

0 comments

Please sign in to leave a comment.