X

1. Introduction

The DM Dot Family (Dot Tag, Dot Glow and Dot Sensor) uses Bluetooth Low Energy (BLE) to broadcast information that can be detected by compatible Digital Matter gateways.

These gateways scan for nearby Dots and forward the collected data to the tracking platform, enabling asset identification, location visibility and sensor monitoring without requiring a cellular connection on each Dot.

Choosing the right BLE gateway depends on several factors, including:

Power availability: Whether the gateway can use external power or needs to operate on batteries.

Installation environment: Whether it will be installed at a fixed location, inside a vehicle or on a moving asset.

Number of Dots: How many tags the gateway needs to detect within its coverage area.

Scanning requirements: How frequently Dots need to be detected and their information reported.

Sensor monitoring: Whether the application requires sensor readings, alerts or additional actions based on Dot data.

This guide compares the recommended Digital Matter BLE gateways and helps you select the most suitable option for your application.

2. How to Choose the Right BLE Gateway

Choosing the right gateway for your DM Dots mainly depends on power availability, installation environment, number of tags and scanning requirements.

Start by identifying where and how your gateway will be deployed.

Step 1: Power Availability and Installation

The first consideration is whether external power is available. This determines whether the gateway can scan continuously or needs to use periodic scanning to conserve battery life.

Key difference:

Powered gateways can scan continuously, allowing faster detection of tags entering or leaving an area.

Battery-powered gateways scan at configured intervals to extend battery life, making them better suited to deployments where immediate detection is not essential.

Step 2: Number of Tags

Consider how many tags might be within range of the gateway at the same time.

Up to 1,000 tags: Hawk Pro with Bluetooth+ card or G150 Global (hardware revision 108.2).

Up to 100 tags: Most other supported gateways, including Manta Fusion, Oyster3 BLE, Oyster Edge, Remora3, Dart3 4G BLE and G70 4G BLE. G150 Global revision 108.1 also supports 100 tags.

Up to 50 tags: Arrow Global BLE (current documented limit, pending optimisation).

These limits refer to how many tags a gateway can manage in its tag list, not the total number of tags in your deployment.

Step 3: Scanning and Sensor Requirements

Finally, consider how quickly you need information and what you want to collect from your Dots.

Fast detection: Choose a powered gateway with continuous scanning for applications requiring frequent visibility of tag presence.

Long-term battery operation: Choose periodic scanning when detection at scheduled intervals is sufficient.

Sensor monitoring: If using Dot Sensor, check whether the gateway supports the required sensor data mapping and alert functionality. Some gateways can map readings from up to three sensor tags, while others have more limited capabilities.

The following section compares the recommended gateways in more detail to help you select the best option for your application.

3. Recommended BLE Gateways

Digital Matter offers a range of BLE-compatible gateways for different applications, from fixed installations and vehicles to battery-powered asset tracking.

The table below compares the recommended gateways based on their typical applications, power options, scanning capabilities and supported number of tags.

For fixed installations: Hawk Pro with the Bluetooth+ card is particularly well suited to warehouses and other stationary deployments. It supports up to 1,000 tags and can operate with a fixed location, without requiring a GPS fix. It also supports battery-powered operation with periodic scanning.

For vehicles and powered equipment: G150 Global offers high tag capacity, while Arrow Global BLE is suited to compact installations. Dart3 4G BLE and G70 4G BLE provide additional I/O and sensor integration capabilities.

For battery-powered deployments: Manta Fusion offers a compact option for smaller or concealed assets. Oyster3 4G BLE suits outdoor applications, Oyster Edge adds Wi-Fi geolocation for indoor environments, and Remora3 is designed for rugged, long-term installations.

Important: All listed gateways support the DM Dot Family with the appropriate Bluetooth firmware. However, advanced features such as sensor data mapping and local alerting vary by gateway. These requirements should be checked before deployment.

4. Typical Applications by Industry

The DM Dot Family can be used across a wide range of industries to improve asset visibility, identification and condition monitoring.

