Alarmbridge Connect Service - Getting Started

The Alarmbridge Connect Service setup is streamlined to ensure secure, reliable communication between group scheme alarm devices and ARCs, supporting both analog and IP-based protocols. Follow these steps to get started with the Alarmbridge Connect Service.

1. Prepare the ARC Side

   Set up the ARC to receive group scheme alarms via the SCAIP or NOW-IP protocol from devices that previously used analog protocols such as TT92 or TTNew.

2. Order the Alarmbridge Connect Service Gateway

   Order the Alarmbridge Connect Gateway device from a distribution partner to be used at the local site. For enhanced reliability, consider installing an optional mobile router and battery backup to maintain service during power outages.

3. Install the Gateway at the Site

   Once the iotcomms.io service is provisioned (see the next section), the Gateway is ready for installation.

   • Connect the Gateway to the router and plug it in.

   • The Gateway will automatically load its configuration from the cloud.

   • Unplug the PSTN wire from the PSTN socket and plug it into the Gateway.

1. Provision the Alarmbridge Connect Service Gateway

   Use the Device Provisioning web interface or API to register the Gateway:

   • Assign it a device ID corresponding to the telephone number previously associated with the PSTN subscription. This allows you to maintain the group scheme controller's existing configuration.

2. Provision the Alarmbridge Service

   • Set up an Event Receiver with the phone number of the old analog ARC. This ensures compatibility with the existing group scheme controller.

   • Configure an Event Sender to forward incoming alarm events to the ARC using the NOW-IP protocol.

1. Trigger an Alarm Event

   Initiate an alarm event from a group scheme unit to test the setup.

2. Verify Gateway Connectivity

   Ensure that the Gateway successfully connects with the Alarmbridge Connect Service and transmits the alarm event.

3. Confirm Event Receipt at the ARC

   Verify that the alarm event is received correctly at the ARC via the SCAIP or NOW-IP protocol.

By following these steps, you can deploy Alarmbridge Connect Service with ease, ensuring reliable, future-proof alarm communication for your group scheme or other critical applications.

The service supports giving installers of physical devices read-only access to a specific set of devices. To configure this, there are three settings to consider:

• Installer Role: The user needs to be assigned the installer role for the tenant. Admin users on the tenant can create and manage accounts with the installer role through the User Management Page.

  Accounts with higher-privileged roles that cannot be managed by an admin can have the installer role and installerId assigned by the iotcomms.io team upon requests. Requests typically take up to 48 hours to process.

• Installer ID: A specific ID for the installer on the tenant, used to determine which devices the installer has access to. An installer can have only one installer ID per tenant, but multiple installers can share the same installer ID.

• Device Group ID: Devices can be configured with a groupId property, which is a prefixed property for assigning a device to a group. For example, an installer with installerId = "123", will get access to devices where groupId = "installer-123".

  When managing devices through the Device Configuration Page, the installer id can be set directly and will automatically be converted to a prefixed groupId for the device. However, when managing devices through the Provisioning API, the prefix needs to be handled manually.

An installer for a tenant gets read-only access to devices on the same tenant where the device groupId matches the user's installerId.