DMP
Native Integration Available
This integration requires a Class 3 License and a Device Server. Please contact your account manager for more details.
Native Integrations Supported Features
- Alarms
Network Requirements
| From | To | Port | Use |
| DMP Receiver |
Device Server |
9020 TCP | DMP Host Automation Alarming Port |
Configuring Your Device
Native Integration - Device Setup
In SureView
Using the SureView Advanced Device Setup add "DMP" to your Top level / Tenant area. with the following device field settings
Important: You must add the DMP to your Top Level Area (Your Tenant). You can only have one DMP device added for your account.
| Host | leave blank |
| Port | 9020 |
| Username | leave blank |
| Password | leave blank |
| Extra value |
Optional: networkHeartbeat=20000; The above option is to configure the timeout for the heartbeat interval from the DMP Panel, the default is 60 seconds. |
When SureView receives an alarm from DMP, it constructs a SourceID in the format "{Account #}-{SubTypeId}". Though, given that the SubType can vary based on the on the Event Type, the following two properties let us control how alarms are matched to Responses when they reach SureView.
includeTypePrefix: If the Event SubType code is included in this array, the SubTypeId will be prefixed with it's type. e.g. 12345-a1 for an Arming at Area 1 at a location with Account # 12345
onlyIncludeAccountNumberForSignal: If the Event Type code is included in this array, the SubTypeId will be excluded, causing these alarms to come in 'at the Panel level'.
DMP Event SubTypes
- DeviceID: v
- Area: a
- HolidayNumber: h
- EquipmentID: g
- ServiceCodeID: s
- Message number: t
- Zone: z
DMP Event Types
- Schedule: l
- Door Access: j (includes SubType v)
- Arming Status: q (includes SubType a)
- Holidays: g (includes SubType h)
- Equipment: e (includes SubType g)
- Service Code: m (includes SubType s)
- System Message: s (includes SubType t)
- Device Status: c (includes SubType v)
Go to the Alarms Tab in your Device Setup screen and add your alarm points. One for each Panel Zone.
When adding the Alarm use the following alarm properties
| Input1 |
Enter a unique number for each individual alarm point. Starting at '1' and increasing for each alarm. |
| Input2 | -1 |
|
Extra value |
e.g. if you have a panel "1234" in your "Headquarters" building with the zones "1"="HQ Lobby Fire" and "2"="HQ Lobby Panic", then add alarms of 1234-1 named HQ Lobby Fire and 1234-2 named HQ Lobby Panic. If leveraging includeTypePrefix, be sure to include the relevant SubType prefix, e.g. 1234-z2 for the Zone described above, or 1234-a4 for Area 4. |
In DMP
The Receiver must be programmed to send its Host Automation to the IP of the Device Server on TCP port 9020 (is a push-type integration) along with the following settings. NOTE: Receiver programming is very complex and SureView cannot provide direct support. Please refer to the manufacturer's documentation and support
| Protocol | TCP only (Enable UDP=off) |
| Container Format |
%s-%5a %m%13x (same as the default for the old-style settings of Start Character=off, CRC=off, Sequence Number=off, Line Number Length=0) |
| Expected ACK | %6x |
| Outgoing ACK | %6x%13x |
| Outbound server primary address | IP of your Device Server running the integration on port 9020 |
| Keep connection to automation servers alive | Yes |
Troubleshooting
Q: I am getting constant DMP Heartbeat failure alarms?
We have found that in some occurrences when the primary DMP Panel fails, the backup panel is setup for a lower heartbeat interval than the primary. In this case, you will need to update networkHeartbeat option in the SureView device's ExtraValue. Please see the 'Configuring your device' section for additional information.
Comments
0 commentsPlease sign in to leave a comment.