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 permissions for

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

Update Permissions for

• Event Message

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

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

Title
The friendly name for the Area Sync

Area
Which SureView Area should the sync use when adding doors/alarms etc

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

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

If you are using sub instances you will need to add the Instance sync filter (which can be used in combination with the other filters with a ; separator if needed). For example:

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

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

• BuildingA-1
• BuildingA-2
• BuildingA-3

Notice: Commas and semicolons , and ; are not currently supported within the Acre Identifier Names

e.g. Instance=MySubInstance\BuildingA, BuildingB;ControllerName=Window*

Would fail to sync due to the comma in the Instance Name "Building A, BuildingB"

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 need to configure this for each subinstance that you want to alarm into SureView

1. (if using sub instances) In the "Instance Explorer" right click on the instance you want to configure and click "Select Current Instance"
2. Navigate to General Configuration -> Alarm Actions -> Add Alarm Action then select the Web Hook option.
   
    
3. 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)
     

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.
   
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.
     

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

Acre -> General Configuration -> Event Definitions

The Alarm Event Types for each Acre account are unique: This means that during initial set up SureView will need to perform an Acre Alarm Type Export / Import before the alarm types can be used.  This can take a week or more to action depending on the level of alarm type customisations that's needed.

Troubleshooting

Sync has only brought in one alarm point with an ExtraValue "instanceKey=xxxxxx" (where the xxx is your instance key)

The most common cause is that the Sync Identifier is incorrect and hasn't matched to the appropriate entities.

Remember that if you are using sub instances in Acre then you will need to include the Instance name as part of any sync identifier e.g.

Instance=Home\Building 1;ControllerName=Testing

This will bring in the "Testing" controller for Home\Building 1.

Sync Fails with the error: Call failed with status code 404 (Not Found):

The most common cause of this is if you are using an incorrect username / password OR the user you have entered does not have the appropriate permissions for what you are trying to sync

Remember that Usernames must be in the format

InstanceName/Username

I don't have any Acre Event Types in Event Type Setup

Acre Event Types are unique per account. This means there are no default Event Types pre-configured.  Please raise a support ticket to request that SureView exports your unique Event Type list from Acre and imports them into your SureView Event Type Setup