Below are some common applications and recommended gateway options for three key industries.

Choosing a Gateway for Your Application

These examples are starting points. The best gateway depends on how your assets move, where Bluetooth coverage is available and how frequently you need to receive updates.

For example, a logistics operation might use Hawk Pro gateways inside warehouses and G150 Global gateways in delivery vehicles, allowing the same Dots to be detected at different stages of the journey.

For applications without external power, battery-powered gateways provide an alternative, with periodic scanning to help extend battery life.

Refer to the gateway comparison and technical considerations in this guide to select the most suitable configuration.

5. Important Considerations

Before selecting a BLE gateway, there are a few additional factors to consider. These can affect how quickly Dots are detected, how much power the gateway consumes, and what information can be collected.

5.1 Continuous vs. Periodic Scanning

BLE gateways can detect nearby tags using two scanning modes:

With periodic scanning, longer or more frequent scans improve detection opportunities but also increase battery consumption.

Tip: The scan duration should generally be at least three times the Dot's advertising interval. For example, a Dot advertising every 5 seconds should have a scan window of at least 15 seconds.

5.2 Tag Capacity and Coverage

Each gateway has a practical limit on how many BLE tags it can manage simultaneously, as shown in the comparison table above.

Keep in mind:

Nearby BLE devices count: Other detectable BLE beacons can also occupy space in the gateway's tag list.

Filtering improves performance: Configure tag-type filters and minimum RSSI thresholds to focus on relevant Dots.

Gateway placement matters: Walls, metal structures and other obstacles can affect BLE signal strength and detection reliability.

For sites using multiple gateways, adjust RSSI thresholds and test coverage to reduce overlapping detections.

Note: Tag Found/Lost events require careful configuration in multi-gateway installations to avoid inaccurate location reporting.

5.3 Sensor Data and Mapping

All recommended gateways can detect compatible DM Dots, but their ability to process sensor readings differs.

For applications using Dot Sensor, consider whether you need:

Tag list reporting: Collecting readings from multiple nearby Dots and forwarding them to the platform.

Sensor data mapping: Assigning readings from specific sensor tags to the gateway's analog or digital inputs for monitoring and automation.

Advanced digital and analog mapping is supported by third-generation BLE gateways, including Hawk, Manta Fusion, Arrow Global BLE, Dart3 4G BLE and G70 4G BLE, subject to firmware requirements.

Sensor mapping is generally best suited to applications with a small number of consistently associated sensor tags (up to three). For larger or changing groups of Dots, tag list reporting is usually more appropriate.

5.4 Alerts and Reporting

Depending on the gateway and platform configuration, Dot data can be used to monitor asset presence and sensor conditions.

For example, Telematics Guru can generate alerts when:

A Dot is detected or is no longer detected by a gateway.

A sensor reading exceeds a configured threshold.

A tag-related event occurs within a specified geofence.

Some gateways also support additional functions, such as immediate uploads when mapped sensor values cross thresholds or local actions using digital outputs.

These advanced capabilities vary by gateway and should be verified for the intended application.

Important: With periodic scanning, alerts reflect when a change was detected during a scan, rather than necessarily when the event occurred.

[Learn more: Bluetooth Tag Alerts on Telematics Guru | Analog Threshold Parameters]

5.5 Power, Range and Firmware

A few final considerations can influence overall performance:

Battery life: For battery-powered gateways, autonomy depends on scanning frequency, scan duration and data uploads. Check the relevant battery life estimates before deployment.

BLE range: Actual detection range depends on the environment, gateway placement and Bluetooth configuration. Long-range scanning requires compatible hardware and settings on both devices.

Firmware compatibility: Ensure the gateway is running a Bluetooth firmware version that supports the DM Dot Family.

Dot activation: Dots must be activated using the Digital Matter Wireless Provisioning Tool before deployment.

Learn more: DM Dot Integration | Bluetooth Long Range | Bluetooth Getting Started