Cloud to Cloud Integration
This integration requires a Class 3 License and is only available for SureView Response (SaaS). Please contact your account manager for more details.
Supported Features
- Alarms
Requirements
Version Requirements
N/A - Connects to Kastle Cloud
License Requirements
No additional Manufacturer License Requires
Network Requirements
N/A - Cloud to Cloud integration with no on-premise network requirements.
Device Configuration
Important: As soon as your Kastle device is added, all associated alarms will begin flowing into SureView.
To prevent your alarm queue from being flooded during initial setup, it is recommended to mask your Kastle Root Area until your alarm points and event types have been fully configured.
Once configuration is complete, the Root Area can be safely unmasked, ensuring that only relevant and properly configured alarms are received.
Using the SureView Advanced Device Setup go to the Devices and add "Kastle" as a new Device including the following fields
| Field | Value |
| Title | The user facing name of the system you are connecting to |
| Type | Kastle |
| Area |
Kastle Root Area If a “Kastle Root Area” does not already exist, it is recommended that you create one before adding your Kastle device. |
| OpsLink | Leave Blank |
| Host | mykastle.com |
| Port | 0 |
| Username | Leave Blank |
| ExtraValue |
The Kastle Client Id & Secret you are connecting to
Important: This is not available in the Kastle User Interface: You will need to contact your Kastle representative to request your jwtClientId & jwtClientSecret
Example jwtClientId=SureView;jwtClientSecret=12343528593bdvjdsbvjdbv;
|
Alarm Event Types
Kastle Alarm Event Types are defined using the Kastle eventType and eventStatus fields.
These values are not easily accessible within the Kastle interface. To obtain them, you will need to contact your Kastle Account Representative and request a list of:
- eventType (used for standard alarm events)
- eventStatus (used for access-related events)
SureView recommends configuring your Alarm Event Types before adding your Kastle device.
This includes ensuring that any high-frequency but non-actionable events (such as “Access Allowed”) are set to Default Ignore This helps prevent your alarm queue from being flooded with unnecessary events when the Kastle device is first added.
For events that are useful to retain but do not require operator action, you may choose to configure them as Auto Handle. These events are logged in the system history but do not appear in the alarm queue.
Auto Handle is best suited for events that are relevant from a security or audit perspective but do not require any operator action. It is not recommended for high-volume, routine events (such as access-granted events), as these are typically already recorded within the access control system and can create unnecessary noise in your system history.
Once received, these values can be configured within SureView using the Event Type Setup screen.
- Go to Event Types setup screen
- Select Kastle in the "Filter by Server Type" drop down
- Click Add Event
- Complete the fields and add the event type
| Field | Value |
| Title | The name of the Event Type |
| Description | Can be left blank or enter a friendly description of the Event Type |
| Device Type | Kastle |
| Area | Your Tenant/Account (top level area) |
| Default Priority | Enter the default sureview priority for this alarm type. The higher the number the more important the alarm |
| Default Action Plan | Select the default action plan (if required) for this type |
| Alarm Behaviour |
Not Set : The alarm is treated as standard and is added to the alarm queue for operator review.
Default Ignore: The alarm is ignored and not added to the alarm queue. (Recommended for events such as “Access Allowed”)
Default Ignore with Status: The alarm is ignored and not added to the alarm queue, but still updates the health/status of the associated alarm point.
Default Auto Handle: The alarm is automatically processed and recorded in the system history but is not presented to operators in the alarm queue.
|
| Default Alarm Tag | Add the relevant tag to the alarm type if required, otherwise leave blank |
| Event Code | This is the Kastle Event Identifier. (eventType or eventStatus code) |
Alarm Points
Kastle Alarm Points are matched within SureView using the Kastle locationId.
This identifier is not visible within the Kastle interface. To obtain it, you will need to contact your Kastle Account Representative and request a list of your alarm points, including:
- Alarm Point Name
- Alarm Point Area (e.g. site name)
locationId
Once received, this information can either be provided to SureView for bulk import, or entered manually within the Device Setup screen for each alarm point.
To manually add an alarm point
- Go to Device Setup
- Edit your Kastle Device
- Go to the Alarms tab
- Click ADD ALARM
- Complete the alarm fields and add the alarm point
| Field | Value |
| Device | Your Kastle Device |
| Event Type | leave as "Default |
| Title | The name of your alarm point |
| Action Plan | Leave blank or select an Action Plan if required |
| Input1 |
1 input number isn't used by Kastle, you can increment it manually to help with organisation but this value does not make a technical different to any alarm matching |
| Input1 | -1 |
| ExtraValue |
The Kastle alarm point "locationId"
example |
| Priority |
0 How important the alarm is. The higher the number the more important the alarm. Recommended: set to 0 to use the Alarm Event Type default |
| Grouping |
By Alarm = Group alarms based on individual alarm points (recommended) By Area = Group alarms by Area Not Grouped = Trigger each alarm individually (not recommended) |
Alarm Text
The alarm text in sureview follows this format
Standard Alarms
{SureviewEventType} - {SureviewAlarmPoint} - {Kastle_alarm_eventType} event {alarm_designator} at location {Kastle_alarm_locationDescription} ({Kastle_alarm_locationId})
Access Alarms
{SureviewEventType} - {SureviewAlarmPoint} - {Kastle_access_eventStatus}, {Kastle_alarm_designator} at location {Kastle_alarm_locationDescription} ({Kastle_alarm_locationId})
Example
Access Denied - Swansea - Reader 17 - Access Denied, at location DC1352 Floor 01, H1 Reader 17 (63606653)
Comments
0 commentsPlease sign in to leave a comment.