Troubleshoot Aruba Sensor Issues

There are many reason why the Aruba Sensor (AS-100) may not be connecting to the Editor. This article describes some of the troubleshooting steps you can take.

There are two main issues that can prevent the Sensor from working properly. The Beacons app may fail to configure the Sensor properly. The Sensor may fail to connect to the local Wi-Fi network.

This article lists the questions you'll need to answer to troubleshoot an Aruba Sensor that's failing to configure, connect to Wi-Fi, or report to the Meridian Editor.

Configure

The Aruba Sensor can be successfully configured with the Beacons app, even if it can't connect to a Wi-Fi network. Before troubleshooting any Wi-Fi connectivity issues, make sure that the Beacons app can configure the Sensor.

Were you able to configure the Sensor with the Beacons app?

If you were able to successfully deploy and configure the Sensor with the Beacon app, go to the Network section.

How many times have you deployed the Aruba Sensor?

When deploying an Aruba Sensor to a location using the Beacons app, the deployment will sometimes fail when setting up the Wi-Fi configuration. In some cases, deleting the deployed Sensor and redeploying with the Beacons app will fix this.

Has the Sensor been deployed to another location?

If a Sensor has been deployed to a previous location, you'll need to do a hardware factory reset.

To do this, unplug the Aruba Sensor. Before plugging it back in, press and hold the reset button for at least five seconds. While pressing and holding it, turn on the Aruba Sensor.

Use the Aruba Beacons app to deploy the Sensor to its new location.

Have you checked the Beacons Management token?

If the Aruba Sensor token is longer than 256 characters, the Aruba Sensor will fail to connect to the Editor.

To generate a new token, on the Editor Beacons Settings page under Controller Configuration, click Generate a New Access Token.

If you generate a new token and you have an Aruba controller, you'll need to update your controller with the new token.

What is the SensorOS version?

When contacting Meridian to get support for your Aruba Sensor, it can be helpful to know the SensorOS version on the Aruba Sensor.

Complete these steps to get the SensorOS version using the Beacons app.

  1. In the Nearby Beacons list, find the MAC address for your Sensor, and then tap the i button.
  2. On the Beacon Info screen, tap the Console button on the bottom left.
  3. Wait for the Beacons app to connect to the Sensor.
  4. In the header, tap the star, and then tap show image version.

If the Beacons app console can't connect to the Sensor and you've checked all of the previous questions, please contact technical support.

Network

There are several reason an Aruba Sensor might fail to connect to a Wi-Fi network.

Does the Wi-Fi password have spaces?

The Aruba Sensor does not support Wi-Fi passwords with spaces. Any spaces in the Wi-Fi password will need to be removed before an Aruba Sensor will connect to it.

Is the Wi-Fi network set to the correct type in the Editor?

The Aruba Sensor will fail to connect to a Wi-Fi network if the network type is incorrect in the Meridian Editor.

On the Beacons > Settings page, click Aruba Sensor Wi-Fi Settings.

Click the gear button to go to the Settings page.

There are three different Wi-Fi network types: Open, WPA2-PSK, and WPA2 Enterprise.

If you're not sure what Wi-Fi network type to use or the Wi-Fi authentication details, contact your local network administrator.

Is the capitalization in your SSID correct?

The SSID is case-sensitive. Please make sure that the capitalization is correct.

Is Meridian receiving information from the Sensor?

On the Beacons Management page, can you find the Sensor in the Beacons list?

Has the Sensor been heard from within minutes rather than hours? If so, the Sensor is reporting its own status to the Editor.

Have nearby battery-powered Beacons been heard from within minutes rather than hours? If so, the Sensor is reporting the status of nearby battery-powered Beacons to the Editor.

Is the observed by MAC address the same as the Sensor BLE MAC address?

To be on the safe side, compare the BLE MAC address printed on the Aruba Sensor sticker to the MAC address being reported to the Editor.

Is the NTP clock set correctly?

Using the Beacons app, check the Aruba Sensor's clock.

  1. In the Nearby Beacons list, find the MAC address for your Sensor, and then tap the i button.
  2. On the Beacon Info screen, tap the Console button on the bottom left.
  3. Wait for the Beacons app to connect to the Sensor.
  4. In the header, tap the star, and then tap show clock.

The clock date and time will be incorrect if it hasn't been successfully configured by the Beacons app.

Contact Support

If you've answered all of the above questions and your issue is still unresolved, please contact Support.