Architecture
...
The following screenshot shows an example.
Finish the configuration by going through the remaining steps 5 - 7.
Afterwards, change to the tab "Operations", select "Subscription" and add a new subscription. Select the events, the user and the locks. Within the last step (step 4) of the wizard, "Notify me on my Web server" should be selected and the web service URL should be shown.
As next, open the studio. First, configure the communication port that you have enter within the web service URL. This can be done by selecting "Driver Configuration" within the menu "Modules" -> "Kaba".
...
Then, the used devices have to be created. This is done within the "Device definitions" within the menu "Modules" -> "Kaba". Each definition line corresponds to one device. The first column defines the device name. The device name must be unique and is shown within the item tree the NETx Server. The next column "Device ID" is optional. "Device Name" and "Device ID" are used to assign a web service notification to the corresponding item within the item tree. This means that either "Device Name" or "Device ID" must be the same as the Kaba software uses within the web service request. The 3rd column "Path" is used to define an optional structure within the item tree. "Description" is used to provide additional information which is stored within the item property "Description". The remaining field "Persistent", "Historical" (NETx BMS Server 2.0 only) and "Synchronize" have the same functionality as for all other interfaces within the NETx Server.
| Filed | Description |
|---|---|
| Device Name | Must be the same as the Kaba software uses within the web service request |
| Device ID | Must be the same as the Kaba software uses within the web service request |
| Path | Define an optional structure within the item tree |
| Description | Provide additional information which is stored within the item property |
...
Event ID | Event Name |
|---|---|
Event ID | Event Name |
| Date time Error | |
| Date time OK | |
| 42 | Deadbolt reset (retracted) |
| 26 | Deadbolt / Privacy |
| 4 | Door ajar clear or Door Secure |
| Door ajar Generic | |
| 41 | Door Ajar Guest Long |
| Door Ajar Guest Short | |
Door Ajar Staff Long | |
| Door Ajar Staff Short | |
| Door Latched | |
| Door Unlatched | |
| 17 | Generic Egress |
| Guest Key Used | |
| 8195 | Hub status OFFLINE |
| 8194 | Hub status ONLINE |
| Key Error - Canceled Key Used | |
| 66 | Key error - Expired |
| Key Error - Other | |
| Key error - Wrong Room | |
| 55 | Lock status OFFLINE |
| 54 | Lock status ONLINE |
| Low battery | |
| Low Battery Clear or Battery Normal | |
| Mechanical Key Override | |
| New Guest Key Used | |
| Paging Keys | |
| Staff Key Used | |
| Standing Intruder | |
| Transaction Failed | |
| Wandering Intruder |
Article applies to the following products:
- NETx BMS Platform
- NETx Multi Protocol Server
- NETx BMS Server 2.0